Pre-migration Steps

For information about the pre-migration tasks that you must perform, see Performing Pre-migration Tasks in SAS Intelligence Platform: Migration Guide. Here are some important steps to help with your migration:
  • Back up your SAS system, including servers and desktop clients.
  • Back up the SAS Web Infrastructure Platform Services database if you are migrating a SAS 9.3 or SAS 9.4 system.
  • Back up the SAS Model Manager database if you are migrating SAS Model Manager 12.1 on a SAS 9.3 system or SAS Model Manager 12.3 on a SAS 9.4 system.
  • Back up the SAS Decision Manager database if you are migrating from SAS Decision Manager 2.2, 3.1, or 3.2 to SAS Decision Manager 3.2 on a SAS 9.4 system.
  • If you are moving to a new system, ensure that the required operating system user accounts that you use for SAS in your current operating system also exist in your new operating system. These accounts are required for running scoring tests, performance definitions, retraining models, and scheduling jobs.
  • Before you migrate to SAS Decision Manager 3.2, you should record the database settings in your current environment. Verify that these settings are entered in the SAS Deployment Wizard when you run the migration.
    • If you are migrating from SAS Model Manager 12.1, or 12.3, record the database name and the user name for your SAS Model Manager database. The default database name is mdlmgrdb.
    • If you are migrating from SAS Decision Manager 2.2 or later, record the database name and the user ID for your SAS Decision Manager Common Data Server database. The default database name is dcmdb.
      You can find the database name in the /SAS-configuration-directory/Levn/Web/WebAppServer/SASServer7_1/conf/server.xml file on the middle-tier server. 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 the database name is dcmdb.
    • If you are using Oracle for your database, ensure that the Oracle client is installed on your server tier and that there is a matching tnsnames.ora file that corresponds to your database.
    • If you are using Oracle for your database, record the information that is listed in the following table.
      You enter this information in the SAS Decision Manager Database Properties and SAS Decision Manager Database JDBC Properties windows.
      SAS Deployment Wizard Information for Oracle
      Prompt
      Description
      Host Name
      Specifies the fully qualified host name of the server on which the database is installed.
      Port
      Specifies the port number that is used by the database. The default port for Oracle is 1521.
      Directory containing JDBC driver jars
      Specifies the location of the database vendor’s JDBC JAR file. This file must be available on the middle tier and on any machine on which you are deploying SAS Decision Manager in order to configure SAS Decision Manager database.
      See Verify JDBC Drivers for Oracle for more information.
      Database SID or Service Name
      Specifies the Oracle database name. The database name must match either the service name or the Oracle site identifier (SID), both of which can be found in the tnsnames.ora file.
      If you select Use Oracle database name as a Service Name, then you must enter the service name that is specified in the tnsnames.ora file. For example, if you had the following entry in the tnsnames.ora file, you would enter monitordb in the Database SID or Service Name field: 
      monitordb =
  (DESCRIPTION =
    (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = TCP_COMM)
          (PROTOCOL = TCP)
          (HOST = hostname.your.company.com)
          (PORT = 1521)
        )
    )
    (CONNECT_DATA =
      (SERVICE_NAME = monitordb)  
    )
  )
      Note: In the tnsnames.ora file, the Net Service Name and the Service Name fields must be the same.
      You can also find the Oracle SID in the tnsnames.ora file. Alternatively, you can run the following query using a database user ID on your Oracle instance:
      select instance from v$thread
      User ID
      Specifies the user ID of the database user whose credentials are used to access SAS Decision Manager data on the server.
      Password
      Specifies the password of the user ID whose credentials are used to access SAS Decision Manager data on the server.
      Schema Pattern
      Specifies the schema name for the database. The default schema name is the same as the user ID.
  • If you are using Oracle for your database, verify that you have the correct JDBC drivers. For more information, see Verify JDBC Drivers for Oracle.
  • Use the SAS Migration Utility to create a migration package.You must enter the configuration properties for the SAS Model Manager Mid-Tier (MMAPI) database management system in the SAS Migration Utility properties file.
    The values for the SAS Migration Utility properties can be found in SAS Management Console. Select the Folders tab and expand Systemthen selectApplicationsthen selectSAS Model Manager Mid-Tier. Select the Model Manager Mid-Tier version folder, right-click the Model Manager-Mid-Tier version application object, and then select Propertiesthen selectConfiguration. The prefix for the configuration properties that are equivalent to the SAS Migration Utility properties is dbms.mmapi.
    Note: If you are migrating from SAS Model Manager 12.1 or 12.3, the default name of the SAS Model Manager database is mdlmgrdb. Beginning with SAS Model Manager 13.1, the database is called the SAS Decision Manager database. The default name is dcmdb.
    Here is the list of configuration properties that should be used to populate the migration properties:
    SAS Migration Utility Properties
    Configuration Properties in SAS Management Console
    mmapi.data.dbms.type
    dbms.mmapi.type
    mmapi.dbms.data.name
    dbms.mmapi.name
    SMU.mmapi.dbms.host
    dbms.mmapi.host
    SMU.mmapi.dbms.port
    dbms.mmapi.port
    SMU.mmapi.dbms.userid
    dbms.mmapi.userid
    SMU.mmapi.dbms.password
    <not stored here>
    SMU.mmapi.jdbc.driver
    dbms.mmapi.jdbc.dir
    For more information, see SAS Migration Utility Reference in SAS Intelligence Platform: Migration Guide, and SAS Model Manager Properties in SAS Intelligence Platform: Migration Guide.
Copyright © SAS Institute Inc. All Rights Reserved.
Last updated: February 22, 2017