IBM BJ0NJML - Service And Asset Management - Interface Table Error Management

Interface Table Error Management
Error Management 117
Interface Table Error Management
Errors can occur in the following two stages when inbound interface tables are
processed:
T Writing data from the interface table to the queue
T Processing data from the queue into the integration framework
The integration framework does not apply any business rules to the inbound
interface table records as it writes them to the inbound JMS queue. Errors that do
occur can occur for one of the following reasons:
T The JMS queue is deactivated or free space is not available.
T The enterprise service or external system name is not valid.
T The enterprise service is not enabled for the external system.
T The external system is not enabled.
When an error occurs during inbound interface table processing, the polling
program writes the exception trace in the IMPORTMESSAGE column of the
MXIN_INTER_TRANS queue table. For the first error in the
MXIN_INTER_TRANS queue table, the system sends an e-mail notification to the
administrator e-mail address that is specified in the System Properties
application.
After the cron task processes subsequent records in the MXIN_INTER_TRANS
queue table, it switches to an idle state. When processing resumes, the cron task
tries to process the records in error, as well as new records added to the
MAX_INTER_TRANS queue table.
After sending an error notification, the cron task does not send notification of
additional errors if the queue table contains one transaction that is marked in
error. The assumption is that the person who was notified of, and is researching,
the initial error sees and corrects additional errors when the queue table is
examined. After all current errors are corrected, the cron task sends a notification
when it encounters a new error.
Any errors that occur after the cron task successfully writes an interface table
message to an inbound queue are managed by the error handling process for the
queues.