Post-Migration Tasks :: SAS(R) Decision Manager 2.2: Administrator's Guide

Overview of Post-Migration Tasks

After you have migrated to SAS Decision Manager 2.2 on SAS 9.4, perform the following post-migration manual steps:

Copy or move the contents of the channels directories from the source machine to the target machine. See Publishing Channels for more information.
Run post-migration macros if you are migrating from one UNIX operating system to different type of UNIX system, or from a Windows 32-bit server to a Windows 64-bit server. See Operating System Migration for more information.
Migrate the SAS Decision Manager Common Data Server database if you are performing a hardware upgrade. See Migrate the SAS Decision Manager Data Server 2.2 Database for more information.

Note: All user-defined templates are copied from the source system to the target system by the migration process. This content includes all user-defined life cycle templates, model templates, report templates, and SAS code files. The user-defined templates are located on the SAS Content Server at http://hostname:port/SASContentServer/repository/default/ModelManager/ConfigTemplates/ext/.

Publishing Channels

When migrating from a previous release of SAS Decision Manager, you must manually copy the contents of the channels directory from your old system to a directory on the new machine that is running SAS Workspace Server. It is recommended that you use the same directory name when migrating from an existing SAS Decision Manager 2.2 deployment to a new deployment of SAS Decision Manager 2.2. If you use the same directory name, you do not need to copy the contents of the channels directory. The default directory path for channels is \SASConfigDir\Lev#\AppData\SASModelManager13.1\Channels.

For example, in Windows the path might be C:\SAS\Config\Lev1\AppData\SASModelManager13.1\Channels.

If you use a different directory name, then you must modify the channel persistent store directory location in the SAS Management Console. For more information, see Modify an Existing Channel or Channels Node Location.

Operating System Migration

If you are migrating from one UNIX operating system to another, or from a Windows 32-bit server to a Windows 64-bit server, then some post-installation tasks are required to complete the migration process. SAS Decision Manager provides post-migration macros to assist with this process. Only SAS files on the WebDAV server in the \\ModelManagerDefaultRepository\Project\Version\Resources directory are handled by the post-migration macros. If you have SAS files in another directory location, you must manually migrate them.

Note:

You must have access to the SAS deployment on the source system and target system to run these macros.
Two of the macros are available for download at http://ftp.sas.com/techsup/download/blind/mm_migration.sas.

Perform the following steps to ensure that all data, content, and link and filename references that are used by SAS Decision Manager are accessible by the new SAS 9.4 deployment:

Run the %MM_migrationStep1() macro on the SAS Workspace Server in your source system.
Run the %MM_migrationStep2() macro on the SAS Workspace Server in your target system.

Note: For more information about the migration macros, see Post-Migration Macros.

Migrate the SAS Decision Manager Data Server 2.2 Database

You need to run PostgreSQL commands in order to migrate the SAS Decision Manager Common Data Server database. These commands are located in the following directory:

!SASHOME/SASWebInfrastructurePlatformDataServer/9.4/bin

When you run these commands, substitute the correct values for the host name, port number, and user ID for your database. These commands prompt you to enter a password.

Note: If you are performing the upgrade in a UNIX operating environment and these commands fail, you might need to set environment variables. See Set Environment Variables for UNIX for more information.

On the source machine, run the pg_dump command. This command creates a script file that contains the SQL commands that are needed to reconstruct the database:
```
pg_dump --host=host_name --port=nnnn --username=database_owner_userID 
--password –Fp dcmdb > dcmdb.dump
```
Copy the generated file dcmdb.dump to the target server.
Stop SASServer7.
On the target server, run the dropdb command to drop the database that was created by the SAS Deployment Wizard:
```
dropdb --host=host_name --port=nnnn --username=database_owner_userID 
--password database_name
```
On the target server, run the createdb command to create a new, empty database:
```
createdb --host=host_name --port=nnnn --username=database_owner_userID 
--password database_name
```
On the target server, restore the exported database:
```
psql --host=host_name --port=nnnn -f dcmdb.dump database_name userID
```
Note: Specify the user ID for Decision Manager Common Middle Tier. Do not specify the user ID of the database owner account.

Note: You might see messages such as no privileges were granted for "public" or role userID does not exist. These messages mean that these users are no longer applicable to the upgraded database instance and can be ignored.

Set Environment Variables for UNIX

If you are upgrading SAS Decision Manager in a UNIX operating environment, you might need to set environment variables in order for the migrate commands described in to succeed. If the migrate commands fail, use the following export commands to set the LD_LIBRARY_PATH and LIBPATH environment variables:

export LD_LIBRARY_PATH=/install/cfgsas1/SASHome/
SASWebInfrastructurePlatformDataServer/9.4/lib:$LD_LIBRARY_PATH

export LIBPATH=/install/cfgsas1/SASHome/
SASWebInfrastructurePlatformDataServer/9.4/lib:$LIBPATH

Replace SASHome with the value for your site.