Hot fix S37001 addresses the issue(s) in SAS Strategy Management 5.5_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/S37.html#S37001
S37001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
S38001 updates SAS Strategy Management Logical Types 5.5
S39001 updates SAS Strategy Management Mid-Tier 5.5_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, S37001pt.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 S37001pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of S37001pt.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 S37001pt.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.
SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at http://ftp.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.
For each product installed, click the link to be redirected to post-installation instructions.
S38001 updates SAS Strategy Management Logical Types 5.5
S39001 updates SAS Strategy Management Mid-Tier 5.5_M1
S38001 updates SAS Strategy Management Logical Types 5.5
NONE
S39001 updates SAS Strategy Management Mid-Tier 5.5_M1
Updates to the SAS Strategy Management Mid-Tier 5.5_M1 provided in this hot fix require that Web Applications
be rebuilt and redeployed. If this component is installed on Windows, follow the steps below to rebuild and redeploy
the web application:
Re-build Web Application
Before re-building the SAS Strategy Management web application, start all SAS services except the SAS Web Application Servers. For example, WebAppServer SASServer1_1 through WebAppServer SASServerX_1, where X is your highest SAS Web Application server, should be stopped.
1. Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.4
2. Select a language in the Choose Language box
3. Select Rebuild Web Applications
4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
5. Specify Connection Information, including the sasadm User ID and Password
6. Select SAS Strategy Management Mid-Tier 5.5 as the Web Application to rebuild
7. Verify the information on the Summary screen and select Start
8. Select Finish when the deployment is complete
This process will update the SAS Strategy Management Mid-Tier 5.5_M1 ear in
<SASCONFIGDIR>/Web/StagingA backup of the original ear file will be placed in the directory
<SASCONFIGDIR>/Web/Staging/Backup
9. Exit the SAS Deployment Manager 9.4
Re-deploy Web Application
The SAS Web Application servers should still be stopped as described in the Re-build Web Application section.
1. Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.4
2. Select a language in the Choose Language box
3. Select Deploy Web Applications
4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
5. Specify Connection Information, including the sasadm User ID and Password
6. Check the Allow the application server to stop checkbox
7. Select SAS Strategy Management Mid-Tier 5.5 as the Web Application to Deploy
8. Verify the information on the Summary screen and select Start
Note, if an error occurs in Stage 3: Start Web Application Server, try to start the SAS Web Application Servers manually, but first determine if SAS_Server1_1 has been started. It is recommended to look for the "server startup" message in the server.log file located in the
<SASCONFIGDIR>/Lev1/Web/WebAppServer/SASServer1_1/logs
folder before starting the next server.
If the servers fail to start, please contact SAS Technical Support.
9. Select Finish and exit the SAS Deployment Manager when the deployment is complete
This completes the installation of hot fix S37001 on 64-bit Enabled Solaris.