Prepackaged MQ function selectors

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 MQ function selectors

Several MQ function selectors come with the product.
The following prepackaged MQ function selectors are available.
If that selections are filtered. If you only had one operation, for example, then the one operation function selector would be available.

Prepackaged function selectors
Function selector Description
MQ handleMessage function selector This function selector (default) returns handleMessage as a value. The value is mapped using the export's method bindings to the name of an operation on the interface. The native method is assumed to be handleMessage from the SCA application's perspective. The SCA application does not need to understand the internal representation of the MQ message, but only how it drives the current operation on the interface. It is the recommended selection for most applications. It may be necessary to edit one of the method bindings to bind an operation to the handleMessage native function.
MQ uses JMS default function selector This function selector means that the JMS function selector is used to create a method in your export binding. The name of the method will be the interface operation name. This function selector reads the native operation from the TargetFunctionName property of the folder of an MQRFH2 header. This function selector is configurable with a data handler.
MQ uses message body format as native function This function selector finds the Format field of the last header and returns that field as a String.
MQ type function selector This function selector creates a method in your export binding by retrieving a URL containing the Msd, Set, Type and Format properties found in the MQRFH2 header. The name of the method will be the interface operation name. This selector can by used to interoperate with messages coming from MQ JMS clients and WebSphere Business Integration Message Broker flows.
MQ service gateway function selector This function selector should be used in conjunction with a binding using the service gateway interface. It uses the MsgType property in the MQMD header to determine the operation name.
One operation function selector

MQ data bindings

Related concepts:
Prepackaged MQ data format transformations

Related reference:
Overview of MQ data format transformations
Data handlers
Overview of the MQ function selectors
Prepackaged JMS and MQ fault selectors

Function selector	Description
MQ handleMessage function selector	This function selector (default) returns handleMessage as a value. The value is mapped using the export's method bindings to the name of an operation on the interface. The native method is assumed to be handleMessage from the SCA application's perspective. The SCA application does not need to understand the internal representation of the MQ message, but only how it drives the current operation on the interface. It is the recommended selection for most applications. It may be necessary to edit one of the method bindings to bind an operation to the handleMessage native function.
MQ uses JMS default function selector	This function selector means that the JMS function selector is used to create a method in your export binding. The name of the method will be the interface operation name. This function selector reads the native operation from the TargetFunctionName property of the folder of an MQRFH2 header. This function selector is configurable with a data handler.
MQ uses message body format as native function	This function selector finds the Format field of the last header and returns that field as a String.
MQ type function selector	This function selector creates a method in your export binding by retrieving a URL containing the Msd, Set, Type and Format properties found in the MQRFH2 header. The name of the method will be the interface operation name. This selector can by used to interoperate with messages coming from MQ JMS clients and WebSphere Business Integration Message Broker flows.
MQ service gateway function selector	This function selector should be used in conjunction with a binding using the service gateway interface. It uses the MsgType property in the MQMD header to determine the operation name.
One operation function selector