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.
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.logfor example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.
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.
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
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
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
-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.
This completes the installation of hot fix F55002 on Windows.