Installation Instructions for Hot Fix D17021

64-bit Enabled AIX

*** Please see the disclaimer regarding this experimental fix at the bottom of this page. ***

D17021 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.

D14021 for SAS Enterprise GRC Administrative Tools 4.3
D15026 for SAS Enterprise GRC Mid-Tier 4.3

IMPORTANT NOTES

1. You must have previously downloaded and applied hot fix container D17020 prior to installing this hot fix.

2. You must use the -alwaysoverwrite command line option to apply this hot fix.

3. 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.

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

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

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

INSTALLATION

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 D17021r6.bin.

When downloading SAS 9.2 hot fix packages, you must choose to Save the hot fix to disk, then execute the install from the saved location. Attempting to install a hot fix directly from the download page results in the error documented in SAS Note 37104.

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 D17021r6.bin

export DISPLAY=<your_node_name>:0

<path_to_downloaded_file>/D17021r6.bin -alwaysoverwrite

./D17021r6.bin -alwaysoverwrite

See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.

The content of this hot fix is listed in the hot fix manifest.

This completes the installation of D17021. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.

POST-INSTALLATION INSTRUCTIONS

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

D14021 for SAS Enterprise GRC Administrative Tools 4.3
D15026 for SAS Enterprise GRC Mid-Tier 4.3

D14021 for SAS Enterprise GRC Administrative Tools 4.3

NONE

D15026 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 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 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 Applications

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

1. Two new parameters as follows are now available to be used to control if user can see the close or delete actions for these components.

   CPB components:

   RiskRatingsSummaryTable
   ControlRatingsSummaryTable

   New parameters are:

   showCloseAction
   showDeleteAction

   The default value for these 2 parameters is "true" i.e. the close and delete actions will show. If users don't want to show the close and delete actions, then pass these parameters as "false".

   Example: In RatingsSummary.xml

   <field name="TEMP.populatedRisks" type="component"
   component-name="RiskRatingsSummaryTable"
   ..........
   <param name="showCloseAction" value="false" />
   <param name="showDeleteAction" value="false" />
   ...........
   </field>

2. With this hotfix, if the config option is set to monitor.validation.return.returnToOriginator=false, and the Kri Observation validator returns an observation, then it will go to the preceding stage instead of to the roginator. However, the message shown during this observation return will still be something like :

   Observation for "KRI name" returned to originator.

   If user wants to set a different message for this case, then they need to set the key "KriObservationEditor.returnToPrecedingStage.fmt.txt" in customMessages.properties. For example:

   KriObservationEditor.returnToPrecedingStage.fmt.txt=Observation returned to preceding stage

   If the above key is set, then it will display that message when returning observation. Otherwise, it will show the original message of observation returned to originator.

3. New config options are used to control max length validation during data loading for KriTemplates and Kris. If user sets these config options, then they are used to validate, otherwise the max length is not validated.

   monitor.nameTxt.maxLength
   monitor.descTxt.maxLength
   monitor.helpTxt.maxLength

   For example, if user sets:

   monitor.nameTxt.maxLength=100
   monitor.descTxt.maxLength=1000
   monitor.helpTxt.maxLength=1000

   then it will give error during data load for KriTemplates and Kris if the name text has more than 100 chars and if description text and help texts have more than 1000 chars.

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

SAS Institute Inc.

License Agreement for Corrective Code or Additional Functionality

SAS INSTITUTE INC. IS PROVIDING YOU WITH THE COMPUTER SOFTWARE CODE INCLUDED WITH THIS AGREEMENT ("CODE") ON AN "AS IS" BASIS, AND AUTHORIZES YOU TO USE THE CODE SUBJECT TO THE TERMS HEREOF. BY USING THE CODE, YOU AGREE TO THESE TERMS. YOUR USE OF THE CODE IS AT YOUR OWN RISK. SAS INSTITUTE INC. MAKES NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, WITH RESPECT TO THE CODE.

The Code is intended to be used solely as part of a product ("Software") you currently have licensed from SAS Institute Inc. or one of its subsidiaries or authorized agents ("SAS"). The Code is designed to either correct an error in the Software or to add functionality to the Software, but has not necessarily been tested. Accordingly, SAS makes no representation or warranty that the Code will operate error-free. SAS is under no obligation to maintain or support the Code.

Neither SAS nor its licensors shall be liable to you or any third party for any general, special, direct, indirect, consequential, incidental or other damages whatsoever arising out of or related to your use or inability to use the Code, even if SAS has been advised of the possibility of such damages.

Except as otherwise provided above, the Code is governed by the same agreement that governs the Software. If you do not have an existing agreement with SAS governing the Software, you may not use the Code.

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. (r) indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.