Message Reprocessing; Message Statuses - IBM BJ0NJML - Service And Asset Management Integration Manual

Message Reprocessing

Message Statuses

Error Management
When you use the Message Reprocessing application, you can manage and view
integration messages that are flagged with an error. You can view the error XML
file without accessing the integration server error files.
Failed messages can be managed in the following ways in the Message
Reprocessing application:
Change the message statuses to stop message processing or to reprocess a
message
Correct, process, save, or cancel the error XML file
Delete the message from the database
The Message Reprocessing application works with the Message Tracking
application when you enable message tracking in either the Publish Channels
application or the Enterprise Services application. In the Message Tracking
application, you can determine which tracked messages are flagged with an error
and then correct the erroneous data.
If you have not enabled message tracking, you can go to the Message
Reprocessing application to check for transaction errors.
You use the Change Status action in the Message Reprocessing application to
change the status of a message. The system designates a status to each message to
indicate whether it is ready for processing.
A message can have a status of RETRY or HOLD:
Status
RETRY
HOLD
The RETRY status is the default status for messages that are flagged with an error.
Until you correct the processing problem, the system continues to reprocess the
message according to the configured queue retry count. When the retry count
condition is met, the system changes the messages status to HOLD.
You can halt message reprocessing by changing the message status to HOLD. A
hold status prevents the system from reprocessing the flagged message and from
updating the system database tables.
Message Reprocessing
Description
The message is ready to be
reprocessed by the system.
The message is not ready to be
reprocessed by the system.
121