Synchronous integration with an invocation channel

The integration framework uses invocation channels to process synchronous outbound messages that require a confirmation or response content from the external application. The export is started by an action class that calls the invocation channel.

Sending an invocation channel message is initiated by an action Java™ class that is coded to start the channel. Invocation channels are used, for example, to call an external application to validate data, to start a process on an external application, or to retrieve data. An invocation channel can be triggered by a user interface control that is configured to call the action class that starts the channel.

When an invocation channel message is started by an action class, the integration framework performs a sequence of tasks:
  1. Identifies the object structure that is associated with each invocation channel and identifies the component objects.
  2. Constructs the object structure for the transaction and forms an XML message that is based on the content of the objects.
  3. If any custom processing Java classes, automation scripts, or an XSL map are associated with the invocation channel request, processes them in the following order:
    1. Runs the preprocessing method in the request user exit processing class, if one is provided.
    2. Runs an invocation channel request processing class, if one is provided.
    3. Runs the postprocessing method in the request user exit class, if one is provided.
    4. Applies an XSL map, if one is provided.
  4. Writes the XML message to the destination that is specified by the endpoint.
  5. The endpoint handler specifies the transport mechanism to use.
  6. When the response is received from the end point, if any custom Java classes, automation scripts, or XSL maps are associated with the response, processes them in the following order:
    1. Runs the preprocessing method in the response user exit processing class, if one is provided.
    2. Runs an invocation channel response processing class, if one is provided.
    3. Runs the postprocessing method in the response user exit class, if one is provided.
    4. Applies an XSL map, if one is provided.
  7. Objects are built from the data in the response object structure and are passed to the system where standard processing is applied.
  8. If all the objects that are created from the response object structure process successfully, they are committed to the database.

The response content can be managed by the invoker based on integration requirements, for example to update business object data or display the response to a user. A default action class is provided that you can use or extend to implement an invocation channel integration.