Invoke webMethods Integration Server
Specifically, you would need to configure the Invoke webMethods Integration Server action to:
Pre-process the request messages into the format required by the native API, before
Mediator sends the requests to the native APIs.
Pre-process the native API’s response messages into the format required by the clients, before
Mediator returns the responses to the clients.
In some cases an API might need to process messages.
For example, you might need to accommodate differences between the message content that a client is capable of submitting and the message content that a native API expects. For example, if the client submits an order record using a slightly different structure than the structure expected by the native API, you can use this action to process the record submitted by the client to the structure required by the native API.
In the Request Handling sequence, this action invokes the webMethods IS service to pre-process the request received from the client and before it is submitted to the native API.
In the Response Processing sequence, this action invokes the webMethods IS service to process the response message received from the native API and before it is returned to the client.
Note:
A webMethods IS service must be running on the same Integration Server as Mediator. It can call out a C++ or Java or .NET function. It can also call other Integration Server services to manipulate the message.
Input Parameters
webMethods IS Service | (String). Enter a name for the webMethods IS Service. This service is used to manipulate the request or response (the axis2 MessageContext instance). Mediator passes to the invoked IS service the request message context (the axis2 MessageContext instance), which contains the request-specific information. Also, you can use the public IS services that accept MessageContext as input to manipulate the response contents. |