Post-migration Steps

Migrate to Version 3.2 for SAS Decision Manager Common Data Server

Overview of Post-migration Steps

After you have migrated to SAS Business Rules Manager 3.2 on the fourth maintenance release of SAS 9.4, perform the following post-migration steps:

Copy or move the contents of the rule flow testing directories. See Copying Rule Flow Test Results for more information.
Run the appropriate migration script to migrate your database to SAS Business Rules Manager 3.2. See the following topics for additional information:
- Migrate to Version 3.2 for Oracle
- Migrate to Version 3.2 for SAS Decision Manager Common Data Server
Note: If you are migrating from SAS Business Rules 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.
(Optional) Configure your deployment to use HTTPS. See Configure Your Deployment for HTTPS for more information.
Update your user group memberships, authorization, roles, and capabilities as needed. See Updating Groups and Roles for SAS Business Rules Manager 3.2 for more information.
(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.
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.
(Optional) If you are migrating from SAS Business Rules Manager 2.1, perform post-installation configuration and verification steps for SAS Workflow. For more information, see Configuring SAS Workflow for Use with SAS Business Rules Manager.

Copying Rule Flow Test Results

Rule flow testing results are not automatically migrated. For any results that you want to access with SAS Business Rules Manager 3.2:

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.
(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.
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
```

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 to SAS Business Rules Manager 3.2, run the migration_brm_version_to_brm_3.2.sql script for your current release of SAS Business Rules Manager.

For example, you can use SQL*Plus to run the script to migrate from SAS Business Rules 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 Business Rules Manager 2.1 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.

Verify that the SAS Decision Manager Common Data Server is running on both the source and target machines.
Shut down all SAS Web Application Server processes.
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.1, 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. If you are migrating from SAS Business Rules Manager 2.1, find the resource with the name sas/jdbc/dcmSharedDataSource. If you are migrating from SAS Business Rules Manager 2.2 or later, find the resource with the name sas/jdbc/DecisionManagerDS. 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.

Last updated: February 22, 2017