Parameter | Description |
Error conditions. Specifies the error conditions and how these error conditions should be processed. | |
Status Code Error Criteria | Specify the error status code. Provide a value for the Code. |
Header Error Criteria | Provide the details of the custom HTTP header(s) included in the client requests. Provide the following information: ![]() ![]() |
Payload Criteria | Provide the details of the payload criteria in the API request. In the Payload identifier section, click Add payload identifier, provide the following information, and click Add. ![]() ![]() ![]() The response maybe a native service error or API Gateway generated error. ![]() ![]() Note: You can add multiple namespace prefix and URI by clicking ![]() ![]() The response maybe a native service error or API Gateway generated error. ![]() The response maybe a native service error or API Gateway generated error. You can add multiple payload identifiers as required. Note: Only one payload identifier of each type is allowed. For example, you can add a maximum of three payload identifiers, each being of a different type. Value: Specifies a value that has to match with the value contained in the error Response. |
Pre-Processing. Specifies how the native error response is to be processed before API Gateway processes it. . | |
Invoke webMethods Integration Server Service | Specify the webMethods IS service to pre-process the error message. Provide the following information ![]() You can add multiple entries for webMethods IS service by clicking ![]() ![]() ![]() ![]() |
XSLT Transformation | Provide the XSLT file and feature you want to use to transform the service error response. Click Browse to select the XSLT file and upload it. Provide the following information for the XSLT feature: ![]() ![]() You can add multiple entries for feature name and value by clicking ![]() |
Custom Error Variables. Specifies the error variables to be used in the custom error message. | |
Payload Type | Specify the payload type. Available values are: ![]() ![]() |
Name | Provide a name for the payload type. |
Payload Identifier | Provide the details of the payload criteria in the API request. In the Payload identifier section, click Add payload identifier, provide the following information, and click Add. ![]() ![]() ![]() ![]() Note: You can add multiple namespace prefix and URI using the Add button. You can add multiple payload identifiers as required. |
Failure Message. Specifies the custom failure message format that API Gateway should send to the application. Specify whether the message should be in the text, json, or xml format. | |
Send Native Provider Fault Message | Enable this parameter so that API Gateway sends the native SOAP or REST failure message to the application. When you disable this parameter, the failure message is ignored when a fault is returned by the native API provider. |
Post-Processing. Specifies how the error response sent by the native service is to be processed before sending the same to the application. | |
Invoke webMethods Integration Server Service | Specify the webMethods IS Service for post-processing the error message. Provide the following information ![]() You can add multiple entries for webMethods IS service by clicking ![]() ![]() ![]() ![]() |
XSLT Transformation | Provide the XSLT file that you want to use to transform the service error response. Provide the following information for the XSLT feature: ![]() ![]() You can add multiple entries for feature names and values by clicking ![]() |