Inbound Queue Message Retrieval; Object Structure Identification - IBM BJ0NJML - Service And Asset Management Integration Manual

Asynchronous Inbound Integration Processing
Data Import Cron Task

Inbound Queue Message Retrieval

Summary

Object Structure Identification

Summary
24
The following steps describe the initiation of inbound processing that uses a data
import cron task.
1
The XMLFILECONSUMER cron task or the FLATFILECONSUMER cron task
regularly polls the source directory that is specified in its corresponding
configuration.
2
The files in the source directory are processed according to the cron task
configurations.
3
The integration framework checks that the external system and enterprise
service are valid and enabled.
If you are importing flat files, the integration framework also checks that the
enterprise service object structure supports flat structures.
If the verification fails, the integration framework sends an error notification
to the system administrator and stops processing the inbound message.
4
If the verification is successful, the integration framework identifies the
inbound JMS queue that is assigned to the enterprise service and the external
system, and writes the message to that queue.
You can choose to process inbound messages through the sequential queue, the
continuous queue, or a combination of the two. The sequential queue processes
messages on a strict first-in-first-out basis. The continuous queue supports multi-
threaded processing of messages.
When an error occurs in the sequential queue, the application sends an e-mail
message to the system administrator. The sequential queue also flags the message
as an error and continues to reprocess the message in error. Until the error is
corrected or removed, the queue stops processing all unflagged messages.
When an error occurs in the continuous queue, the application sends an e-mail
message to the system administrator. The continuous queue also flags the
message as an error, then continues processing subsequent messages in the
queue.
T
To see which inbound queue (sequential or continuous) that an external system
IP
uses, go to the System tab in the External Systems application.
The inbound messages that are received into the queue from the interface tables
or flat files are converted to an XML format.
A message remains in the inbound queue until the message processing completes.
The transaction is then deleted from the queue.
The integration framework identifies the object structures that are associated with
the enterprise service and creates a copy of the message for each object structure.
Integration Guide