Installation Instructions for Hot Fix D63004

64-bit Enabled AIX


Hot fix D63004 addresses the issue(s) in SAS Fraud Management 3.2 on 64-bit Enabled AIX.

This hot fix contains updates to the following software components:

D71004 - SAS Fraud Management Mid-Tier 3.2
D93003 - SAS Fraud Management Alert Generation Server 3.2
D94003 - SAS Fraud Management Scoring Engine 3.2
D55003 - SAS Fraud Management Reporting History DB Maintenance Macros 3.2
D95001 - SAS Fraud Management System of Record DB Maintenance Macros 3.2
D75002 - SAS Fraud Management Transaction Extensions 3.2
E64001 - SAS Fraud Management Common Macros 3.2
E65001 - SAS Fraud Management Reporting History ETL Server Macros 3.2
sasfmcp_db2_rpthist_patch_3.2.0.1 - RH updates (1)
rpthist_hotfix_3.2.0.2 - RH updates (2)
rpthist_hotfix_3.2.0.3 - RH updates (3)
sasfmcp_db2_sor_patch_3.2.0.1 - SOR updates (1)
sor_hotfix_3.2.0.2 - SOR updates (2)
sor_hotfix_3.2.0.2.5 - SOR updates (3)
sor_hotfix_3.2.0.3 - SOR updates (4)

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 software components and release numbers should match the list of software components updated by the individual hot fix installers.


IMPORTANT NOTES

  1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

  2. You must have Administrator Privileges on your CLIENT or SERVER machine.

  3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  4. This hot fix should be installed using the same userid who performed the initial software installation.

  5. ECM Integration Queue
    A new ECM integration queue will be required to use this functionality. If one is not provided to the application, then the ECM integration message will not be sent when confirmed fraud alerts are saved. The queue configuration will be managed inside the WebSphere Deployment Manager and the MQ queue manager. Persistence and expiry settings are managed outside of SAS Fraud Management. These values must be based on average message size and queue depth and how quickly the consumer of the information can process the contents of the message before removing them from the queue. SSL communication between WebSphere Application Server and WebSphere MQ is a supported configuration with the SAS Fraud Management web application. These security settings are managed in the WebSphere Console.

  6. Work Manager
    The work manager will provide the container managed threads. The maximum number of threads in the thread pool depends on the average number of confirmed fraud alerts per day and the average number of fraudulent transactions per alert that are serialized to XML. Any changes to the thread pool are managed through the WebSphere console.


INSTALLATION


  1. The D63004r6.bin download is a compressed tar file. Copy D63004r6.bin to each 64-bit Enabled AIX machine on which SAS Fraud Management 3.2 components are installed.
    Uncompress the tar file with this command:
    $> cd ~
    $> tar -xf D63004r6.tar

    This will extract these components to the user's D63004 subdirectory:
    D71004r6.bin
    D93003r6.bin
    D94003r6.bin
    D55003r6.bin
    D95001r6.bin
    D75002r6.bin
    E64001r6.bin
    E65001r6.bin
    sasfmcp_db2_rpthist_patch_3.2.0.1.tar
    rpthist_hotfix_3.2.0.2.tar
    rpthist_hotfix_3.2.0.3.tar
    sasfmcp_db2_sor_patch_3.2.0.1.tar
    sor_hotfix_3.2.0.2.tar
    sor_hotfix_3.2.0.2.5.tar
    sor_hotfix_3.2.0.3.tar

  2. Copy D71004r6.bin to each machine where SAS Fraud Management Mid-Tier 3.2 is installed.

  3. Copy D93003r6.bin to each machine where SAS Fraud Management Alert Generation Server 3.2 is installed.

  4. Copy D94003r6.bin to each machine where SAS Fraud Management Scoring Engine 3.2 is installed.

  5. Copy D55003r6.bin to each machine where SAS Fraud Management Reporting History DB Maintenance Macros 3.2 is installed.

  6. Copy D95001r6.bin to each machine where SAS Fraud Management System of Record DB Maintenance Macros 3.2 is installed.

  7. Copy D75002r6.bin to each machine where SAS Fraud Management Transaction Extensions 3.2 is installed.

  8. Copy E64001r6.bin to each machine where SAS Fraud Management Common Macros 3.2 is installed.

  9. Copy E65001r6.bin to each machine where SAS Fraud Management Reporting History ETL Server Macros 3.2 is installed.

  10. Copy sasfmcp_db2_rpthist_patch_3.2.0.1.tar, rpthist_hotfix_3.2.0.2.tar, and rpthist_hotfix_3.2.0.3.tar to each machine.

  11. Copy sasfmcp_db2_sor_patch_3.2.0.1.tar, sor_hotfix_3.2.0.2.tar , sor_hotfix_3.2.0.2.5.tar, and sor_hotfix_3.2.0.3.tar to each machine.

  12. Follow the INSTALLATION instructions for each individual hot fix to complete the deployment of this hot fix.
    SAS Fraud Management Mid-Tier 3.2: Installation Instructions for Hot Fix D71004

    SAS Fraud Management Alert Generation Server 3.2: Installation Instructions for Hot Fix D93003

    SAS Fraud Management Scoring Engine 3.2: Installation Instructions for Hot Fix D94003

    SAS Fraud Management Reporting History DB Maintenance Macros 3.2: Installation Instructions for Hot Fix D55003

    SAS Fraud Management System of Record DB Maintenance Macros 3.2: Installation Instructions for Hot Fix D95001

    SAS Fraud Management Transaction Extensions 3.2: Installation Instructions for Hot Fix D75002

    SAS Fraud Management Common Macros 3.2: Installation Instructions for Hot Fix E64001

    SAS Fraud Management Reporting History ETL Server Macros 3.2: Installation Instructions for Hot Fix E65001

    RH updates: Installation Instructions for RH updates (1)

    RH updates: Installation Instructions for RH updates (2)

    RH updates: Installation Instructions for RH updates (3)

    SOR updates: Installation Instructions for SOR updates (1)

    SOR updates: Installation Instructions for SOR updates (2)

    SOR updates: Installation Instructions for SOR updates (3)

    SOR updates: Installation Instructions for SOR updates (4)


