Installation instructions for hot fix A1I002 on 64-bit Enabled Solaris

Installation Instructions for Hot Fix A1I002

64-bit Enabled Solaris

Hot fix A1I002 addresses the issue(s) in SAS Compliance Solutions 6.3_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/A1I.html#A1I002

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

A1G001 updates SAS Compliance Solutions Mid-Tier 6.3_M1
A1H002 updates SAS Compliance Solutions Server 6.3_M1
A2K001 updates SAS High-Performance Anti-Money Laundering Server 6.3_M1

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

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

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

IMPORTANT NOTES

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.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
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.

INSTALLATION

Hot Fix A1I002 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of SAS Compliance Solutions 6.3_M1 require updating on the machine. See SAS Note 44810 for more details.

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

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

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

A1G001 updates SAS Compliance Solutions Mid-Tier 6.3_M1
A1H002 updates SAS Compliance Solutions Server 6.3_M1
A2K001 updates SAS High-Performance Anti-Money Laundering Server 6.3_M1

A1G001 updates SAS Compliance Solutions Mid-Tier 6.3_M1

This hot fix requires that the WebApps be rebuilt and redeployed. Use the following steps to perform this post-installation task:

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/Staging
A 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

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

Update UI definitions

Copy the file $SASHOME/SASComplianceSolutionsMidTier/6.3/deploy/uidef/aml-alert-details-01.xml.orig
to
$SASCONFIG/Web/Applications/SASComplianceSolutions/install/uidef/aml-alert-details-01.xml.
Edit the file and globally search and replace:
@fcf.software.component.name@ with Compliance Solutions Mid 6.3
@war.context.name@ with SASComplianceSolutionsMid
Log into the Mid-Tier Web Application as the installation or administration user.
On the Menu bar, choose Administration->UI Definitions.
For the field ‘UI definition XML filename:’ press the ‘Choose File’ button. Choose the full path to the modified aml-alert-details-01.xml file and then press the ‘Validate XML’ button.
When the validation succeeds, press the ‘Upload UI Definition’ button.

A1H002 updates SAS Compliance Solutions Server 6.3_M1

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.

UNIX:
export SASROOT=/install/SASHome/SASFoundation/9.4
Windows:
set SASROOT=C:\Program Files\SASHome\SASFoundation\9.4

# This should be the SAS Configuration Path and Level

UNIX:
export FCFROOT=/install/config/Lev1/Applications/SASComplianceSolutions
Windows:
set FCFROOT=C:\SAS\Config\Lev1\Applications\SASComplianceSolutions

This hot fix contains updated stored process code that needs to be copied into the $FCFROOT/sasstp folder. The following files should be copied, and the final .orig extension should be removed from the filenames:

UNIX

$SASROOT/sasstp/antimnycmn/aml_account_monthly_transaction_amounts.sas.orig
$SASROOT/sasstp/antimnycmn/aml_account_monthly_transaction_counts.sas.orig
$SASROOT/sasstp/antimnycmn/aml_party_monthly_transaction_amounts.sas.orig
$SASROOT/sasstp/antimnycmn/aml_party_monthly_transaction_counts.sas.orig

Windows

%SASROOT%\antimnycmn\sasstp\aml_account_monthly_transaction_amounts.sas.orig
%SASROOT%\antimnycmn\sasstp\aml_account_monthly_transaction_counts.sas.orig
%SASROOT%\antimnycmn\sasstp\aml_party_monthly_transaction_amounts.sas.orig
%SASROOT%\antimnycmn\sasstp\aml_party_monthly_transaction_counts.sas.orig

Edit each of these files and replace @fcf.stp@ with ${FCFROOT}/sasstp, manually replacing FCFROOT with the fully-qualified path to the Financial Crimes application folder. Also replace @nefs@ with the path separator character, a slash (/) for UNIX or a backslash (\) for Windows.

This hot fix contains code to improve AGP performance which requires the addition of a new knowledge center table, FSK_ACCOUNT_KEYS_ACC, and its associated business unit knowledge center view of the same name.

To leverage this improvement, you will need to execute one of the DDL scripts below, based 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.

For DB2:

Using the DB2 command line processor, execute the following commands:

Windows
db2 connect to user <system userid> using <system password>
db2 –tf $SASROOT\antimnycmn\sasmisc\ddl\db2\db2_6.3M1_to_6.3M1HF2_ddl.sql
UNIX
db2 connect to user <system userid> using <system password>
db2 –tf $SASROOT/misc/antimnycmn/ddl/db2/db2_6.3M1_to_6.3M1HF2_ddl.sql

For Oracle:

Using the SQLPlus command line utility, execute the following command:

Windows
sqlplus system/password@aml_sid @$SASROOT\antimnycmn\sasmisc\ddl\oracle\oracle_6.3M1_to_6.3M1HF2_ddl.sql
UNIX
sqlplus system/password@aml_sid @$SASROOT/misc/antimnycmn/ddl/oracle/oracle_6.3M1_to_6.3M1HF2_ddl.sql

For SQLServer:

Windows
In the $SASROOT\antimnycmn\sasmisc\ddl\sqlserver folder, change the first line of the following file, so that the “USE [LOCALDB]” command uses your SQLServer database name, for example “USE [MYDB]”.
$SASROOT\antimnycmn\sasmisc\ddl\sqlserver\sqlserver_6.3M1_to_6.3M1HF2_ddl.sql

Using the SQLCMD command-line utility, execute the following command:
sqlcmd –U sa –P password –i $SASROOT\antimnycmn\sasmisc\ddl\sqlserver\sqlserver_6.3M1_to_6.3M1HF2_ddl.sql

UNIX
In the $SASROOT/misc/antimnycmn/ddl/sqlserver folder, change the first line of the following file, so that the “USE [LOCALDB]” command uses your SQLServer database name, for example “USE [MYDB]”.
$SASROOT/misc/antimnycmn/ddl/sqlserver/sqlserver_6.3M1_to_6.3M1HF2_ddl.sql

Using the SQLCMD command-line utility, execute the following command:
sqlcmd –U sa –P password –i $SASROOT/misc/antimnycmn/ddl/sqlserver/sqlserver_6.3M1_to_6.3M1HF2_ddl.sql

For Teradata:

Using SQL Assistant or BTEQ, execute the following script:

Windows
$SASROOT\antimnycmn\sasmisc\ddl\teradata\teradata_6.3M1_to_6.3M1HF2_ddl.sql
UNIX
$SASROOT/misc/antimnycmn/ddl/teradata/teradata_6.3M1_to_6.3M1HF2_ddl.sql

A2K001 updates SAS High-Performance Anti-Money Laundering Server 6.3_M1

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

# This should be the SAS Configuration Path and Level

export HPAMLROOT=/install/config/Lev1/Applications/SASHighPerformanceAntiMoneyLaundering

This hot fix contains code that needs to be copied into the $HPAMLROOT/custom/source folder:

Copy $SASROOT/samples/hpamlsvr/pga_calculate_entity_history.sas into the $HPAMLROOT/custom/source folder.