Post-Installation Verification and Configuration of SAS Model Manager

After you install SAS 9.3 and SAS Model Manager 12.1 using SAS Software Depot, you must perform additional configuration steps before you can use SAS Model Manager.
  1. Verify that all installation and configuration steps in the instructions.html file have been completed. The instructions.html file is located in \sasconfigdir\Lev#\Documents\.
  2. The SAS Deployment Wizard does not create SAS Model Manager users by default. The SAS Administrator must create users in SAS Management Console with the appropriate group and role permissions. Verify that all users who were created during the installation process to use SAS Model Manager are granted the appropriate permissions to the SAS Workspace Server. In a Windows environment, each user or group must be granted permission to the Log on as a batch job local security policy. For more information, see Create Windows Operating System Accounts and Groups for Users of SAS Model Manager.
    In a UNIX environment all SAS Model Manager users must be part of a group that has the appropriate group permissions. For more information, see Creating Operating System Accounts in UNIX Environments and Configuring Users, Groups, and Roles.
  3. If the SAS Workspace Server is located in a UNIX environment, you must enable the SAS Workspace Server XCMD option in order to support R model functionality. For more information, see Enabling the SAS Workspace Server XCMD Option.
  4. During installation, if you chose to perform a manual configuration of the SAS Model Manager database, or you chose a third-party database vendor that does not support automated creation of tables and loading of data, additional configuration steps are required. For more information, see Configure the SAS Model Manager Database .
  5. If the SAS Scoring Accelerator or SAS Model Manager In-Database Scoring Scripts products are a part of your SAS 9.3 deployment, additional configuration steps are required to prepare the database for publishing and scoring in SAS Model Manager. For more information, see Preparing a Database for Use with SAS Model Manager in SAS In-Database Products: Administrator's Guide.
  6. If the Web application server is configured to use HTTPS, you must configure Secure Sockets Layer (SSL) and client-certificate authentication on the Client machine and on the SAS Workspace Server.
    For more information, see the application server documentation page for your Web application server. The documentation for your server that is specific to SAS is available at http://support.sas.com/resources/thirdpartysupport/v93/appservers/.
    The following are the security-related configuration documents for the currently supported Web application servers:
    • “Configuring the JBoss Application Server for Secure Sockets Layer and Client-Certificate Authentication on SAS® 9.3 Enterprise BI Server Web Applications”
    • “Configuring Secure Socket Layer and Client-Certificate Authentication on SAS 9.3 Enterprise BI Server Systems That Use Oracle WebLogic 10.3”
    Note: A document about configuring the IBM WebSphere Application Server 7 for Secure Sockets Layer and client-certification authentication on SAS 9.3 Enterprise BI Server Web Applications will be placed at the same location. Contact SAS Technical Support for questions until the document is available.
  7. Configure SAS Workflow. For more information, see Configuring SAS Workflow for Use with SAS Model Manager.
  8. Verify the configuration of the dashboard reports directory on the SAS Workspace Server. For more information, see Configuring the Dashboard Reports Directory.
  9. Configure the Model Manager Java Services Options. For more information, see Configuring Model Manager Java Services Options.
  10. If the machine where SAS Workspace Server is located for SAS Model Manager supports IPV4 and IPV6 network addresses, in order for a user to perform tasks such as performance monitoring and model retrain, you must modify the contents of the -JREOPTIONS parameter by using the sasv9_usermods.cfg file. There are multiple versions of this file. Modify the file that is located in the \sasconfigdir\Lev#\SASApp\WorkspaceServer\ directory.
    The following lines of code and user-supplied values must be added to the file:
    -JREOPTIONS=(
    -Djava.net.preferIPv4Stack=true
    -Djava.net.preferIPv6Addresses=false
    )
    If you use IPv4 network addresses, the true and false values above are valid. If you use the IPv6 network address, you must reverse the true and false values. That is preferIPv4Stack=false and preferIPv6addresses=true.
    SAS Model Manager uses JGroups to perform multicast communication between the SAS Application Server and the SAS middle-tier. The JGroups software bind to the IP address of the first non-loopback network interface that it can detect on the machine. In certain circumstances, such as machines with multiple network adapters or protocols, the SAS Application Server could bind to an address that is not able to use multicasting to communicate to the SAS middle-tier. In these cases, you must also add the following line of code to the JREOPTIONS parameter:
    -Djgroups.bind_addr=[IP Address]
    
    If you do not know the correct value for the JGroups bind address, you can consult your network administrator to select the appropriate IP address. The address selected should be able to support multicasting to communicate to the SAS middle-tier. For more information, see Configuring the JGroups Bind Address in SAS Intelligence Platform: Middle-Tier Administration Guide.
  11. If you have installed SAS Model Manager to use with SAS Enterprise Miner, you must access the SAS Content Server and create a public directory for SAS Enterprise Miner to register a model SAS package (SPK) file. To create a SAS Content Server public directory, follow these steps:
    1. Access the SAS Content Server Administration Console by entering http://hostname:port/SASContentServer/dircontents.jsp. An example of hostname:port is localhost:8080. Log in using the SAS Administrator account (for example, sasadm@saspw) that you defined during the SAS installation process.
    2. In the Add folder field, enter a folder name such as Models.
    3. Click Add folder.
    4. The Models folder is displayed in the Item name column.
    5. Click the Permissions icon that is associated with the Models folder.
    6. In the Add principal field, enter the value jcr:all. Change all of the permissions to Yes.
    7. Click Save Changes.
    8. Log off from the SAS Content Server Administration Console and restart any open SAS Enterprise Miner sessions to pick up the changes.
  12. If you have installed SAS Model Manager to use with SAS Enterprise Miner, you must configure the SAS Metadata Repository to use the SAS Content Server public directory that you created previously. Follow these steps:
    1. In SAS Management Console, expand Application Management on the Plug-ins tab. SAS Enterprise Miner should be listed and should contain subfolders.
    2. Expand the Projects folder.
    3. Right-click the SAS Workspace Server that is associated with your SAS Enterprise Miner installation, and select Properties. An example is SASApp - Logical Workspace Server.
    4. Click the Options tab.
    5. In the WebDAV URL field, enter http://hostname:port/SASContentServer/repository/default/Models/.
      Note: WebDAV is used to register a model SPK file from SAS Enterprise Miner.
    6. Click OK and then restart any open SAS Enterprise Miner sessions to pick up the changes.
For more information about post-installation tasks, see the SAS 9.3 installation documentation.