Pre-upgrade Steps

Before you upgrade to SAS Decision Manager 3.1, record the database settings in your current environment. You must enter this information in SAS Deployment Wizard.
  • If you are upgrading from SAS Decision Manager 2.2, 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 SASCONFIG/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. Record the information 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 is the same as the user ID.
Last updated: February 22, 2017