Installation Instructions for Hot Fix W72005

Windows for x64


Hot fix W72005 addresses the issue(s) in SAS Model Risk Management 6.1 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/W72.html#W72005


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

W79006  updates  SAS Model Risk Management Administrative Tools 6.1
W80005  updates  SAS Model Risk Management Mid-Tier 6.1

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.


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

Do NOT extract the contents of W72005pt.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.

  5. CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.


INSTALLATION

Hot Fix W72005 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of SAS Model Risk Management 6.1 require updating on the machine. See SAS Note 44810 for more details.

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 W72005pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.


The hot fix installation process generates the log file

<!SASHOME>\InstallMisc\InstallLogs\IT_date-and-time-stamp.log
for 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.


POST-INSTALLATION INSTRUCTIONS

Security Update for SAS Model Risk Management Mid-Tier 6.1

The following instruction applies only for environments running SAS 9.4 M6 or earlier:

SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at https://tshf.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.


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

W79006  updates  SAS Model Risk Management Administrative Tools 6.1
W80005  updates  SAS Model Risk Management Mid-Tier 6.1


W79006  updates  SAS Model Risk Management Administrative Tools 6.1

Update the picklist for the administrative tools

Perform the following steps to ensure the administrative tools are running with the latest updates.

1. Make a backup of the file “picklist” under <SASCONFIGDIR>\Applications\SASModelRiskManagementAdministrativeTools\dbscripts

2. Copy the new “picklist” from

<SASHOME>\SASModelRiskManagementAdministrativeTools\6.1
to
<SASCONFIGDIR>\Applications\SASModelRiskManagementAdministrativeTools\dbscripts
and overwrite the current contents.


W80005  updates  SAS Model Risk Management Mid-Tier 6.1

Re-build Web Application

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

1. Invoke the SAS Deployment Manager 9.4

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

<SASHOME>\SASDeploymentManager\9.4

2. Select a language in the Choose Language box

3. Select Rebuild Web Applications

4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

5. Specify Connection Information, including the sasadm User ID and Password

6. Select SAS Model Risk Management Mid-Tier 6.1 as the Web Application to Rebuild

7. Verify the information on the Summary screen and select Start

8. Select Finish when the deployment is complete

This process will update the SAS Model Risk Management Mid-Tier 6.1 ear in

<SASCONFIGDIR>\Web\Staging
A backup of the original ear file will be placed in the directory
<SASCONFIGDIR>\Web\Staging\Backup

9. Exit the SAS Deployment Manager 9.4


Re-deploy Web Application

1. Restart all SAS sessions, daemons, spawners and servers.

2. Invoke the SAS Deployment Manager 9.4

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

<SASHOME>\SASDeploymentManager\9.4

3. Select a language in the Choose Language box

4. Select Deploy Web Applications

5. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

6. Specify Connection Information, including the sasadm User ID and Password

7. Check the Allow the application server to stop checkbox

8. Select SAS Model Risk Management Mid-Tier 6.1 as the Web Application to Deploy

9. Verify the information on the Summary screen and select Start

10. Select Finish and exit the SAS Deployment Manager when the deployment is complete


NOTES:

  1. This fix adds support for a maximum file size for content server attachments. By default, only attachments under 100MB will be accepted.

    To change this property, set the value “monitor.rest.attachments.maxSize” in configdata.properties to the maximum size file that should be allowed, in megabytes.

    If the value is changed above the default of 100MB, you should also configure your SAS Content Server to use the “data store”. See the section titled “Enabling the Data Store” in the SAS 9.4 Middle-Tier Administration Guide.

    By default, for Internet Explorer, the limit is enforced in the application server, while Chrome and Firefox enforce it in the browser. For Internet Explorer 11, enforcement can be performed in the browser as long as it is not set to “Compatibility View”, and the following changes are made to the configuration. Edit the file “<SASCONFIGDIR>\Web\WebAppServer\SASServer8_1\sas_webapps\sas.modelriskmanagement.war\WEB-INF\spring-config\webapp-config.xml”. Change the following line:
           <sas-web:theme-support-filter id="themeSupportFilter"/>
           to
           <sas-web:theme-support-filter id="themeSupportFilter" ie-compatibility-mode="false"/>

  2. This fix adds the ability to exclude specific business objects types from the task list table. To use this option, set the following property in configdata.properties:

           monitor.tasklist.excludedtypes=<values>

    where <values> is a comma-separated list of business object type names to exclude. For example “monitor.tasklist.excludedtypes=CustomObject7,TestPlan” will exclude tasks for custom object 7 and test plans from the task list. By default this property is not set, and no object types are excluded.

  3. This fix adds the ability to exclude model review (audit) entries from the task list by status. To use this option, set the following property in confidata.properties:

           monitor.tasklist.exclude.Audit=<values>

    where <values> is a comma-separated list of status code values to exclude. For example “monitor.tasklist.exclude.Audit=CREATED” will exclude model review tasks for objects with a status value of “CREATED”. By default this property is not set, and no model review tasks are excluded.

  4. This fix adds a CPB function “GetPendingLinkInstancesOfType()” that can be used to retrieve and count “pending” link instances in a validation block or in a finalize block. See the online function documentation for details.

  5. If you have enabled dimensional browser security in the Model Risk Mgt Mid-Tier properties in the SMC (Application -> OL Chooser -> Enable Security within Dimension browser?), then you must add the following in the dimensionality.xml file on the SAS Content Server, under sasdav\Products\SASModelRisk\ModelRiskMgtMid-Tier\Config\dimensionality.xml.
    Under the existing “alias” entries, add the following:

            <alias new="RiskDriver" old="Cause"/>

    By default, dimensional browser security is disabled, and no action is needed.



This completes the installation of hot fix W72005 on Windows for x64.


Copyright 2018 SAS Institute Inc. All Rights Reserved.