IBM BJ0NJML Integration Guide - Page 175

Queue Tables To list multiple interface names in the ENTERPRISESERVICE property: T Set ENTERPRISESERVICE=MXPOInterface|MXPRInterface|... Requirements for configuring multiple instances of the cron task: T The selectors must be mutually exclusive, so messages are not processed multiple times. T The selectors must retrieve all the enterprise service transactions that you use, so no messages are left unprocessed. Queue Tables One method of improving interface table processing is to use multiple queue tables. The MXIN_INTER_TRANS queue table is the default queue table. The IFACETABLECONSUMER cron task reads the MXIN_INTER_TRANS table and uses it as a driver to find and process the corresponding data in the interface tables. You can improve performance by setting up multiple queue tables. For example, you can write each interface to a separate queue table and define separate cron tasks to process the queue tables independently of one another. You also can set up separate queue tables for each external system and, within each queue table, define selectors for each interface. Depending upon the complexity of your integration, you can use multiple queue tables instead of multiple selectors. To set up multiple queue tables, create the queue tables in the same database as the interface tables, and include all the columns that are in the MXIN_INTER_TRANS queue table. You must design the external system to write to the appropriate queue tables. Ensure that the external system does not insert an interface table message into more than one queue table, or the message is processed multiple times. Advanced Interface Table Polling 161