Installation Instructions for Hot Fix F55002

64-bit Enabled Solaris

Hot fix F55002 addresses the issue(s) in SAS Model Manager 3.1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/F55.html#F55002

F55002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.

F54002  updates  SAS Model Manager Client 3.1
G97001  updates  SAS Model Manager Common JAR Files 3.1
F53002  updates  SAS Model Manager Mid-Tier 3.1

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, F55002pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save F55002pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of F55002pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

INSTALLATION

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading F55002pt.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide; see the Applying Hot Fixes for Windows and UNIX section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the ‘member’ hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each ‘member’ hot fix applied (member hot fixes are listed at the top of these instructions).

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

F54002  updates  SAS Model Manager Client 3.1
G97001  updates  SAS Model Manager Common JAR Files 3.1
F53002  updates  SAS Model Manager Mid-Tier 3.1

F54002  updates  SAS Model Manager Client 3.1

1. Go to <SASHOME>\SASModelManagerClient\3.1
2. Create a backup of the ModelManager.ini file
3. Open the ModelManager.ini file and add the following lines immediately after existing JavaArgs lines in this file:

   JavaArgs_<NEXT NUMBERIC VALUE*>=-Dhttp.proxyHost=<serverName.proxy.domain.com>
   JavaArgs_<NEXT NUMBERIC VALUE>=-Dhttp.proxyPort=<proxy server port>**
   JavaArgs_<NEXT NUMBERIC VALUE>=-Dhttps.proxyHost=<serverName.proxy.domain.com>
   JavaArgs_<NEXT NUMBERIC VALUE>=-Dhttps.proxyPort=<proxy server port>
   
   *Increment to be one greater than the numeric value on the previous line
   **See your instructions.html file found in <config dir>\Lev1\Documents to determine the
   appropriate port value to use here.
   
   Note that if your site only supports HTTP then just make the HTTPS entries the same as the
   HTTP entries.
   

G97001  updates  SAS Model Manager Common JAR Files 3.1

These instructions are to be used to modify the configuration of the Workspace Server that Model Manager is using. Note that this instructions provide example filenames and directory names based on a Windows deployment; if your deployment is to a different host OS please make the appropriate adjustments

1. Go to <SASCONFIGDIR>\Lev1\SASApp\WorkspaceServer.

   Note that your Lev# may be different so use the one appropriate for your environment. Also your .SASApp. directory may have a different name if it was changed during the configuration phase

2. Create a backup of the sasv9_usermods.cfg
3. Open the sasv9_usermods.cfg file and add the following lines in the JREOPTIONS section:

   -JREOPTIONS=(-Dhttp.proxyHost=<serverName.proxy.domain.com>
               -Dhttp.proxyPort=<proxy server port>*
               -Dhttps.proxyHost=<serverName.proxy.domain.com>
               -Dhttps.proxyPort=<proxy server port>
               )
   
   *See your instructions.html file found in <config dir>\Lev1\Documents to determine the
   appropriate port value to use here.
   
   Note that if your site only supports HTTP then just make the HTTPS entries the same as the
   HTTP entries.
   

F53002  updates  SAS Model Manager Mid-Tier 3.1

The following Post-Install instructions for the mid-tier only needs to be followed, if you site obtain the MM3.1 client via Java Web Start. If they don.t then you can skip this step.

Note that this instructions provide example filenames and directory names based on a Windows deployment; if your deployment is to a different host OS please make the appropriate adjustments.

1. Stop the <web application server> containing the sas.modelmanager3.1.ear.
   1. Because of step outlined earlier this server should be stopped already.
2. Once the application server has stopped then you will need to copy the sas.svcs.assembly.jar out of the VJR and use it to replace the jar of the same name in the jws-lib directory as described below. Remember that the jar you want is the signed version of the jar since that is what Java Web Start needs to send down to the client. Within the SAS Version Jar Repository the appropriate sas.svcs.assembly.jar file can be found in the folder named similar to:
   1. C:\Program Files\SASHome\SASVersionedJarRepository\eclipse\plugins\sas.svcs.assembly.signed_20130919_903000.0.0.20110518190000_v930\
      1. Note that the date and time stamp between .assembly.signed_ and _v930 may be different on your installation.
   2. Copy that jar to <ApplicationServerInstallDir>\server\SASServer11_Lev1\deploy_sas\sas.modelmanager3.1.ear\sas.modelmanager.jws.war\WEB-INF\jws-lib
      1. Note that your installation might only have a SASServer1 and not a SASServer11 so use that instead. Also your Lev# may be different so use the one appropriate for your environment.
3. Start the SAS Metadata Server and launch the SAS Management Console connecting to that Metadata Server.
4. In the Plug-ins panel open the following tree:
   1. Application Management->Configuration Manger->SAS Application Infrastructure->Model Manager JWS 3.1
5. Right click on the last entry in the tree above and select Properties.
6. Under the Settings tab select the Virtual Machine Options in the left-hand pane.
7. In the VM arguments: text box enter the following after substituting the proper host and port information for your forward proxy:
   1. http.proxyHost=<serverName.proxy.domain.com>; http.proxyPort=<proxy server port>; https.proxyHost=<serverName.proxy.domain.com>; https.proxyPort=<proxy server port>
   2. If you only support HTTP then you do not need to include the two HTTPS entries though adding them and giving them the same values the HTTP entries will not hurt anything.
8. Save this information.
9. Restart all the services and servers previously stopped.

This completes the installation of hot fix F55002 on 64-bit Enabled Solaris.