SAS(R) Intelligence Platform: 9.1.3 to 9.2 Migration Guide

Product	Release
SAS Enterprise Data Integration Server	9.1.3
4.2
SAS Enterprise BI Server	9.1.3
4.2
SAS Migration Utility	9.1.3.14
9.1.3.13
9.1.3.12
9.1.3.11
9.1.3.10
SAS Data Integration Server	9.1.3
4.2
SAS BI Server	9.1.3
4.2
SAS Metadata Server	9.2
SAS Deployment Wizard	9.2
SAS Management Console	9.2

What's Next?

First-Priority Setup Tasks

The following tasks are necessary to protect the integrity of your system. Complete these steps as soon as possible after migration, before you complete any of the other tasks that are outlined in this chapter.

First-Priority Setup Tasks
Task	Description
Secure the SAS configuration on each server machine.	For a secure deployment, the configuration directory on each server machine must be protected by operating system controls. These controls will prevent inappropriate access to repository data sets, server scripts, server logs, and configuration files. On Windows systems, all configuration directories, files, and scripts are owned by the user who performs the installation. You must update the permissions as shown in Recommended and Default Operating System Protections. These recommendations assume that your SAS servers and spawners run as services under the Local System account. On UNIX and z/OS systems, the SAS Deployment Wizard automatically applies the appropriate permissions. The default permissions are shown in Recommended and Default Operating System Protections.
Establish a formal, regularly scheduled backup process.	Establish a formal, regularly scheduled backup process that includes your metadata repositories as well as the associated physical files. SAS provides backup and restore utilities that enable you to perform correct backups and restores of your metadata repositories, the repository manager, the metadata journal file, and the metadata server configuration files while minimizing disruptions in service. It is important to also back up the physical data that is associated with the metadata so that related information will be synchronized if a restore becomes necessary. Regardless of whether you choose to migrate SAS 9.1.3 content that is stored outside of the configuration directory, we strongly recommend that you back up this content before proceeding. Before you back up your SAS Intelligence Platform, read Best Practices for Backing Up and Restoring Your System in the SAS Intelligence Platform: System Administration Guide.
Manage your SAS server start-up.	If you have SAS 9.1.3 servers on the same machine as your SAS 9.2 servers, then make sure that the SAS 9.1.3 servers are not set to automatically start at boot up.

The following table shows the recommended operating system protections for configuration directories on Windows server machines, as well as the default protections that are provided automatically on UNIX and z/OS machines. All of these directories are located in SAS-configuration-directory/Levn.

Recommended and Default Operating System Protections
Directories		Default and Recommended Permissions
Documents ReportBatch SAS-configuration-directory and its subdirectory Lev1 SASApp SASMeta Utilities Web		Default permissions on UNIX and z/OS: SAS Installer: Read, Write, and Execute All other users: Read and Execute Recommended permissions on Windows: SYSTEM and Administrators: Full Control All other users: List Folder Contents, Read
SASApp subdirectories ConnectServer/Logs, Data/wrsdist, Data/wrstemp, PooledWorkspaceServer/Logs, PooledWorkspaceServer/sasuser, StoredProcessServer/Logs , StoredProcessServer/sasuser, and WorkspaceServer/Logs SASMeta/WorkspaceServer/Logs		Default permissions on UNIX and z/OS: SAS Installer: Read, Write, and Execute sas group: Read, Write, and Execute Recommended permissions on Windows: SYSTEM, Administrators, and SAS Spawned Servers (sassrv): Full Control
SASApp/PooledWorkspaceServer SASApp/StoredProcessServer		Default permissions on UNIX and z/OS: SAS Installer: Read, Write, and Execute sas group: Read and Execute Recommended permissions on Windows: SYSTEM , Administrators, and SAS Spawned Servers (sassrv): Full Control Remove all other users and groups.
ConnectSpawner Logs ObjectSpawner SASApp/OLAPServer SASMeta/MetadataServer SASTS ShareServer		Default permissions on UNIX and z/OS: SAS Installer: Read, Write, and Execute All other users: no access Recommended permissions on Windows: SYSTEM and Administrators: Full Control Remove all other users and groups.
sasv9_meta.cfg file		Default permissions on UNIX and z/OS: SAS Installer: Read and Write All other users: no access Recommended permissions on Windows: SYSTEM and Administrators: Read and Write Remove all other users and groups.

Note:

On Windows, these recommendations assume that your SAS servers and spawners run as services under the Local System account. If servers and spawners are run under a different account, then grant that account the permissions that are recommended for SYSTEM.
You might have selected the custom installation option to place all of your log files in a single directory. If you selected this option, then on Windows you will need to grant the SAS Spawned Servers (sassrv) user Full Control of the central log destination (for example, SAS-configuration-directory/Lev/n/Logs).
If you enable logging for a workspace server, then you will need to grant all users of the workspace server the appropriate permissions on the workspace server log destination. On UNIX and z/OS, assign these users Read, Write, and Execute permission on the log directory. On Windows, assign these users Full Control of the log directory. (See Create a Log File for Workspace Server Troubleshooting in the SAS Intelligence Platform: System Administration Guide.)
The user who backs up the metadata server must have full access to SAS-configuration-directory/Levn/SASMeta/MetadataServer, to its subdirectories rposmgr and Foundation, and to the backup destination (for example, SAS-configuration-directory/Lev1/SASMeta/MetadataServer/SASBackup). On UNIX and z/OS systems, the SAS Installer user has the required access. On Windows systems, the user who runs the backup should be added to the Administrators group to provide the required access.

CAUTION:
On UNIX and z/OS systems, do not run a backup or a restore as the Root user. Doing so will change ownership of the metadata server files.
For details about the configuration directory, see Overview of the Configuration Directory Structure in the SAS Intelligence Platform: System Administration Guide.

Top of Page