Installation instructions for hot fix B6P007 on Windows for x64

Installation Instructions for Hot Fix B6P007

Windows for x64

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

https://tshf.sas.com/techsup/download/hotfix/HF2/B6P.html#B6P007

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

B6G003 updates SAS High-Performance Risk Mid-Tier 3.9
B5E007 updates SAS High-Performance Risk Server Component 3.9
D5X002 updates SAS Risk Work Group Mid-Tier 3.9

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

Do NOT extract the contents of B6P007pt.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 B6P007 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.9 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 B6P007pt.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.

D5X002 updates SAS Risk Work Group Mid-Tier 3.9
B6G003 updates SAS High-Performance Risk Mid-Tier 3.9
B5E007 updates SAS High-Performance Risk Server Component 3.9

D5X002 updates SAS Risk Work Group Mid-Tier 3.9

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.

Rebuild Web Applications
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
Re-build the SAS Risk Work Group Mid-Tier
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.

B6G003 updates SAS High-Performance Risk Mid-Tier 3.9

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.

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

Optional: Exporting Risk Explorations from SAS High-Performance Risk 3.9 to SAS High-Performance Risk 4.1

To allow for an easier transition from SAS High-Performance Risk 3.9 to SAS High-Performance Risk 4.x, SAS High-Performance Risk 3.9 Hotfix B6P007 enables Risk Explorations to be exported for use in SAS High-Performance Risk 4.1 and future releases.

You enable this feature by including “/?migrate=True” in your address bar after downloading and installing this Hotfix.
There are two methods to export Risk Explorations from SAS High-Performance 3.9 to SAS High-Performance 4.1.

To export all Risk Explorations from SAS High-Performance Risk 3.9 to SAS High-Performance Risk 4.1 in a folder:

Click Export Risk Explorations to 4.1 on the initial “Open Data Source” screen
Navigate to the folder that contains the explorations you would like to export for use in SAS High-Performance Risk 4.1
You must select one of the explorations in that folder. It does not matter which exploration you select. Each Risk Exploration that does not contain the _HPR41_ prefix will be exported to a SAS High-Performance Risk 4.1 exploration
Click OK
The system will systematically open each Risk Exploration in the current folder and all subfolders and create and save a new exploration in the High-Performance Risk 4.1 format.
Review any messages that are reported during the migration process. Due to fundamental differences between the Flex-based technology of High-Performance Risk 3.9 and the HTML5-based technology of High-Performance Risk 4.1 and later, some elements of certain explorations might change, or not be able to be migrated.

The risk explorations contained in that folder have been exported with the prefix _HPR41_.

To export a single Risk Exploration to SAS High-Performance Risk 4.1:

You open the desired exploration in SAS High-Performance Risk 3.9
Click Data at the top left corner, and click Export Risk Exploration to 4.1
Name your new Risk Exploration and click Save.

You should take care to name the Risk Exploration in such a way that allows users to differentiate between a 3.9 Risk Exploration and a 4.1 Risk Exploration.

Using SAS Management Console
A SAS administrator navigates to the migrated explorations and manually selects every exploration they wish to move to the 4.1 system. You can use the Export SAS Package Wizard to create the package file. Information about using the Export SAS Package Wizard can be found at Example Usage Scenario for Export SAS Package and Import SAS Package Wizards

Using Batch Tools
You can use the ExportPackage command line tool to create a package by selecting Risk Explorations that match a particular query. This is useful if you have a lot of explorations that have the same prefix. The below example creates a RiskExplorationExport.spk package by selecting all Risk Explorations that start with _HPR41_ that are in the “sasdemo” user folder “My Folder” or below.


	C:\SASHome\SASPlatformObjectFramework\9.4\ExportPackage ^
	-host example.orion.com ^
	-user sasadm@saspw ^
	-password  ^
	-port 8561 ^
	-objects "/User Folders/sasdemo/My Folder" ^
	-name "_HPR41_" ^
	-nameMatchType STARTSWITH ^
	-types RiskExploration ^
	-package C:\temp\RiskExplorationExport.spk ^
	-log C:\temp\RiskExplorationExport.log

Import the migrated Risk Explorations into SAS High-Performance Risk 4.1 or later:

The SAS administrator should copy the previously created metadata packages containing the migrated Risk Explorations to the machine hosting the metadata server in your SAS High Performance Risk 4.1 (or later) deployment
Import the package using the SAS Management Console into the desired user metadata folder.
(Optional) – rename the imported explorations. If you used the Export All Risk Explorations functionality during the export from SAS High-Performance Risk 3.9, your explorations have a _HPR41_ prefix added to them. You might wish to remove this prefix after importing the package into your SAS High Performance Risk 4.1 or later deployment. You can rename the explorations in Metadata manually using SAS Management Console or use SAS data step code to rename them all at once. Below is an example data step code that will remove the _HPR41_ prefix from all Risk Explorations in Metadata.


option metaserver=example.orion.com metauser="sasadm@saspw" metapass="" metaport=8561;

data _null_;
    length uri $256 name $100 newname $100;
    uri="";
    name="";
    nobj=1;
    n=1;

    /* Search for Risk Explorations with the _HPR41_ prefix and remove the prefix from the name. */
    do while(nobj >= 0);
        nobj=metadata_getnobj("omsobj:Transformation?@Name contains '_HPR41_'",n,uri);
        if nobj>0 then do;
            rc = metadata_getattr(uri, "Name", name);
            newname=tranwrd(name,"_HPR41_","");
            rc = metadata_setattr(uri, "Name", newname);
            put "(" n "of " nobj"):";
            put @5 "Original Name: " name ;
            put @5 "New Name:      " newname;
            if rc=0 then do;
               put @5 "Name change:  Success!";
               end;
            else do;
               put @5 "Name change:  Failure!";
               end;
        end;
        n=n+1;
    end;
run;

B5E007 updates SAS High-Performance Risk Server Component 3.9

High Performance Risk Server 3.9 Grid Update

Copy SASFoundation/9.4/hprisksvr/sasmisc/TKGrid_HF_x86_64_tkhprisk_07.sh grid hot fix installer to the parent directory of the existing TKGrid installation on the head grid node.
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.
Run the grid hot fix installer script:
$ ./TKGrid_HF_x86_64_tkhprisk_07.sh
You should see the following:
Verifying archive integrity... All good. Uncompressing TKGrid........... running TKGrid/bin_tkhprisk_07/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_07 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 3.9 optional integration with SAS Event Stream Processing (ESP)

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

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