Hot fix M62002 addresses the issue(s) in SAS Model Manager 12.3_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/M62.html#M62002
M62002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
M71002 updates SAS Model Manager Client 12.3_M1
M60002 updates SAS Model Manager Common Components 12.3
M70002 updates SAS Model Manager Common JAR Files 12.3
M61002 updates SAS Model Manager Mid-Tier 12.3_M1
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, M62002pt.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 M62002pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of M62002pt.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 M62002pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User’s Guide.
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.
M71002 updates SAS Model Manager Client 12.3_M1
M60002 updates SAS Model Manager Common Components 12.3
M70002 updates SAS Model Manager Common JAR Files 12.3
M61002 updates SAS Model Manager Mid-Tier 12.3_M1
M71002 updates SAS Model Manager Client 12.3_M1
The “SAS Model Manager Mid-Tier 12.3” is the web application to re-build. For more information, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications -> Rebuilding the SAS Web Applications.
The “SAS Model Manager Mid-Tier 12.3” is the web application to re-deploy. For more information, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications -> Redeploying the SAS Web Applications.
M60002 updates SAS Model Manager Common Components 12.3
NONE
M70002 updates SAS Model Manager Common JAR Files 12.3
NONE
M61002 updates SAS Model Manager Mid-Tier 12.3_M1
The “SAS Model Manager Mid-Tier 12.3” is the web application to re-build. For more information, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications -> Rebuilding the SAS Web Applications.
The “SAS Model Manager Mid-Tier 12.3” is the web application to re-deploy. For more information, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications -> Redeploying the SAS Web Applications.
Update the Contents of the SAS Content Server