Hot fix I73002 addresses the issue(s) in Risk Management for Banking 3.11 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/I73.html#I73002
I73002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
R04001 updates SAS Asset and Liability Management for Banking Server 3.11
R62001 updates SAS Firmwide Risk for Banking Server 3.11
I72002 updates SAS Risk Management for Banking Mid-Tier 3.11
I71002 updates SAS Risk Management for Banking Server 3.11
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, I73002pt.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 I73002pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of I73002pt.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 I73002pt.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).
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.
R04001 updates SAS Asset and Liability Management for Banking Server 3.11
R62001 updates SAS Firmwide Risk for Banking Server 3.11
I72002 updates SAS Risk Management for Banking Mid-Tier 3.11
I71002 updates SAS Risk Management for Banking Server 3.11
R04001 updates SAS Asset and Liability Management for Banking Server 3.11
NONE
R62001 updates SAS Firmwide Risk for Banking Server 3.11
NONE
I72002 updates SAS Risk Management for Banking Mid-Tier 3.11
Re-build and Re-deploy Web Application
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.3
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:<SASHOME>\SASDeploymentManager\9.31.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 Risk Management for Banking 3.1 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 Risk Management for Banking 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 applications based on the instructions for the web application server you are using.
I71002 updates SAS Risk Management for Banking Server 3.11
NOTE: If you have already applied hot fix I73001, skip to the section
"...to update the metadata for the stored processes" below.
Follow the steps below to regenerate the Solution Data Mart (SDM):
%create_solution_data_mart(soln_data_mart_dir=&sysparm);
%create_solution_data_mart(soln_data_mart_dir=<complete path to indata directory in your install>);Example of indata path: <CONFIGDIR>/AppData/SASRiskManagementForBanking/3.1/indata
If you are re-creating a playpen that uses a private entity data mart, select File > Manage Playpens from the menu, and for each playpen you are re-creating, follow instructions for creating a playpen that uses a private entity data mart. Any private playpens created prior to the re-creation of the solution data mart cannot receive updates that have been applied to the solution data mart.
If you are re-creating a shared entity data mart, select File > Manage Shared Data Mart from the menu, and click Change to update the existing shared data mart. (Playpens that use the shared data mart do not require re-creation.)
The following steps update sample data in SAS Risk Reporting Repository - RRR:
<SASHOME>/SASFoundation/9.3/misc/rmbfirmmva/Config/Deployment/Packages
- Login to SMC as sasadm user
- Navigate to Folders -> System -> Applications -> SAS Risk Management for Banking -> Firmwide Risk Server 3.1
- Right click on "Firmwide Risk Server 3.1" and select "Import SAS Package"
- Provide the path and SAS package filename. For e.g. <SASHOME>/SASFoundation/9.3/misc/rmbfirmmva/Config/Deployment/Packages/reports.spk
- Click Next. Ensure that the objects are being imported under the correct metadata tree (Folder structure)
- Provide the SAS Application Server that you want to associate the metadata with. The application server name should be the same as the one associated with Risk Management for Banking
- Provide the stored process code location to be associated with metadata to be imported. For SAS Risk Management for Banking, this should be the corresponding component STP location under <SASConfig>
- Click Next and Finish to complete the import process
Follow the steps below to update the ETLs (for populating data from Banking DDS to RMB Solution data mart)
This completes the installation of hot fix I73002 on 64-bit Enabled Solaris.