Hot fix H77002 addresses the issue(s) in SAS Activity-Based Management 7.2_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/H77.html#H77002
H77002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated.
H74002 updates SAS Activity-Based Costing 7.2_M1
H76001 updates SAS Activity-Based Management Client 7.21
H75002 updates SAS Activity-Based Management Mid-Tier 7.2_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, H77002pt.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 H77002pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of H77002pt.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 H77002pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: 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).
For each product installed, click the link to be redirected to post-installation instructions.
H74002 updates SAS Activity-Based Costing 7.2_M1
H76001 updates SAS Activity-Based Management Client 7.21
H75002 updates SAS Activity-Based Management Mid-Tier 7.2_M1
H74002 updates SAS Activity-Based Costing 7.2_M1
NONE
H76001 updates SAS Activity-Based Management Client 7.21
NONE
H75002 updates SAS Activity-Based Management Mid-Tier 7.2_M1
Updates to the SAS Activity-Based Management Mid-Tier 7.2 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:
Remove com.sas.app.launcher.cacheFile
1. Delete
<SASHOME>\SASVersionedJarRepository\eclipse\com.sas.app.launcher.cacheFile
Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
1. Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory launch sasdm.exe.
SAS Deployment Manager is installed in the following default location:
<SASHOME>\SASDeploymentManager\9.3
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 Activity-Based Mgmt 7.2 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 Activity-Based Management Mid-Tier 7.2 ear in
<SASCONFIGDIR>\Web\StagingA backup of the original ear file will be placed in the directory
<SASCONFIGDIR>\Web\Staging\Backup
Re-deploy Web Application
1. Re-deploy the web application using the process documented for the initial deployment process.
Change "Class Loader Order" setting in WebSphere Application Server (WAS)
After re-building and re-deploying the web application the Class Loader Order setting in WebSphere Application Server must be changed to Class loaded with local class loader first (parent last) in order to prevent failures with ABM client connections. To change this setting
This completes the installation of hot fix H77002 on Windows.