Deployment examples > BAI2 > About deploying BAI2

Deploying FEX for BAI2

About BAI2 message handling

BAI2 standards define a single Cash Management message type. To transform and route this message type, Integrator parses the message to an Inhouse Business-Document.

To enhance BAI2 message processing, FEX provides two Integrator Java Message Components (JMCA JMC is a utility program for Integrator written in Java language, that resides on the Integrator Server and that you can select to use in any integration running on that server. JMCs extend the standard functions of Integrator.).

Delivered add-ons for BAI2

Integrator JMCs for BAI2

BAI2 Receive JMC

The JMC that provides processing for input messages is JMC_SFEX_BAI2_Receive.jar.

This JMC applies the following modifications to the BAI2 message to prepare it for parsing to an Inhouse Business-Document:

Checks the Record Count value in the records 49 Account Trailer, 98 Group Trailer, 99 File Trailer, and rejects the message if the Record Count is invalid.
Sets the Record 01 Physical Record Length field to a default value, thus defining a Variable format.
Merges all 88 - Continuation records, which removes all Continuation records from a parent record.
Replaces any end-of-line with CRLF on Windows platforms, and LF only on UNIX platforms with the UNIX Convention.
Removes any trailing spaces from records.
Adds a specific "03 – Account Identifier and Summary status / Funds Type / "D – Availability Distribution" end of sequence to the value "0xAB".
Adds a forward slash character ("/") at the end of the 16 – Transaction Detail text field.

BAI2 Send JMC

The JMC that provides processing to prepare for sending messages is the JMC_SFEX_BAI2_Send.jar.

This JMC applies the following modifications to the output Inhouse Business-Document to prepare it for parsing to a BAI2 message structure:

Sets the File Header (01 record) to the new Physical Record Length
Splits lines by adding the necessary 88 records, using the Physical Record Length as a maximum length for each record.
Applies the System-dependant end-of-line convention to separate records: CRLF on Windows platforms, and LF only on Unix platforms .
Uses the Padding parameter to decide if trailing spaces should be generated or not.

Additionally the BAI2 Send has the capacity to read the following set of attribute fields:

DECLARE PUBLIC RECORD Bai2

{

DECLARE PUBLIC FIELD $BAI2_FixedLength INTEGER;

DECLARE PUBLIC FIELD $BAI2_DebugLevel INTEGER;

DECLARE PUBLIC FIELD $BAI2_Padding STRING;

}

If you set these fields, you can override the values defined in Integrator.

To set these parameters, you must copy the file sfex_att_bai2.s4h (delivered in the FEX installation package) to the Integrator Server directory $CORE_ROOT/local/config/attribute

Using this Attribute is not mandatory, but makes the JMC use more flexible: instead of using the static Composer-set parameters, you can, as part of a previous Mapping step, set values for these parameters.

Integrator Business-Document for BAI2

The FEX installation package includes an XML file that enables you to generate the BAI2 Cash Management Balance Reporting Business-Document in Composer.

The name of the file is Business-Document.bai2.xml.

Example Integration-Process

The FEX installation package includes an XML file that you can import to generate an example Integration-Process for BAI2 message handling.

This Integration-Process:

Receives an input BAI2 file
Sets the length of the record and the Mapping according to the BAI2 Send specifications
Copies the file to an output directory

To work with this Integration-Process, refer to Configuring an Integration-Process for BAI2.