Inbound Customization; Interface Table User Exit - IBM BJ0NJML - Service And Asset Management Integration Manual

Inbound Customization

Interface Table User Exit

Integration Framework Customization with Java and XSL
The integration framework processes inbound messages by using enterprise
services. Enterprise services provide placeholders, or user exits, in the inbound
processing flows for customization.
You can customize an enterprise service in the following ways:
In an interface table user exit
In the following Java exits:
First user exit (user exit preprocessing)
Enterprise service processing class
Second user exit (user exit postprocessing)
With XSL mapping
With object structure and object processing rules
In a business object user exit
The following diagram shows the flow of a message that uses an enterprise
service. The process flow starts at the receipt of a message that uses one of
multiple protocols supported by the framework, through to the setting of the data
in the object structure and system business objects. The enterprise services that
use XML can bypass the JMS queue.
The external system can deliver an enterprise service message by using interface
tables. When you use interface tables to receive messages from an external
system, you can perform customization in the polling program that retrieves the
data from the interface table and sends data to the system.
The following figure shows the interface table processing exit classes that the
external system uses when sending transactions to the system.
Inbound Customization
223