You must copy certain JAR files to the SAS® Business Orchestration Services directory after installing a SAS® Fraud Management hot fix


If SAS Business Orchestration Services is used to send transactions to SAS Fraud Management, then three Java JAR files must match between the SAS Fraud Management installation and the SAS Business Orchestration Services installation. The three JAR files are the following:

After a hot-fix installation of SAS Fraud Management, you might need to update these JAR files in the SAS Business Orchestration Services installation directory.

Important: Before you replace them, ensure that you back up copies of the original JAR files in the SAS Business Orchestration Services directory.  

 

Steps

A.  Determine the required SAS Fraud Management JAR versions.

  1. Log on to the SAS® OnDemand Decision Engine server as the SAS installation user.
  2. Change to the SASHome/SASFraudManagementDecisionEngine/n.n directory.
  3. Run this command and note the version displayed:  grep -1 fraud.engine picklist
  4. Run this command and note the version displayed:   grep -1 fraud.transaction picklist
  5. Run this command and note the version displayed:  grep -1 creditfraud.common picklist

An example from a SAS Fraud Management 6.1 HF 8 server is shown below:

NameVersionDirectory  (Name_Version)
sas.finance.fraud.engine601001.3.0.20210505112700_f0rapt61 sas.finance.fraud.engine_601001.3.0.20210505112700_f0rapt61 
sas.finance.fraud.transaction601001.4.0.20211102082900_f0rapt61sas.finance.fraud.transaction_601001.4.0.20211102082900_f0rapt61
sas.finserv.creditfraud.common 601001.4.0.20211102082900_f0rapt61sas.finserv.creditfraud.common_601001.4.0.20211102082900_f0rapt61

 

B.  Copy the JAR files to a temporary directory on the SAS OnDemand Decision Engine server.

  1. Create a temporary directory to hold the three JAR files. Here is an example:  mkdir /tmp/fraud_jars
  2. Change to the SASHome/SASVersionedJarRepository/eclipse/plugins directory.
  3. Build the directory name for each of the three JAR files by adding an underscore character ( _ ) between the Name and the Version. See the examples in the Directory (Name_Version) column in the table above.
  4. Copy the sas.finance.fraud.engine.jar file to your temporary directory.   
    • For example:  cp sas.finance.fraud.engine_601001.3.0.20210505112700_f0rapt61/sas.finance.fraud.engine.jar /tmp/fraud_jars
  5. Copy the sas.finance.fraud.transaction.jar file to your temporary directory. 
    • For example:  cp sas.finance.fraud.transaction_601001.4.0.20211102082900_f0rapt61/sas.finance.fraud.transaction.jar /tmp/fraud_jars
  6. Copy the sas.finserv.creditfraud.common.jar file to your temporary directory. 
    • For example:  cp sas.finserv.creditfraud.common_601001.4.0.20211102082900_f0rapt61/sas.finserv.creditfraud.common.jar /tmp/fraud_jars

C. Copy the JAR files from the temporary directory to the SAS Business Orchestration Services server.

  1. Log on to the SAS Business Orchestration Services server as a user who has Write permissions to the installation directory.
  2. Change to the lib directory under the installation directory. This location varies depending on the version. 
    • For SAS Business Orchestration Services on the SAS Viya Platform, the directory is /opt/sas/viya/config/etc/boss/lib.
    • For SAS Business Orchestration Services 10.n, the directory is /opt/sas/viya/home/lib/boss.
    • For SAS Business Orchestration Services 1.n, the directory is installation-directory/EOP-1.n.0/lib.
  3. Make backup copies of the following three JAR files. Note that in version 10.n, the JAR file names contain the version number.
    • sas.finance.fraud.engine.jar
    • sas.finance.fraud.transaction.jar
    • sas.finserv.creditfraud.common.jar
  4. Stop SAS Business Orchestration Services.
  5. Using the Secure Copy Protocol or another method, transfer the JAR files from the temporary directory on the SAS OnDemand Decision Engine server to the SAS Business Orchestration Services server.
  6. Copy the JAR files into the lib directory under the installation directory. This location varies depending on the version.
    • For SAS Business Orchestration Services on the SAS Viya Platform, the directory is /opt/sas/viya/config/etc/boss/lib.
    • For SAS Business Orchestration Services 10.n, the directory is /opt/sas/viya/home/lib/boss.
    • For SAS Business Orchestration Services 1.n, the directory is installation-directory/EOP-1.n.0/lib.
  7. Confirm that the ownership and permissions of the JAR files are correct.
  8. Start SAS Business Orchestration Services.
  9. Test SAS Business Orchestration Services with the new JAR files.