Hot fix R06001 addresses the issue(s) in SAS Risk Management for Banking 3.2_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/R06.html#R06001
R06001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
P89001 updates SAS Risk Dimensions Java Client 6.2_M1
M87001 updates SAS Risk Management for Banking Mid-Tier 3.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, R06001pt.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 R06001pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of R06001pt.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 R06001pt.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.
P89001 updates SAS Risk Dimensions Java Client 6.2_M1
M87001 updates SAS Risk Management for Banking Mid-Tier 3.2_M1
P89001 updates SAS Risk Dimensions Java Client 6.2_M1
NONE
M87001 updates SAS Risk Management for Banking Mid-Tier 3.2_M1
This hot fix requires that the WebApp be rebuilt and redeployed. Use the following steps to perform this post-installation task:
Step 1: Re-build Web ApplicationIn order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.exe.
SAS Deployment Manager is installed in the following default location:<SASHOME>/SASDeploymentManager/9.41.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select SAS Risk Management for Banking 3.2 as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
This process will update the SAS Risk Management for Banking 3.2 ear in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear file will be placed in the directory below:
<SASCONFIGDIR>/Web/Staging/Backup
Step 2: Re-deploy Web ApplicationsRe-deploy the web application.
This completes the installation of hot fix R06001 on Windows for x64.