Specifies the error conditions and how each of these error conditions are to be processed. You can define a maximum of three conditions. You can configure only one error condition per type. For example, you cannot define two status code conditions. To specify multiple conditions, use the plus button to add rows.

Default Specify the error status code. For example: 400, 500.

Specify the details of the custom HTTP header(s) included in the client requests. The parameters are:

Specifies the details of the XPath expression in the API request. The parameters are:

Specifies how the native service error response is to be processed before sending the same to Mediator. You can configure multiple ESB and XSLT processing steps. You can either log the error message sent by the native service without any changes or you can remove any critical information that you do not want Mediator to log or send to the client. The processing of these steps is taken up in the order in which they are configured.

String. Optional. Specify the XSLT file that you want to use to transform the service error response. Use the Choose button to browse to and select a file.

Default. String. Optional.

Specify the webMethods IS Service.

Invokes one or more webMethods IS services to manipulate the response message from the native API before it is returned to the consuming application. The IS service will have access to the response message context (the axis2 MessageContext instance) before it is updated with the custom error message. For example, you might want to send emails or perform custom alerts based on the response payload.

String. Specify the custom failure message that Mediator should send to the client. You can configure an error template each for the content types: Text, XML, and JSON. For addition details, see the fault handler variables listed in the table below. For example, $CONSUMER_APPLICATION $OPERATION :$ERROR_MESSAGE.

Specifies the content type for which the failure message is defined. You can select the following content types:

Specifies the content of the error template to use. You can use predefined fault handler variables to create the error template. A list of the predefined variables is available in the table below.

Specifies the error template to use as the default.

Specify the error variables to be used in the custom error message. To specify multiple error variables, use the plus button to add rows.

Select the payload type.

Selects the request payload type.

Selects the response payload type.

Specifies the name of the payload.

Specifies the details of the XPath expression in the API request.

Specifies the namespace of the XPath expression. To specify multiple namespaces , use the plus button to add rows.

The prefix for the namespace.

The namespace URI.

You can configure multiple ESB and XSLT processing steps. You can either log the error message sent by the native service without any changes or you can remove any critical information that you do not want Mediator to log or send to the client. The processing of these steps is taken up in the order in which they are configured.

String. Optional. Specify the XSLT file that you want to use to transform the service error response. Use the Choose button to browse to and select a file.

Default. String. Optional.

Specify the webMethods IS Service.

Invokes one or more webMethods IS services to manipulate the API fault after the Conditional Error Processing action is invoked. The IS service will have access to the entire API fault and the Conditional Error Processing message. You can make further changes to the fault message structure, if needed.

When the parameter is enabled, Mediator sends the native SOAP / REST failure message to the client. When you enable this parameter, the Failure Message is ignored when a fault is returned by the native API provider. (Faults returned by internal Mediator exceptions will still be handled by the Failure Message.)