IBM BJ0NJML Integration Guide - Page 74

Synchronous Outbound Integration Processing Output The following table shows the possible response user exit preprocessing outcomes. Condition No preprocessing method exists. The preprocessing method skips the record The preprocessing method stops the record. The preprocessing method completes successfully. Output The existing object structure or invocation channel, unchanged. None; processing ends. None; processing ends, and an exception is returned to the caller of the invocation channel. The existing response object structure. Response XSL Mapping Summary The integration framework applies any custom response mapping to the invocation channel. You can use XSL mapping to map user-defined invocation channels or customize the mapping done by predefined invocation channel processing classes. Both the response object structure and invocation channel are available. TIP To see if response XSL mapping exists for an invocation channel, go to the Invocation Channel tab in the Invocation Channel application. Look on the Service Response Configuration table window for a response XSL map. Output The output of this activity must be an XML message in an invocation channel format. Object Processing Summary The objects are build from response object structure data and are passed to the system where standard system processing is applied. The system must successfully process all the objects that are created from the response object structure that is created from the invocation channel response before it performs the database commit. 60 Integration Guide