Configuring Global Service Fault Responses for All Virtual Services

Field	Description
Default Fault Response	When you select this option, Mediator returns the following fault response to the consuming application: Mediator encountered an error:$ERROR_MESSAGE while executing operation:$OPERATION service:$SERVICE at time:$TIME on date:$DATE. The client ip was:$CLIENT_IP. The current user:$USER. The consumer application:$CONSUMER_APPLICATION". The fault response contains predefined fault handler variables that are described in The Fault Handler Variables. This fault response is returned in both of the following cases: In cases where a fault is returned by the native service provider. In this case, the $ERROR_MESSAGE variable in the fault response contains the message produced by the provider's exception that caused the error. Mediator discards the native service provider's fault and does not return this content to the web service caller since it could be considered a security issue, especially if the native provider is returning a stack trace with its response. In cases where a fault is returned by internal Mediator exceptions (policy violation errors, timeouts, and so on). In this case, the $ERROR_MESSAGE variable contains the error message generated by Mediator. You can customize the default fault response using the following substitution variables, where Mediator replaces the variable reference with the real content at run time: Mediator's predefined context variables. Custom context variables that you declare using the Mediator API. For details about the predefined and custom context variables, see CentraSite User’s Guide.
Send Native Provider Fault	When you select this option, Mediator sends the native service provider's fault content, if available. Mediator sends whatever content it received from the native service provider. If you select this option, the Default Fault Response is ignored when a fault is returned by the native service provider. (Faults returned by internal Mediator exceptions are handled by the Default Fault Response option.)

Note: Unlike with SOAP specifications, there is no agreed upon format to suggest an error condition for XML and REST services (that is, there is no element nested in a </soap:Fault> element nested in a </soap:Body>). Mediator assumes that XML and REST services follows HTTP conventions and return responses with return codes in the 200-299 range when service calls are successful. This is the only way Mediator can determine that a native provider's response must be interpreted as a failure.