Installation Instructions for Hot Fix F6R002

Linux for x64


Hot fix F6R002 addresses the issue(s) in SAS Fraud Management 6.1 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/F6R.html#F6R002


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

G6C001  updates  SAS Fraud Management Data Services 6.1
F8Y001  updates  SAS Fraud Management Decision Engine 6.1
F6S002  updates  SAS Fraud Management Mid-Tier 6.1***
F6T001  updates  SAS Fraud Management Transaction Extensions 6.1
F8Z001  updates  SAS Fraud Transactional Analysis Engine 6.1

*** member hot fixes that have been updated since the previously released hot fix (F6R001)


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


HOT FIX COMPONENT HISTORY

Software Component Server F6R001 HF1 F6R002 HF2
SAS FM Data Services 6.1 Data Server (Unix) G6C001 -
SAS FM Decision Engine 6.1 Decision Server F8Y001 -
SAS FM Mid-Tier 6.1 Midtier F6S001 F6S002
SAS FM Transaction Extensions 6.1 Decision Server (Unix), Rules Server (Unix) F6T001 -
SAS Fraud Transactional Analysis Engine 6.1 Transaction Analysis Server F8Z001 -


IMPORTANT NOTE

CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.


PRE-INSTALLATION INSTRUCTIONS

  1. Create a Deployment Registry report on each server:

    Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report.

    Commands to create the report:
    1. cd <SASHome>/deploymntreg
    2. <JAVA_HOME>/bin/java -jar sas.tools.viewregistry.jar

    Two files are created: DeploymentRegistry.txt and DeploymentRegistry.html. 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 HOT FIX COMPONENT HISTORY chart above with the hot fix entries in the Deployment Registry report.

  2. Backups:  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.

    Backup the following on each Server:

    1. <SASHOME> directory
    2. <CONFIGDIR> directory
    3. Database(s) that will be updated by this hot fix. Review the POST-INSTALLATION INSTRUCTIONS: DATA TIER section to determine if there are database updates.

    For a detailed list of updated files, see the hot fix manifest.  NOTE: The manifest is cumulative for all hot fixes for this release.

  3. Stop Servers:

    1. Stop the OnDemand Decision Engine (ODE) server(s).
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/engine/Server<n>/bin
      $ ./ose.sh stop

    2. Stop the Transactional Analysis Server (TAS).
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/analysis/bin
      $ ./tas.sh stop

    3. All batch jobs running against the SAS FM databases should be paused.


SERVER INSTALLATION

  1. Important:  Install this hot fix using the same userid who performed the initial software installation.

  2. Install the hot fix using the SAS Deployment Manager (SDM):

    Hot Fix F6R002 must be installed on each machine where the updated components of the product, listed above, are installed.

    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   F6R002pt.zip into the selected directory. The hot fix installation process will extract the contents as needed.

    After copying F6R002pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

    For example:

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

    2. From the SASDeploymentManager directory execute sasdm.sh

      $ cd <SASHOME>/SASDeploymentManager/9.4
      $ ./sasdm.sh

    Notes:

    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 complete. These log files identify 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).


POST-INSTALLATION INSTRUCTIONS: SERVER TIER

    This section describes custom steps that depend on the starting version of your system before this hot fix was installed. Locate your starting version in the first column of the table below and perform only those steps listed in the second column for that version.

    Starting Version Steps
    6.1M0 (No Hot Fix)
    or
    6.1M0 HF1    		 Steps for upgrade from base 6.1M0 or HF1 to HF2

    There are no custom steps for the server tier to upgrade from 6.1M0 to 6.1M0 HF2.


POST-INSTALLATION INSTRUCTIONS: DATA TIER

  1. Execute SAS Fraud Management DBMS Package to Update the Databases

    1. The following table describes the database changes for each hot fix. The DBMS script for each database will examine the current state of the database and apply the required changes for the all previous hot fixes and the current hot fix.

      Vendor Database Hot fix Updates
      PostgreSQL MEH HF1 Authorizations are added to the static partition tables.
      Oracle TDR HF1 Peformance improvments are made to the DECODE_BASE64_SIGNATURE function.

    2. As the SAS installation user, log on to the server where the SAS Fraud Management Data Services component is installed.

    3. Change to the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/dbms/bin directory.

    4. (Optional) To preview the SQL for the changes that will be applied to each database, run the following commands:
      $ ./mehddl.sh preview
      $ ./sorddl.sh preview
      $ ./tdrddl.sh preview
    5. Run the database update scripts. Check each log for errors. By default, the logs are in <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/dbms/logs directory.
      $ ./mehddl.sh update
      $ ./sorddl.sh update
      $ ./tdrddl.sh update
      Notes:
      • You can run all three <db>ddl.sh scripts whether there are database changes or not. The DBMS package will determine what updates are needed and skip the rest. If you prefer, you can use the chart in the begining of this section to determine which databases have changes between your starting hot fix level and ending hot fix level and then run only scripts for those databases.
      • If a script fails with a checksum error, clear the checksums for the failed database:
        $ ./mehddl.sh clearCheckSums
        $ ./sorddl.sh clearCheckSums
        $ ./tdrddl.sh clearCheckSums
      • You can update the logging level and log file location the database properties files located in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/dbms/etc directory.


POST-INSTALLATION INSTRUCTIONS: MID TIER

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

    IMPORTANT: Perform this step only if "SAS Fraud Management Mid-Tier" component was updated by this hot fix.

    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.4

        From the SASDeploymentManager directory execute sasdm.sh, for example

        $ cd <SASHOME>/SASDeploymentManager/9.4
        $ ./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 Application

      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.4

        From the SASDeploymentManager directory execute sasdm.sh, for example

        $ cd <SASHOME>/SASDeploymentManager/9.4
        $ ./sasdm.sh

      3. Select a language in the Choose Language box

      4. Select Deploy 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. Check the Allow the application server to stop checkbox

      8. Select SAS Fraud Management Mid-Tier as the Web Application to Deploy

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

      10. Select Finish when the deployment is complete

      See SAS 9.4 Intelligence Platform Middle-Tier Administration Guide for more details on deploying Web Applications.


POST-INSTALLATION: START SERVERS

  1. Redeploy Rules Files in SAS Fraud Management Web Application:

    Log in to the web application as a user with the privilege to deploy rules on the Console tab. Deploy all the existing rules files.

  2. Start Servers:

    1. Start the TAS server. Confirm there are no errors in the log.
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/analysis/bin
      $ ./tas.sh start tail

    2. Start the ODE server(s). Confirm there are no errors in the log.
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.1/<Auth-Domain>/engine/Server<n>bin
      $ ./ose.sh start tail

    3. Start any batch jobs that were paused before the installation.

  3. Create a final Deployment Registry report on each server:

    Run a new SAS Deployment 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.


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


Copyright 2019 SAS Institute Inc. All Rights Reserved.