Installation Instructions for Hot Fix L50007

Linux for x64


Hot fix L50007 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:

http://ftp.sas.com/techsup/download/hotfix/HF2/L50.html#L50007


L50007 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.

L70005  updates  SAS Fraud Management Alert Generation Server 3.3_M1 ***
L55002  updates  SAS Fraud Management Common Macros 3.3_M1
L51007  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 (L50006)


See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.


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.


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. Install the hot fix using the SDM:

    Hot Fix L50007 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 L50007pt.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 L50007pt.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.log
    for 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.


  2. Install the miscellaneous files:

    1. Create a "L50007pt" directory on your machine and unzip the contents of L50007pt.zip into that directory.

    2. Go to the L50007pt/Miscellaneous directory.

    3. Copy meh_oracle_upgrade_3.3.1.1.tar to each machine.

    4. Copy rpthist_db2_upgrade_3.3.1.1.tar to each machine.

    5. Copy rpthist_db2_upgrade_3.3.1.2.tar to each machine.

    6. Copy rpthist_db2_upgrade_3.3.1.5.tar to each machine.

    7. Copy rpthist_oracle_upgrade_3.3.1.1.tar to each machine.

    8. Copy rpthist_oracle_upgrade_3.3.1.2.tar to each machine.

    9. Copy rpthist_oracle_upgrade_3.3.1.5.tar to each machine.

    10. Copy sor_db2_upgrade_3.3.1.1.tar to each machine.

    11. Copy sor_db2_upgrade_3.3.1.2.tar to each machine.

    12. Copy sor_db2_upgrade_3.3.1.5.tar to each machine.

    13. Copy sor_oracle_upgrade_3.3.1.1.tar to each machine.

    14. Copy sor_oracle_upgrade_3.3.1.2.tar to each machine.

    15. Copy sor_oracle_upgrade_3.3.1.3.tar to each machine.

    16. Copy sor_oracle_upgrade_3.3.1.5.tar to each machine.


POST-INSTALLATION INSTRUCTIONS

  1. Follow the installation instructions for each appropriate MEH, RH and SOR component.
    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)

  2. Copy the updated SAS Fraud Management Reporting History DB Maintenance Macros files to the appropriate configuration directories.
    You must be logged in to the SAS Fraud Management ETL Server host machine as the configuration user.

    1. Navigate to $SASROOT/misc/fsmrh/data.
    2. Copy the frx_scd_column.csv to <implement_root>/dbloader/data/sas
    3. Copy the frx_scd_column_maint.csv to <implement_root>/dbmaint/data/sas
    4. Copy the frx_scd_column_upgrade.csv to <implement_root>/dbmaint/data/sas

  3. Set the test_area_path and test_area_path_webapp properties.
    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.

  4. Alternate connection method
    Use the following instructions if an alternate connection method from the Alert Generation Server to an Oracle database is desired. 

    1. After applying this hot fix, edit $SASFMCP_IMPLEMENT_HOME/ags/etc/ags_env and insert this line at the bottom of the file:
      # export ORACLE_URL_TEMPLATE=jdbc:oracle:thin:@host:port:sid;
    2. Uncomment and save the file.
    3. Restart the Alert Generation Server.

    NOTE:  The host, port, and sid values in the URL will be substituted by AGS. 

  5. 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.3

        From the SASDeploymentManager directory execute sasdm.sh, for example

        $ cd <SASHOME>/SASDeploymentManager/9.3
        $ ./sasdm.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 appropriate for your web application server. See SAS 9.3 Intelligence Platform Middle-Tier Administration Guide, Chapter 7, for more details.



This completes the installation of hot fix L50007 on Linux for x64.