Hot fix T69004 addresses the issue(s) in SAS Compliance Solutions 6.3 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/T69.html#T69004
T69004 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
T67003 updates SAS Compliance Solutions Mid-Tier 6.3
T68004 updates SAS Compliance Solutions Server 6.3
T88002 updates SAS High-Performance Anti-Money Laundering Server 6.3
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, T69004pt.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 T69004pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of T69004pt.zip. The hot fix installation process will extract the contents as needed.
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 T69004pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.
Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.
The hot fix installation process generates the log file
<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.logfor 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.
For each product installed, click the link to be redirected to post-installation instructions.
T67003 updates SAS Compliance Solutions Mid-Tier 6.3
T68004 updates SAS Compliance Solutions Server 6.3
T88002 updates SAS High-Performance Anti-Money Laundering Server 6.3
T67003 updates SAS Compliance Solutions Mid-Tier 6.3
Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
1. Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.4
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 SAS Compliance Solutions Mid 6.3 as the Web Application to Rebuild
7. Verify the information on the Summary screen and select Start
8. Select Finish when the deployment is complete
This process will update the SAS Compliance Solutions Mid 6.3 ear in
<SASCONFIGDIR>/Web/StagingA backup of the original ear file will be placed in the directory
<SASCONFIGDIR>/Web/Staging/Backup
9. Exit the SAS Deployment Manager 9.4
Re-deploy Web Application
1. Restart all SAS sessions, daemons, spawners and servers.
2. Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:
<SASHOME>/SASDeploymentManager/9.4
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 Compliance Solutions Mid 6.3 as the Web Application to Deploy
9. Verify the information on the Summary screen and select Start
10. Select Finish and exit the SAS Deployment Manager when the deployment is complete
T68004 updates SAS Compliance Solutions Server 6.3
Important Note:
For ease of completion of post-installation tasks, you can export the following:
# This should be the path that SAS was installed to. export SASROOT=/install/SASHome/SASFoundation/9.4This hot fix contains code to update watchlist import and processing capabilities that requires making updates to the Compliance Solutions database using the provided data definition language (DDL) files. Several tables, including FCFCORE.FSC_EXT_PARTY_ACCOUNT_DIM, FCFCORE.FSC_PARTY_DIM, FCFCORE.FSC_ENTITY_WATCH_LIST_DIM, and FCFCORE.FSC_ADDRESS_DIM, need changes made to the size of match code fields. A new table, FCFCORE.FSC_TRANSPORT_WATCH_LIST_DIM, must be created. To accomplish this, you will need to execute some DDL scripts, depending on which database management system you use.If you do not use the default FCFCORE, FCFKC, and FCFBU1 user/schema names, you will need to edit the scripts to change the schema names to the appropriate values, before they are executed.# This should be the SAS Configuration Path and Level export FCFROOT=/install/config/Lev1/Applications/SASComplianceSolutions
For DB2:
Using the DB2 command line processor, execute the following commands:
db2 connect toFor Oracle:user using db2 –tf $SASROOT/antimnycmn/sasmisc/ddl/db2/db2_core_wl.sql db2 –tf $SASROOT/antimnycmn/sasmisc/ddl/db2/db2__bu1_wl.sql db2 –tf $SASROOT/antimnycmn/sasmisc/ddl/db2/db2_create_grants.sql –r $SASROOT/antimnycmn/sasmisc/ddl/db2/db2_grants.sql db2 –tf $SASROOT/antimnycmn/sasmisc/ddl/db2/db2_grants.sql
Using the SQLPlus command line utility, execute the following commands:
sqlplus system/password@aml_sid @$SASROOT/antimnycmn/sasmisc/ddl/oracle/oracle_core_wl.sql sqlplus system/password@aml_sid @$SASROOT/antimnycmn/sasmisc/ddl/oracle/oracle_create_grants.sql sqlplus system/password@aml_sid @$SASROOT/antimnycmn/sasmisc/ddl/oracle/oracle_grants.sql sqlplus system/password@aml_sid @$SASROOT/antimnycmn/sasmisc/ddl/oracle/oracle_bu_wl.sql
For SQLServer:
In the $SASROOT/antimnycmn/sasmisc/ddl/sqlserver folder, change the first line of the following two files, so that the “USE [LOCALDB]” command uses your SQLServer database name, for example “USE [MYDB]”.
Using the SQLCMD command-line utility, execute the following commands:
sqlcmd –U sa –P password –i $SASROOT/antimnycmn/sasmisc/ddl/sqlserver/sqlserver_core_wl.sql sqlcmd –U sa –P password –i $SASROOT/antimnycmn/sasmisc/ddl/sqlserver/sqlserver_bu1_wl.sqlFor Teradata:
NOTE: changes in teradata_core_wl.sql will drop three FSC_PARTY_DIM indexes then recreate them after the ALTER TABLE statements are made. If you have a large number of party rows in your database, this could take a while.
Using SQL Assistant or BTEQ, execute the following scripts:
$SASROOT/antimnycmn/sasmisc/ddl/teradata/teradata_core_wl.sql $SASROOT/antimnycmn/sasmisc/ddl/teradata/teradata_bu1_wl.sqlTo install language files for Hong Kong and Taiwan into the Compliance Solutions 6.3 Server, execute the following commands:
cp $SASROOT/antimnycmn/sasmisc/notify_manager_messages_zt.sas $FCFROOT/custom/source cp $SASROOT/antimnycmn/sasmisc/notify_manager_messages_zx.sas $FCFROOT/custom/source cp $SASROOT/antimnycmn/sasmisc/send_alert_reminder_messages_zt.sas $FCFROOT/custom/source cp $SASROOT/antimnycmn/sasmisc/send_alert_reminder_messages_zx.sas $FCFROOT/custom/source
T88002 updates SAS High-Performance Anti-Money Laundering Server 6.3
NONE
This completes the installation of hot fix T69004 on Windows for x64.
Copyright 2016 SAS Institute Inc. All Rights Reserved.