IBM BJ0NJML - Service And Asset Management Integration Manual page 37

Interface Tables
Inbound Integration Processing
If the verification fails, the integration framework issues an error and does not
process the message.
2
If the verification is successful, the integration framework identifies the
inbound JMS queue that is assigned to the enterprise service and the external
system.
3
The integration framework writes the message to the inbound queue. If the
message contains multiple instances of a document, for example, if a single
message contains ten person records, the application writes ten messages to
the queue.
If one of the messages has a processing error, a single message processing
exception is identified and none of the other messages that can be successfully
processed are committed to the database.
4
The integration framework updates the JMS message header with the external
system and enterprise service names.
You can preview the data that you want to import to check the format and the
data validity of a source file. It is a synchronous validation mechanism that
presents all the source file processing errors without committing data to the
database.
The preview data process checks that the data structure of the selected file
complies with the integration XML or flat file definitions.
The following steps describe the initiation of inbound processing that uses
interface tables.
1
The external system writes message data to the appropriate interface tables. It
also updates the MXIN_INTER_TRANS queue table with information about
the sequence in which the interface table records must be processed.
2
A system cron task regularly polls the MXIN_INTER_TRANS queue table for
records to be processed.
3
If any records are ready to be processed, the integration framework identifies
the sender as the external system and the enterprise service name from the
MXIN_INTER_TRANS queue table.
4
The integration framework checks that the external system and enterprise
service are valid and enabled.
The integration framework 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.
5
If the verification is successful, the integration framework identifies the
inbound JMS queue that is assigned to the enterprise service and external
system and writes the message to that queue.
Asynchronous Inbound Integration Processing
23