Administrative Changes in the SAS Intelligence Platform

System Administration for SAS Intelligence Platform

Server logging is performed by the new SAS logging facility. For more information, see Administering Logging for SAS Servers in the SAS Intelligence Platform: System Administration Guide.

SAS Application Servers

SASApp or SASMain Application Server

If you use the SAS Migration Utility with the SAS Deployment Wizard to migrate to SAS 9.2, then the SAS Application Server that was configured in SAS 9.1.3 is carried forward to your SAS 9.2 system. The server name that was assigned in SAS 9.1.3 is retained. The default names in SAS 9.1.3 are SASMain for single-machine deployments and SASApp for multiple-machine deployments. You might have assigned a different name for your server. In addition, your deployment might include other application servers that were created in SAS 9.1.3 and migrated to SAS 9.2.

If you choose not to use the SAS Migration Utility, the SAS Deployment Wizard creates an application server called SASApp. (You can assign a different name during the deployment process.)

The SASApp or SASMain application server is intended for use by client applications and can include SAS Workspace Servers, SAS Pooled Workspace Servers, SAS Stored Process Servers, SAS OLAP Servers, SAS/CONNECT servers, SAS grid servers, SAS DATA step batch servers, and SAS Java batch servers.

SASMeta Application Server

The SAS Deployment Wizard creates an additional application server called SASMeta, which is new in SAS 9.2. This server is visible only to users with certain administrative privileges. It includes the following components:

the SAS Metadata Server.
a SAS Workspace Server and a SAS DATA step batch server. These servers are to be used only for running metadata utilities such as the Backup and Restore Wizard. Do not use these servers for other SAS processing.

Metadata Repositories

The following differences pertain to metadata repositories:

The use of third-party database management systems to store the repository manager and metadata repositories is no longer supported.
You cannot pause a repository. Existing programs that use PROC METAOPERATE to pause a repository must be changed to pause the metadata server instead.
The repository auditing feature provided in previous releases has been removed. The new SAS logging facility captures security-related events for the metadata server and for components of SAS Application Servers. For more information, see Administering Logging for SAS Servers in the SAS Intelligence Platform: System Administration Guide.
It is not necessary to define dependencies between repositories. If a repository dependency was defined in SAS 9.1.3, then the dependency relationship is eliminated during the SAS 9.1.3 to SAS 9.2 migration process. However, the existing associations between metadata objects still remain in effect.

Metadata Server Backup

The following differences pertain to backups and restores that are performed with the %OMABAKUP macro:

Selective backups and restores are not supported. Therefore, backup and restore scripts that use the REPOSITORYLIST option must be updated to remove the option.
You cannot back up a foundation repository that has a registered access mode of ReadOnly.
In SAS 9.1.3, the RESTORE option did not restore the repository manager when it was run in its default mode. In SAS 9.2, the RESTORE option restores the repository manager and all registered repositories by default.
%OMABAKUP backs up and restores the metadata server's configuration files.

SAS Management Console

The following differences appear in SAS Management Console:

Content is stored in a hierarchy of SAS folders that are visible in the Folders tab of SAS Management Console. The BI Manager import and export wizards have been replaced with the Export SAS Package and Import SAS Package wizards.
If you use SAS Management Console's BI Manager to export metadata from a SAS 9.1.3 metadata server, then you can import the metadata to a SAS 9.2 metadata server. (This feature is useful for customers who are running the two releases in parallel.) However, your SAS 9.1.3 system must have SAS Foundation Services 1.4. If it has a different version of SAS Foundation Services, then the package cannot be imported to SAS 9.2.
SAS 9.1.3 objects that were not contained in folders (for example, OLAP schemas and cubes) are moved to the Shared Data folder in SAS 9.2.
For each user who had objects (for example, report objects) in SAS 9.1.3 personal folders, a home folder and a personal folder are created in SAS 9.2 and appear under the Users folder. Users' objects are moved from the SAS 9.1.3 personal folders to the SAS 9.2 personal folders.
The SAS 9.1.3 BIP tree folder structure is moved in its entirety to SAS 9.2 under a folder called BIP Tree. (This folder appears only in migrated systems.)
The Replication Wizard in SAS Management Console has been deprecated. For more information, see SAS Note 40834 at http://support.sas.com/kb/40/834.html or contact SAS Technical Support.

For details about these differences, see Using the Promotion Tools and Working with SAS Folders in the SAS Intelligence Platform: System Administration Guide.

Top of Page