How SAS Management Console Works
Recommended by 0 users
How SAS Management Console Works
SAS Management Console provides a single point of control for managing resources that are used throughout a business intelligence environment.
SAS Management Console works in conjunction with SAS Metadata Servers.
A metadata server must be set up and started, way before work begins with SAS Management Console.
When SAS Management Console is invoked, a metadata profile is selected which specifies
- the metadata server to which metadata definitions will be written
- the active metadata repository
- information required to connect to the metadata server.
When a metadata profile is defined, the server to which the application connects is specified along with the user ID it uses to connect to the server. When an application opens a metadata profile, it has access to the metadata on the specified server based on the security credentials of the user ID under which the connection was made.
Connecting to SAS Metadata Servers
The SAS Metadata Server is an object server.
After you open the metadata profile to connect to the metadata server, you can begin using the SAS Management Console to create metadata definitions. As you create definitions, they are stored in the active repository on the metadata server.
Each metadata server can contain multiple repositories, and the SAS Management Console can be used to store definitions in any of the repositories.
The active repository is the repository that is currently selected and is receiving metadata definitions from the application.
SAS management console can be used to set up a hierarchy of repositories on the metadata server, consisting of different repository types including:
A foundation repository acts as a parent repository for all other repositories on the server.
A project repository is a development repository that has dependencies on a foundation or custom repository.
In addition to these two repository types, a third type can also be defined:
Custom Repositories specifies repositories that are dependent on the foundation repository or other custom repositories and accesses and uses resources from the parent(s).
A repository that is dependent upon another repository inherits metadata from the repository on which it is dependent.
Metadata and Repositories – Review
Metadata is information about data and computing resources, or data about data. Metadata definitions are stored in a repository, where they are available for use by other applications.
The Foundation repository is the parent repository for all other repositories on the server and includes metadata objects that describe SAS servers, data libraries, data tables, and metadata users.
SAS Servers – Review
The various SAS Servers in the Intelligence Platform are defined in the metadata. These server definitions include details on where the process is executing and how to connect to it.
An individual server definition may be part of an Application Server context that provides a place to attach libraries, schemas, directories, and any resources that are to be available to the SAS servers.
Metadata users may have their own metadata identity and/or belong to a user group. All users who can access the metadata server implicitly belong to a special group named PUBLIC.
There are several different types of users in the metadata, as shown below:
SAS Management Console Case Study Tasks
In class, you only have one repository, a foundation repository named Foundation.
Within the Foundation repository, the application server context is named SASMain, which holds the various SAS Servers.
There are several users and groups defined that will be used during class, including
- PUBLIC (group)
- sasadm (unrestricted user)
- sasdemo (demo user).