INTEGRATION FRAMEWORK(Business Event)

Setup IF.INTEGRATION.SERVICE.PARAM
EVENTS BATCH SIZE: This field defines the number of events to be batched together for delivery
within a single transaction. This field is not effective if field “Msg Delivery Mode” is set to “No
Batch”.
DESTINATION STATIC: This field defines a static destination identifier (activation string in the
case of CALLJEE/Event Delivery Service) to be used when delivering the events as JMS messages.
Usage of this field value is subject to value in related field “Destination Prop”.
MSG DELIVERY MODE: This field defines the deliver mode which is to be used by the integration
service when delivering the events as JMS messages within a single transaction. This field value is
used along with values in related fields “Events Batch Size” and “Msg Batch Xml”.
MSG BATCH XML: This field defines whether or not the batched events to be delivered as
individual JMS messages (i.e., 1 event = 1 JMS message) or as a single JMS message with a batched
XML of events.
COMPANIES LIST: The company list is the various branches for which the event will be published
for.
Setup IF.INITIAL.LOAD.PARAMETER
APPLICATION: This specifies the application for which the event will be delivered to the queue
FILE: This specifies the file type that will be selected for the application, i.e. LIVE, $ARC, $HIS,
$HIS$RO.
SERVICE STATUS: This specifies if the application has been added to the load(ACTIVE). Once it
is added, it changes to INACTIVE.
Create An Integration Project which includes the Events and Flow in Design Studio
We now publish the event and the flow created. This then creates a file for that event and flow in
IF.EXIT.POINTS and IF.INTEGRATION.FLOW.CATALOG.
IF.EXIT.POINTS includes the various application, versions, and services.
IF.INTEGRATION.FLOW.CATALOG includes the application, the exit points , fields to be
populated in the message and the schema that will be used to format the xml for delivery.
The value in the EXIT.POINT field in IF.INTEGRATION.FLOW.CATALOG will be link to the
entry in IF.EXIT.POINTS
IF.EXIT.POINTS for Customer
Next you post a transaction, which any of the applications specified in the
IF.INITIAL.LOAD.PARAMETER.
Next, we run the TSA service BNK/IF.INITIAL.LOAD.SERVICE. This selects the application
specified in the IF.INITIAL.LOAD.PARAMETER and allows selection of transactions to generate
events .

TSA SERVICE for BNK/IF.INITIAL.LOAD.SERVICE(set Service control to START/AUTO)

On successful execution of the service, IF.EVENTS.INTERFACE.TABLE will be loaded with data

for those applications that has an exit point and flow defined .
An example is Customer creation. After the customer created is authorized, the
IF.EVENTS.INTERFACE.TABLE is updated with the data of the customer created with the event
schema which includes all the fields specified in the IF.INTEGRATION.FLOW.CATALOG for the
application, CUSTOMER.
 An event record in IF.EVENTS.INTERFACE.TABLE to be sent to JMS queue

BNK/INTEGRATION.SERVICE is responsible for delivering the event record from the

TSA
SERVICE for BNK/INTEGRATION.SERVICE(set Service control to START/AUTO)

IF.EVENTS.INTERFACE.TABLE to the JMS queue. The service checks the setup of

IF.INTEGRATION.SERVICE.PARAM and formats the event record in the
IF.EVENTS.INTERFACE.TABLE based on this setup. The service then checks if the field
EVENTS.TIMESTAMP is empty, and also selects the event record to be delivered based on the
company specified in the COMPANIES.LIST field as setup in
IF.INTEGRATION.SERVICE.PARAM.

After the event record is delivered, the EVENT.DATA field of record in the
IF.EVENTS.INTERFACE.TABLE is updated with the formatted message sent to the JMS queue.
OLD.EVENT.XML field is updated with the xml that was generated before the message is formatted
and sent to the queue.
EVENT.TIMESTAMP field is updated in the event record in the IF.EVENTS.INTERFACE.TABLE
with the time at which the event was delivered to the JMS queue. The event record is now ready for
archival.

An event record with EVENT.DATA ,EVENT.TIMESTAMP and OLD.EVENT.XML fields updated

after delivery to JMS queue
In the Jboss Admin Console, the JMS queue for IF(queue/t24IFInboundQueue) is updated with the
count of the delivered events.

The queue/t24IFInboundQueue before the BNK/INTEGRATION.SERVICE service is run.

 The queue/t24IFInboundQueue after the BNK/INTEGRATION.SERVICE service is run.

A local development was done to send the delivered events from the queue/t24IFInboundQueue to
RabbitMQ. This is started as a shell script(businessevent.sh) on the server which call a
jar(capitalbankservice-0.0.1-SNAPSHOT.jar) file which runs as the service. A log of delivered events
to RabbitMQ is also kept for monitoring.

capitalbankservice-
0.0.1-SNAPSHOT.jar
The queue/t24IFInboundQueue after the local development service(businessevent.sh) is run.

The IF.EVENTS.INTERFACE.TABLE is purged by archiving the delivered event records and

deleting them from the table. This will enable the BNK/INTEGRATION.SERVICE to run faster since
the selection list will be minimum.