|
|
Implementation & Administration Guide 1.1 |
|
If you have implemented a data warehouse using the SAS/Warehouse Administrator, you can export metadata for selected warehouse views from the Warehouse Administrator's enterprise directory to the portal's enterprise directory. Authorized portal users can then view the most current warehouse data directly from the portal.
In the portal, warehouse content is displayed in a manner similar to channels. The user opens the warehouse entry to see the list of tables, multidimensional databases (MDDBs), and InfoMarts that it contains. When the user selects a particular content item, the portal displays it using the appropriate viewer (for example, the portal table viewer, MDDB viewer, or document viewer).
The warehouse export capability is an efficient alternative to the manual entry of metadata for tables and MDDBs in the portal. After the warehouse export process is completed, you must make several adjustments to the resulting metadata so that the various SAS components will work together correctly. These adjustments are described in detail in the steps below.
To add a warehouse view to the portal, follow these steps:
Make note of the logical name attributes currently assigned to the portal's SAS server and spawner definitions.
Export the appropriate metadata from Warehouse Administrator to the portal's enterprise directory.
Update logical name attributes as necessary in the SAS server and SAS spawner definitions.
Update the domain name attribute in the SAS server definition.
Ensure that fully qualified paths are provided for the SAS libraries that contain the warehouse.
Ensure that a SAS login has been defined to allow access to the SAS server that contains the warehouse.
Before you perform the export from Warehouse Administrator, use either the SAS Integration Technologies (IT) Administrator or the enterprise directory console to examine any SAS spawner and SAS server definitions that are already present in the portal's enterprise directory. Make note of the logical name attributes that are present in these definitions, since you may need to use them in a later step.
For detailed instructions on using IT Administrator, refer to the IT Administrator section of the SAS Integration Technologies Web site.
In the Warehouse Administrator application, select the specific warehouse view that you would like to make available to portal users. Then choose Tools, LDAP Security from the SAS menu bar. On the panels provided, enter the required information about the export operation. Then click the Export button. The SAS log will display results of the export operation and any error messages. For more detail, refer to the Data Warehouse Export Example.
The following metadata is exported from Warehouse Administrator:
Metadata describing the selected warehouse view. This metadata is exported to the sasMetadataRepository component of the portal's enterprise directory.
A SAS server definition and SAS spawner definition for the host on which the warehouse resides. This metadata is exported to the sasServer component of the portal's enterprise directory.
Note: If the portal's enterprise directory already contains a server definition with the appropriate machine DNS, protocol, port, and command attributes, then the export procedure updates this definition with the logical name attributes for the warehouse server. If the portal's enterprise directory already contains a spawner definition with the appropriate machine DNS attribute, then the export procedure attempts to update this definition with the logical name attributes for the warehouse spawner. In these cases, you must manually inspect the logical names and adjust them as necessary so that server connections can be made successfully. For details, see Step 3.
Metadata describing the data sources. This metadata, which is stored in the sasDataSources component of the enterprise directory, includes definitions for the following objects:
The SAS libraries that contain the warehouse view.
The SAS MDDBs and tables that are included in the view.
Each of the columns included in these MDDBs and tables.
Infomarts included in the view.
In the following cases, the export procedure makes changes to logical name attributes on the portal's enterprise directory. You must correct the logical names manually in order for the object spawner to run correctly and server connections to be made successfully.
If the portal already has a SAS server definition with the appropriate machine DNS, protocol, port, and command attributes, then the export procedure updates this definition with the logical name attributes for the warehouse server.
When the export is complete, use either IT Administrator or the enterprise directory console to determine if the server definition's original logical name attributes are still present. If they are not, you must re-enter the original logical names that were overwritten. However, do not replace the logical name that was exported from Warehouse Administrator.
If the portal already has a SAS spawner definition with the appropriate machine DNS attribute, then the export procedure attempts to update this definition with the logical name attributes for the warehouse spawner.
When the export is complete, use either IT Administrator or the enterprise directory console to determine if the spawner definition's original logical name attributes are still present. If they are not, you must re-enter the original logical names that were overwritten.
You must also determine if the spawner definition contains a logical name attribute that matches the logical name for the warehouse server. If this logical name is not present in the spawner definition, you must add it.
If the export operation creates a new SAS server definition on the portal's enterprise directory, you must add a domain attribute to this definition. The object spawner requires that the domain be identified so that the correct server can be located. You can make this change using either IT Administrator or the enterprise directory console.
The portal requires that SAS library definitions contain fully qualified path information. If relative paths are used in any of the library definitions that were exported from Warehouse Administrator, you must extend this information to include the entire path to the root of the server. You can use either IT Administrator or the enterprise directory console to perform this modification.
Since the exported metadata does not include a SAS login definition, you must create one. The login definition should specify:
The same logical name and the same domain as the associated SAS server and SAS spawner definitions.
The SAS login id and password which are to be used as credentials to access the server that hosts the warehouse.
Distinguished names (DNs) for the portal users and/or groups of users who are authorized to access the warehouse view.
To create the SAS login, you can use the IT Administrator application. For detailed instructions, see Adding a SAS Login on the SAS Integration Technologies Web site.
Since warehouse views can include MDDBs, you must ensure that SAS has been updated to enable the portal's MDDB viewer to communicate with the SAS server. The steps for performing this update, which are included in the portal's installation instructions, are as follows:
Copy the transport file, mddbview.cpo, from the SASUpdates subdirectory of the Portal setup directory to the appropriate SAS server.
Start SAS on the server.
Enter and submit the following code:
filename updates 'path-to-transport-file';
proc cimport library=sashelp infile=updates force; run;
Exit SAS.
If the warehouse view is accessible to all portal users, the public content administrator can use the Personalize feature to add the view to a public list. When the administrator performs this function, the portal application displays a list box containing all warehouse views in the enterprise directory that are accessible to all portal users. From the list box, the public content administrator selects the warehouse views that are to appear on the public list.
Group owners can use the Personalize feature to add a warehouse view to a role-based list. When the group owner performs this function, the portal application displays a list box containing all warehouse views in the enterprise directory that the group is authorized to access. From the list box, the group owner selects the warehouse views that are to appear on the role-based list.
Individual users can use the Personalize feature to add the warehouse view to a personal list. When the user performs this function, the portal application displays a list box containing all warehouse views in the enterprise directory that the user is authorized to access. From the list box, the user selects the warehouse views that are to appear on his or her personal list.
|
|
Implementation & Administration Guide 1.1 |
|