SAS Model Manager

New Functionality

The third maintenance release for SAS 9.2 fixes the following problems that previously affected SAS Model Manager 2.2:

Before this release, SAS Model Manager 2.2 used random ports when performing tasks such as attaching documents or importing models, which caused problems when you ran SAS Model Manager in a firewall environment. Functionality has been added to allow specific ports to be used for your firewall environment.
The SAS Model Manager Data Source viewer now supports using libraries and tables created in custom repositories.

Note: When you create the model scoring output table, choose a library that exists in the Foundation repository instead of a custom repository.

Post-Configuration Steps for SAS Model Manager

When These Post-Configuration Steps Are Required

Use the following table to determine what (if any) post-configuration steps you need to complete. To determine the product release number for Base SAS, see the deployment registry report that you generated before you applied the third maintenance release. For more information, see Determining the Product Release Numbers for Products at Your Site.

When Post-Configuration Steps Are Required

Update Scenario	Are Post-Configuration Steps Required?
You are installing SAS Model Manager for the first time.	No
You are upgrading from SAS Model Manager 2.2 to SAS Model Manager 2.3.	Yes When you upgrade to SAS Model Manager 2.3, the updateInstructions.html file lists any post-configuration steps that you need to complete. For example, you might need to restore any customizations that you made to the app.config and picklist files. You do not need to complete the post-configuration steps that are described in the rest of this section. For more information about the post-configuration steps to complete when upgrading to SAS Model Manager 2.3, see SAS Model Manager 2.3. If your order does not include SAS Model Manager 2.3 and you want to upgrade to this release, contact the SAS installation representative at your site.
You are applying the third maintenance release, and the product release number for Base SAS is 9.21_M1.	Yes The 9.21_M1 product release number indicates that you previously applied the second maintenance release for SAS 9.2 at your site. In the third maintenance release for SAS 9.2, additional steps are required to use the Java Web Start application or a firewall with SAS Model Manager 2.2. For the post-configuration steps, see How to Use the Java Web Start Application and How to Configure Your Firewall for Use with SAS Model Manager 2.2. These steps are not required if you are running a release before SAS Model Manager 2.2.
You are applying the third maintenance release to an existing SAS 9.2 deployment, and the product release number for Base SAS is 9.2 or 9.21.	Yes The 9.2 or 9.21 product release number indicates that you have not applied the second maintenance release for SAS 9.2. Maintenance releases are cumulative. Therefore, when you apply the third maintenance release, you will also receive the changes that were part of the second maintenance release for SAS 9.2. In the third maintenance release for SAS 9.2, additional steps are required to use the Java Web Start application or a firewall with SAS Model Manager 2.2. For the post-configuration steps, see How to Use the Java Web Start Application and How to Configure Your Firewall for Use with SAS Model Manager 2.2. These steps are not required if you are running a release before SAS Model Manager 2.2.
You have applied the third maintenance release for SAS 9.2, and you have upgraded to SAS Model Manager 2.3. Now, you are updating other products at your site.	No post-configuration steps are required for SAS Model Manager 2.3. However, post-configuration steps could be required for the products that you are updating. Review the “Product-Specific Details and Post-Configuration Requirements” chapter in Parts 3 and 4 of this document. To complete the post-configuration steps for a product-specific maintenance release, see Product-Specific Details and Post-Configuration Requirements in Part 3. To complete the post-configuration steps for a new product release, see Product-Specific Details and Post-Configuration Requirements in Part 4.

How to Use the Java Web Start Application

To use the Java Web Start application with SAS Model Manager:

On the middle tier server where the SAS Analytics Platform server is installed, access the SAS-configuration-directory\Lev1\AnalyticsPlatform\apps\ModelManager\ directory.
Rename the file picklist.mds to picklist.mds.bak.
Copy the file picklist from the SAS-installation-directory\SASModelManagerApplicationProgrammingInterface\2.2\Picklists\wars\sas.analytics.mm directory to the ModelManager directory that is specified in Step 1.
In the ModelManager directory, rename the file picklist to picklist.mds.
Stop and restart the SAS Analytics Platform server by completing the steps in SAS Analytics Platform Server.

Note: The Web application server (such as WebLogic, WebSphere, or JBoss) must be available to connections before you restart the SAS Analytics Platform server. For more information, see Availability of the Web Application Server.

How to Configure Your Firewall for Use with SAS Model Manager 2.2

To configure your firewall for use with SAS Model Manager 2.2:

Make a backup copy of the app.config file located in the SAS-configuration-directory\Lev1\AnalyticsPlatform\apps\ModelManager\ directory.
Use a text editor to add the following lines to the end of the app.config file in the SAS-configuration-directory\Lev1\AnalyticsPlatform\apps\ModelManager\ directory.
```
application.client.port=6931 
application.client.port.range=10 
```
Here is an explanation of how to set the parameters in step 2.
1. application.client.port specifies the port at which the range starts.
2. application.client.port.range specifies the number of open ports. The range of open ports ends at the application.client.port plus the application.client.port.range minus 1.
Note: If you do not modify the parameters in theapp.config file, then the default values added in step 2 are used to open the range of ports for the firewall.
Stop and restart the SAS Analytics Platform server by completing the steps in SAS Analytics Platform Server.

Note: The Web application server (such as WebLogic, WebSphere, or JBoss) must be available to connections before you restart the SAS Analytics Platform server. For more information, see Availability of the Web Application Server.

Availability of the Web Application Server

SAS Model Manager has a dependency on the SAS Content Server that provides the interface to WebDAV, which is needed by SAS Model Manager. The SAS Content Server runs as a Web application. Before the SAS Analytics Platform can successfully start SAS Model Manager, your Web application server (WebLogic, WebSphere, or JBoss) must be available for connections. You can verify that the SAS Content Server is available by accessing the URL that is provided in the Instructions.html file (http://server-name:port/SASContentServer/dircontents.jsp) and logging in as the SAS Model Manager administrator.

For more information about configuring environments, creating user accounts, and general SAS Model Manager administration, see the SAS Model Manager: Administrator's Guide. This documentation is available at http://support.sas.com/documentation/onlinedoc/modelmgr/.