http://ftp.sas.com/techsup/download/hotfix/HF2/L50.html#L50015
L70007 updates SAS Fraud Management Alert Generation Server 3.3_M1See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.
L55005 updates SAS Fraud Management Common Macros 3.3_M1
L51014 updates SAS Fraud Management Mid-Tier 3.3_M1 ***
L77002 updates SAS Fraud Management Multi Entity History DB Maintenance Macros 3.3_M1
L53011 updates SAS Fraud Management Reporting History DB Maintenance Macros 3.3_M1***
L54004 updates SAS Fraud Management Reporting History ETL Server Macros 3.3_M1
L68004 updates SAS Fraud Management Scoring Engine 3.3_M1
L64008 updates SAS Fraud Management System of Record DB Maintenance Macros 3.3_M1***
L52009 updates SAS Fraud Management Transaction Extensions 3.3_M1***
*** member hot fixes that have been updated since the previously released hot fix (L50014)
Software Component | Server | L50001 HF1 | L50002 HF2 | L50003 HF3 | L50004 HF4 | L50005 HF5 | L50006 HF6 | L50007 HF7 | L50008 HF8 | L50009 HF9 | N/A HF10 | L50010 HF11 | L50011 HF12 | L50012 HF13 | L50013 HF14 | L50014 HF15 | L50015 HF16 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SAS FM Alert Generation Server 3.3_M1 | AGS | L70001 | L70002 | - | L70003 | L70004 | - | L70005 | - | L70006 | - | - | - | - | L70007 | - | - |
SAS FM Common Macros 3.3_M1 | Rules Server/AGS/JOSE | L55001 | L55002 | - | - | - | - | - | L55003 | L55004 | - | - | - | - | L55005 | - | - |
SAS FM Mid-Tier 3.3_M1 | Midtier | L51001 | L51002 | L51003 | L51004 | L51005 | L51006 | L51007 | L51008 | L51009 | - | L51010 | L51011 | - | L51012 | L51013 | L51014 |
SAS FM Multi Entity History DB Maintenance Macros 3.3_M1 | JOSE | L77001 | L77002 | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
SAS FM Reporting History DB Maintenance Macros 3.3_M1 | Rules Server/AGS | L53001 | L53002 | - | L53003 | - | L53004 | - | L53005 | L53006 | - | L53007 | L53008 | - | L53009 | L53010 | L53011 |
SAS FM Reporting History ETL Server Macros 3.3_M1 | Rules Server/AGS | L54001 | L54002 | - | - | - | - | - | - | - | - | L54003 | - | - | - | L54004 | - |
SAS FM Scoring Engine 3.3_M1 | JOSE | L68001 | L68002 | - | - | L68003 | - | - | - | - | - | - | - | - | - | L68004 | - |
SAS FM System of Record DB Maintenance Macros 3.3_M1 | AGS | L64001 | L64002 | - | L64003 | - | L64004 | - | L64005 | L64006 | - | L64007 | - | - | - | - | L64008 |
SAS FM Transaction Extensions 3.3_M1 | Rules Server/AGS/JOSE | L52001 | L52002 | L52003 | - | - | L52004 | - | L52005 | L52006 | - | - | - | L52007 | L52008 | - | L52009 |
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.xml. 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 the software component information in the chart above with the Deployment Registry report.
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 L50015 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.
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. Do NOT extract the contents of L50015pt.zip into the selected directory. The hot fix installation process will extract the contents as needed.
After copying L50015pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.
Note: If this hot fix has been previously installed, use the -reinstallhotfix option when running the SDM. If friendly fixes have been previously installed, use the -alwaysoverwrite option.
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).
Database updates are generally performed by the DBA. The files required are found in the Miscellaneous directory in the L50015pt.zip file and must be manually extracted and copied to a location accessible by the DBA.
You must be logged in to the SAS Fraud Management ETL Server host machine as the configuration user.
A new property, test_area_path_webapp, has been created as part of this hot fix. This property is closely related to the property "test_area_path". Both properties can be found on the SAS Fraud Management web application under the Preferences tab. From the Preferences tab, select System Properties -> Rule Testing.
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.
Use the following instructions if an alternate connection method from the Alert Generation Server (AGS) to an Oracle database is desired.
Note: The host, port, and sid values in the URL will be substituted by AGS.
ags_mq_ssl_cipher_suite | Specifies the SSL Cipher Suite. If not null, then SSL will be enabled. In testing, ags_mq_ssl_cipher_suite property value was set to SSL_RSA_WITH_3DES_EDE_CBC_SHA while the MQ Channel SSL Cipher Spec was set to TLS_RSA_WITH_3DES_EDE_CBC_SHA. |
ags_mq_ssl_truststore | Specifies the location of the SSL TrustStore |
ags_mq_ssl_keystore | Specifies the location of the SSL KeyStore |
ags_mq_ssl_fips_required | Indicates if FIPS is required |
ags_mq_channel | Optional, depending on your configuration you may need to create a separate MQ channel dedicated to SSL. |
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
$ ./sasdm.sh
See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details on Re-deploying Web Applications.
Run a new SAS Depployment 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.