Installation Instructions for Hot Fix A2W006

Linux for x64


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

https://tshf.sas.com/techsup/download/hotfix/HF2/A2W.html#A2W006


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

A3B004  updates  SAS Fraud Management Common Macros 4.4
A2Y006  updates  SAS Fraud Management Decision Engine 4.4***
A2X006  updates  SAS Fraud Management Mid-Tier 4.4***
A9L001  updates  SAS Fraud Management Multi Entity History DB Maintenance Macros 4.4
A3C004  updates  SAS Fraud Management Reporting History ETL Server Macros 4.4
A3E002  updates  SAS Fraud Management Scoring Engine for zOS 4.4
A3D004  updates  SAS Fraud Management System of Record DB Maintenance Macros 4.4
A3A007  updates  SAS Fraud Management Transaction Extensions 4.4***
A2Z005  updates  SAS Fraud Transactional Analysis Engine 4.4***

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


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 A2W001 HF1 A2W002 HF2 A2W003 HF3 A2W004 HF4 A2W005 HF5 A2W006 HF6
SAS FM Common Macros 4.4 Batch Server (Unix) A3B001 A3B002 A3B003 A3B004 - -
SAS FM Scoring Engine 4.4 Decision Server A2Y001 A2Y002 A2Y003 A2Y004 A2Y005 A2Y006
SAS FM Mid-Tier 4.4 Midtier A2X001 A2X002 A2X003 A2X004 A2X005 A2X006
SAS FM Multi Entity History DB Maintenance Macros 4.4 Batch Server (Unix) - - A9L001 - - -
SAS FM Reporting History ETL Server Macros 4.4 Batch Server (Unix) A3C001 A3C002 A3C003 A3C004 - -
SAS FM Scoring Engine for zOS 4.4 Decision Server A3E001 A3E002 - - - -
SAS FM System of Record DB Maintenance Macros 4.4 Batch Server (Unix) A3D001 A3D002 A3D003 - A3D004 -
SAS FM Transaction Extensions 4.4 Decision Server (Unix), Rules Server (Unix), Scoring Server (Z64) A3A001 A3A002 A3A003 A3A004 A3A006 A3A007
SAS Fraud Transactional Analysis Engine 4.4 Transaction Analysis Server A2Z001 A2Z002 A2Z003 A2Z004 - A2Z005


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/4.4/<Auth-Domain>/engine/Server<n>/bin
      $ ./ose.sh stop

    2. Stop the Transactional Analysis Server (TAS).
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<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 A2W006 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   A2W006pt.zip into the selected directory. The hot fix installation process will extract the contents as needed.

    After copying A2W006pt.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
    4.4M0
    (No Hot Fix)

    Steps for upgrade from 4.4M0 to HF6

    1. Configure the Transactional Analysis Server (TAS):

      1. On the TAS host server, back up the contents of the /bin and /etc directories under the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis directory.

      2. Copy these scripts:
        • esrt.sh
        • esrt_tests.sh
        • functions.sh
        • tas.sh
        • tas-esc.sh
        • wipeout.sh

        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/bin

      3. Merge changes
        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig
        Into: <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc/tas.properties

    2. Update ODE Server Configuration Files:

      IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc directory.

      2. Copy all files ending with '.xml':
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

    3. Update ODE Property Files:

      1. Copy ose.properties.orig:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

        Merge any changes from the ose.properties.orig file into the ose.properties file. Do not update properties that contain placeholder values surrounded by @. These are custom for your environment.

      2. Copy txn.properties.orig:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

        Merge any changes from the txn.properties.orig file into the txn.properties file. Do not update properties that contain placeholder values surrounded by @. These are custom for your environment.

    4. Update ODE Server Scripts:

      IMPORTANT: If you have customized any of the scripts copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin directory.

      2. Copy all the files ending in '.sh':
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin

    5. Create the ODE 'failed' Directory:

      On each ODE server, create a directory named failed under each <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n> directory. This step should be executed as the userid who performed the initial software installation so that the directory is owned by that user id. Set the permissions on the directory to 775 to ensure that the ODE user can create files in this directory.

      For example:
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server1
      $ mkdir failed
      $ chmod 775 failed

    4.4M0 HF1

    Steps for upgrade from HF1 to HF6

    1. Update Transactional Analysis Server (TAS) files:

      1. On the TAS host server, copy these scripts:
        • esrt.sh
        • esrt_tests.sh
        • wipeout.sh

        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/bin

      2. Merge changes
        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig.
        Into: <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc/tas.properties.

    2. Update ODE Server Configuration Files:

      IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc directory.

      2. Copy all files ending with '.xml':
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

    3. Update ODE Property Files:

      1. Copy ose.properties.orig:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

        Merge any changes from the ose.properties.orig file into the ose.properties file. Do not update properties that contain placeholder values surrounded by @. These are custom for your environment.

      2. Copy txn.properties.orig:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

        Merge any changes from the txn.properties.orig file into the txn.properties file. Do not update properties that contain placeholder values surrounded by @. These are custom for your environment.

    4. Update ODE Server Scripts:

      IMPORTANT: If you have customized any of the scripts copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin directory.

      2. Copy all the files ending in '.sh':
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin

    5. Create the ODE 'failed' Directory:

      On each ODE server, create a directory named failed under each <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n> directory. This step should be executed as the userid who performed the initial software installation so that the directory is owned by that user id. Set the permissions on the directory to 775 to ensure that the ODE user can create files in this directory.

      For example:
      $ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server1
      $ mkdir failed
      $ chmod 775 failed

    4.4M0 HF2

    Steps for upgrade from HF2 to HF6

    1. Update the Tranaction Analysis Server (TAS) Configuration

      IMPORTANT: If you have customized the tas.properties file, you must merge your updates into the new version.

      1. On the TAS server, back up the tas.properties file in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc directory.

      2. Merge changes
        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig
        Into: <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc/tas.properties

    2. Update ODE Server Configuration Files:

      IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the actions.xml, ose.xml, post-score-actions.xml and txn.xml files in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc directory.

      2. On each ODE server, copy these files:
        • actions.xml
        • ose.xml
        • post-score-actions.xml
        • txn.xml

        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

    3. Update ODE Server Script:

      IMPORTANT: If you have customized this script, you must merge your updates into the new version.

      1. On each ODE server, back up the ose.sh file in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin directory.

      2. Copy the ose.sh file:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin

    4.4M0 HF3

    Steps for upgrade from HF3 to HF6

    1. Update the Tranaction Analysis Server (TAS) Configuration

      IMPORTANT: If you have customized the tas.properties file, you must merge your updates into the new version.

      1. On the TAS server, back up the tas.properties file in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc directory.

      2. Merge changes
        From: <SASHOME>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig
        Into: <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/etc/tas.properties

    2. Update ODE Server Configuration Files:

      IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.

      1. On each ODE server, back up the actions.xml, ose.xml, post-score-actions.xml and txn.xml files in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc directory.

      2. On each ODE server, copy these files:
        • actions.xml
        • ose.xml
        • post-score-actions.xml
        • txn.xml

        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/etc
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/etc

    3. Update ODE Server Script:

      IMPORTANT: If you have customized this script, you must merge your updates into the new version.

      1. On each ODE server, back up the ose.sh file in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin directory.

      2. Copy the ose.sh file:
        From: <SASHOME>/SASFraudManagementDecisionEngine/4.4/Config/bin
        To:   <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>/bin

    4.4M0 HF4

    Steps for upgrade from HF4 to HF6

    There are no custom steps for the server tier to upgrade from HF4 to HF6.
    4.4M0 HF5

    Steps for upgrade from HF5 to HF6

    There are no custom steps for the server tier to upgrade from HF4 to HF6.


