Enter Metadata for Servers | SAS 9.1.3 ETL Studio: Users Guide

< Day Day Up >

The SAS Configuration Wizard in the SAS Software Navigator enables you to run a script that will automatically add metadata for some servers. Use SAS Management Console to add metadata that is not provided by the scripts in the SAS Software Navigator.

The following table summarizes how the servers for the example data warehouse would be made available to SAS ETL Studio users.

Table 5.2: Main Servers for the Example Data Warehouse
Software	Required in Order to Perform These Tasks	Where Metadata Is Specified
SAS Metadata Server	Read and write metadata in a SAS Metadata Repository.	Specified in the metadata profiles for administrators and users. Administrators should see "Create a Metadata Profile and a Foundation Repository" on page 40. Users should see "Create a Metadata Profile" on page 57.
SAS Workspace Server	Access data and execute SAS code.	Can be specified as one component of the default SAS application server for SAS ETL Studio. See "Default SAS Application Server" on page 42.
SAS OLAP Server	Create cubes and process queries against cubes.	Can be specified as one component of the default SAS application server for SAS ETL Studio.

For details about entering metadata for the SAS Data Quality Servers or job scheduling servers from Platform Computing, see the SAS ETL Studio chapter in the SAS Intelligence Platform: Planning and Administration Guide.

For details about entering metadata for a SAS/SHARE server, a SAS Scalable Performance Data (SPD) Server, a DBMS, or an enterprise application, see the Preparing Data for Use chapter in the SAS Intelligence Platform: Planning and Administration Guide.

Default SAS Application Server

SAS ETL Studio enables users to select a default SAS application server. The default SAS application server enables SAS ETL Studio to execute SAS code, to access data, and to perform other tasks that require a SAS server—without having to specify a server each time.

When you select a default SAS application server, you are actually selecting a metadata object that can provide access to a number of servers, libraries, schemas, directories, and other resources. Typically, a metadata administrator defines the metadata for a SAS application server and tells users which object to select as the default in SAS ETL Studio.

For the example data warehouse, assume the metadata object for the default SAS application server is called SASMain. To support the example data warehouse, SASMain must include the following components:

a SAS Workspace Server component
a SAS OLAP Server component.

To enter metadata for SAS application servers, follow the instructions that are provided by the SAS Configuration Wizard that is associated with the SAS Software Navigator. See also the Servers in the SAS Intelligence Platform chapter in the SAS Intelligence Platform: Planning and Administration Guide.

Impact of the Default SAS Application Server in SAS ETL Studio

In a client/server environment, the terms local and remote are relative. The same resource can be local in one context and remote in another.

Code Generation

When SAS ETL Studio generates code for a job, a resource is local or remote relative to the default SAS application server that is specified on the SAS Server tab of the Options window.

To submit a job for execution on a machine that is local to the default SAS application server, the default SAS application server must have a SAS Workspace Server component.

To submit a job to a machine that is remote from the default SAS application server, both of the following conditions must exist:

The default SAS application server must have a SAS Workspace Server component.
The default SAS application server must have access to a SAS/CONNECT server on the remote machine where the job is to be executed.

Interactive Access to Data

When SAS ETL Studio is used to access information interactively, the server that is used to access the resource must be able to resolve the physical path to the resource. The path can be a local path or a remote path, but the relevant server must be able to resolve the path. The relevant server is the default SAS application server unless another SAS application server is specified in the metadata for the resource.

For example, in the source designer wizard for external files, the Host field on the External File Selection window enables you to specify the SAS application server that is used to access the external file. This server must be able to resolve the physical path that you specify for the external file.

As another example, suppose that you use the View Data option to view the contents of a table. To display the contents of the table, the default SAS application server in SAS ETL Studio, or a SAS application server that is specified in the metadata for the table, must be able to resolve the path to the table.

For the relevant server to resolve the path to a table in a library, one of the following conditions must be met:

The metadata for the library does not include an assignment to a SAS application server, and the default SAS application server can resolve the physical path that is specified for this library.
The metadata for the library includes an assignment to a SAS application server that contains a SAS Workspace Server component, and the SAS Workspace Server is accessible in the current session.
The metadata for the library includes an assignment to a SAS application server whose metadata contains a SAS/CONNECT server component, and the SAS/ CONNECT server component is accessible to the default SAS application server.

Note

If you select a library that is assigned to an inactive server, you will receive the error "Cannot connect to workspace server". Check to make sure that the server assigned to the library is running and is the active server.

< Day Day Up >