Queue Error Management - IBM BJ0NJML - Service And Asset Management Integration Manual

Integration guide
Table of Contents

Advertisement

Queue Error Management

Queue Error Management
116
Outbound processing errors can occur as the message is sent from the queue to
the external system. These errors are typically caused by a communication failure
between the queue and external system, or a problem with database configuration
when writing to interface tables or files.
Inbound processing errors can occur when the integration framework tries to
process a message into the application. Inbound processing errors are typically a
result of business rule validations in the objects or in the inbound processing logic
of the integration framework.
The sequential queue processes messages one at a time, in a first-in-first-out
sequence. When the integration framework encounters an error in processing a
message in a sequential queue, inbound or outbound, the error management
mechanism is initiated and the message is flagged as having an error. Subsequent
messages in the queue are not processed until the message in error is resolved. As
a result, only one error at a time can exist in a sequential queue.
The continuous queue processes messages in a multi-threaded mode. When an
error occurs in the continuous queue, the error management mechanism is
initiated and the message is flagged as having an error. The integration
framework continues to process subsequent messages in the queue. As a result,
multiple errors can exist in a continuous queue.
Depending on your system configuration, the integration framework makes
several attempts to reprocess the message before determining that an error
requires intervention. The system also performs the following activities when
encountering an error:
Sends a notification to a specified e-mail account, informing the recipient that
an error occurred.
On an IBM WebSphere Application Server environment, the integration
framework sends an additional e-mail message to the specified e-mail account
each time that you successfully restart your application server.
Creates an error file that contains the original message and information about
the error.
Creates a record in the Message Reprocessing application.
Integration Guide

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents