![IBM BJ0NJML - Service And Asset Management Integration Manual Download Page 134](http://html1.mh-extra.com/html/ibm/bj0njml-service-and-asset-management/bj0njml-service-and-asset-management_integration-manual_3468932134.webp)
Error Notification
120
Integration Guide
Error Notification
When an inbound or outbound transaction results in an error in a queue, the
application sends an e-mail notification to the system administrator only if no
other errors are awaiting correction in the same queue. The notification informs
the system administrator that the queue contains one or more transactions with
errors. If multiple errors exist in the queue, the system administrator must resolve
all of them before notification of new errors is sent.
An e-mail error message includes a Java error stack trace and the error file name
with its full folder path information, which is relative to the server location. The
following example shows a typical folder path:
C:\error\jms.maximo.int.queues.cqin\EXTSYS1\EXTSYS1_MXCOAInterf
ace_11017328950785131.xml
The notification process works the same way regardless of the type of queue
(continuous or sequential) or the processing direction (inbound or outbound) in
which the error occurs, or whether the system is running in a clustered or
non-clustered environment.
For example, assume that the continuous inbound queue contains ten messages.
The system successfully processes the first four, and then encounters an error in
the fifth. (Depending on the value of the Maximum Try Count property, the
message might be tried one or more times.) An e-mail notification is sent to the
system administrator, and subsequent messages in the queue are processed.
If another error occurs in the seventh message, another e-mail notification is not
generated if the system administrator did not resolve the original error. If the
system administrator resolved the original error and no errors are pending, a new
e-mail notification is sent to the system administrator.
If the error is encountered in a sequential queue, processing is the same as in a
continuous queue except that the system does not process subsequent messages
until the message with the error is resolved.
Multiple errors exist only in the continuous inbound queue. In a clustered
environment, the system administrator might receive one e-mail error notification
per application server, depending upon the timing of the transactions in error.
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 ...