Hot fix Z41007 addresses the issue(s) in SAS Fraud Management 4.3 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/Z41.html#Z41007
Z41007 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
Z92002 updates SAS Fraud Management Common Macros 4.3
Z43006 updates SAS Fraud Management Decision Engine 4.3***
Z42007 updates SAS Fraud Management Mid-Tier 4.3***
B1L001 updates SAS Fraud Management Reporting History ETL Server Macros 4.3
A3K004 updates SAS Fraud Management System of Record DB Maintenance Macros 4.3
B1M002 updates SAS Fraud Management Transaction Extensions 4.3
*** member hot fixes that have been updated since the previously released hot fix (Z41006)
Software Component | Server | Z41001 HF1 | Z41002 HF2 | Z41003 HF3 | Z41004 HF4 | Z41005 HF5 | Z41006 HF6 | Z41007 HF7 |
---|---|---|---|---|---|---|---|---|
SAS FM Common Macros 4.3 | Batch Server (Unix) | Z92001 | - | Z92002 | - | - | - | - |
SAS FM Decision Engine 4.3 | Decision Server | Z43001 | Z43002 | Z43003 | Z43004 | Z43005 | - | Z43006 |
SAS FM Mid-Tier 4.3 | Midtier | Z42001 | Z42002 | Z42003 | Z42004 | Z42005 | Z42006 | Z42007 |
SAS FM Reporting History ETL Server Macros 4.3 | Batch Server (Unix) | - | - | B1L001 | - | - | - | - |
SAS FM System of Record DB Maintenance Macros 4.3 | Batch Server (Unix) | - | A3K001 | A3K002 | A3K003 | - | A3K004 | - |
SAS FM Transaction Extensions 4.3 | Decision Server (Unix), Rules Server (Unix) | - | - | B1M001 | - | B1M002 | - | - |
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.
Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report.
Commands to create the report:Two files are created: DeploymentRegistry.txt and DeploymentRegistry.html. Either of these files can be used to verify that the appropriate product releases are installed on your system. The release number information in the Deployment Registry report should match the 'member' release number provided above for the software components installed on each machine in your deployment. In addition, you can determine the current hot fix level by comparing the HOT FIX COMPONENT HISTORY chart above with the hot fix entries in the Deployment Registry report.
For Oracle 11g environments, download the ojdbc7.jar from the Oracle website and add it to the <ORACLE_DIR>/client_1/jdbc/lib directory on the ODE server(s).
Backup the following:
For a detailed list of updated files, see the hot fix manifest. NOTE: The manifest is cumulative for all hot fixes for this release.
Hot Fix Z41007 must be installed on each machine where the updated components of the product, listed above, are installed.
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. Do NOT extract the contents of Z41007pt.zip into the selected directory. The hot fix installation process will extract the contents as needed.
After copying Z41007pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User’s Guide.
For example:
$ export DISPLAY=<displayname>:0
From the SASDeploymentManager directory execute sasdm.sh
$ cd <SASHOME>/SASDeploymentManager/9.4
$ ./sasdm.sh
Notes:
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).
This section describes custom steps that depend on the starting version of your system before this hot fix was installed. Locate your starting version in the first column of the table below and perform only those steps listed in the second column for that version.
Starting Version | Steps |
---|---|
4.3M0 (No hot fix) or 4.3M0 HF1 through HF4 |
Steps for upgrade from 4.3M0, HF1, HF2, HF3, HF4 to HF7
|
4.3M0 HF5 or 4.3M0 HF6 |
Steps for upgrade from HF5 or HF6 to HF7There are no custom steps for the server tier to upgrade from HF5 or HF6 to HF7. |
IMPORTANT: Database updates may not be required for every hot fix.
Review this section carefully to determine if updates are needed.
IMPORTANT: Files that have been run during previous hot fix
installations should NOT be run a second time.
The table below indicates the files that need to be run for each individual hot fix. These files are not cumulative. You will need to know the prior hot fix level of your system to determine which files to run. The SAS Deployment Registry report created in the PRE-INSTALLATION INSTRUCTIONS step can be used to determine the prior hot fix level if you do not already know it.
IMPORTANT: Perform this step only if "SAS Fraud Management Mid-Tier" component was updated by this hot fix.
In order for this step to execute correctly, the Metadata Server must be running.
$ export DISPLAY=<displayname>:0
From the SASDeploymentManager directory execute sasdm.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.4
$ ./sasdm.sh
In order for this step to execute correctly, the Metadata Server must be running.
$ export DISPLAY=<displayname>:0
From the SASDeploymentManager directory execute sasdm.sh, for example
$ cd <SASHOME>/SASDeploymentManager/9.4
$ ./sasdm.sh
See SAS 9.4 Intelligence Platform Middle-Tier Administration Guide for more details on deploying Web Applications.
Log in to the web application as a user with the privilege to deploy rules on the Console tab. Deploy all the existing rules files.
Run a new SAS Deployment Registry report following the same steps as in the PRE-INSTALLATION INSTRUCTIONS. The new report files will overwrite the existing ones. To retain the old files, save them to a new location or rename them before running the commands.
Please send a copy of the final Deployment Registry report to SAS Fraud Management support.
This completes the installation of hot fix Z41007 on Linux for x64.
Copyright 2016 SAS Institute Inc. All Rights Reserved.