*** Please see the disclaimer regarding this experimental fix at the bottom of this page. ***
D17006 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.
D14007 for SAS Enterprise GRC Administrative Tools 4.3
D15008 for SAS Enterprise GRC Mid-Tier 4.3
D16004 for SAS Enterprise GRC Server 4.3
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 D17006s6.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 D17006s6.bin2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:03. Execute D17006s6.bin using the -alwaysoverwrite option
<path_to_downloaded_file>/D17006s6.bin -alwaysoverwriteFor example:
./D17006s6.bin -alwaysoverwrite
See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.
This completes the installation of D17006. 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.
D14007 for SAS Enterprise GRC Administrative Tools 4.3
D16004 for SAS Enterprise GRC Server 4.3
D15008 for SAS Enterprise GRC Mid-Tier 4.3
D14007 for SAS Enterprise GRC Administrative Tools 4.3
NONE
D16004 for SAS Enterprise GRC Server 4.3
Copy SAS Changes to <SASCONFIGDIR>
The following files were updated as part of the this hotfix to address reported errors but are not directly copied to
the <SASCONFIGDIR> in case there have been customizations performed to the files.
First, backup any files that you have customized before copying the new versions of the files. After copying the
new versions of the files, merge back in your customizations.
Copy the files listed below from
<SASHOME>/SASFoundation/9.2Copymisc/ormonitormva/sample/config/load_custom_field_defs.sas
misc/ormonitormva/sample/config/load_named_list_mappings.sas
misc/ormonitormva/sample/config/load_named_lists.sas
misc/ormonitormva/sample/config/named_list_options.properties
to
<SASCONFIGDIR>/Applications/SASEnterpriseGRCServerCfg/4.3/Source/misc/sample/config
<SASHOME>/SASFoundation/9.2misc/ormonitormva/sample/properties/customMessages.propertiesto
<SASCONFIGDIR>/Applications/SASEnterpriseGRCServerCfg/4.3/Source/misc/sample/properties
D15008 for SAS Enterprise GRC Mid-Tier 4.3
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 ApplicationNew configuration options: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.21.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 Enterprise GRC MidTier 4.3 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 Enterprise GRC MidTier 4.3 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.
monitor.validation.nearMissEvent.estimatedAmount
When the monitor.validation.nearMissEvent.estimatedAmount is set to true, all "near miss" incidents validation stage calculation will based on Estimated Amount of the Incident. Other Incidents will continue to calculate based on total financial amounts.By default, or if not specified, this option is set to false.
monitor.qba.sort.customfield.name
This config option specifies the custom field name to store user's selection for sort order in Questionnaire Based Assessment (QBA). In this fix we provided changes in SAS code to add a custom field named "x_assessment_sort_order" for Assessment, but user can specify to another custom field with different name if needed. This custom field has to be mapped to the new named list "x_assessment_sort_order_option". If "x_assessment_sort_order" is not a custom field of Assessment, or whatever the custom field name specified by this config option does not exist, QBA will behave the same as before this fix.
If either of the options are reset, the application server hosting GRC will need to be restarted.