Invoke webMethods IS Policy Properties for Response Processing
If Comply to IS Spec parameter is configured as true, webMethods 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 |
|
|
SOAP |
|
|
WebSocket |
|
|
- For SOAP to REST APIS, the payload contains the transformed JSON response.
- 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.
- 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. IBM 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, webMethods 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)
Property | 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 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
You can use the delete icon |
Adding Custom Fields to Transactional Events
- Create webMethods IS service by specifying the pub.apigateway.utils:customFieldInTransactionEventSpec as a specification reference.
- In the webMethods IS service, set the required custom fields in the customFieldsMap output variable.
- Once when customFieldsMap gets created, the custom fields will be available in the transactional events.
- Invoke the API with the Invoke webMethods IS policy.