EasyManua.ls Logo

IBM BJ0NJML - Service And Asset Management - Request XSL Map; Send the Invocation Channel Data to the Endpoint

IBM BJ0NJML - Service And Asset Management
330 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Synchronous Outbound Integration Processing
58
Integration Guide
Output The following table shows the possible request user exit preprocessing outcomes.
Request XSL Map
Summary The integration framework applies any custom request 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
object structure and invocation channel are available.
T
IP To see if request XSL mapping exists for an invocation channel, go to the
Invocation Channel tab in the Invocation Channel application. Look on the
Service Request Configuration table window for a request XSL map.
Output The output of this activity must be an XML message in invocation channel format.
The notation used by the integration framework to represent numbers greater
than seven digits is controlled by the
mxe.int.usesscientific variable. By
default, numbers greater than seven digits use a scientific notation.
Send the Invocation Channel Data to the Endpoint
Summary The integration framework writes the invocation channel data to the location that
you specify on the endpoint. The endpoint determines the data transport
mechanism of an invocation channel.
1 The integration framework writes the XML message to the endpoint location.
T
IP To see what location, and the transport mechanism the endpoint uses,
go to the End Point tab in the End Points application.
To see which handler an endpoint uses, select Add/Modify End Points
from the Select Action menu in the End Points application.
2 The handler processing class invokes an external application or system.
Condition Output
No preprocessing method exists. The existing object structure or
invocation channel, unchanged.
The preprocessing method skips the
record.
None; processing ends.
The preprocessing method stops the
record.
None; processing ends, and an
exception is returned to the caller of
the invocation channel.
The preprocessing method completes
successfully.
The existing invocation channel,
possibly updated.

Table of Contents

Related product manuals