Common Causes of Errors
124
Integration Guide
Message Deletion
You can choose to delete a message from a queue. After you delete a message, the
system cannot reprocess it.
When the system deletes the message, the record is deleted from the
MAXINTERRORMSG and MAXINTERROR tables.
The application refreshes the result set and omits the deleted message listing on
the main tab of the Message Reprocessing application.
Critical Errors
Critical errors are transaction processing exceptions that the integration
framework error correction process cannot retry. Transaction processing
exceptions can occur when incorrect data, such as a special character, is present in
the XML file. When the integration framework identifies a critical error, ER and IR
sections in the corresponding error file are not present.
To correct the critical error, remove the incorrect data from the error XML. You
can see incorrect data that is associated with a critical error in the main tab of the
Message Reprocessing application.
Common Causes of Errors
Errors that occur when a message is processed from an outbound queue are
related to the problematic delivery of a message to the endpoint that is specified
for the external system. Typical problems are disruptions of the communication
link between the system and the external application, or database table space, or
file space issues in the external application. To resolve an outbound error, you
typically do not need to modify the XML message.
Errors that occur when a message is processed from an inbound queue are
typically related to a business rule validation in an object or in the inbound
processing of the enterprise service.
The following table describes the most common message errors that you can
encounter. Perform the suggested actions to correct your message errors.
Correcting an error in the XML file might create a mismatch in data between the
sending and receiving systems.
Error Type
Description
Actions
Sequence error
Caused by sequencing problems between
messages. The system stops message
processing when one record is referencing
another record that is in a pending state.
No action required. The system
resolves the error.
Data error
Occurs because the data or record does not
exist in the system database, and is not part of
the inbound messages in the queue.
Add the missing data to the
system database.
Summary of Contents for BJ0NJML - Service And Asset Management
Page 12: ...xii Integration Guide ...
Page 14: ...xiv Integration Guide ...
Page 16: ......
Page 31: ...Integration Framework for User Interface Integration Integration Framework Architecture 17 ...
Page 32: ...Integration Framework for User Interface Integration 18 Integration Guide ...
Page 60: ...Synchronous Inbound Integration Processing 46 Integration Guide ...
Page 122: ...Configuring External Systems 108 Integration Guide ...
Page 142: ...Non queue Error Management 128 Integration Guide ...
Page 154: ...Integration Components 140 Integration Guide ...
Page 156: ......
Page 172: ...Writing Custom Handlers 158 Integration Guide ...
Page 176: ...Queue Tables 162 Integration Guide ...
Page 190: ...IBM WebSphere MQ 176 Integration Guide ...
Page 212: ...Inbound Message Receipt 198 Integration Guide ...
Page 226: ...Integration Controls 212 Integration Guide ...
Page 252: ...Predefined External System Modifications 238 Integration Guide ...
Page 263: ...Web Service Queries Integration Queries 249 ...
Page 264: ...Web Service Queries 250 Integration Guide ...
Page 272: ...Integration Web Service Invocations 258 Integration Guide ...
Page 276: ...Multilanguage Attributes 262 Integration Guide ...
Page 293: ...Integration Module Invocation Integration Modules 279 ...
Page 294: ...Integration Module Invocation 280 Integration Guide ...
Page 302: ...Associating a Condition with a Signature Option 288 Integration Guide ...
Page 320: ...Work Order Collaboration Switches 306 Integration Guide ...
Page 324: ...310 Integration Guide ...