Installation Instructions for Hot Fix M96001

Solaris for x64


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

http://ftp.sas.com/techsup/download/hotfix/HF2/M96.html#M96001


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

M89001  updates  SAS High-Performance Risk Mid-Tier 3.2
M94001  updates  SAS High-Performance Risk Server Component 3.2

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

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


INSTALLATION

Hot Fix M96001 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.2 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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 M96001sx.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User’s Guide.


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.

M89001  updates  SAS High-Performance Risk Mid-Tier 3.2
M94001  updates  SAS High-Performance Risk Server Component 3.2


M89001  updates  SAS High-Performance Risk Mid-Tier 3.2

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

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

<SASHOME>/SASDeploymentManager/9.4

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 SAS High Performance Risk MidTier 3.2 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 SAS High Performance Risk 3.2 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.


M94001  updates  SAS High-Performance Risk Server Component 3.2

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

  2. Log in to the head grid node and run the following (modify path to match your installation location):
    $ cd /install $ ./TKGrid_HF_x86_64.sh
    You should see the following:

    Verifying archive integrity... All good. Uncompressing TKGrid........... running TKGrid/bin2/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)

  3. 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/lib2 folder (or libN where N is the version number for the hot fix update).
    If necessary, the permissions on the /install/TKGrid folder for all grid nodes may need to be updated for group read/write permissions.


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