Hot fix K99001 addresses the issue(s) in SAS Financial Crimes Monitor Mid-Tier 3.1_M1 on Solaris for x64 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/K99.html#K99001
The hot fix downloaded, K99001pt.zip, contains the updated files required to address
the documented issues.
Do NOT extract the contents of K99001pt.zip. The hot fix installation process will extract
the contents as needed.
After downloading K99001pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.
The content of this hot fix is listed in the hot fix manifest.
Web application Update
This hot fix requires steps that will update the web application deployed to your application server.
Step 1: Stop the JBoss Server
1.1 Using the Instructions.html located in <SASConfig>/Lev1/Documents, review the section labeled "Web Application Server".
Located in that section are instructions for stopping the Web Application Server. An example of the command to shutdown SASServer8 on using JBoss is:
<JBOSSHOME>/bin/SASServer8.sh stop
Step 2: Backup the contents of the SAS Financial Crimes Monitor ear.
1.1 Make a copy of the SAS Financial Crimes Monitor ear that you have deployed. The ear is located in the JBoss install directory. Copy the following directory
to the temporary location of your choice:
<JBOSSHOME>/server/SASServer8/deploy_sas/sas.financialcrimesmonitor3.1.ear
Step 3: Re-build Web Applications
In order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory launch sasdm.sh. The default installation path for the SAS Deployment Manager is
SASHOME/SASDeploymentManager/9.3
1.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select SAS Financial Crimes Monitor Mid-Tier as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
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.
Step 4: Copy the WEB-INF/lib/sas.sso.fcmserver.jar file
1.1 Locate the exploded ear directory for SAS Financial Crimes Monitor in the configuration directory:
<CONFIGDIR>/Lev1/Web/Staging/exploded/sas.financialcrimesmonitor3.1.ear/sas.sso.fcmserver.war/WEB-INF/lib
1.2 Copy the sas.sso.fcmserver.jar file from the exploded ear directory (above) to the SAS Financial Crimes Monitor deployment within the JBoss Web Application Server. For example, copy
<CONFIGDIR>/Lev1/Web/Staging/exploded/sas.financialcrimesmonitor3.1.ear/sas.sso.fcmserver.war /WEB-INF/lib/
to
<JBOSSHOME>/server/SASServer8/deploy_sas/sas.financialcrimesmonitor3.1.ear/sas.sso.fcmserver.war/WEB-INF/lib/
Step 5: Delete the tmp and work directories in SASServer8
1.1 Delete the tmp and work directories in SASServer8
rm -rf <JBOSSHOME>/server/SASServer8/tmp
rm -rf <JBOSSHOME>/server/SASServer8/work
Step 6: Restart the JBoss Server
1.1 Using the Instructions.html located in <SASConfig>/Lev1/Documents, review the section labeled "Web Application Server". Review the section "Starting Your JBoss Web Application Servers". An example of the command to start SASServer8 on using JBoss is:
<JBOSSHOME>/bin/SASServer8.sh start
This completes the installation of hot fix K99001 on Solaris for x64.