Installation Instructions for Hot Fix G2F005

64-bit Enabled Solaris


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

https://tshf.sas.com/techsup/download/hotfix/HF2/G2F.html#G2F005


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

G2H003  updates  SAS High-Performance Risk Mid-Tier 4.2
F7P006  updates  SAS High-Performance Risk Server Component 4.2
G6T001  updates  SAS Risk Dimensions Server Component 6.12
G2G003  updates  SAS Risk Scenario Manager 4.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, G2F005pt.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 G2F005pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of G2F005pt.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 G2F005 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 4.2 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 G2F005pt.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.

G2H003  updates  SAS High-Performance Risk Mid-Tier 4.2
F7P006  updates  SAS High-Performance Risk Server Component 4.2
G6T001  updates  SAS Risk Dimensions Server Component 6.12
G2G003  updates  SAS Risk Scenario Manager 4.2


G2H003  updates  SAS High-Performance Risk Mid-Tier 4.2

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

  1. Rebuild Web Applications

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

    Re-build the SAS High-Performance Risk Mid-Tier

  2. 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".
  3. Redeploy Web Applications
    Redeploy the updated wars to the web application server.


F7P006  updates  SAS High-Performance Risk Server Component 4.2

High Performance Risk Server 4.2 Grid Update

  1. Copy SASFoundation/9.4/hprisksvr/sasmisc/TKGrid_HF_x86_64_tkhprisk_06.sh grid hot fix installer to the parent directory of the existing TKGrid installation on the head grid node.

  2. Log in to the head grid node and run the following (modify path to match your installation location):
    $ umask 022
    $ cd /install

    The output of the file command should indicate that TKGrid is a directory. If so, then proceed to the next step. When the output of the file command indicates that TKGrid is a symbolic link (i.e., softlink), issue the "cd" command to change to the parent folder of the resolved link location. Repeat the "file TKGrid" and "cd" commands until the "file TKGrid" output indicates that TKGrid is a directory.

  3. Run the grid hot fix installer script:
    $ ./TKGrid_HF_x86_64_tkhprisk_06.sh
    You should see the following:

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

  4. 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_06 folder.
    If necessary, the permissions on the /install/TKGrid folder for all grid nodes may need to be updated for group read/write permissions.


High-Performance Risk Server 4.2 optional integration with SAS Event Stream Processing (ESP)

If you are integrating SAS High-Performance Risk with ESP, perform the following post-installation steps:

  1. If the SAS installation was previously configured for ESP with modifications of the LD_LIBRARY_PATH and DFESP_HOME on the command line or in batch files used to launch SAS, then these should be removed.

  2. Modify the ${SASROOT}/bin/sasenv_local script to set the environment variables: LD_LIBRARY_PATH, DFESP_HOME, and TKPATH.
    Note: If your deployment uses the alternative scripts ${SASROOT}/bin/sasenv_local.ksh or ${SASROOT}/bin/sasenv_local.csh then you will need to make equivalent modifications in these files.
    LD_LIBRARY_PATH:
    The path ${SASROOT}/misc/hprisksvr/misc/espps/lib must be placed at the start of the LD_LIBRARY_PATH variable.
    The path ${SASROOT}/misc/hprisksvr/misc/espps/tksf must be placed at the end of the LD_LIBRARY_PATH variable.

    DFESP_HOME:
    Set this environment variable to the ESP client located at the directory ${SASROOT}/misc/hprisksvr/espps. This must not be set to an external ESP installation as HPRisk now only works with the ESP client that is installed with this hotfix.

    TKPATH:
    Set this environment variable to the path for the SAS executables located in ${SASROOT}/sasexe

    NOTE It is important that this be done in ${SASROOT}/bin/sasenv_local and not on the command line when launching SAS to ensure the ESP libraries are first in the LD_LIBRARY_PATH.

    The following is an example modification to ${SASROOT}/bin/sasenv_local that assumes $SASROOT is set to the root directory of the SAS installation (you will need to change this value based on your deployment).

    #########################################################################
    # Set path to internal ESP PubSub Client to the start of LD_LIBRARY_PATH
    # and set ESP variables DFESP_HOME and TKPATH.
    #########################################################################

    SASROOT=/path/to/sas/installation/dir

    if [ "$LD_LIBRARY_PATH" != "" ] ;  then
       LD_LIBRARY_PATH=${SASROOT}/misc/hprisksvr/espps/lib:${LD_LIBRARY_PATH}
    else
       LD_LIBRARY_PATH=${SASROOT}/misc/hprisksvr/espps/lib
    fi
    # Add the path to libtksf.so at the end so the installed version is used
    # if one is found.
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${SASROOT}/misc/hprisksvr/espps/tksf
    export LD_LIBRARY_PATH
    export DFESP_HOME=${SASROOT}/misc/hprisksvr/espps
    export TKPATH=${SASROOT}/sasexe

    #########################################################################


G6T001  updates  SAS Risk Dimensions Server Component 6.12

NONE


G2G003  updates  SAS Risk Scenario Manager 4.2

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

  1. Rebuild Web Applications

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

    Re-build the SAS Risk Scenario Manager

  2. 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".
  3. Redeploy Web Applications
    Redeploy the updated wars to the web application server.


This completes the installation of hot fix G2F005 on 64-bit Enabled Solaris.


Copyright 2020 SAS Institute Inc. All Rights Reserved.