Hot fix P31002 addresses the issue(s) in SAS Anti-Money Laundering 6.1_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/P31.html#P31002
P31002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
P33002 updates SAS Anti-Money Laundering Investigation Mid-Tier 6.1_M1
P37002 updates SAS Compliance Solutions Mid-Tier 6.1_M1
P32002 updates SAS Compliance Solutions Server 6.1_M1
P35002 updates SAS Customer Due Diligence Mid-Tier 6.1_M1
P36001 updates SAS Peer Group Analysis Server 6.1_M1
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, P31002r6.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 P31002r6.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of P31002r6.zip. The hot fix installation process will extract the contents as needed.
The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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 P31002r6.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.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.
Important Note:
For ease of completion of post-installation tasks, you can export the following:
export SASHOME=/install/SASHome This should be the path that SAS was installed to.For each product installed, click the link to be redirected to post-installation instructions.
export SASCONFIG=/install/config/Lev1 This should be the path that SAS was deployed/configured to.
export FCFROOT=$SASCONFIG/Applications/SASFinancialCrimesFoundation6.1
export AMLROOT=$SASCONFIG/Applications/SASAntiMoneyLaundering6.1
export CDDROOT=$SASCONFIG/Applications/SASCustomerDueDiligence6.1
export FCFMIDROOT=$SASCONFIG/Web/Applications/SASFinancialCrimesFoundation6.1
export AMLMIDROOT=$SASCONFIG/Web/Applications/SASAntiMoneyLaundering6.1
export CDDMIDROOT=$SASCONFIG/Web/Applications/SASCustomerDueDiligence6.1
export PGAROOT=$SASCONFIG/Applications/SASPeerGroupAnalysis6.1
P33002 updates SAS Anti-Money Laundering Investigation Mid-Tier 6.1_M1
P37002 updates SAS Compliance Solutions Mid-Tier 6.1_M1
P32002 updates SAS Compliance Solutions Server 6.1_M1
P35002 updates SAS Customer Due Diligence Mid-Tier 6.1_M1
P36001 updates SAS Peer Group Analysis Server 6.1_M1
P33002 updates SAS Anti-Money Laundering Investigation Mid-Tier 6.1_M1
Copy the following files from $SASHOME/SASAntiMoneyLaunderingInvestigationMidTier/6.1 to $AMLMIDROOT/install/uidef, removing the ‘.orig’ extension:
Config/uidef/aml-manual-alert-01.xml.origMake the following token substitutions in the same files:
Config/uidef/aml-manual-risk-assessment-01.xml.orig
Config/uidef/aml-risk-assessment-details-01.xml.orig
Config/uidef/aml-alert-details-01.xml.orig
Config/uidef/aml-available-alerts-01.xml.orig
Config/uidef/aml-closed-alerts-01.xml.orig
Config/uidef/aml-fin-rr-01.xml.orig
Config/uidef/aml-my-alerts-01.xml.orig
Config/uidef/aml-suppressed-alerts-01.xml.orig
@aml.software.component.name@=AntiMoneyLaund Mid 6.1
@war.context.name@=SASFinancialCrimesFdnMid
P37002 updates SAS Compliance Solutions Mid-Tier 6.1_M1
Copy the following files from $SASHOME/SASFinancialCrimesFoundationMidTier/6.1 to $FCFMIDROOT/install/uidef, removing the ‘.orig’ extension:
Config/uidef/fcf-sa-header-01.xml.origMake the following token substitutions in the same files:
Config/uidef/fcf-sa-scenario-01.xml.orig
Config/uidef/fcf-customer-details-01.xml.orig
@fcf.software.component.name@=Financial Crimes Fdn Mid 6.1
@aml.software.component.name@=AntiMoneyLaund Mid 6.1
@aml.dav.path@=Products/SASAntiMoneyLaundering
@segment_id@=FCFBU1
@war.context.name@=SASFinancialCrimesFdnMid
P32002 updates SAS Compliance Solutions Server 6.1_M1
Copy the following file from $SASHOME/SASFoundation/9.4 to $FCFROOT/install:
misc/antimnycmn/config/cdd_ecm_config_hotfix.sasMake the following token substitutions in those files. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@ecm.autoexec.path@=$SASCONFIG/Applications/SASEnterpriseCaseManagement/6.1/Source/control/ecm_autoexec.sasCopy the following file from $SASHOME/SASFoundation/9.4 to $FCFROOT/custom/config:
@cdd.autoexec.path@=$SASCONFIG/Applications/SASCustomerDueDiligence6.1/custom/config/autoexec.sas
@authdomain@=DefaultAuth
samples/antimnycmn/autoexec.sasMake the following token substitutions in the file above. You should merge it with a backup of your previous autoexec.sas, because there are a lot of settings that need to be the same as before. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@iomsrv.metadatasrv.host@={metadata tier host name}Copy the following files from <SASHOME>/SASFoundation/9.4 to $FCFROOT/custom/source:
@iomsrv.metadatasrv.port@={metadata port, usually 8561}" />
@oma.repository.foundation.name@={metadata repository name, usually “Foundation”}
@install.cmacros.dir@=$SASCONFIG/SASFoundation/9.4/cmacros/antimnycmn
@custsrc@=$FCFROOT/custom/source
@fcfroot@=$FCFROOT
@cmnroot@=$FCFROOT
@fcfdata@=$FCFROOT/data
@fcfland@=$FCFROOT/landing
@sysadmin.email@=%LET sysadmin=sysadmin@mycompany.com;
@agp.mlrisk@=1000
@agp.tfrisk@=1000
@agp.scoring.duration@=31
@agp.replicate.suppressed.alerts@=N
@agp.autoroute@=Y
@dbms.engine"@={database engine, which can be oracle, odbc, db2, or teradata}
@dbms.mode@={remove this token, replacing it with nothing, unless your configuration had it before}
@dbms.kc.schema@=FCFKC
@dbms.kc.userid@=FCFKC
@dbms.kc.connopts@={database connection options, for example "path=dbserver"}
@dbms.libopts@={remove this token, replacing it with nothing, unless your configuration had it before}
@dbms.segkc.schema@=FCFBU1
@dbms.segkc.userid@=FCFBU1
@dbms.segkc.connopts={database connection options, for example "path=localdb"}
@dbms.core.schema@=FCFCORE
@dbms.core.userid@=FCFCORE
@dbms.core.connopts@={database connection options, for example "path=localdb"}
@ecm.db.conopts@=%str({database connection options, for example "path=localdb"}
@custfmt@=$FCFROOT/custom/fmts
@jobstat@=$FCFROOT/jobstats
@cmndata@=$FCFROOT/data
@fcf.software.component.name@="Financial Crimes Fdn Mid 6.1"
@install.xml.map@=$SASHOME/SASFoundation/9.4/misc/antimnycmn/xml/map
@source_system_cd@=FCFBU1;
samples/antimnycmn/fcf_agp.sas
samples/antimnycmn/fcf_iem_close_dimension_rels.sas
samples/antimnycmn/fcf_iem_fb_alerts_risks.sas
samples/antimnycmn/fcf_iem_fb_man_alerts_risks.sas
samples/antimnycmn/fcf_iem_fb_party.sas
samples/antimnycmn/fcf_iem_load_alert_rels.sas
samples/antimnycmn/fcf_iem_load_dimension_rels.sas
samples/antimnycmn/fcf_iem_load_risk_rels.sas
samples/antimnycmn/fcf_iem_update_account.sas
samples/antimnycmn/fcf_iem_update_associate.sas
samples/antimnycmn/fcf_iem_update_household.sas
samples/antimnycmn/fcf_iem_update_party.sas
samples/antimnycmn/fcf_iem_update_subject.sas
samples/antimnycmn/fcf_sa_get_file_from_dav_server.sas
samples/antimnycmn/fcf_iem_cdd_control.sas
samples/antimnycmn/fcf_iem_cdd_del_rel.sas
samples/antimnycmn/fcf_iem_cdd_load_case.sas
samples/antimnycmn/fcf_iem_cdd_load_rel.sas
samples/antimnycmn/fcf_iem_cdd_update_case.sas
samples/antimnycmn/fcf_iem_cdd_update_closed.sas
samples/antimnycmn/fcf_iem_cdd_upd_sc_event.sas
samples/antimnycmn/fcf_iem_load_account.sas
samples/antimnycmn/fcf_iem_load_alerts.sas
samples/antimnycmn/fcf_iem_load_associate.sas
samples/antimnycmn/fcf_iem_load_ext_party.sas
samples/antimnycmn/fcf_iem_load_household.sas
samples/antimnycmn/fcf_iem_load_incident.sas
samples/antimnycmn/fcf_iem_load_party.sas
samples/antimnycmn/fcf_iem_load_risks.sas
samples/antimnycmn/fcf_iem_load_subject.sas
samples/antimnycmn/fcf_sa_ecm_ui_data.sas
samples/antimnycmn/fcf_stp_ecm_ui_response.sas
samples/antimnycmn/fcf_write_ecm_ui_xml_data.sas
On the file, $FCFROOT/custom/source/fcf_sa_get_file_from_dav_server.sas, replace the token @authdomain@ with the default authentication domain selected at configuration time (usually, DefaultAuth).
Copy the following files from <SASHOME>/SASFoundation/9.4 to $FCFROOT/sasstp, removing the ‘.orig’ extension from each:
sasstp/antimnycmn/fcf_sa_export_sp.sas.orig
sasstp/antimnycmn/fcf_sa_import_sp.sas.orig
sasstp/antimnycmn/fcf_sa_test_scenarios_sp.sas.orig
sasstp/antimnycmn/fcf_sa_update_fcf_tables_sp.sas.orig
sasstp/antimnycmn/cdd_attribute_score.sas.orig
sasstp/antimnycmn/cdd_case_details.sas.orig
sasstp/antimnycmn/cdd_category_score.sas.orig
sasstp/antimnycmn/cdd_overall_score.sas.orig
sasstp/antimnycmn/cdd_scoring_trend.sas.orig
sasstp/antimnycmn/fcf_customer_current.sas.orig
sasstp/antimnycmn/fcf_get_ecm_entities_sp.sas.orig
sasstp/antimnycmn/fcf_init.sas.orig
sasstp/antimnycmn/fcf_list_cases.sas.orig
Make the following token substitutions in those files. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@ecm.autoexec.path@=$SASCONFIG/Applications/SASEnterpriseCaseManagement/6.1/Source/control/ecm_autoexec.sasExecute the following program using UTF-8 SAS:
@aml.autoexec.path@=$SASCONFIG/Applications/SASAntiMoneyLaundering6.1/custom/config/autoexec.sas
@hpaml.autoexec.path@=$SASCONFIG/Applications/SASHighPerformanceAntiMoneyLaundering/6.1/custom/config/autoexec.sas
@aml.dav.path@=Products/SASAntiMoneyLaundering
@authdomain@=DefaultAuth
@nefs@=/ (should be a forward slash for UNIX; a backslash for Windows)
@fcf.stp@=$SASCONFIG/Applications/SASFinancialCrimesFoundation6.1/sasstp
@fcf.software.component.name@= Financial Crimes Fdn Mid 6.1
@fcf.autoexec.path@=$SASCONFIG/Applications/SASFinancialCrimesFoundation6.1/custom/config/autoexec.sas
$SASROOT/SASFoundation/9.4/bin/sas_u8 $FCFROOT/install/cdd_ecm_config_hotfix.sas
P35002 updates SAS Customer Due Diligence Mid-Tier 6.1_M1
Copy the following files from $SASHOME/SASCustomerDueDiligenceMidTier/6.1 to $CDDMIDROOT/install/uidef, removing the ‘.orig’ extension:
Config/uidef/cdd-case-details-01.xml.origMake the following token substitutions in the same files:
@cdd.software.component.name@=Cust Due Diligence Mid-Tier 6.1Concatenate together the following files into a new file called $SASHOME/SASFinancialCrimesFoundationMidTier/6.1/custom.properties:
@war.context.name@=SASFinancialCrimesFdnMid
@segment_id@=FCFBU1
$SASHOME/SASFoundation/9.4/misc/casemgmtmva/sample/properties/custom.properties
$SASHOME/SASFinancialCrimesFoundationMidTier/6.1/Config/uidef/custom.properties
$SASHOME/SASFinancialCrimesFoundationMidTier/6.1/Config/menu/custom.properties
$SASHOME/SASAntiMoneyLaunderingInvestigationMidTier/6.1/Config/uidef/custom.properties
$SASHOME/SASCustomerDueDiligenceMidTier/6.1/Config/uidef/custom.properties
P36001 updates SAS Peer Group Analysis Server 6.1_M1
Copy the following files from $SASHOME/SASFoundation/9.4 to $PGAROOT/sasstp, removing the ‘.orig’ extension:
sasstp/pgamva/pga_get_alert_details_sp.sas.origMake the following token substitutions in the same files. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@ecm.autoexec.path@=$SASCONFIG/Applications/SASEnterpriseCaseManagement/6.1/Source/control/ecm_autoexec.sas
@pga.autoexec.path@=$SASCONFIG/Applications/SASPeerGroupAnalysis6.1/custom/config/autoexec.sas
Follow steps below to complete deployment of this hot fix:
This hot fix requires that the WebApps be rebuilt and redeployed. Use the following steps to perform this post-installation task:
Step 1: Re-build Web ApplicationsUpload UI Definitions:In order for this step to execute correctly, the Metadata Server must be running.
1.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.41.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 the following WebApps:
SAS Financial Crimes Fdn Mid 6.1
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 ear files in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear files will be placed in the directory below:
<SASCONFIGDIR>/Web/Staging/Backup
Step 2: Re-deploy Web ApplicationsRe-deploy the web applications based on the instructions for the web application server you are using.
After rebuilding the web applications, start all servers. Wait until they are running, then complete the followings steps:
$AMLMIDROOT/install/uidef/aml-manual-alert-01.xml
$AMLMIDROOT/install/uidef/aml-manual-risk-assessment-01.xml
$AMLMIDROOT/install/uidef/aml-risk-assessment-details-01.xml
$CDDMIDROOT/install/uidef/cdd-case-details-01.xml
$FCFMIDROOT/install/uidef/fcf-sa-header-01.xml
$FCFMIDROOT/install/uidef/fcf-sa-scenario-01.xml
$FCFMIDROOT/install/uidef/fcf-customer-details-01.xml
$AMLMIDROOT/install/uidef/aml-alert-details-01.xml
$AMLMIDROOT/install/uidef/aml-available-alerts-01.xml
$AMLMIDROOT/install/uidef/aml-closed-alerts-01.xml
$AMLMIDROOT/install/uidef/aml-fin-rr-01.xml
$AMLMIDROOT/install/uidef/aml-my-alerts-01.xml
$AMLMIDROOT/install/uidef/aml-suppressed-alerts-01.xml.orig
Note: when uploading cdd-case-details-01.xml, two warning messages appear:
1. Field “CASE.CASE_ID” is required by the data model but marked “readonly” in the screen definition.
2. Field “CASE.REGULATORY_RPT_RQD_FLG” is required by the data model but marked “readonly” in the screen definition.
In order to leverage the updates provided by this hot fix, please read the following document:
Additional Documentation
This completes the installation of hot fix P31002 on 64-bit Enabled AIX.