Post-migration Steps

Overview of Post-migration Steps
Copying Rule Flow Test Results
Copying Publishing Channels
Migrate to Version 3.2 for Oracle
Migrate to Version 3.2 for SAS Decision Manager Common Data Server
Migrate Model Information to a New Operating System
Prerequisites
Run the Migration Macros

Overview of Post-migration Steps

After you have migrated to SAS Decision Manager 3.2 on the fourth maintenance release of SAS 9.4, perform the following post-migration steps:
  1. Copy or move the contents of the rule flow testing directories. See Copying Rule Flow Test Results for more information.
  2. Copy or move the contents of the channels directory from the source machine to the target machine. See Copying Publishing Channels for more information.
  3. Run post-migration macros if you are migrating from one UNIX operating system to a different type of UNIX system. See Migrate Model Information to a New Operating System for more information.
  4. Run the appropriate migration script to migrate your database to SAS Decision Manager 3.2. See the following topics for additional information:
    Note: If you are migrating from SAS Decision Manager 3.2 to 3.2 (hardware upgrade) and you are using Oracle for your database, you do not need to run a migration script.
  5. (Optional) Configure your deployment to use HTTPS. See Configure Your Deployment for HTTPS for more information.
  6. Update your user group memberships, authorization, roles, and capabilities as needed. See Updating Groups and Roles for SAS Decision Manager 3.2 for more information.
  7. (Optional) Add the Visual Analytics: Data Building and Data Management: Lineage roles to the Decision Manager Users group. See Administering Group and Role Membership for more information. These roles enable users to run SAS Visual Data Builder and view lineage information for rule flows.
  8. Review the configuration properties in SAS Management Console. Ensure that the values are appropriate for the new environment. See Review Application Properties in SAS Management Console for more information.
  9. If you are migrating from SAS Model Manager 12.1 or earlier, see SAS Model Manager: Migration Guide for additional post-migration steps that you might need to perform.
Note: All user-defined model 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/.

Copying Rule Flow Test Results

Rule flow testing results are not automatically migrated. For any results that you want to access with SAS Decision Manager 3.2:
  1. Copy the test results from your old deployment to the new deployment. The directory path for rule flow test results is specified by the Business Rules Manager Web property Test Library Root File System Directory in SAS Management Console. You must use the same directory path in the new deployment. See Review Application Properties in SAS Management Console for more information.
  2. (Optional) If you are running in a UNIX operating environment and the user that needs to access the test results is different from the current user, use the chown -R command to change the ownership of the testing folders. For more information, refer to the UNIX man page for the chown command.
  3. Update the relationship information for the test results so that users can view the test results and re-run the test cases. To update the relationship information, run the following REST service: 
    http://host:port/SASBusinessRulesManagerWeb/rest/RuleflowTestLibMigrate

Copying 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 3.2 deployment to a new deployment of SAS Decision Manager 3.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 \SAS-Configuration-dirctory\Levn\AppData\SASModelManager14.2\Channels.
For example, in Windows the path might be C:\SAS\Config\Lev1\AppData\SASModelManager14.2\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.

Migrate to Version 3.2 for Oracle

The scripts for migrating an Oracle database are located in the following directory:
SASHome/SASDecisionManagerCommonDataServer/3.2/Config/Deployment/dbscript/oracle/migration/.
To migrate an Oracle database from SAS Decision Manager 2.2 or 3.1 to 3.2, run the migration_brm_version_to_brm_3.2.sql script for your current release of SAS Decision Manager.
For example, you can use SQL*Plus to run the script to migrate from SAS Decision Manager 2.2 to 3.2 as follows: 
sqlplus username@tnsname @/install/SASHome/
SASDecisionManagerCommonDataServer/3.2/Config/Deployment/
dbscript/oracle/migration/migration_brm_2.2_to_brm_3.2.sql schemaName

Migrate to Version 3.2 for SAS Decision Manager Common Data Server

