Hot fix P04004 addresses the issue(s) in SAS Enterprise GRC 5.1_M5 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/P04.html#P04004
P04004 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
P03004 updates SAS Enterprise GRC Administrative Tools 5.1_M5
P02004 updates SAS Enterprise GRC Mid-Tier 5.1_M5
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, P04004pt.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 P04004pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of P04004pt.zip. The hot fix installation process will extract the contents as needed.
The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager 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 P04004pt.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.
P03004 updates SAS Enterprise GRC Administrative Tools 5.1_M5
P02004 updates SAS Enterprise GRC Mid-Tier 5.1_M5
P03004 updates SAS Enterprise GRC Administrative Tools 5.1_M5
NONE
P02004 updates SAS Enterprise GRC Mid-Tier 5.1_M5
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 ApplicationClean up the Application Server cache. Please contact your Administrator for detail steps specific to your application server.In 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 Enterprise GRC MidTier 5.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 Enterprise GRC MidTier 5.1 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.
Notes:
monitor.incidentAllocation.enable = false
monitor.incidentMonetaryBreakdown.enable = false
By default, both values are true. A restart of the SAS Enterprise GRC MidTier server is required for this change to take effect.
monitor.controlTesting.canDeleteAcceptedTest = true
By default, the value is false, and accepted tests cannot be deleted or unloaded.
SAMEORIGIN - only allows current site to frame content
ALLOW-FROM uri - only allows the page to be framed from the specified origin (may not be supported on all browsers)
DENY - prevents any domain from framing the content (not recommended)
none - turn off header, do not set any value (default)