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
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.
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.logfor 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.
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.
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
Re-build the SAS Risk Work Group Mid-Tier
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 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.
NOTE: In order for this step to execute correctly, the Metadata Server must be running.
Re-build the SAS High-Performance Risk Mid-Tier
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 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:
#!/bin/ksh export DISPLAY=<yourmachine>:0.0 /install/SASHome/SASPlatformObjectFramework/9.4/ExportPackage \ -host example.orion.com \ -user sasadm@saspw \ -password <pass> \ -port 8561 \ -objects "/User Folders/sasdemo/My Folder" \ -name "_HPR41_" \ -nameMatchType STARTSWITH \ -types RiskExploration \ -package /tmp/RiskExplorationExport.spk \ -log /tmp/RiskExplorationExport.log
Import the migrated Risk Explorations into SAS High-Performance Risk 4.1 or later:
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
$ 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.
$ ./TKGrid_HF_x86_64_tkhprisk_07.shYou 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)
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:
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}/sasexeNOTE 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#########################################################################
This completes the installation of hot fix B6P007 on Linux for x64.
Copyright 2019 SAS Institute Inc. All Rights Reserved.