Parameter name | Description | |
Input parameters | headers | Headers in response. Data type: Document |
payload | Payload of the response. Data type: String | |
payloadObject | The payload for binary content types like multi-part / form-data. Data type: Object | |
statusCode | Status code of the response. Data type: String | |
statusMessage | Status message of the response. Data type: String | |
MessageContext | The message context object of the response. Data type: Object | |
apiName | Name of the API invoked by the response. Data type: String | |
requestUrl | URL of the response. Data type: String | |
ipInfo | Contains IP information of the response. Data type: Document | |
websocketInfo | Websocket related information of the response. Data type: Document | |
correlationID | Correlation ID of the request/response. This is unique and same for a request and response. Data type: String | |
customFieldsMap | Custom transactional fields can be added to the transactional events using this field. For more information, see Adding Custom Fields to Transactional Events section. Data type: Document | |
Output parameters | headers | Headers in response. Data type: Document |
payload | Payload of the response. Data type: String | |
payloadObject | The payload for binary content types like multi-part / form-data. Data type: Object | |
statusCode | Status code of the response. Data type: String | |
statusMessage | Status message of the response. Data type: String | |
MessageContext | The message context object of the response. Data type: Object | |
customFieldsMap | Custom transactional fields can be added to the transactional events using this field. For more information, see Adding Custom Fields to Transactional Events section. Data type: Document |
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: ![]() The webMethods IS service must be running on the same Integration Server as API Gateway Note: If an exception occurs when invoking the webMethods IS service, by default API Gateway displays the status code as 500 and error message as Internal Server Error. You can set custom status code and error message by setting the following properties in the message context of the webMethods IS service: ![]() ![]() The sample code is given below: IDataCursor idc = pipeline.getCursor(); MessageContext context = (MessageContext)IDataUtil.get(idc,"MessageContext"); if(context != null) { context.setProperty("service.exception.status.code", 404); context.setProperty("service.exception.status.message", "Object Not Found"); throw new ServiceException(); } Note: If ServiceException or FlowException occurs when invoking webMethods IS Service, the message given in the exception is displayed to the client. If any other exception occurs, a generic error message is displayed to the client. ![]() 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 ![]() You can use the delete icon ![]() |