Configuring Global Service Fault Responses

Administering Mediator : Mediator Configurations : Configuring Global Service Fault Responses

Configuring Global Service Fault Responses for All Virtual Services

You can use these options to configure global error responses for all virtual services or virtual APIs.

Alternatively, you can configure each virtual service or virtual API individually, as follows:

For a virtual service, you can configure an Error Messaging step on the virtual service’s Response Processing tab, as described in the CentraSite User’s Guide.

For a virtual API, you can configure a Custom SOAP Response Message action for the virtual API, as described in the CentraSite User’s Guide.

The precedence of the error or response messaging instructions is as follows:

If you configure an Error Messaging step or a Custom SOAP Response Message action, that step or action takes precedence over any settings on the global Service Fault Configuration page.

If you do not configure an Error Messaging step or a Custom SOAP Response Message action, the settings on the global Service Fault Configuration page take precedence.

Note:

By default, when Mediator receives 4xx error codes from the native services, Mediator sends 500 error codes to the client. If you want Mediator to send the 4xx error codes to the client, go to:

Integration Server_directory\instances\instance_name\packages\WmMediator\config\resources\beans\pg-core.xml

and set the handleClientErrorCode property for the following bean to true:

When the handleClientErrorCode property is set to true, the following native service response error codes is sent to the client: 400, 401 (if the request returns the user), 403, 406, 407, 408, 409, 412, 413, 415, 416, 417. For all other error codes, error code 500 is sent back to the client.

Contact Support | Community | Feedback