SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 67596: The amlcdd_multiTenant_config (or aml_multiTenant_config) post-installation script fails while seed data is loaded

DetailsHotfixAboutRate It

The amlcdd_multiTenant_config (or aml_multiTenant_config) post-installation script for SAS Anti-Money Laundering fails while seed data is loaded. When this problem happens, the following error is generated:

ERROR: The archive directory  /opt/sas/viya/home/amlRegReportConfiguration/resources/data does not exist

The directory exists on the microservices tier, but the playbook searches for it on the compute tier.

To work around this problem in SAS® Anti-Money Laundering 8.1 and  8.2, you need to edit the csCore_load_seed_data.sh script (which resides in /opt/sas/spre/home/SASFoundation/misc/amlcoresrv/csCore/deploy_scripts/tasks/) on the compute server machine. In the script file, change line 133 by removing the space between the equal sign (=) and the dollar sign ($) .

To work around this problem in SAS® Anti-Money Laundering 8.3, you need to edit the csCore_load_seed_data.sh script (which resides in /opt/sas/spre/home/SASFoundation/misc/amlcoresrv/bin/) on the compute server machine. In the script file, change line 288 by removing the space between the equal sign (=) and the dollar sign ($) .

      # if the file doesn't exist then change the artifacts directory to /tmp/sas/fcf
      # this is the case where we had to copy the file over from the AML core microservice (see the playbook yml file)
      # replace /opt/sas/viya/home with /tmp/sas/fcf
      if [[ ! -f ${artifacts_dir}/${jsonName} ]]; then
         artifacts_dir= ${artifacts_dir//opt\/sas\/viya\/home/tmp/\sas/\fcf}  <----- Remove space between
                                                                                = and $ on this line 
      fi


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Anti-Money LaunderingLinux for x648.2Viya
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.