POST INSTALLATION

  1. Add the LIBPATH java system variable to the ags_server.sh script for server start commands. See the Post Installation section in the Installation Instructions for Hot Fix D93003 for details.

  2. As the RH batch user, copy the file frx_job.xml from SAS_ROOT/misc/fsmrh/data to SASFMCP_IMPLEMENT_HOME/rh/dbmaint/data/sas . Then run batch job 6020 to reload the FRX_JOB table (bat_run_job.sh -j 6020 -d RH).

  3. As the SOR batch user, copy the file fmx_job.xml in SAS_ROOT/misc/fsmsor/data to SASFMCP_IMPLEMENT_HOME/sor/dbmaint/data/sas. Then run batch job 2050 to reload the FMX_JOB table (bat_run_job.sh -j 2050 -d SOR).

  4. Using WebSphere MQ Explorer, connect to the Queue Manager defined by jms/SASCreditFraudConFactory
    1. Create a new local queue
      • Name: ECMI_Request
    2. General Properties
      • Default Persistence: Persistent

  5. Create ECM Integration MQ Queue Resource by logging onto your WAS Console and performing the following steps:
    1. Navigate to Resources > JMS > Queues
    2. Click New
    3. Select WebSphere MQ messaging provider
    4. Enter the General Properties (example values)
      • Name: SASCreditFraudECMISendDest
      • JNDI name: jms/SASCreditFraudECMISendDest
      • Queue name: ECMI_Request
    5. Under Advanced Properties (depends on your policy rules)
      • Persistence: As per WebSphere MQ queue definition or WebSphere MQ persistent
      • Priority: As per WebSphere MQ queue definition or Specified
      • Expiry: Unlimited or Specified

  6. Create a Work Manager by logging onto your WAS Console and performing the following steps:
    1. Navigate to Resources > Asynchronous beans > Work managers
    2. Click New
    3. Enter the General Properties (example values)
      • Name: SASCreditFraudWorkManager
      • JNDI name: wm/ SASCreditFraudWorkManager
      • Maximum number of threads : 50
      • Work request queue full action: Block
      • Service names, uncheck:
        • Security
        • Internationalization
        • WorkArea
        • Application Profiling Services

  7. To update the web application deployed to your application server:

    Step 1: Re-build Web Applications

    In order for this step to execute correctly, the Metadata Server must be running.

    1.1 Set the DISPLAY environment variable, for example

    $ export DISPLAY=<displayname>:0

    1.2 Invoke the SAS Deployment Manager 9.2

    From the SASDeploymentManager directory execute config.sh, for example

    $ cd <SASHOME>/SASDeploymentManager/9.2
    $ ./config.sh

    1.3 Select a language in the Choose Language box

    1.4 Select Rebuild Web Applications

    1.5 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

    1.6 Specify Connection Information, including the sasadm User ID and Password

    1.7 Select SAS Fraud Management Mid-Tier as the Web Application to Rebuild

    1.8 Verify the information on the Summary screen and select Start

    1.9 Select Finish when the deployment is complete


    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.


    Step 2: Re-deploy Web Applications

    2.1 Re-deploy the web applications based on the instructions in SAS Web Application Administration Guide, Chapter 8, for the web application server you are using.





This completes the installation of hot fix D63004 on 64-bit Enabled AIX.