Invoke webMethods IS
This policy processes the native API’s response messages into the format required by the application, before API Gateway returns the responses to the application.
If Comply to IS Spec parameter is configured as true, API Gateway invokes the IS Service with IS specification in the path pub.apigateway.invokeISService.specifications:ResponseSpec (for Response Processing)
The following are the input and output parameters for REST, SOAP, and WebSocket APIs as specified in the above IS Specification.
API type | Input parameters | Output parameters |
REST |  headers payload messageContext statusCode statusMessage proxy.name requestUrl correlationID (this is unique for request and response) | headers payload messageContext statusCode statusMessage |
SOAP | headers payload messageContext statusCode statusMessage proxy.name payloadObject requestUrl correlationID (this is unique for request and response) | headers payload messageContext statusCode statusMessage |
WebSocket | headers payload (this is applicable when the message type is Text) binaryMessage (this is applicable when the message type is Binary) messageContext proxy.name requestUrl websocketInfo correlationID (this is unique for request and response) | headers payload messageContext binaryMessage |
Note: For SOAP to REST APIS:
For SOAP to REST APIS, the payload contains the transformed JSON response.
In the 10.2 release, payload transformation does not happen automatically for content-type transformation. When you change the content type, ensure to do payload transformation also as part of IS Service.
Only Method Transformation happens when configured, but you have to take care of adding payload during transformations involving method change like GET to POST, and so on.
When
Comply to IS spec is true, you can change the values of headers, query, payload, and so on, programatically using Message Context, as well as using the pipeline variables given.
Software AG recommends you do not change those values directly in Message Context, as the values in output pipeline variables are written to Message Context after the invocation of IS Service.
If Comply to IS Spec parameter is set to false, API Gateway invokes the IS Service with the same input and output parameters supported in 10.1 and the earlier versions::
proxy.name
JSONRESTContentString (REST only)
SOAPEnvelope (SOAP only)
EnvelopeString (SOAP only)
The table lists the properties that you can specify for this policy:
Parameter | Description |
Invoke webMethods Integration Server Service |
Add invoke webMethods Integration Server service | Specifies the webMethods IS service to be invoked to process the response messages and the authentication mode for the IS service. Provide the following information: webMethods IS Service. Specify the webMethods IS service to be invoked to pre-process the response messages. Note: The webMethods IS service must be running on the same Integration Server as API Gateway. Run as User. Specifies the authentication mode to invoke the IS service. If this field is left blank the incoming credentials of the user, identified by API Gateway, are used to authenticate and invoke the IS service. You can also specify a particular user, you want API Gateway to invoke the IS service. Note: You can add multiple entries by clicking  . Comply to IS Spec. Specifies whether you want the input parameters and the output parameters to comply to those present in pub.apigateway.invokeISService.specifications. Note: Software AG recommends users to configure the policy with Comply to IS Spec as true, as you can read or change the values of headers, and so on, without having to read from or write to the message context. |
webMethods IS Service alias | Specifies the webMethods IS service alias used to invoke the webMethods IS service to pre-process the response messages. Start typing the webMethods alias name, select the alias from the type-ahead search results displayed and click  to add one or more aliases. You can use the delete icon  to delete the added aliases from the list. |