Communicating with Business Rules

AutoAdjust can be configured to validate transaction updates and inserts the same way ingestion originally validated the transactions. If calling Business Rules Server is enabled, AutoAdjust queries tables in the database to obtain the following validation parameters for the batch (ICL) containing the transaction:

Sort pattern (for example, sort type) number
Business Rules Server workflow name

The Transaction Server stores this information in the database when it creates a batch (ICL). When AutoAdjust finds a Business Rules workflow name, it assumes that Business Rules originally validated the transaction during ingestion and it uses the Business Rules Server to validate any updates to the transaction. AutoAdjust installs a J2CA resource adapter module to connect to Business Rules.

In the Business Rules custom properties, select additional property and then custom properties to provide the Business Rules connection properties shown in Table 1.

Table 1. Business Rules Custom Properties
Name	Default	Type	Description	Required
PrimaryServer	localhost	String	Business Rules Server primary host name	Yes
Business Rules SSL Configuration Name	null	String	The Business Rules SSL configuration alias to be used. For example, `NodeDefaultSSLSettings`.
RequestTimeout	999999	Integer	Maximum time the Business Rules Server remains inactive between decision requests	Yes
ResponseTimeout	20000	Integer	Wait time when waiting for a general response from the Business Rules Server	Yes
UserClass		String	User exit class	No

The UserClass variable specifies the name of the user exit. The class must be in a JAR file that is installed in the correct location. For more information, see User exits for the FTM components.

AutoAdjust supplies sample Business Rules user exit classes. The files for user exits are provided in the FTM artifacts pod and must be downloaded from the pod. For more information about getting files from the artifacts container for your offering, see Getting the files from the artifacts container for your FTM offering.

The sample user exits are:

com.ibm.paydir.izw.samples.SampleUXBusinessRules: SampleUXBusinessRules is a general example of how to write a Business Rules user exit.
com.ibm.paydir.autoadj.samples.AdmRet01AABrulUserExit: AdmRet01AABrulUserExit shows how to handle administrative return payments that are processed by the sample AutoAdjust chargeback user exit. This user exit preserves the endpoint and return reason code assigned to the payment.