Installation Instructions for Hot Fix T04004

64-bit Enabled AIX

Hot fix T04004 addresses the issue(s) in SAS Enterprise GRC 6.1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/T04.html#T04004

T04004 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

T10004  updates  SAS Enterprise GRC Administrative Tools 6.1
T11004  updates  SAS Enterprise GRC Mid-Tier 6.1

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, T04004pt.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 T04004pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of T04004pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

INSTALLATION

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 T04004pt.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.log

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.

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

T10004  updates  SAS Enterprise GRC Administrative Tools 6.1
T11004  updates  SAS Enterprise GRC Mid-Tier 6.1

T10004  updates  SAS Enterprise GRC Administrative Tools 6.1

NONE

T11004  updates  SAS Enterprise GRC Mid-Tier 6.1

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 Application

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Invoke the SAS Deployment Manager 9.4

From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:

<SASHOME>/SASDeploymentManager/9.4

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 Enterprise GRC MidTier 6.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 6.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 Applications

Re-deploy the web applications based on the instructions for the web application server you are using.

1. Update the customMessages.properties to include these lines:

   #{0}nodename dataload.data.moveself.fmt.txt=Attempting

   to move an existing node {0} so that it will be a child of itself.

2. A new configuration option has been added.

   monitor.validation.modifyDataWithValidation=true

   The following behavior changes would happen only when this option is set to "true".
   The default is false.
   
   
   • When rejecting the incident, validator should be able to select a specific stage to return
   • Modify confidentiality level number during validation state transition to hide the incident
   • Copy MO of Discovery Location to Event Location when Sending incident for Validation
   • Allow Validator to recall signoff as what Assessor could do

3. A new configdata option has been added.

   monitor.kri.canDeleteValidatedObservations.enabled=true

   When this option is set to "true", customer can unload a fully validated observation, or delete an observation request with fully validated observation, so they can add a new observation request for the same period.
   The default is false.

4. An additional new feature is added to Test Definition.
   A new parameter "globalTester" is added to the "LinkedControlTable" component in Test Definition CPB XML, TestDefinition.xml

   <field type="component" component-name="LinkedControlTable" name="linkedControl" required="true">
         <param name="statusFilter">APPROVED</param>
         <param name="globalTester" value="'ADDALL'" />
   </field>

   There are 3 acceptable values for the new globalTester parameter: "ADDALL", "FORCE" and "EMPTYONLY". Once this parameter is set in TestDefinition.xml, and the configdata.properies option: "monitor.controlTesting.newTestsLocation" is set to "useTestDef", a new User chooser is available on the Controls table in Test Definition to select a Tester for all associated Controls to the current Test Definition.
   
   The 3 options have different behaviors concerning how to add the selected Tester to the Controls, and customer can choose which one is best for their business use cases.
   
   "ADDALL": the selected Tester will be added to all the Controls currently associated to the Test Definition, in addition to any testers previously assigned to those Controls. So assuming there are 2 Controls: Control A and Control B, with Control A alreadyhas tester userA previously assigned to it, select tester userB with make Control A has 2 potential testers: userA and userB, which Control B will have only 1 potential tester: userB.
   
   "FORCE": the selected Tester will be the potential tester of all the Controls currently associated to the Test Definition. All the testers previously assigned to the Controls are overwritten. Using previous example, assuming there are 2 Controls: Controland Control B, with Control A already has tester userA previously assigned to it, select tester userB with make both Control A and Control B have only 1 potential tester: userB.
   
   "EMPTYONLY": the selected Tester will be assigned as potential tester to only the Controls that have not assign a potential tester yet. Using previous example, assuming there are 2 Controls: Control A and Control B, with Control A already has tester userA previously assigned to it, select tester userB with make Control A remains with only userA as its potential tester, and Control B is now has userB as its potential tester.

5. As part of a security fix, an additional configuration option has been added to control what content can be embedded into the product. To control new configuration option is listed below:

   # List of acceptable embedded urls.
   # If urls start with / the context root is prefixed before checking
   # Otherwise an exact match is used.
   monitor.embed.whitelist=/CPBDocumentation?docType=COMPONENTS&topLevel=true,/CPBDocumentation?docType=FUNCTIONS&topLevel=true,/CPBDocumentation?docType=DIRECTIVES&topLevel=true,/CPBDocumentation?docType=PROPERTIES&topLevel=true

   IMPORTANT: This option is enabled by default with the values shown above, even though it may not be shown in configdata.properties. After installing the HF, you must check your menu XML for any menu items with embed="true", append them to the default property values. For example:

   monitor.embed.whitelist=/CPBDocumentation?docType=COMPONENTS&topLevel=true, /CPBDocumentation?docType=FUNCTIONS&topLevel=true,/CPBDocumentation?docType=DIRECTIVES&topLevel=true, /CPBDocumentation?docType=PROPERTIES&topLevel=true,<menu-option1>,<menu-option2>

   Although not recommended, this option may be disabled altogether by setting monitor.embed.whitelist=OFF

This completes the installation of hot fix T04004 on 64-bit Enabled AIX.


Copyright 2015 SAS Institute Inc. All Rights Reserved.