Installation Instructions for Hot Fix G49002

AIX


Hot fix G49002 addresses issues in SAS Fraud Management 3.2_M2 on AIX.

This hot fix download consists of the following components:

G49002 - SAS Fraud Management 3.2_M2
rpthist_db2_hotfix_3.2.2.3 - RH updates for DB2
rpthist_teradata_hotfix_3.2.2.3 - RH updates for teradata
sor_hotfix_3.2.2.3 - SOR updates


The G49002 component is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated. See the Container Hot Fixes section in the Maintenance Install Tool (MIT) Usage Guide for more information about container hot fixes.

G51002 for SAS Fraud Management Alert Generation Server 3.2_M2
G50001 for SAS Fraud Management Mid-Tier 3.2_M2
G70001 for SAS Fraud Management Multi Entity History DB Maintenance Macros 3.2_M2
G52002 for SAS Fraud Management Scoring Engine 3.2_M2
G63002 for SAS Fraud Management Transaction Extensions 3.2_M2

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.


INSTALLATION

  1. The G49002r6.tar download is a compressed tar file. Download this file to the user's root directory. Uncompress the tar file with this command:
    $> cd ~
    $> tar -xf G49002r6.tar

    This will extract these components to the user's G49002 subdirectory:
    G49002r6.bin
    rpthist_db2_hotfix_3.2.2.3.tar
    rpthist_teradata_hotfix_3.2.2.3.tar
    sor_hotfix_3.2.2.3.tar

  2. Copy G49002r6.bin to each machine where SAS Fraud Management 3.2_M2 is installed.

  3. Copy rpthist_db2_hotfix_3.2.2.3.tar and rpthist_teradata_hotfix_3.2.2.3.tar to each machine.

  4. Copy sor_hotfix_3.2.2.3.tar to each machine.

  5. Install G49002r6.bin:

    1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.
      $> chmod 755 G49002r6.bin

    2. Set your $DISPLAY environment variable
      export DISPLAY=<your_node_name>:0

    3. Execute G49002r6.bin
      <path_to_downloaded_file>/G49002r6.bin
      For example:
      ./G49002r6.bin
      This will initiate the installation wizard, which will guide you through the hot fix installation process. During the installation you will be prompted for the SASHOME location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists.

      See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.

      The contents of G49002r6.bin are listed in the hot fix manifest.


  6. Follow the installation instructions for each appropriate RH and SOR component.
    RH_db2 updates:Installation Instructions for RH_DB2 updates

    RH_teradata updates:Installation Instructions for RH_teradata updates

    SOR updates:Installation Instructions for SOR updates


This completes the installation of G49002. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.


POST-INSTALLATION INSTRUCTIONS

  1. If you use the Java OSE, follow the steps below to update your implementation of the BPI script.

    You must be logged in to the J-OSE host machine as the configuration user.

    1. cd $SASOSE_IMPLEMENT_HOME/ose/Server1/bin

    2. Rename "bpi_server.sh" (otherwise it will be overwritten in step 4):
      mv bpi_server.sh bpi_server.sh.R32M2

    3. cd $SASHOME/SASFoundation/9.2/misc/fsmmeh/scripts

    4. Copy the new bpi_server.sh.orig to the OSE implementation directory:
      cp bpi_server.sh.orig $SASOSE_IMPLEMENT_HOME/ose/<Server#>/bin

    5. cd $SASOSE_IMPLEMENT_HOME/ose/<Server#>/bin

    6. Set permissions on the file:
      chmod 755 bpi_server.sh.orig

    7. Rename the file to remove the .orig extension:
      mv bpi_server.sh.orig bpi_server.sh

    8. Edit bpi_server.sh:

      1. Change "@ose.server.name@" to the appropriate OSE server for your implementation.
        For example: Server1

      2. Replace MACHINE_TYPE value "@os.localhost.machine.type@" with the appropriate machine type for your implementation.
        Valid values: aix, lax

      3. Replace these tokens at the beginning of the script with the corresponding values from the implementation's version of the bpi_server.sh:
        JAVA_HOME
        SASVJR_HOME
        FRAUDOSEINSTALLDIR



  2. Update the web application deployed to your application server:

    1. Re-build Web Applications

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

      1. Set the DISPLAY environment variable, for example
        $ export DISPLAY=<displayname>:0

      2. Invoke the SAS Deployment Manager 9.2

        From the SASDeploymentManager directory execute config.sh, for example

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

      3. Select a language in the Choose Language box

      4. Select Rebuild Web Applications

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

      6. Specify Connection Information, including the sasadm User ID and Password

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

      8. Verify the information on the Summary screen and select Start

      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.


    2. Re-deploy Web Applications

      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 G49002 on AIX.