The following instructions update ECM configuration data and stored processes related to the new FinCEN SAR reports. If your installation is not filing SAR reports, these post-installation steps are not necessary.

1.       Back up of all files under <ECMconfig>directory.

An example of <ECMconfig> is '/sasinstall/Config/Lev1/Applications/SASCaseManagementServerCfg/3.1'.

2.       Customize ".orig" files and copy form_template directory

Copy the files listed in the table below from the source location to the target location. Remove the extension .orig from the target file names. Then edit the target files according to the instructions in the 'Edit' column.

An example of <sashome> and <ECMconfig> are '/sasinstall/SASFoundation/9.3' and '/sasinstall/Config/Lev1/Applications/SASCaseManagementServerCfg/3.1'.

Source File	Target File	Edit
<sashome>/ucmacros/casemgmtmva/ecm_global_mvar.sas.orig (for Unix) <sashome>/casemgmtmva/ucmacros/ecm_global_mvar.sas.orig (for Windows)	<ECMconfig>/Source/ucmacros/ecm_global_mvar.sas	Specify ecm_webusername, ecm_webuserpass if you want to hard-code the account used to run PROC SOAP and PROC HTTP.   Review the other parameters. In particular, if the server tier is a Windows environment notice that the path for winzip is required. Winzip is required to properly generate the SAR efile.
<sashome>/ucmacros/casemgmtmva/ecmrr_efile_fincen_trnsmttr_var.sas.orig (for Unix) <sashome>/casemgmtmva/ucmacros/ecmrr_efile_fincen_trnsmttr_var.sas.orig (for Windows)	<ECMconfig>/Source/ucmacros/ecmrr_efile_fincen_trnsmttr_var.sas	Enter transmitter information
<sashome>/sasstp/casemgmtmva/ecmrr_efile.sas.orig (for Unix) <sashome>/casemgmtmva/sasstp/ecmrr_efile.sas.orig (for Windows)	<ECMconfig>/Source/sasstp/ecmrr_efile.sas (overwrite existing file)	Replace "@casemgmtmvac.config.control.dir@" with the path of ecm_autoexec.sas
<sashome/sassstp/casemgmtmva/ecmrr_efile_data_loader.sas.orig (for Unix) <sashome/casemgmtmva/sasstp/ecmrr_efile_data_loader.sas.orig (for Windows)	<ECMconfig>/Source/sasstp/ecmrr_efile_data_loader.sas	Replace "@casemgmtmvac.config.control.dir@" with the path of ecm_autoexec.sas
<sashome>/misc/casemgmtmva/sample/form_template (for Unix) <sashome>/casemgmtmva/sasmisc/sample/form_template (for Windows)	<ECMconfig>/Source/form_template	Replace all form_template files with the new versions.   Review PROC SOAP timeout parameter in ecm_soap_config.xml. The current setting is 2 minutes.

3.       Import New Stored Process

1. Using SAS Management Console, log on as an adminstrative user.
2. Click on the Folders tab, expand System/Applications/SAS Enterprise Case Management/Ent Case Mgmt Configuration 3.1/Application SAS Code.
3. Right-click on Application SAS Code, and select Import SAS Package....
4. Click Browse.
5. Select the file <sashome>/casemgmtmva/sasmisc/sample/config/ecmrr_efile_data_loader.spk (Windows)
   or <sashome>/misc/casemgmtmva/sample/config/ecmrr_efile_data_loader.spk (Unix), and click OK.
6. Take the default values in the Import SAS Package Wizard until you get to the SAS Application Servers page.
7. Select your SASApp application server and click Next.
8. On the Source Code Repositories page, select <ECMconfig>/Source/sasstp.
9. Click Next and verify that the Summary information is correct.
10. Click Next.
11. When the import process finishes, click Finish.

4.        Configure Stored Process Server to Run System Commands

The new FinCEN efile process requires reports to be zipped together. In order to execute the zip command, the XCMD option must be enabled for the SAS Stored Process Server so that the SYSTEM function can be used. To allow the XCMD option:

1. Using SAS Management Console, log on as an adminstrative user.
2. From the Plug-ins tab, select Environment Management -> Server Manager -> SASApp -> SASApp - Logical Stored Process Server -> SASApp - Stored Process Server.
3. Right-click and select Properties.
4. On the SASApp - Stored Process Server Properties popup window, select the Options tab and press the Advanced Options... button.
5. In the Advanced Options popup, select the Launch Properties tab.
6. Check the Allow XCMD checkbox.
7. Click OK in Advanced Options and again on the SASApp - Stored Process Server Properties window.
8. Stop and Restart your SAS 9.3 Object Spawner.

5.       Run New SAR Form Configuration Scripts

The next step is to run two SAS scripts that load configuration data for the new FinCEN SAR form. The scripts assume that the original 3.1 form configuration scripts have already been run. If you are uncertain if those scripts have been run, check the results of the PROC SQL query listed below. If the returned value is greater than 0, load_rr_config_fincen_base.sas has already been run. If the returned value is 0, run load_rr_config_fincen_new_base.sas. That file is contains the configuration data that is shared by the old SAR-DI and the new SAR forms.

The SAS scripts can be found here on Windows:

• <sashome>/casemgmtmva/sasmisc/sample/config/ loadrr_config_fincen_new.sas
• <sashome>/casemgmtmva/sasmisc/sample/config/loadrr_config_fincen_sar.sas

and here on Unix:

• <sashome>/misc/casemgmtmva/sample/config/loadrr_config_fincen_new.sas
• <sashome>/misc/casemgmtmva/sample/config/loadrr_config_fincen_sar.sas

Here is the PROC SQL code to check if form configuration data has already been loaded:

proc sql;
select count(*) from ecm_db.generic_data_udf_def
where udf_table_nm = 'X_INSTITUTION';
quit;

In summary, the steps to complete are:

1. Open a Base SAS Session
2. Open and run the program <ECMConfig>/Source/control/ecm_autoexec.sas.
3. Open a New Program window.
4. Run the macro %ecm_db_connect;. Verify in the log window that the ecm_db libname has been defined.
5. Run the proc sql query to verify whether the original 3.1 form configuration scripts have already been run.
6. If necessary, run the program load_rr_config_fincen_new_base.sas
7. Open and run the program loadrr_config_fincen_new.sas
8. Open and run the program loadrr_config_fincen_sar.sas

6.       Clear Cache

Logon to the ECM web application as an administrator. Run Clear Cache under the 'Administration' tab.

7.       Upload UI definitions

1. As an administrative user, logon to the ECM web application.
2. Go to the Administration tab.
3. Upload the following UI definition files from <sashome>/casemgmtmva/sasmisc/sample/uidef (Windows) or <sashome>/misc/casemgmtmva/sample/uidef (Unix):
   • efile-fincen-new-01.xml
   • party-cus-01.xml
   • rr-fincen-sar-01.xml

Note: the new version of party-cus-01.xml will overwrite the existing version. If you have customized that UI definition file, you may need to merge your own changes into the new document. In that case, download the file from the server and compare it with the new file before uploading.

8.       Upload custom.properties

A new version of custom.properties is included with this hotfix. If your custom.properties has been customized, compare it with the new version of custom.properties in <sashome>/casemgmtmva/sasmisc/sample/properties (Windows) or <sashome>/misc/casemgmtmva/sample/properties (Unix). Incorporate any differences into the new custom.properties.

1. As an administrative user, logon to the ECM web application.
2. Go to the Administration tab.
3. Select the Custom Properties Files tab and upload the new file.