Installation Instructions for Hot Fix M46008

Linux for x64

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

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

M48003  updates  SAS Fraud Management Alert Generation Server 3.3
M53001  updates  SAS Fraud Management Common Macros 3.3
M47003  updates  SAS Fraud Management Mid-Tier 3.3
U90001  updates  SAS Fraud Management Multi Entity History DB Maintenance Macros 3.3
P82002  updates  SAS Fraud Management Reporting History DB Maintenance Macros 3.3
T31001  updates  SAS Fraud Management Reporting History ETL Server Macros 3.3
M49002  updates  SAS Fraud Management Scoring Engine 3.3
M50003  updates  SAS Fraud Management System of Record DB Maintenance Macros 3.3***
P60001  updates  SAS Fraud Management Transaction Extensions 3.3

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

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


Software Component Server M46001 HF1 M46002 HF2 M46003 HF3 M46004 HF4 M46005 HF5 M46006 HF6 M46007 HF7 M46008 HF8
SAS FM Alert Generation Server 3.3 AGS M48001 M48002 - - M48003 - - -
SAS FM Common Macros 3.3 Rules Server/AGS/JOSE M53001 - - - - - - -
SAS FM Mid-Tier 3.3 Midtier M47001 M47002 - - M47003 - - -
SAS FM Multi Entity History DB Maintenance Macros 3.3 JOSE - - - U90001 - - - -
SAS FM Reporting History DB Maintenance Macros 3.3 Rules Server/AGS/JOSE - P82001 - - - P82002 - -
SAS FM Reporting History ETL Server Macros 3.3 Rules Server/AGS - - T31001 - - - - -
SAS FM Scoring Engine 3.3 JOSE M49001 M49002 - - - - - -
SAS FM System of Record DB Maintenance Macros 3.3 AGS M50001 - - - - M50002 - M50003
SAS FM Transaction Extensions 3.3 Rules Server/AGS/JOSE - P60001 - - - - P60002 -

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.

The hot fix downloaded,, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of The hot fix installation process will extract the contents as needed.


  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.


  1. Install the hot fix:
    Hot Fix M46008 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 require updating on the machine. See SAS Note 44810 for more details.

    The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager 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 downloading, 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

    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.


  1. Update the Databases:

    Database updates are generally performed by the DBA. The instructions for each file should be reviewed before running each update.

    Create a "M46008pt" directory on your machine and unzip the contents of into that directory.

    Go to the M46008pt/Miscellaneous directory. Based on the table below, determine which files need to be run and copy those files to the appropriate database server.

    Vendor Database Hot fix File Instructions
    DB2 SOR HF2 sor_db2_upgrade_3.3.0.2.tar Installation Instructions for DB2_SOR updates
    DB2 MEH HF4 meh_db2_upgrade_3.3.0.4.tar Installation Instructions for DB2_MEH updates
    DB2 SOR HF6 sor_db2_upgrade_3.3.0.6.tar Installation Instructions for DB2_SOR updates

  2. (Step needed only if "SAS Fraud Management Mid-Tier" component was updated) 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, for example

        $ cd <SASHOME>/SASDeploymentManager/9.3
        $ ./

      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 M46008 on Linux for x64.

Copyright 2015 SAS Institute Inc. All Rights Reserved.