Installation instructions for hot fix B2T002 on Linux for x64

Installation Instructions for Hot Fix B2T002

Linux for x64

Hot fix B2T002 addresses the issue(s) in SAS High Performance Risk 3.8 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/B2T.html#B2T002

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

B2R002 updates SAS High-Performance Risk Mid-Tier 3.8
B2S002 updates SAS High-Performance Risk Server Component 3.8
B2Q002 updates SAS Risk Common Scenario Repository 3.8
B2Y001 updates SAS Risk Work Group Mid-Tier 3.8

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

Do NOT extract the contents of B2T002pt.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 B2T002 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 High Performance Risk 3.8 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 B2T002pt.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

Web Application Update

This hot fix requires steps that will update the web application deployed to your application server. Make sure that the SAS Metadata Server is running prior to rebuild/redeploy activities.

Rebuild the following Web Applications:

SAS High-Performance Risk Mid-Tier 3.8
SAS Risk Common Scenario Repository 3.8
SAS Risk Work Group Mid-Tier 3.8

Redeploy the following Web Applications:

SAS High-Performance Risk Mid-Tier 3.8
SAS Risk Common Scenario Repository 3.8
SAS Risk Work Group Mid-Tier 3.8

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.

High Performance Risk Server 3.8 Grid Update

IMPORTANT NOTE: If you are applying this hot fix after an upgrade-in-place of the SAS High-Performance Risk software from release 3.8 to release 3.9, the following steps should be skipped:

Copy SASFoundation/9.4/misc/hprisksvr/TKGrid_HF_x86_64.sh grid hot fix installer to the parent directory of the existing TKGrid installation on the head grid node. For RHEL5, use the TKGrid_HF_x86_64_rhel5.sh script.
Log in to the head grid node and run the following (modify path to match your installation location):
$ umask 022
$ cd /install
$ ./TKGrid_HF_x86_64.sh

You should see the following:
Verifying archive integrity... All good. Uncompressing TKGrid........... running TKGrid/bin_tkhprisk_02/hfInstall TKGrid /install TKGrid HotFix Configuration Utility. Running on 'gridnode01.orion.com' Using stdin for options. Shared install or replicate to each node? (Y=SHARED/n=replicated)
Check with your grid install team to determine if the existing grid software was deployed using a replicated or shared approach. Answer the question accordingly and proceed with the grid software update. If necessary, respond with YES to confirm the software update on all of the other grid nodes.
The updated shared libraries will be located in the /install/TKGrid/lib_tkhprisk_02 folder.
If necessary, the permissions on the /install/TKGrid folder for all grid nodes may need to be updated for group read/write permissions.