IBM BJ0NJML Integration Guide - Page 119

Interface Table Polling Interface Table Polling A predefined cron task, IFACETABLECONSUMER, polls the MXIN_INTER_TRANS queue table and uses the IFACENAME, EXTSYSNAME, and TRANSID values in the queue table to place the corresponding interface table records into the appropriate inbound JMS queue. Then, individual records in the JMS queue are processed. The interface table polling process checks that the record external system and enterprise service names are valid and currently enabled. If they are not, the record is marked in error and remains in the interface table. If you disable interface table polling, new records remain in the interface tables. The messages that were sent to the inbound JMS queue are processed. You must set up a mechanism to retrieve outbound transactions from the interface tables. You can use a polling program, as the system does for inbound transactions, triggers, or any other mechanism. The cron task has the following configurable parameters. All parameters are optional. Parameter EXITCLASS ENDPPOINT ENTERPRISESERVICE TARGETENABLED EXTSYSNAME QUEUETABLE Description Java exit class that enables the manipulation of data before it is written to an inbound queue. Endpoint that is associated with the interface table. The default value is the predefined endpoint value that points to the local database. Enterprise service to be polled. The default (null value) is all enterprise services. If you specify a value for this parameter, you also must specify a value for the EXTSYSNAME parameter. The values limit the polling thread to a specific enterprise service instead of the default behavior, which polls for all enterprise services. Optional Boolean flag that controls whether the cron task runs on a specific application server. The default value is 0 (false). External system to be polled. Enterprise service queue table. The default value is MXIN_INTER_TRANS. Interface Tables 105