IBM BJ0NJML - Service And Asset Management - Processing Rules

Outbound Customization
Integration Framework Customization with Java and XSL 215
The primary difference between an invocation channel and a publish channel is
that application code invokes the invocation channel, while an event or a data
export initiates a publish channel. Additionally, the synchronous processing of an
invocation channel can return a response and update the system business objects.
For invocations, you can customize an invocation channel in the following ways:
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
For responses, you can customize an invocation channel in the following ways:
T In the following Java exits:
 First user exit (user exit preprocessing)
 Publish channel processing class
 Second user exit (user exit postprocessing)
T With XSL mapping
The following diagram illustrates the flow of a message that uses an invocation
channel. The process flow starts from the object structure to the endpoint. The
endpoint delivers the message to its destination and a response can be returned to
the invoker of the invocation channel.
Processing Rules
You can use the publish channel processing rules engine to customize outbound
transactions without writing Java code or using XSL.
Processing rules are available only to a publish channel, not to an invocation
channel.