SAS OLAP Server
Product Release Number
After you
apply the third maintenance release for SAS 9.2, you can view the
release information in two different locations:
For more information,
see About the Deployment Summary.
Post-Configuration Steps for SAS OLAP Server
When These Post-Configuration Steps Are Required
Use the following table
to determine what (if any) post-configuration steps you need to complete.
To determine the Technical Support Number for SAS OLAP Server, review
the SAS OLAP Server log before you apply the third maintenance release.
To determine the product release number for SAS OLAP Cube Studio,
see the deployment registry report that you generated before you applied
the third maintenance release. For more information, see Determining the Product Release Numbers for Products at Your Site.
When Post-Configuration Steps Are Required
|
The Technical Support
Number (TS2M2) and the product release number (4.2_M1) indicate that
you previously applied the second maintenance release for SAS 9.2
at your site. When you applied the second maintenance release, you
completed the required post-configuration steps. Therefore, you do
not need to complete these steps again.
|
|
|
The Technical Support
Number (TS2M0) and the product release number (4.2) indicate that
you have not applied the second maintenance release for SAS 9.2. Maintenance
releases are cumulative. Therefore, when you apply the third maintenance
release, you will also receive the changes that were part of the second
maintenance release for SAS 9.2.
For the post-configuration
steps, see ExportCubes and ImportCubes Batch Tools and Drill-through to Metadata Security.
|
ExportCubes and ImportCubes Batch Tools
The ExportCubes and
ImportCubes command-line batch tools enable you to move your SAS 9.1.3
SP4 cubes to the third maintenance release for SAS 9.2. These batch
tools are available for use on Windows and are executed from a DOS
command line. To use the batch tools, you must go to the DOS command
line on your operating system. The batch tool can be found in the
following directory paths:
The ExportCubes batch
tool exports the metadata for your cubes into individual XML files
that are stored in a designated directory. The ExportCubes batch tool
exports all cubes on the metadata server. The ImportCubes batch tool
enables you to import SAS 9.1.3 OLAP cube metadata files that have
been exported using the ExportCubes batch tool on your SAS 9.1.3
SP4 environment.
With the ImportCubes
batch tool you can specify the location of multiple exported SAS 9.1.3
XML files and import them to your SAS 9.2 OLAP environment. The SAS
9.1.3 SP4 cube metadata is imported and added to the SAS 9.2 Metadata
Server. After the metadata files are imported, you can then rebuild
your SAS 9.1.3 SP4 cubes on your SAS 9.2 system. You can use SAS OLAP
Cube Studio to build the physical data for the cubes.
Note: For further information,
see “ExportCubes
and ImportCubes Batch Tools” in the SAS OLAP Server: User’s Guide.
Drill-through to Metadata Security
When selecting a data
table for drill-through, you might need to define user restrictions
for certain data in the drill-through table. In the second maintenance
release for SAS 9.2, the drill-through to detail functionality enforces
metadata security. The SAS Metadata LIBNAME engine is now used to
assign the drill-through table library on a per-session basis. This
allows client credentials to be used when determining which columns
the user can see. Columns that have ReadMetadata permissions denied
on the drill-through table will not be visible to the user. If access
is denied for a column on the drill-through table, that level must
also be denied Read access in the cube. Conversely, if a level is
denied Read access in the cube, that column in the drill-through table
must have ReadMetadata access denied.
Note: For more information, see
“Security
for Drill-through Tables” in the SAS OLAP Server: User’s Guide.