Hot fix L50006 addresses the issue(s) in SAS Fraud Management 3.3_M1 as documented in the Issue(s) Addressed section of the hot fix download page:
L50006 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.
L70004 updates SAS Fraud Management Alert Generation Server 3.3_M1
L55002 updates SAS Fraud Management Common Macros 3.3_M1
L51006 updates SAS Fraud Management Mid-Tier 3.3_M1 ***
L77002 updates SAS Fraud Management Multi Entity History DB Maintenance Macros 3.3_M1
L53004 updates SAS Fraud Management Reporting History DB Maintenance Macros 3.3_M1 ***
L54002 updates SAS Fraud Management Reporting History ETL Server Macros 3.3_M1
L68003 updates SAS Fraud Management Scoring Engine 3.3_M1
L64004 updates SAS Fraud Management System of Record DB Maintenance Macros 3.3_M1 ***
L52004 updates SAS Fraud Management Transaction Extensions 3.3_M1 ***
*** member hot fixes that have been updated since the previously released hot fix (L50003)
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.
Hot Fix L50006 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 Fraud Management 3.3_M1 require updating on the machine. See SAS Note 44810 for more details.
Do NOT extract the contents of L50006pt.zip. The hot fix installation process will extract the contents as needed.
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 copying L50006pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.
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.
MEH_Oracle updates: Installation Instructions for MEH_Oracle updates
RH_DB2 updates (1): Installation Instructions for RH_DB2 updates (1)
RH_DB2 updates (2): Installation Instructions for RH_DB2 updates (2)
RH_DB2 updates (3): Installation Instructions for RH_DB2 updates (3)
RH_Oracle updates (1): Installation Instructions for RH_Oracle updates (1)
RH_Oracle updates (2): Installation Instructions for RH_Oracle updates (2)
RH_Oracle updates (3): Installation Instructions for RH_Oracle updates (3)
SOR_DB2 updates (1): Installation Instructions for SOR_DB2 updates (1)
SOR_DB2 updates (2): Installation Instructions for SOR_DB2 updates (2)
SOR_DB2 updates (3): Installation Instructions for SOR_DB2 updates (3)
SOR_Oracle updates (1): Installation Instructions for SOR_Oracle updates (1)
SOR_Oracle updates (2): Installation Instructions for SOR_Oracle updates (2)
SOR_Oracle updates (3): Installation Instructions for SOR_Oracle updates (3)
SOR_Oracle updates (4): Installation Instructions for SOR_Oracle updates (4)
The value for both of these properties needs to be set to a logical location that is shared between the server running WebSphere and the server hosting the SAS IOM Server. If the properties are not set correctly, rule testing may fail.
It is suggested that the TestArea directory should be in the same location as the Estimates directory as defined in the properties
"estimate_results_dir_sasiom" and "estimate_results_dir_webapp" found in the Preferences Tab under System Properties -> Estimation.
NOTE: The host, port, and sid values in the URL will be substituted by AGS.
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.3
Re-deploy the web applications based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details.