Outbound Customization
214
Integration Guide
Outbound Customization
The integration framework processes outbound messages by using either a
publish channel or invocation channel. Publish channels and invocation channels
use placeholders, or user exits, in the outbound processing flows.
Publish Channel
The integration framework processes asynchronous outbound messages by using
publish channels. Publish channels provide placeholders, or user exits, in the
outbound processing flows for customization.
You can customize a publish channel in the following ways:
T Publish channel processing rules.
T In the following Java exits:
First user exit (user exit preprocessing)
Processing class
Second user exit (user exit postprocessing)
T With XSL mapping
T In a handler exit
The following diagram shows the flow of a message that uses a publish channel.
The process flow starts from the object structure to the endpoint. The endpoint
delivers the message to its destination.
Invocation Channel
The customization of an invocation channel is comparable to the publish channel.
On the invocation side, the invocation channel has an XSL file and three Java exits:
preprocessing user exit, processing class, and postprocessing user exit. The same
level of customization is available to the transaction response component. The exit
layer can map the response from the external service back to an object structure
which can be used to update system business objects.
Processing rules are not available to an invocation channel.
To Next Page
Loading...