<HTML><HEAD><META content="IE=5.0000" http-equiv="X-UA-Compatible"> <TITLE>Installation instructions for hot fix A2W006 on Linux for x64 </TITLE> <META http-equiv="Content-Type" content="text/html; charset=windows-1252"> <META name="GENERATOR" content="MSHTML 10.00.9200.17116"> <style> table, th, td { border: 1px solid black; border-collapse: collapse; } th, td { padding: 5px; text-align: left; } </style> </head> <body> <h2> Installation Instructions for Hot Fix A2W006 </h2> <h3> Linux for x64 </h3> <p><br> Hot fix <b>A2W006</b> addresses the issue(s) in <b><i>SAS Fraud Management 4.4</i></b> as documented in the <i>Issue(s) Addressed</i> section of the hot fix download page: <blockquote> <a href="http://ftp.sas.com/techsup/download/hotfix/HF2/A2W.html#A2W006">http://ftp.sas.com/techsup/download/hotfix/HF2/A2W.html#A2W006</a> </blockquote> <p><br> <b>A2W006</b> is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.<br><br> <blockquote> <b>A3B004</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Common Macros 4.4<FONT color="red"></FONT></b><br> <b>A2Y006</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Decision Engine 4.4<FONT color="red">***</FONT></b><br> <b>A2X006</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Mid-Tier 4.4<FONT color="red">***</FONT></b><br> <b>A9L001</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Multi Entity History DB Maintenance Macros 4.4<FONT color="red"></FONT></b><br> <b>A3C004</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Reporting History ETL Server Macros 4.4<FONT color="red"></FONT></b><br> <b>A3E002</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Scoring Engine for zOS 4.4<FONT color="red"></FONT></b><br> <b>A3D004</b> &nbsp;updates &nbsp;<b>SAS Fraud Management System of Record DB Maintenance Macros 4.4<FONT color="red"></FONT></b><br> <b>A3A007</b> &nbsp;updates &nbsp;<b>SAS Fraud Management Transaction Extensions 4.4<FONT color="red">***</FONT></b><br> <b>A2Z005</b> &nbsp;updates &nbsp;<b>SAS Fraud Transactional Analysis Engine 4.4<FONT color="red">***</FONT></b><br> <P><B><FONT color="red">***</FONT></B> member hot fixes that have been updated since the previously released hot fix (A2W005)</P> </blockquote> </blockquote> <br> See <a href="http://ftp.sas.com/techsup/download/hotfix/faq.html#container_define" target="hffaq">What is a container hot fix?</a> in the Hot Fix FAQ for more information about container hot fixes. <P><BR><H4>HOT FIX COMPONENT HISTORY</H4></P> <table> <tr style="background: #e5dfdf"> <th>Software Component</th> <th>Server</th> <th>A2W001 HF1</th> <th>A2W002 HF2</th> <th>A2W003 HF3</th> <th>A2W004 HF4</th> <th>A2W005 HF5</th> <th>A2W006 HF6</th> </tr><tr> <td>SAS FM Common Macros 4.4</td> <td>Batch Server (Unix)</td> <td>A3B001</td> <td>A3B002</td> <td>A3B003</td> <td>A3B004</td> <td>-</td> <td>-</td> </tr><tr> <td>SAS FM Scoring Engine 4.4</td> <td>Decision Server</td> <td>A2Y001</td> <td>A2Y002</td> <td>A2Y003</td> <td>A2Y004</td> <td>A2Y005</td> <td>A2Y006</td> </tr><tr> <td>SAS FM Mid-Tier 4.4</td> <td>Midtier</td> <td>A2X001</td> <td>A2X002</td> <td>A2X003</td> <td>A2X004</td> <td>A2X005</td> <td>A2X006</td> </tr><tr> <td>SAS FM Multi Entity History DB Maintenance Macros 4.4</td> <td>Batch Server (Unix)</td> <td>-</td> <td>-</td> <td>A9L001</td> <td>-</td> <td>-</td> <td>-</td> </tr><tr> <td>SAS FM Reporting History ETL Server Macros 4.4</td> <td>Batch Server (Unix)</td> <td>A3C001</td> <td>A3C002</td> <td>A3C003</td> <td>A3C004</td> <td>-</td> <td>-</td> </tr><tr> <td>SAS FM Scoring Engine for zOS 4.4</td> <td>Decision Server</td> <td>A3E001</td> <td>A3E002</td> <td>-</td> <td>-</td> <td>-</td> <td>-</td> </tr><tr> <td>SAS FM System of Record DB Maintenance Macros 4.4</td> <td>Batch Server (Unix)</td> <td>A3D001</td> <td>A3D002</td> <td>A3D003</td> <td>-</td> <td>A3D004</td> <td>-</td> </tr><tr> <td>SAS FM Transaction Extensions 4.4</td> <td>Decision Server (Unix), Rules Server (Unix), Scoring Server (Z64)</td> <td>A3A001</td> <td>A3A002</td> <td>A3A003</td> <td>A3A004</td> <td>A3A006</td> <td>A3A007</td> </tr><tr> <td>SAS Fraud Transactional Analysis Engine 4.4</td> <td>Transaction Analysis Server</td> <td>A2Z001</td> <td>A2Z002</td> <td>A2Z003</td> <td>A2Z004</td> <td>-</td> <td>A2Z005</td> </tr> </table> <p><br> <h4>IMPORTANT NOTE</h4> <p> 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 *<b>not</b>* 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. <P><BR><H4>PRE-INSTALLATION INSTRUCTIONS</H4></P> <OL> <LI><B>Create a Deployment Registry report on each server:</B><BR> <P>Before applying this hot fix, follow the instructions in <A href="http://support.sas.com/kb/35/968.html" target="35968">SAS Note 35968</A> to generate a SAS Deployment Registry report. </P> Commands to create the report: <OL type="a"> <LI>cd <I>&lt;SASHome&gt;</I>/deploymntreg</LI> <LI><I>&lt;JAVA_HOME&gt;</I>/bin/java -jar sas.tools.viewregistry.jar<br></LI> </OL> <P>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. </P> </LI> <LI><B>Backups:</B>&nbsp; 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. <P>Backup the following on each Server:</P> <OL type="a"> <LI><I>&lt;SASHOME&gt;</I> directory </LI> <LI><I>&lt;CONFIGDIR&gt;</I> directory </LI> <LI>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. </LI> </OL> <P>For a detailed list of updated files, see the <A href= "../lax/A2W006la_manifest.html" target="manifest">hot fix manifest</A>.&nbsp; NOTE: The manifest is cumulative for all hot fixes for this release.</P> </LI> <P></P> <LI><B>Stop Servers:</B> <P></P> <OL type="a"> <LI>Stop the OnDemand Decision Engine (ODE) server(s). <BR />$ cd <I>&lt;CONFIGDIR&gt;</I>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin <BR />$ ./ose.sh stop </LI> <P></P> <LI>Stop the Transactional Analysis Server (TAS). <BR />$ cd <I>&lt;CONFIGDIR&gt;</I>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/bin <BR />$ ./tas.sh stop </LI> <P></P> <LI>All batch jobs running against the SAS FM databases should be paused.</LI> </OL> </LI> </LI> </OL> <P><BR><H4>SERVER INSTALLATION</H4></P> <OL> <P></P> <LI><B><I>Important:</I></B>&nbsp; Install this hot fix using the same userid who performed the initial software installation. </LI> <P></P> <LI><B>Install the hot fix using the SAS Deployment Manager (SDM):</B><BR> <P>Hot Fix A2W006 must be installed on each machine where the updated components of the product, listed above, are installed. </P> <P>The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM will search in the <I>&lt;SASHOME&gt;/InstallMisc/HotFixes/New</I> 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 &nbsp; A2W006pt.zip into the selected directory. The hot fix installation process will extract the contents as needed. </P> <P>After copying A2W006pt.zip, follow the instructions for applying hot fixes in the <B><A href="http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/default/user.pdf" target="sdm94user">SAS Deployment Wizard and SAS Deployment Manager 9.4: User s Guide</A></B>. </P> <P>For example:</P> <OL type="a"> <LI>Set the DISPLAY environment variable, for example <BLOCKQUOTE>$ export DISPLAY=&lt;displayname&gt;:0 </BLOCKQUOTE> </LI> <P></P> <LI><P>From the SASDeploymentManager directory execute <B><I>sasdm.sh</I></B></P> <BLOCKQUOTE>$ cd &lt;SASHOME&gt;/SASDeploymentManager/9.4<BR> $ ./sasdm.sh </BLOCKQUOTE> </LI> </OL> <P><B><I>Notes:</I></B> <UL> <LI>If this hot fix has been previously installed, use the <i>-reinstallhotfix</i> option when running the SDM.</LI> <LI>If friendly fixes have been previously installed or manual file updates have been made in <I>&lt;SASHOME&gt;</I>, use the <i>-alwaysoverwrite</i> option to ensure that those files are overwritten by the SDM.</P></LI> </UL> <P>The hot fix installation process generates the log file <BLOCKQUOTE><B>&lt;!SASHOME&gt;/InstallMisc/InstallLogs/IT_date-and-time-stamp.log</B> </BLOCKQUOTE>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. </P> <P>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 <I>&lt;!SASHOME&gt;/InstallMisc/InstallLogs</I> directory. There is one postexec log for each  member hot fix applied (member hot fixes are listed at the top of these instructions).</P> </LI> </OL> <p> <!-------------------- POST-INSTALLATION : SERVER TIER ------------------------> <P><BR><H4><A name="Back">POST-INSTALLATION INSTRUCTIONS: SERVER TIER</A></H4></P> <OL> <!-- START CUSTOM Steps Section --> <P>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.</P> <table> <tr style="background: #e5dfdf"> <th>Starting Version</th> <th>Steps</th> </tr> <tr style="background: #ffffff"> <td valign="top">4.4M0<br />(No Hot Fix)</td> <td><H3>Steps for upgrade from 4.4M0 to HF6</H3> <OL> <LI><B>Configure the Transactional Analysis Server (TAS):</B> <P></P> <OL type="A"> <LI>On the TAS host server, back up the contents of the /bin and /etc directories under the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis directory.</LI> <P></P> <LI>Copy these scripts: <UL> <LI>esrt.sh</LI> <LI>esrt_tests.sh</LI> <LI>functions.sh</LI> <LI>tas.sh</LI> <LI>tas-esc.sh</LI> <LI>wipeout.sh</LI> </UL> <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/bin </LI> <P></P> <LI>Merge changes <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig <br />Into: <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc/tas.properties</P> </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Configuration Files:</B> <P><b><i> IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc directory.</LI> <P></P> <LI> Copy all files ending with '.xml': <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc </LI> </OL> <P></P> </LI> <LI><B>Update ODE Property Files:</B> <P></P> <OL type="A"> <LI>Copy ose.properties.orig: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc <P>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. </P> </LI> <LI>Copy txn.properties.orig: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc <P>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. </P> </P> </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Scripts:</B> <P><b><i> IMPORTANT: If you have customized any of the scripts copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin directory.</LI> <P></P> <LI> Copy all the files ending in '.sh': <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin </LI> </OL> </LI> <P></P> <LI><B>Create the ODE 'failed' Directory:</B> <P></P> <P> On each ODE server, create a directory named <i>failed</i> under each <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<i>&lt;n&gt;</i> 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. </P> For example: <BLOCKQUOTE> $ cd <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server1<BR> $ mkdir failed <BR> $ chmod 775 failed </BLOCKQUOTE> </LI> <P></P> </OL> </td> </tr> <tr style="background: #f8f4f4"> <td valign="top">4.4M0 HF1 </td> <td><H3>Steps for upgrade from HF1 to HF6</H3> <OL> <LI><B>Update Transactional Analysis Server (TAS) files:</B> <P></P> <OL type="A"> <P></P> <LI>On the TAS host server, copy these scripts: <UL> <LI>esrt.sh</LI> <LI>esrt_tests.sh</LI> <LI>wipeout.sh</LI> </UL> <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/bin </LI> <P></P> <LI>Merge changes <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig. <br />Into: <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc/tas.properties.</P> </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Configuration Files:</B> <P><b><i> IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc directory.</LI> <P></P> <LI> Copy all files ending with '.xml': <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc </LI> </OL> <P></P> </LI> <LI><B>Update ODE Property Files:</B> <P></P> <OL type="A"> <LI>Copy ose.properties.orig: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc <P>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. </P> </LI> <LI>Copy txn.properties.orig: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc <P>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. </P> </P> </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Scripts:</B> <P><b><i> IMPORTANT: If you have customized any of the scripts copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin directory.</LI> <P></P> <LI> Copy all the files ending in '.sh': <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin </LI> </OL> </LI> <P></P> <LI><B>Create the ODE 'failed' Directory:</B> <P></P> <P> On each ODE server, create a directory named <i>failed</i> under each <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<i>&lt;n&gt;</i> 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. </P> For example: <BLOCKQUOTE> $ cd <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server1<BR> $ mkdir failed <BR> $ chmod 775 failed </BLOCKQUOTE> </LI> <P></P> </OL> </td> </tr> <tr style="background: #ffffff"> <td valign="top">4.4M0 HF2 </td> <td><H3>Steps for upgrade from HF2 to HF6</H3> <OL> <P></P> <LI><B>Update the Tranaction Analysis Server (TAS) Configuration</B> <P><b><i> IMPORTANT: If you have customized the tas.properties file, you must merge your updates into the new version.</i></B> </P> <OL type="A"> <LI>On the TAS server, back up the tas.properties file in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc directory.</LI> <P></P> <LI> Merge changes <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig <br />Into: <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc/tas.properties </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Configuration Files:</B> <P><b><i> IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the actions.xml, ose.xml, post-score-actions.xml and txn.xml files in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc directory.</LI> <P></P> <LI> On each ODE server, copy these files: <UL> <LI>actions.xml</LI> <LI>ose.xml</LI> <LI>post-score-actions.xml</LI> <LI>txn.xml</LI> </UL> <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc </LI> </OL> <P></P> </LI> <LI><B>Update ODE Server Script:</B> <P><b><i> IMPORTANT: If you have customized this script, you must merge your updates into the new version.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the ose.sh file in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin directory.</LI> <P></P> <LI> Copy the ose.sh file: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin </LI> <P></P> </OL> </LI> <P></P> </OL> </td> </tr> <tr style="background: #f8f4f4"> <td valign="top">4.4M0 HF3 </td> <td><H3>Steps for upgrade from HF3 to HF6</H3> <OL> <P></P> <LI><B>Update the Tranaction Analysis Server (TAS) Configuration</B> <P><b><i> IMPORTANT: If you have customized the tas.properties file, you must merge your updates into the new version.</i></B> </P> <OL type="A"> <LI>On the TAS server, back up the tas.properties file in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc directory.</LI> <P></P> <LI> Merge changes <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudTransactionalAnalysisEngine/4.4/Config/etc/tas.properties.orig <br />Into: <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/etc/tas.properties </LI> </OL> </LI> <P></P> <LI><B>Update ODE Server Configuration Files:</B> <P><b><i> IMPORTANT: If you have customized any of the files copied in this step, you must merge your updates into the new versions.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the actions.xml, ose.xml, post-score-actions.xml and txn.xml files in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc directory.</LI> <P></P> <LI> On each ODE server, copy these files: <UL> <LI>actions.xml</LI> <LI>ose.xml</LI> <LI>post-score-actions.xml</LI> <LI>txn.xml</LI> </UL> <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/etc <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/etc </LI> </OL> <P></P> </LI> <P></P> <P></P> <LI><B>Update ODE Server Script:</B> <P><b><i> IMPORTANT: If you have customized this script, you must merge your updates into the new version.</i></B> </P> <OL type="A"> <LI>On each ODE server, back up the ose.sh file in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin directory.</LI> <P></P> <LI> Copy the ose.sh file: <br />From: <i>&lt;SASHOME&gt;</i>/SASFraudManagementDecisionEngine/4.4/Config/bin <br />To: &nbsp; <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>/bin </LI> </OL> <P></P> </LI> <P></P> </OL> </td> </tr> <tr style="background: #ffffff"> <td valign="top">4.4M0 HF4 </td> <td><H3>Steps for upgrade from HF4 to HF6</H3> <P></P> There are no custom steps for the server tier to upgrade from HF4 to HF6. </td> </tr> <tr style="background: #f8f4f4"> <td valign="top">4.4M0 HF5 </td> <td><H3>Steps for upgrade from HF5 to HF6</H3> <P></P> There are no custom steps for the server tier to upgrade from HF4 to HF6. </td> </tr></table> <P></P> </OL> <!-------------------- POST-INSTALLATION : DATA TIER ------------------------> <P><BR><H4><A name="Back">POST-INSTALLATION INSTRUCTIONS: DATA TIER</A></H4></P> <OL> <P>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. </P> <P>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. <P> 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: <A href="../44M0HF4_SASFM_DBMS_Package_Configuration_Instructions.pdf" target="new">44M0HF4 SAS Fraud Management DBMS Package Configuration Instructions</A> </P> </P> <LI><B>Update the Databases to 4.4M0 HF3 level:</B><BR> <P> <B><i>IMPORTANT: Database updates that have been run during previous hot fix installations should NOT be run a second time.</i></B> </P> <OL type="A"> <LI>Select the database update files to run. If there are no files that need to be run, skip to Step 2. <P>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. </P> <UL> <LI>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.</LI> <LI>Run only the files for your database vendor.</LI> <LI>Database updates are generally performed by the database administrator (DBA).</LI> </UL> <P></P> </LI> <P></P> <table> <tr style="background: #e5dfdf"> <th>Vendor</th> <th>Database</th> <th>Hot fix</th> <th>File</th> <th>Instructions</th> </tr><tr> <td>DB2</td> <td>SOR</td> <td>HF1</td> <td>sor_db2_upgrade_4.4.0.1.tar.gz</td> <td><A href="../R4.4_DB2_SOR_patch_4.4.0.1_Upgrade_Instructions.pdf" target="new">SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (1)</A></td> </tr><tr> <td>DB2</td> <td>SOR</td> <td>HF2</td> <td>sor_db2_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_DB2_SOR_patch_4.4.0.2_Upgrade_Instructions.pdf" target="new">SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (2)</A></td> </tr><tr> <td>DB2</td> <td>SOR</td> <td>HF3</td> <td>sor_db2_upgrade_4.4.0.3.tar.gz</td> <td><A href="../R4.4_DB2_SOR_patch_4.4.0.3_Upgrade_Instructions.pdf" target="new">SOR_DB2 updates: Installation Instructions for SOR_DB2 updates (3)</A></td> </tr><tr> <td>DB2</td> <td>TDR</td> <td>HF2</td> <td>tdr_db2_base_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_DB2_TDR_patch_4.4.0.2_NON-Partitioned_Upgrade_Instructions.pdf" target="new">TDR_DB2_NON-Partitioned updates: Installation Instructions for TDR_DB2_NON-Partitioned updates (1)</A></td> </tr><tr> <td>DB2</td> <td>TDR</td> <td>HF2</td> <td>tdr_db2_range_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_DB2_TDR_patch_4.4.0.2_Partitioned_Upgrade_Instructions.pdf" target="new">TDR_DB2_Partitioned updates: Installation Instructions for TDR_DB2_Partitioned updates (1)</A></td> </tr><tr> <td>Oracle</td> <td>MEH</td> <td>HF2</td> <td>meh_oracle_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_Oracle_MEH_patch_4.4.0.2_Upgrade_Instructions.pdf" target="new">MEH_Oracle updates: Installation Instructions for MEH_Oracle updates (1)</A></td> </tr><tr> <td>Oracle</td> <td>MEH</td> <td>HF3</td> <td>meh_oracle_non_partitioned_upgrade_4.4.0.3.tar.gz</td> <td><A href="../R4.4_Oracle_MEH_patch_4.4.0.3_Upgrade_Instructions_NonPartitioned.pdf" target="new">MEH_Oracle_NON-Partitioned updates: Installation Instructions for MEH_Oracle_NON-Partitioned updates (2)</A></td> </tr><tr> <td>Oracle</td> <td>MEH</td> <td>HF3</td> <td>meh_oracle_partitioned_upgrade_4.4.0.3.tar.gz</td> <td><A href="../R4.4_Oracle_MEH_patch_4.4.0.3_Upgrade_Instructions_Partitioned.pdf" target="new">MEH_Oracle_Partitioned updates: Installation Instructions for MEH_Oracle_Partitioned updates (2)</A></td> </tr><tr> <td>Oracle</td> <td>SOR</td> <td>HF1</td> <td>sor_oracle_upgrade_4.4.0.1.tar.gz</td> <td><A href="../R4.4_Oracle_SOR_patch_4.4.0.1_Upgrade_Instructions.pdf" target="new">SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (1)</A></td> </tr><tr> <td>Oracle</td> <td>SOR</td> <td>HF2</td> <td>sor_oracle_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_Oracle_SOR_patch_4.4.0.2_Upgrade_Instructions.pdf" target="new">SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (2)</A></td> </tr><tr> <td>Oracle</td> <td>SOR</td> <td>HF3</td> <td>sor_oracle_upgrade_4.4.0.3.tar.gz</td> <td><A href="../R4.4_Oracle_SOR_patch_4.4.0.3_Upgrade_Instructions.pdf" target="new">SOR_Oracle updates: Installation Instructions for SOR_Oracle updates (3)</A></td> </tr><tr> <td>Oracle</td> <td>TDR</td> <td>HF2</td> <td>tdr_oracle_base_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_Oracle_TDR_patch_4.4.0.2_NON-Partitioned_Upgrade_Instructions.pdf" target="new">TDR_Oracle_NON-Partitioned updates: Installation Instructions for TDR_Oracle_NON-Partitioned updates (1)</A></td> </tr><tr> <td>Oracle</td> <td>TDR</td> <td>HF2</td> <td>tdr_oracle_range_upgrade_4.4.0.2.tar.gz</td> <td><A href="../R4.4_Oracle_TDR_patch_4.4.0.2_Partitioned_Upgrade_Instructions.pdf" target="new">TDR_Oracle_Partitioned updates: Installation Instructions for TDR_Oracle_Partitioned updates (1)</A></td> </tr> </table> <P></P> </LI> <P></P> <LI>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 <i>Miscellaneous</i> subdirectory </LI> <P></P> <LI>Copy the files to a location accessible by the DBA on the database server. Review all database update instructions carefully before running each update. </LI> </OL> <P></P> </LI> <P></P> <LI><B>Execute SAS Fraud Management DBMS Package to Update the Databases</B> <P><B><i>IMPORTANT: The SAS Fraud Management DBMS Package must be configured before completing this section. The configuration steps are described in this document:</i></b> <A href="../44M0HF4_SASFM_DBMS_Package_Configuration_Instructions.pdf" target="new">44M0HF4 SAS Fraud Management DBMS Package Configuration Instructions</A> </P> <P><B><i>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_<I>&lt;MEH|SOR|TDR&gt</I>;</I></B> </P> <P> <OL type="A"> <LI> 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. </P> <P> <table> <tr style="background: #e5dfdf"> <th>Vendor</th> <th>Database</th> <th>Hot fix</th> <th>Updates</th> </tr><tr> <td>DB2 and Oracle</td> <td>SOR</td> <td>HF4</td> <td>Remove support for O##</td> </tr><tr> <td>DB2 and Oracle</td> <td>TDR</td> <td>HF4</td> <td>Remove the FCM_<i>&lt;tabname&gt;</i>_OXX tables.</td> </tr><tr> <td>DB2</td> <td>MEH</td> <td>HF4</td> <td>Update the MEH_DELETE_DATA stored procedure.</td> </tr><tr> <td>DB2 and Oracle</td> <td>SOR</td> <td>HF5</td> <td>Add the new analyst.alert.alertInfoPanelDisplay property.</td> </tr><tr> <td>Oracle</td> <td>TDR</td> <td>HF5</td> <td>Update the GET_SIGNATURE stored procedure. </td> </tr><tr> <td>Oracle</td> <td>TDR</td> <td>HF6</td> <td>Add new index, NDX6_<i>&lt;tabname&gt;</i>, for the transaction tables.</td> </tr> </table> </LI> <P></P> <LI>Log on to the ODE Server as the SAS installation user.</LI> <P></P> <LI>Change to the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/dbms/bin directory. </LI> <P></P> <LI>(Optional) To preview the SQL for the changes that will be applied to each database, run the following commands: <BLOCKQUOTE> $ ./mehddl.sh preview <BR> $ ./sorddl.sh preview <BR> $ ./tdrddl.sh preview </BLOCKQUOTE> <LI>Run the database update scripts. Check each log for errors. By default, the logs are in <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/dbms/logs directory. <BLOCKQUOTE> $ ./mehddl.sh update <BR> $ ./sorddl.sh update <BR> $ ./tdrddl.sh update </BLOCKQUOTE> Notes: <UL> <LI>You can run all three <i>&lt;db&gt;</i>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. </LI> <LI> If a script fails with a checksum error, clear the checksums for the failed database: <BLOCKQUOTE> $ ./mehddl.sh clearCheckSums<BR> $ ./sorddl.sh clearCheckSums <BR> $ ./tdrddl.sh clearCheckSums </BLOCKQUOTE> </LI> <LI>You can update the logging level and log file location the database properties files located in the <i>&lt;CONFIGDIR&gt;</i>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/dbms/etc directory. </LI> </UL> </LI> </OL> </LI> </OL> <!-------------------- POST-INSTALLATION : MID TIER ------------------------> <P><BR><H4><A name="Back">POST-INSTALLATION INSTRUCTIONS: MID TIER</A></H4></P> <OL> <LI><B>Update the web application deployed to your application server:</B> <P><B><i>IMPORTANT: Perform this step only if "SAS Fraud Management Mid-Tier" component was updated by this hot fix.</i></B> </P> <OL type="A"> <LI>Re-build Web Applications <P>In order for this step to execute correctly, the Metadata Server must be running.</P> <P></P> <OL> <LI>Set the DISPLAY environment variable, for example <BLOCKQUOTE>$ export DISPLAY=&lt;displayname&gt;:0 </BLOCKQUOTE> </LI> <P></P> <LI>Invoke the SAS Deployment Manager 9.4 <P>From the SASDeploymentManager directory execute <B><I>sasdm.sh</I></B>, for example</P> <BLOCKQUOTE>$ cd &lt;SASHOME&gt;/SASDeploymentManager/9.4<BR>$ ./sasdm.sh </BLOCKQUOTE> </LI> <P></P> <LI>Select a language in the <I>Choose Language</I> box </LI> <P></P> <LI>Select Rebuild Web Applications </LI> <P></P> <LI>Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated </LI> <P></P> <LI>Specify Connection Information, including the <I>sasadm</I> User ID and Password </LI> <P></P> <LI>Select <B><I>SAS Fraud Management Mid-Tier</I></B> as the Web Application to Rebuild </LI> <P></P> <LI>Verify the information on the Summary screen and select Start </LI> <P></P> <LI>Select Finish when the deployment is complete </LI> </OL> <P></P> This process will update the Fraud Management ear in <I>&lt;CONFIGDIR&gt;/Lev1/Web/Staging</I>. A backup of the original ear file will be placed in the <B><I>Backup</I></B> directory. <P></P> </LI> <LI>Re-deploy Web Application <P></P> <P>In order for this step to execute correctly, the Metadata Server must be running.</P> <P></P> <OL> <LI>Set the DISPLAY environment variable, for example <BLOCKQUOTE>$ export DISPLAY=&lt;displayname&gt;:0 </BLOCKQUOTE> </LI> <P></P> <LI>Invoke the SAS Deployment Manager 9.4 <P>From the SASDeploymentManager directory execute <B><I>sasdm.sh</I></B>, for example</P> <BLOCKQUOTE>$ cd &lt;SASHOME&gt;/SASDeploymentManager/9.4<BR>$ ./sasdm.sh </BLOCKQUOTE> </LI> <P></P> <LI>Select a language in the <I>Choose Language</I> box </LI> <P></P> <LI>Select <I>Deploy Web Applications</I> </LI> <P></P> <LI>Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated </LI> <P></P> <LI>Specify Connection Information, including the <I>sasadm</I> User ID and Password </LI> </LI> <P></P> <LI>Check the <I>Allow the application server to stop</I> checkbox </LI> <P></P> <LI>Select <B><I>SAS Fraud Management Mid-Tier</I></B> as the Web Application to Deploy </LI> <P></P> <LI>Verify the information on the Summary screen and select Start </LI> <P></P> <LI>Select Finish when the deployment is complete </LI> </OL> <P>See <A href="http://support.sas.com/documentation/cdl/en/biwaag/65229/HTML/default/viewer.htm" target="webadmin">SAS 9.4 Intelligence Platform Middle-Tier Administration Guide</A> for more details on deploying Web Applications.</P> <P></P> </LI> </OL> <P></P> </OL> <!-------------------- POST-INSTALLATION: FINAL ------------------------> <P><BR><H4><A name="Back">POST-INSTALLATION: START SERVERS </A></H4></P> <OL> <LI><B>Redeploy Rules Files in SAS Fraud Management Web Application: </B> <P>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. </B> </LI> <P></P> <LI><B>Start Servers:</B> <P></P> <OL type="a"> <LI>Start the ODE server(s). Confirm there are no errors in the log. <BR />$ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/engine/Server<I>&lt;n&gt;</I>bin <BR />$ ./ose.sh start tail </LI> <P></P> <LI>Start the TAS server. Confirm there are no errors in the log. <BR />$ cd <CONFIGDIR>/Lev1/Applications/SASFraudManagement/4.4/<i>&lt;Auth-Domain&gt;</i>/analysis/bin <BR />$ ./tas.sh start tail </LI> <P></P> <LI>Start any batch jobs that were paused before the installation.</LI> </OL> </LI> </LI> <P></P> <LI><B>Create a final Deployment Registry report on each server:</B><BR> <P>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. </P><P> Please send a copy of the final Deployment Registry report to SAS Fraud Management support. </P> </LI> <P></P> </OL> <P><BR> This completes the installation of hot fix <b>A2W006</b> on <b>Linux for x64</b>. <br><br><br> Copyright 2017 SAS Institute Inc. All Rights Reserved. <br><br> </body> </html>