FIFO Message Processing (V5.2.0 - 5.2.1)

Sterling B2B Integrator supports FIFO processing of messages through adapters.

Introduction to FIFO Message Processing
Sterling B2B Integrator supports ordered processing of files and messages for the JMS Queue adapter, JMS Topic adapter, and MSMQ adapter.
Configuring FIFO Execution
You can customize the name and number of queues used in the FIFO framework.
FIFO Error Elements
The FifoError Type indicates the type of FIFO task that is being executed. At present, Async WorkFlow is the only type supported.
FIFO Error Queue Listener
The FIFO Error Queue Listener {nodename} is an out of the box adapter configured on each node to listen to the error queue.
Recovering Errant Data
The messages in the error queue are written in XML format. The XML format provides information to determine the nature and source of the document containing the error.
FIFORouting Service
The FIFORouting service provides a control and reporting mechanism for interaction between business processes and the FIFO subsystem.
Business Process Error Queue
The business process error queue is defined within the fifo.properties file. The error queue configuration defines the destination of errors within the FIFO framework. The error queue name should not contain spaces or punctuation.
Business Process Queues
The FIFO business process execution queues are defined by rows that are prefixed with workflow.taskqueue.
Cluster Configuration
The FIFO messaging system requires an external clustered JMS provider to allow proper execution and failover in a clustered configuration. An out of the box configuration for ActiveMQ 5.2 is provided to streamline this deployment.
Configure FIFO Services
You can configure FIFO services under the Deployment menu.
ActiveMQ Data Storage
JDBC (Database) Master Slave is the default configuration for data storage employed to store FIFO data for ActiveMQ. In this configuration, each ActiveMQ node in a cluster is configured to utilize a single, shared database.
Configure Shared File System Master Slave for ActiveMQ
You must manually configure the Shared File System Master Slave if you are not using the JDBC (Database) Master Slave configuration option to store FIFO data for ActiveMQ.
Shared File System Assumptions and Limitations
There are some assumptions and limitations you should be aware of when using the Shared File System option to store FIFO data for ActiveMQ.