Installation Instructions for Hot Fix Y11011

Linux for x64

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

https://tshf.sas.com/techsup/download/hotfix/HF2/Y11.html#Y11011

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

Y12010  updates  SAS Fraud Management Mid-Tier 4.2_M1***
Y80003  updates  SAS Fraud Management Reporting History DB Maintenance Macros 4.2_M1
Y13007  updates  SAS Fraud Management Scoring Engine 4.2_M1
Y79004  updates  SAS Fraud Management System of Record DB Maintenance Macros 4.2_M1***

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

HOT FIX COMPONENT HISTORY

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:
   

   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. Download Oracle JDBC Driver for JDK 7:

   For Oracle 11g environments, the ojdbc7.jar is required. If not already installed, download the jar file from the Oracle website and add it to the <ORACLE_DIR>/client_1/jdbc/lib directory on the ODE server(s).

INSTALLATION

1. 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:

   1. The <SASHOME> directory
   2. The <CONFIGDIR> directory
   3. Each database that will be updated by this hot fix. Review the POST-INSTALLATION INSTRUCTIONS 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.

2. Stop Servers:  The ODE server(s) must be stopped via the command line before installing this hot fix. In addition, all batch jobs running against the SAS FM databases should be paused.
3. Important:  Install this hot fix using the same userid who performed the initial software installation.
4. Install the hot fix using the SAS Deployment Manager (SDM):
   

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

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

   Note:   If this hot fix has been previously installed, use the -reinstallhotfix option when running the SDM. If friendly fixes have been previously installed, use the -alwaysoverwrite option.

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

POST-INSTALLATION INSTRUCTIONS

1. Update the Databases:
   

   IMPORTANT: Database updates may not be required for every hot fix. Review this section carefully to determine if updates are needed.
   IMPORTANT: Files 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).

   Vendor	Database	Hot Fix	File	Instructions
   DB2	SOR	HF1	sor_db2_upgrade_4.2.1.1.tar.gz	SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (1)
   Oracle	SOR	HF1	sor_oracle_upgrade_4.2.1.1.tar.gz	SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (1)
   Oracle	SOR	HF5	sor_oracle_upgrade_4.2.1.5.tar.gz	SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (2)

   2. Create a "Y11011pt" directory on your machine and unzip the contents of Y11011pt.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. Update ODE Configuration Files:

   IMPORTANT: If your system was at HF3 or higher before this hot fix install, SKIP this section and proceed to Step 3.
   IMPORTANT: If any custom changes were made to the files overwritten in this step, these changes must be merged into the new files.

   1. Backup the following directories on each ODE server:
      • <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/bin
      • <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/etc
   2. Copy all the files from the <SASHOME>/SASFraudManagementScoringEngine/4.2/Config/bin directory to the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/bin directory.
   3. Copy all the files from the <SASHOME>/SASFraudManagementScoringEngine/4.2/Config/etc directory to the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/etc directory.
   4. Edit the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/etc/txn.properties file to add this line:

      DECK_OFFSET = 0

      immediately below this line:

      DECK = file:///<file-path>

   5. Delete the following files from these two directories: <SASHOME>/SASFraudManagementScoringEngine/4.2/Config/bin and <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.2/<Auth-Domain>/meh/ose/Server/bin.
      • sas_internal_meh.sh
      • sas_internal_update.sh

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

4. Start Servers:  Start the ODE server(s) via the command line. Start any batch jobs that were paused before the installation.
5. Create a final Deployment Registry report:
   

   Run a new SAS Depployment 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 Y11011 on Linux for x64.


Copyright 2016 SAS Institute Inc. All Rights Reserved.