*** Please see the disclaimer regarding this experimental fix at the bottom of this page. ***
D41011 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as indicated. See the Container Hot Fixes section in the
Maintenance Install Tool (MIT) Usage Guide
for more information about container hot fixes.
D39010 for SAS Enterprise GRC Administrative Tools 4.2
D40011 for SAS Enterprise GRC Mid-Tier 4.2
If the updated components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.
The installer downloaded is D41011la.bin. To install the hot fix:
1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.
$> chmod 755 D41011la.bin2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:03. Execute D41011la.bin using the -alwaysoverwrite option
<path_to_downloaded_file>/D41011la.bin -alwaysoverwriteFor example:
./D41011la.bin -alwaysoverwrite
See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.
This completes the installation of D41011. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.
For each product installed, click the link to be redirected to post-installation instructions.
D39010 for SAS Enterprise GRC Administrative Tools 4.2
D40011 for SAS Enterprise GRC Mid-Tier 4.2
D39010 for SAS Enterprise GRC Administrative Tools 4.2
None
D40011 for SAS Enterprise GRC Mid-Tier 4.2
Step 1: Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.2
From the SASDeploymentManager directory launch config.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.2
1.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 OpRisk Monitor MidTier 4.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 OpRisk Monitor MidTier 4.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 Applications
2.1 Re-deploy the web applications based on the instructions for the web application server you are using.
Step 3: Update and upload Assessment screen definition
Update and upload the Assessment screen definition (Assessment.xml) with the following changes in two places. In the out of box Assessment.xml for the fields TEMP.prepopulatedControls and TEMP.prepopulatedRisks the readonly attribute must be changed from readonly="TEMP.planningReadOnly or TEMP.hasBeenStarted" to the following
<field name="TEMP.prepopulatedRisks" type="component" component-name="PopulatedRiskTable" required="false" readonly="TEMP.planningReadOnly"> <field name="TEMP.prepopulatedControls" type="component" component-name="PopulatedControlTable" required="false" readonly="TEMP.planningReadOnly">