Installation instructions for hot fix C3S002 on Linux for x64

Installation Instructions for Hot Fix C3S002

Linux for x64

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

http://ftp.sas.com/techsup/download/hotfix/HF2/C3S.html#C3S002

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

C3T002 updates SAS Model Risk Management Mid-Tier 7.3
D3K001 updates SAS Model Risk Management Server 7.3
C2J002 updates SAS Risk Governance Framework Server 7.3

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

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

IMPORTANT NOTES

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.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
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 C3S002 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 7.3 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 C3S002pt.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

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

C3T002 updates SAS Model Risk Management Mid-Tier 7.3
D3K001 updates SAS Model Risk Management Server 7.3
C2J002 updates SAS Risk Governance Framework Server 7.3

C3T002 updates SAS Model Risk Management Mid-Tier 7.3

This hot fix requires post-installation steps that will update the web application deployed to your application server.

For more information about how to rebuild and redeploy Web Applications, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications.

Rebuild Web Applications
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
Select the appropriate product as the Web Application to Rebuild
Re-start all SAS sessions, daemons, spawners and servers. For more information on the proper order for starting servers, go to SAS® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition and review the section entitled "Starting, Stopping and Checking the Status of Servers".
Redeploy Web Applications
Redeploy the updated wars to the web application server.

D3K001 updates SAS Model Risk Management Server 7.3

NONE

C2J002 updates SAS Risk Governance Framework Server 7.3

Installation and Configuration

1) Copy the following files from <SASHOME> to <SASCONFIGDIR>

<SASHOME>/SASFoundation/9.4/misc/mrmsvr/control/grid_properties.txt
<SASHOME>/SASFoundation/9.4/misc/rskmgtsvr/control/grid_host.map
<SASHOME>/SASFoundation/9.4/misc/rskmgtsvr/control/grid_port.map
<SASHOME>/SASFoundation/9.4/ucmacros/rskmgtsvr/rskmgt_get_grid_props.sas
<SASHOME>/SASFoundation/9.4/ucmacros/rskmgtsvr/rskmgt_add_cust_fields.sas
<SASHOME>/SASFoundation/9.4/ucmacros/rskmgtsvr/rskmgt_add_hist_cust_fields.sas
to
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/misc/control/grid_properties.txt
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/misc/control/grid_host.map
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/misc/control/grid_port.map
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/ucmacros/rskmgt_get_grid_props.sas
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/ucmacros/rskmgt_add_cust_fields.sas
<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/ucmacros/rskmgt_add_hist_cust_fields.sas

2) Delete the "grid_properties.sas7bdat" dataset if it exist. This file should be located here:

<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Libraries/mrmcntl

3) Delete the "grid_host_port.map" file in the following directory:

<SASCONFIGDIR>/Applications/SASModelRiskManagementServer/Source/misc/control

4) Run one of the load ETL jobs in SAS Management Console --> Schedule Manager, verify the MRMLASR server libname is being assigned and the LASR data sources are being loaded.