Installation Instructions for Hot Fix R38002

64-bit Enabled Solaris

Hot fix R38002 addresses the issue(s) in SAS Financial Crimes Monitor 6.2 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/R38.html#R38002

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

R39002  updates  SAS Financial Crimes Monitor Help and Documentation 6.2
R34002  updates  SAS Financial Crimes Monitor Mid-Tier 6.2
R35003  updates  SAS Financial Crimes Monitor Server 6.2

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, R38002pt.zip, 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 R38002pt.zip on each machine or save it in a network location that is accessible to all machines.

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

IMPORTANT NOTES

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.

INSTALLATION

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 R38002pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

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.

POST-INSTALLATION INSTRUCTIONS

Note that these instructions provide example filenames and directory names based on a Unix deployment; if your deployment is to a different host OS please make the appropriate adjustments.

Web application Update

This hot fix requires steps that will update the web application deployed to your application server.

1. Make sure SASServer8_1 is Stopped
   During the installation you should have stopped the SAS servers. As a result SASServer8_1 should be stopped. If not, you need to stop SASServer8_1. For information about stopping and restarting the server, depending on your operating system, see Chapter 6 “Operating Your Servers” in SAS 9.4 Intelligence Platform: System Administration Guide.

2. Move the current contents of the SAS Financial Crimes Monitor war
   This step allows you to keep a backup copy of any local changes you have made to the war and allows you to roll back changes if needed. Move the following directory and it's contents to a location outside of the sas_webapps path:

   <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer8_1/sas_webapps/sas.sso.fcmserver.war

   ** Note: The configuration directory, <CONFIGDIR> is described in the section, “Overview of the Configuration Directory Structure” in the SAS 9.4 Intelligence Platform: System Administration Guide.

   **Note: If you have modified FCM config files, such as those for advanced search/disposition, these changes will be reapplied after the web application gets re-built.

   ** Note: You may want to rename sas.sso.fcmserver.war to something like sas.sso.fcmserver.war.backup to make it clear that it is a backup file.

3. Re-build Web Applications
   This process will update the SAS Financial Crimes Monitor Mid-Tier ear in

   <CONFIGDIR>/Lev1/Web/Staging

   A backup of the original ear file will be placed in the Backup directory

   <CONFIGDIR>/Lev1/Web/Staging/Backup

   In order for this step to execute correctly, the Metadata Server must be running.
   **Note: SDM will start it for you if it is not running.

   1. Invoke the SAS Deployment Manager 9.4
      From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
      

      <SASHOME>/SASDeploymentManager/9.4
      

      **Note: <SASHOME> is defined in Chapter 1 of the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide

   2. Select a language in the Choose Language box
   3. Select Rebuild Web Applications
   4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
   5. Specify Connection Information, including the sasadm User ID and Password
   6. Select Financial Crimes Monitor 6.2 and select Next
   7. Verify the information on the Summary screen and select Start
   8. Select Finish when the deployment is complete

4. Copy files and directories from the exploded ear directory to the SAS Financial Crimes Monitor deployment area.
   
   1. Locate sas.sso.fcmserver.war in the exploded war directory for SAS Financial Crimes Monitor Server:

      <CONFIGDIR>/Lev1/Web/Staging/exploded/sas.financialcrimesmonitor6.2.ear/sas.sso.fcmserver.war ********

   2. Copy the sas.sso.fcmserver.war from the exploded ear directory (above) to the SAS Financial Crimes Monitor Server deployment within SASServer8.

      For example, copy

      sas.sso.fcmserver.war

      from
      <CONFIGDIR>/Lev1/Web/Staging/exploded/sas.financialcrimesmonitor6.2.ear
      to
      <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer8_1/sas_webapps
      

5. Delete the work directory in SASServer8_1
   rm -rf <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer8_1/work

6. Delete the contents of the temp directory in SASServer8_1
   rm -rf <CONFIGDIR>/Lev1/Web/WebAppServer/SASServer8_1/temp/*

7. Clear your browser cache
   Please follow the instructions at the following link to clear your browser cache http://java.com/en/download/help/webcache.xml

8. Reapply any local changes
   In step 2 you moved your old contents of the SAS Financial Crimes Monitor war to a safe location. That war included any modifications you may have made to FCM config files. You now need to copy those changes from your old war directory to the new war directory.

9. Restart SAS Servers
   For information about stopping and restarting the server, depending on your operating system, see Chapter 6 “Operating Your Servers” in SAS 9.4 Intelligence Platform: System Administration Guide.

For each product installed, click the link to be redirected to post-installation instructions.

R39002  updates  SAS Financial Crimes Monitor Help and Documentation 6.2
R34002  updates  SAS Financial Crimes Monitor Mid-Tier 6.2
R35003  updates  SAS Financial Crimes Monitor Server 6.2

R39002  updates  SAS Financial Crimes Monitor Help and Documentation 6.2

NONE

R34002  updates  SAS Financial Crimes Monitor Mid-Tier 6.2

NONE

R35003  updates  SAS Financial Crimes Monitor Server 6.2

NONE

This completes the installation of hot fix R38002 on 64-bit Enabled Solaris.

Copyright 2017 SAS Institute Inc. All Rights Reserved.