If you are migrating from SAS Decision Manager 2.2 or later to 3.2 and you are using the SAS Decision Manager Common Data Server, you must run the database migration script for your operating environment. Run this script on the target middle-tier machine where the SAS Decision Manager Common Data Server is running.
  1. Verify that the SAS Decision Manager Common Data Server is running on both the source and target machines.
  2. Shut down all SAS Web Application Server processes.
  3. Run the database migration script for your operating environment. The script for Windows platforms is named postgres-migration.bat, and the script for UNIX platforms is named postgres-migration.sh. They are located in the following directory:
    SASHome/SASDecisionManagerCommonDataServer/3.2/Config/Deployment/Migration/
    Note: This directory contains a README.TXT file that contains information about the parameters for these scripts.
    When you run the migration script, substitute the correct values for the release you are migrating from, the server name, port number, and user ID for your database. The script prompts you to enter a password. The syntax for these scripts is as follows:
    postgres-migration.[bat | sh] SASHome version
    source_port source_host source_user source_db_name
    target_port target_host target_admin target_user target_db_name
    <target_exists>
    SASHome
    specifies the SAS Home installation directory location. In Windows operating environments, it is recommended that you enclose this parameter in double quotation marks.
    version
    specifies the version number of your current (source) database from which you are migrating content. Specify 2.2, 3.1, or 3.2.
    source_port
    specifies the port number of the database from which you are migrating content.
    source_host
    specifies the host name of the database from which you are migrating content.
    source_user
    specify the user ID for Decision Manager Common Middle Tier. This value must be a user ID that has access to all of the database content that needs to be migrated. You can find the correct value for this parameter in the /SAS-configuration-directory/Levn/Web/WebAppServer/SASServer7_1/conf/server.xml file on the middle-tier server for the source system. Specify the value of the user attribute of the resource with name sas/jdbc/DecisionManagerDS.
    source_db_name
    specifies the name of the database from which you are migrating content. You can find the correct value for this parameter in the /SAS-configuration-directory/Levn/Web/WebAppServer/SASServer7_1/conf/server.xml file on the middle-tier server for the source system. Find the resource with the name sas/jdbc/DecisionManagerDS, and look for the value of the url attribute. The database name is the text after the final forward slash (/) in the URL. For example, if the attribute is url="jdbc:postgresql://host:10482/dcmdb", then specify dcmdb for source_db_name.
    target_port
    specifies the port number of the database to which you are migrating the content.
    target_host
    specifies the host name of the database to which you are migrating the content.
    target_admin
    specifies the user ID of the database administrator for the database to which you are migrating the content. This user ID is used to clean the target database and prepare it for the migrated content.
    target_user
    specifies a database user ID for the database to which you are migrating the content. This user ID is assigned ownership of the migrated content.
    target_db_name
    specifies the database name of the database to which you are migrating the content. The default target database name is dcmdb.
    target_exists
    specifies whether the target database exists. The default value is YES. If you have attempted to run this migration script but the migration failed, specify NO. Normally, the script creates a backup of the source database. If you specify NO, the script does not create an additional backup.
    Note: This parameter is optional.

Migrate Model Information to a New Operating System

If you are migrating from one UNIX operating system to another, then some post-installation steps 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.

Prerequisites

  • You must have access to the SAS deployment on the source system and target system to run these macros.
  • The %MM_migrationStep1 and %MM_migrationStep2 macros are available in the SAS catalog sashelp.modelmgr.migration.source.
  • If your source system is SAS Model Manager 12.3, you must copy the migration.source file from the sashelp.modelmgr catalog on the target system to the sashelp.modelmgr catalog on the source system.
    To make the migration.source file available in the sashelp.modelmgr.catalog on the source system:
    1. Export the migration.source file from the sashelp.modelmgr catalog on the target system into a CPORT file.
      filename exp "C:\temp\modelmgr-migration-source.cpo";
proc cport file=exp cat=sashelp.modelmgr;
select migration.source;
run;
filename exp;
    2. Copy the modelmgr-migration-source.cpo file from the target system to the source system
    3. Import migration.source from the modelmgr-migration-source.cpo file into the sashelp.modelmgr catalog on the source system.
      filename imp "C:\temp\modelmgr-migration-source.cpo";
proc cimport infile=imp cat= sashelp.modelmgr;
select migration.source;
run;
filename imp;
  • You must run the migration macros using Base SAS on the machine where the SAS Model Manager Server is installed for both your source and target systems.

Run the Migration Macros

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:
  1. Run the %MM_migrationStep1 macro in Base SAS on your source system.
  2. Run the %MM_migrationStep2 macro in Base SAS on your target system.
Note: For more information about the migration macros, see Post-Migration Macros.
Copyright © SAS Institute Inc. All Rights Reserved.
Last updated: February 22, 2017