http://ftp.sas.com/techsup/download/hotfix/HF2/P92.html#P92014
T12004 updates SAS Fraud Management Alert Generation Server 4.1See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.
R70008 updates SAS Fraud Management Mid-Tier 4.1 ***
P94005 updates SAS Fraud Management Reporting History DB Maintenance Macros 4.1
P93008 updates SAS Fraud Management Scoring Engine 4.1
R01005 updates SAS Fraud Management Transaction Extensions 4.1
Z11001 updates SAS Fraud Management System of Record DB Maintenance Macros 4.1
*** member hot fixes that have been updated since the previously released hot fix (P92013)
| Software Component | Server | P92001 HF1 | N/A HF2 | P92002 HF3 | P92003 HF4 | P92004 HF5 | P92005 HF6 | P92006 HF7 | P92007 HF8 | P92008 HF9 | P92009 HF10 | P92010 HF11 | P92011 HF12 | P92012 HF13 | P92013 HF14 | P92014 HF15 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SAS FM Alert Generation Server 4.1 | AGS | - | - | T12001 | - | T12002 | - | - | - | - | T12003 | - | - | T12004 | - | - |
| SAS FM Mid-Tier 4.1 | Midtier | R70001 | - | R70002 | R70003 | R70004 | - | - | - | - | R70005 | - | R70006 | R70007 | - | R70008 |
| SAS FM Reporting History DB Maintenance Macros 4.1 | Rules Server/AGS | P94001 | - | - | - | P94002 | - | P94003 | - | - | P94004 | - | P94005 | - | - | - |
| SAS FM Scoring Engine 4.1 | JOSE | P93001 | - | P93002 | P93003 | - | P93004 | - | P93005 | P93006 | P93007 | P93008 | - | - | - | - |
| SAS FM Transaction Extensions 4.1 | Rules Server/AGS/JOSE | R01001 | - | - | R01002 | - | - | - | - | - | R01003 | - | R01004 | - | R01005 | - |
| SAS FM System of Record DB Maintenance Macros 4.1 | AGS | - | - | - | - | - | - | - | - | - | Z11001 | - | - | - | - | - |
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 P92014 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 4.1 require updating on the machine. See SAS Note 44810 for more details.
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 P92014pt.zip into the selected directory. The hot fix installation process will extract the contents as needed.
After copying P92014pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: 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 P92014pt.zip file and must be manually extracted and copied to a location accessible by the DBA.
Overview
AGS has a requirement from several customers to support SSL client connection to WebSphere MQ Queue Managers. Today, AGS only support SSL to Queue Managers used for XAMS. This information covers the enhancement which will allow AGS to use SSL client connections to Queue Managers used for the inbound, SAF and Reject queues.
Restrictions
Customers using the XAMS feature of the AGS are affected by the following restriction. AGS will not support different SSL options for the same AGS instance. The limitation is related to the SSL Key Store and the password used to access that Key Store. The same password and location must be used for the Key Stores defined for the XAMS queue manager and the queue manager used for the inbound, SAF and Reject queues. NOTE: The passwords are actually stored in the OMR (Metadata Server) and the passwords for XAMS user and the AGS MQ user (a new user id) must be the same.
Configuration
AGS will rely on several new configuration properties to manage the SSL connection in MQ. These properties are:
ags_mq_ssl_cipher_suite - Specifies the SSL Cipher Suite. If not null, then SSL will be enabled.
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
Metadata Server Configuration
SQL for new properties In order for this step to execute correctly, the Metadata Server must be running. From the SASDeploymentManager directory execute sasdm.sh,
for example In order for this step to execute correctly, the Metadata Server must be running. From the SASDeploymentManager directory execute sasdm.sh,
for example See SAS 9.4 Intelligence Platform Middle-Tier Administration
Guide for more details on 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.
In addition, a new user group will be required to be added to the Metadata Server. This user must have an account defined that will be used to specify the password required for the SSL KeyStore. The account name must be “agsssl_
See the DDL package released with this hotfix.
This process will update the Fraud Management ear in
<CONFIGDIR>/Lev1/Web/Staging. A backup of the original ear file
will be placed in the Backup directory.
$ export DISPLAY=<displayname>:0
$ cd <SASHOME>/SASDeploymentManager/9.4
$
./sasdm.sh
$ export DISPLAY=<displayname>:0
$ cd <SASHOME>/SASDeploymentManager/9.4
$
./sasdm.sh