INSTALLATION INSTRUCTIONS FOR HOT FIX 14MLD02 ON WINDOWS BEFORE DOWNLOADING: The hot fix 14MLD02 addresses the issues in Release 1.4 of SAS Money Laundering Detection software on Windows as documented in the "Issue(s) Addressed" section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/mld14.html#14mld02 IMPORTANT NOTES: 1. Hot fix 14MLD02 is required for all SAS Money Laundering Detection Release 1.4 sites. 2. You must have SAS Money Laundering Detection Release 1.4 installed on your system before applying this hot fix. It is recommended, where possible, to install the hot fix prior to setting up your !AMLROOT environment. 3. You must have Administrator privileges on your CLIENT and SERVER machines. 4. All currently active SAS sessions, daemons, spawners, and servers must be terminated before applying this hot fix. 5. The hot fix is applied *ONLY* to the SERVER; however, updates to the CLIENT are also required. AFTER DOWNLOADING: The hot fix package is a self-extracting executable named 14mld02wn.exe. Launching the executable will initiate the install wizard, which will guide you through the setup process. When applying this hotfix, there are 2 paths that a site may follow: "NEW SITE" and "EXISTING SITE". An installation is considered "NEW SITE" if the install.sas has *NOT* been executed and there is no data loaded into the CORE/KC. If a site has just started an implementation, it is recommended that you delete !AMLROOT and use the "NEW SITE" installation notes. Sites that have existing CORE/KC data should use the "EXISTING SITE" instructions. NEW SITE - have installed but not configured the software: ========================================================== 1) Follow the instructions in the SAS Money Laundering Detection Installation Manual, Second Edition. 2) For CLIENT installations, use the autoclt.sas file which is located on the SERVER after the hot fix installation. Do *NOT* apply the hot fix to the CLIENT. 3) Review all SAS Notes. 4) This completes the installation of hot fix 14MLD02 on Windows. EXISTING SITE - have already installed\configured the software: =============================================================== It is also assumed that 14MLD01 has already been applied. If you have not applied 14MLD01, please contact SAS Technical Support. To determine if your site has applied 14MLD01, invoke the Scenario Administrator. The following message should be displayed in the SAS LOG: Invoking Scenario Administrator Software, Release 1.4 (071006). SAVE YOUR DATA: It is recommended that a backup of all instances of !AMLROOT is created before proceeding. APPLY CODE FIXES: 1) Merge your site's !AMLROOT\custom\source installations of the following files with the updated versions from !SASROOT\detectionsvr\sample and !SASROOT\detectionclt\sample: * account_event_stage_extract.sas * account_profile_stage_extract.sas * account_stage_extract.sas * alert_transaction_view.sas * associate_stage_extract.sas * autoclt.sas - CLIENT and SERVER * autosvr.sas - comment out the %create_format statement at this time. * batch_reports.sas * branch_stage_extract.sas * cash_flow_stage_extract.sas * create_bank_standard_report.sas * detection.sas * include_custom_source.sas * install.sas * load_address_book.sas * load_core.sas * party_account_stage_extract.sas * party_profile_stage_extract.sas * party_stage_extract.sas * party_view.sas * start_share.sas * transaction_stage_extract.sas * transaction_view.sas 2) Replace your site's !AMLROOT installations of the following files with the updated versions in !SASROOT\detectionsvr. * !SASROOT\detectionsvr\sasmisc\scenario\messages.xml replaces !AMLROOT\scenario\xml\messages.xml * !SASROOT\detectionsvr\sasmisc\scenario\header_source\party_watchlist_header.sas replaces !AMLROOT\scenario\header_source\party_watchlist_header.sas & !AMLROOT\scenario\header_code_active\party_watchlist_header.sas * The following !SASROOT\detectionsvr\sasmisc\scenario\scenario_source\* files replace existing scenarios in !AMLROOT\scenario\scenario_source. Step 7 below will instruct you on how to update the new scenario metadata using the Scenario Administrator. SAS10001.sas SAS10002.sas SAS10003.sas SAS10004.sas SAS10005.sas SAS10006.sas SAS10007.sas SAS10008.sas SAS10009.sas SAS10011.sas SAS10012.sas SAS10014.sas SAS10015.sas SAS10016.sas SAS10017.sas SAS10018.sas SAS10019.sas SAS10020.sas SAS10021.sas SAS10022.sas SAS10023.sas SAS10024.sas SAS10025.sas SAS10026.sas SAS10027.sas SAS10028.sas SAS10029.sas SAS10030.sas SAS10031.sas SAS10032.sas SAS10033.sas SAS10034.sas SAS10035.sas SAS10036.sas SAS10038.sas SAS10039.sas SAS10040.sas SAS10041.sas SAS10076.sas SAS10078.sas SAS10079.sas SAS10080.sas SAS10081.sas SAS10082.sas scenario_messages.sas 3) If the existing report_tree.htm has been copied to !AMLROOT\custom\source, then manually move this file to !AMLROOT\reports\report_html. This applies to sites that have not applied 14MLD01. 4) Production modules were copied to !AMLROOT\custom\source during the initial release of the software. These modules must be removed for the hot fix to be applied correctly. There are two options for performing this step. It is recommended that you make a backup of !AMLROOT\custom\source\sasmacr.sas7bcat, if it exists, before proceeding. This applies to sites that have not applied 14MLD01. a) Delete existing sasmacr.sas7bcat and recompile all custom macros. 1) Delete !AMLROOT\custom\source\sasmacr.sas7bcat using Windows Explorer. 2) Invoke SAS using your SAS Money Laundering Detection shortcut. 3) Execute the updated include_custom_source.sas to recompile newly updated sample macros. 4) Recompile all site-specific custom code. - OR - b) Delete existing product macros from CUSTSRC. Recompile updated sample source code and any custom macros. i) Submit the following code to delete any production modules. proc catalog cat=custsrc.sasmacr entryType=macro; delete account_dim.sas account_event_fact.sas account_profile_fact.sas account_profile_prep.sas account_transactions_prep.sas active_headers_report.sas alert_age_report.sas amlerror.sas amlsuccess.sas associate_dim.sas awstitle.sas branch_dim.sas build_match_codes.sas build_party_match_codes.sas build_report_tree_html.sas cash_flow_fact.sas chkarraydim.sas combine_alerts.sas create_formats.sas create_macro_stubs.sas dist_active_alerts_report.sas dormant_account_prep.sas execute_command.sas execute_macro.sas fsmsolution_check.sas full_name.sas getmaxsurrogatekey.sas getrundate.sas header_change_history_report.sas header_elements_report.sas household_account_bridge.sas household_dim.sas household_party_bridge.sas htmlmail_account_section.sas htmlmail_alert_section.sas htmlmail_comment.sas htmlmail_customer_section.sas htmlmail_report.sas htmlmail_style_format.sas htmlmail_transaction_section.sas iff.sas loadalerts.sas loadriskfactors.sas load_global_qkb.sas mnydencrypt.sas mnydpw.sas monthly_trend_report.sas no_record_htm.sas owner_report.sas party_account_bridge.sas party_dim.sas party_phone_prep.sas party_profile_fact.sas party_profile_prep.sas party_taxid_prep.sas party_transactions_prep.sas put_aml_error.sas rcset.sas replicateprofile.sas replicatetransactions.sas riskranking.sas risk_factor_details.sas route.sas sar_bankstandard.sas sar_securitiesfutures.sas scenariocodegen.sas scenario_audit_report.sas scenario_details.sas update_calendar.sas update_report_output_styles.sas wc_import_watch_list.sas wc_load_entity_watch_list.sas wc_load_watch_list_country.sas wc_normalize_watch_list_data.sas wc_update_entity_watch_list.sas wc_update_watch_list_country.sas wc_watch_list_management.sas weekly_trend_report.sas word_count.sas ; quit; ii) Execute the updated include_custom_source.sas to recompile newly updated sample macros. iii) Recompile all site-specific macros. 5) Delete and re-create all indexes using the updated DDL. a) For sites that have applied 14MLD01: ==================================== Additional indexes will need to be created. See Problem Notes 34452: SASŪ Money Laundering Detection code uses ROLE_DESC, which degrades performance, and 35267 Slow performance opening the SAS Money Laundering Detection investigation UI when there are large numbers of closed alerts. b) For sites that have *NOT* applied 14MLD01. ========================================== i) Using the Windows Explorer, delete all the *.sas7bndx (index) files from !AMLROOT\data\Master\* directories ii) Re-create the CORE, and KC indexes using the updated DDL: sas_base_core_ddl.sas, and sas_base_kc_ddl.sas in !SASROOT\detectionsvr\sasmisc\datamodel directory. WARNING: This step will erase any existing data. 6) The new user security log on policy requires that you perform the following steps. This applies to sites that have not applied 14MLD01. a) Delete the list of "user" tables below using SAS Money Laundering Detection short-cut on the Detection server. * DB_KC.FSK_USER * DB_KC.FSK_USER_ADMIN b) Then re-create them using the User Administrator as documented in the Install Manual, Second Edition, "Install and Configure Detection Client." c) Uncomment the %create_format in !AMLROOT\custom\config\autosvr.sas. (This was commented out in step 1 above.) 7) Apply the scenario source code updates to the Scenario Administrator. This will import the updated scenario source code and maintain the history\version information. a) Invoke the Scenario Administrator. b) Select "Create,Edit and Test Scenarios and Risk Factors" c) Expand "Watch List Entities." d) Select "PEP Identification\Maintenance" scenario and click the "Edit" button. e) On the Scenario Properties window, click the "Configure Scenario" button. f) On the Scenario Configuration window, select the updated Scenario source code, via the "Select File" button or manually update the "Scenario" from: !AMLROOT\scenario\scenario_code_active\SAS10079.000001 to: !AMLROOT\scenario\scenario_source\SAS10079.sas g) Click the "OK" button on the Scenario Configuration window, then click the "OK" button on the Scenario Properties window. You will be prompted, "Do you wish to SAVE your changes?" Select "Yes." Follow this same procedure for all scenarios. 8) Update the "account_header" metadata using the new account_transactions_prep. See SAS Note 35289, Account_transactions_prep contains hard-coded length statements that could cause truncation. 9) Review all SAS Notes. 10) This completes the installation of hot fix 14MLD02 on Windows.