IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with messaging systems > WebSphere MQ (WMQ) > WebSphere MQ data bindings
Prepackaged JMS and MQ fault selectors
Fault selectors handle runtime exceptions. Some fault selectors come ready to use with the JMS, MQ JMS, generic JMS and MQ bindings.
You can configure your import and export bindings to handle faults (for example, business exceptions) that occur during processing. A fault handler can be set up at three levels: you can associate a fault handler with a fault, with an operation, or with a binding. For import bindings, you can also set up a fault selector to determine whether a response is a fault and, if so, the name of the fault. See Handling faults in bindings for more information.
Prepackaged JMS and MQ fault selectors Fault selectors Description Header-based fault selector A header-based fault selector examines the headers in the incoming response message to determine if the response message is a business fault, a runtime exception or a normal message. SOAP fault selector A SOAP fault selector examines the body of the incoming response message for the fault message and examines the SOAP header to determine if the fault is a business or runtime fault, and the fault name in the case of a business fault. See SOAP fault selector.
You can also create a new fault selector resource configuration.
JMS, MQ JMS and generic JMS bindings
Related concepts:
Prepackaged JMS data format transformations
JMS function selectors
Prepackaged MQ data format transformations
Prepackaged MQ function selectors
Related reference:
Overview of JMS, MQ JMS and generic JMS bindings
Data handlers
Work with the simple JMS data bindings
Business object XML using JMS text message serialization
Overview of MQ data format transformations
Overview of the MQ function selectors