POST-INSTALLATION INSTRUCTIONS: DATA TIER

    Prior to HF4, DDL files were manually run against the databases. The DDL packages and installation instructions are listed in Step 1 below. You must apply any DDL that has not yet been applied to your databases before continuing to Step 2.

    Starting with 4.4M0 HF4, SAS Fraud Management has changed to a DBMS Package that is based on a continuous integration process to maintain changes in the three target databases. Step 2 below lists the scripts to run.

    You must manually configure SAS Fraud Management DBMS Package on your Batch server before running the database scripts. The configuration steps are described in this document: 44M0HF4 SAS Fraud Management DBMS Package Configuration Instructions

  1. Update the Databases to 4.4M0 HF3 level:

    IMPORTANT: Database updates that have been run during previous hot fix installations should NOT be run a second time.

    1. Select the database update files to run. If there are no files that need to be run, skip to Step 2.

      The table below indicates the files that need to be run for each individual hot fix. These files are not cumulative. You will need to know the prior hot fix level of your system to determine which files to run. The SAS Deployment Registry report created in the PRE-INSTALLATION INSTRUCTIONS step can be used to determine the prior hot fix level if you do not already know it.

      • Run the files against the appropriate database in sequential order by HF number. Do not run files that have already been run during a prior hot fix install.
      • Run only the files for your database vendor.
      • Database updates are generally performed by the database administrator (DBA).

      2. Vendor Database Hot fix File Instructions
      DB2 SOR HF1 sor_db2_upgrade_4.4.0.1.tar.gz SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (1)
      DB2 SOR HF2 sor_db2_upgrade_4.4.0.2.tar.gz SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (2)
      DB2 SOR HF3 sor_db2_upgrade_4.4.0.3.tar.gz SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (3)
      DB2 TDR HF2 tdr_db2_base_upgrade_4.4.0.2.tar.gz TDR_DB2_NON-Partitioned updates: Installation Instructions for TDR_DB2_NON-Partitioned updates (1)
      DB2 TDR HF2 tdr_db2_range_upgrade_4.4.0.2.tar.gz TDR_DB2_Partitioned updates: Installation Instructions for TDR_DB2_Partitioned updates (1)
      Oracle MEH HF2 meh_oracle_upgrade_4.4.0.2.tar.gz MEH_Oracle updates: Installation Instructions for MEH_Oracle updates (1)
      Oracle MEH HF3 meh_oracle_non_partitioned_upgrade_4.4.0.3.tar.gz MEH_Oracle_NON-Partitioned updates: Installation Instructions for MEH_Oracle_NON-Partitioned updates (2)
      Oracle MEH HF3 meh_oracle_partitioned_upgrade_4.4.0.3.tar.gz MEH_Oracle_Partitioned updates: Installation Instructions for MEH_Oracle_Partitioned updates (2)
      Oracle SOR HF1 sor_oracle_upgrade_4.4.0.1.tar.gz SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (1)
      Oracle SOR HF2 sor_oracle_upgrade_4.4.0.2.tar.gz SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (2)
      Oracle SOR HF3 sor_oracle_upgrade_4.4.0.3.tar.gz SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (3)
      Oracle TDR HF2 tdr_oracle_base_upgrade_4.4.0.2.tar.gz TDR_Oracle_NON-Partitioned updates: Installation Instructions for TDR_Oracle_NON-Partitioned updates (1)
      Oracle TDR HF2 tdr_oracle_range_upgrade_4.4.0.2.tar.gz TDR_Oracle_Partitioned updates: Installation Instructions for TDR_Oracle_Partitioned updates (1)

    2. Create a "A2W006pt" directory on your machine and unzip the contents of A2W006pt.zip into that directory. The database update files are found in the Miscellaneous subdirectory

    3. Copy the files to a location accessible by the DBA on the database server. Review all database update instructions carefully before running each update.

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

    IMPORTANT: The SAS Fraud Management DBMS Package must be configured before completing this section. The configuration steps are described in this document: 44M0HF4 SAS Fraud Management DBMS Package Configuration Instructions

    On the first execution, the runtime will be longer than usual. The DBMS package must mark existing DBMS objects as already installed in the table FMX_CHANGE_LOG_<MEH|SOR|TDR>;

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

      Vendor Database Hot fix Updates
      DB2 and Oracle SOR HF4 Remove support for O##
      DB2 and Oracle TDR HF4 Remove the FCM_<tabname>_OXX tables.
      DB2 MEH HF4 Update the MEH_DELETE_DATA stored procedure.
      DB2 and Oracle SOR HF5 Add the new analyst.alert.alertInfoPanelDisplay property.
      Oracle TDR HF5 Update the GET_SIGNATURE stored procedure.
      Oracle TDR HF6 Add new index, NDX6_<tabname>, for the transaction tables.

    2. Log on to the ODE Server as the SAS installation user.

    3. Change to the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<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/4.4/<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/4.4/<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 ODE server(s). Confirm there are no errors in the log.
      $ cd /Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/engine/Server<n>bin
      $ ./ose.sh start tail

    2. Start the TAS server. Confirm there are no errors in the log.
      $ cd /Lev1/Applications/SASFraudManagement/4.4/<Auth-Domain>/analysis/bin
      $ ./tas.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 A2W006 on Linux for x64.


Copyright 2017 SAS Institute Inc. All Rights Reserved.