Outbound Batch (ICL) Processing

As the Transaction Server ingests incoming work, it organizes the work by batch (ICL). Each batch (ICL) represents a group of transactions that is stored in the FTM database. A single batch (ICL) can contain any number of transactions, not all of which are valid. Often, a percentage of transactions in a batch (ICL) are suspect, which means they have a problem that requires them to be reviewed for correctness before the transactions are ready for processing.

A separate suspect image review engine manages reviews of the Transaction Server transactions that have been flagged as suspect. In addition, a Distribution engine awaits the transactions from the batch (ICL), as they become ready, to build the outbound batches (ICLs). The Transaction Server determines when a batch (ICL) has reached a configured state and then the Transaction Server notifies the Distribution engine that the batch (ICL) is ready for outbound processing. It also notifies the Distribution engine as each suspect transaction finishes review and is ready for outbound processing. Finally, more notifications are required for the end of day and the business day purge operations so that the Distribution engine can accomplish the processing it requires during these events.

To facilitate these notifications, the Transaction Server uses the Messaging API protocol to post messages to a WebSphere® MQ queue. The Transaction Server can be configured to post messages through the target queue belonging to the requisite Distribution engine. These messages notify the Distribution engine that work is available for outbound processing and for various other events where validations and work clean-up are required.

Some messages require guaranteed delivery, which means ensuring that the message is delivered so that work does not remain unprocessed by the Distribution engine. Not all messages require this degree of guarantee.