Invoke webMethods IS Policy
This policy pre-processes the request messages and transforms the message into the format required by the native API or performs some custom logic, before API Gateway sends the requests to the native APIs.
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.
This policy also processes the native API’s response messages into the format required by the application, before API Gateway returns the responses to the application.
The transformations using Invoke webmethods IS policy include Header, Query Parameter, Path Parameter transformation, HTTP Method transformation, Payload transformation, Status Code, and Status Message.
When can you use Invoke webmethods IS policy?
You can use Invoke webmethods IS policy:
When as an API Provider wants to read the contents of the request and response to do audit logging, or trigger a notification based on the contents of the request.
When the API Provider wants to modify the request before forwarding the request to native API as the native API wants to identify all incoming requests from
API Gateway. In such case the API Provider can configure the Invoke webmethods IS policy to add a header to all requests before they get routed to the native API.
When the API Provider wants to achieve complex use cases of transformation by writing an Invoke IS Service.
When the API Provider wants to write some custom logic using Java code to do the transformation.