Installation Instructions for Hot Fix V02003

Solaris for x64


Hot fix V02003 addresses the issue(s) in SAS Risk Management for Banking 3.3 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/V02.html#V02003


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

V03001  updates  SAS Asset and Liability Management for Banking Server 3.3
V05001  updates  SAS Credit Risk for Banking Server 3.3
V06001  updates  SAS Firmwide Risk for Banking Server 3.3
V07001  updates  SAS Market Risk for Banking Server 3.3
V08003  updates  SAS Risk Management for Banking Mid-Tier 3.3
V18001  updates  SAS Risk Management for Banking Mid-Tier Help and Documentation 3.3
V04003  updates  SAS Risk Management for Banking Server 3.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, V02003pt.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 V02003pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of V02003pt.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 required 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 V02003 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 Risk Management for Banking 3.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 V02003pt.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.

V03001  updates  SAS Asset and Liability Management for Banking Server 3.3
V05001  updates  SAS Credit Risk for Banking Server 3.3
V06001  updates  SAS Firmwide Risk for Banking Server 3.3
V07001  updates  SAS Market Risk for Banking Server 3.3
V08003  updates  SAS Risk Management for Banking Mid-Tier 3.3
V18001  updates  SAS Risk Management for Banking Mid-Tier Help and Documentation 3.3
V04003  updates  SAS Risk Management for Banking Server 3.3


V03001  updates  SAS Asset and Liability Management for Banking Server 3.3

NONE


V05001  updates  SAS Credit Risk for Banking Server 3.3

NONE


V06001  updates  SAS Firmwide Risk for Banking Server 3.3

NONE


V07001  updates  SAS Market Risk for Banking Server 3.3

NONE


V08003  updates  SAS Risk Management for Banking Mid-Tier 3.3

Web Application Update

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

Rebuild the following Web Applications:

Redeploy the following Web Applications:

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 on Rebuilding the SAS Web Applications and Redeploying the SAS Web Applications.


V18001  updates  SAS Risk Management for Banking Mid-Tier Help and Documentation 3.3

NONE


V04003  updates  SAS Risk Management for Banking Server 3.3

Run copy scripts

The hot fix provides a script file, copy_files.sh for Unix-based operating systems to enable versioning at the SAS product configuration level.

The file is located at:

<SASHOME>/SASFoundation/9.4/misc/rmbcomnsvr/batch/hfscripts
Depending upon the operating system where the hot fix is installed, use a command prompt (using administrator credentials) to change directory to the location of the appropriate script file above. Next, invoke the script file at the location and pass paths to the SASFoundation and SASCONFIG locations at the command line:
copy_files.sh <SASROOT> <SASCONFIG>

example:

copy_files.sh   /install/SASHome/SASFoundation/9.4   /install/sas/Config/Lev1

Successful script execution will result in copying of all files from SASFoundation under rmbcomnsvr, rmbfirmmva, rmbalmmva, rmbmktmva and rmbcriskmva to their respective folders under <SASCONFIG>. Prior to copying, the script will move the existing source folders and their contents to a new folder named source-pre-YYYY-MM-DD where YYYY-MM-DD corresponds to the current date.

Note: On UNIX systems, the script will actually copy files from SASFoundation to a directory, source-YYYY-MM-DD and create a ‘source’ symbolic link to point to that directory. You should verify that the directory and file permissions for the source-YYYY-MM-DD directory and files are in compliance with your site's security policy.


This completes the installation of hot fix V02003 on Solaris for x64.


Copyright 2018 SAS Institute Inc. All Rights Reserved.