*** Please see the disclaimer regarding this experimental fix at the bottom of this page. ***
D41004 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.
D39004 for SAS Enterprise GRC Administrative Tools 4.2
D40004 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 D41004la.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 D41004la.bin2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:03. Execute D41004la.bin using the -alwaysoverwrite command line option
<path_to_downloaded_file>/D41004la.bin -alwaysoverwriteFor example:
./D41004la.bin -alwaysoverwrite
See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.
This completes the installation of D41004. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.
Step 1: Update configdata.properties file
To see the performance benefit the following property needs to be added to the configdata.properties file:
monitor.incidents.table.usedistinct=falseStep 2: Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
2.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
2.2 Select a language in the Choose Language box
2.3 Select Rebuild Web Applications
2.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
2.5 Specify Connection Information, including the sasadm User ID and Password
2.6 Select Enterprise GRC MidTier 4.2 as the Web Application to Rebuild
2.7 Verify the information on the Summary screen and select Start
2.8 Select Finish when the deployment is complete
This process will update the Enterprise GRC 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 3: Re-deploy Web Applications
Re-deploy the web applications based on the instructions for the web application server you are using.
Step 4: Log on to the web application as an admin user
After logging in to the web application as an admin user, make the following changes to Assessment.xml to include Issue Component:
<section id="issues_section">
<label><message key="iap.issue.issueView.relatedIssues.section.txt" /></label>
<field name="issues" type="component" component-name="Issues" readonly="TEMP.planningReadOnly">
<label><message key="iap.issue.issueView.relatedIssues.section.txt" /></label>
</field>
</section>