Generating an MQ import binding with either a one-way operation or request-response operation is shown in this section. Once generated, the binding properties are discussed.
Beneath End-point Configuration, select Specify properties for configuring WebSphere MQ resources (the default) or Specify JNDI name for pre-configured WebSphere MQ resources. If you choose pre-configured, then add the JNDI names for the connection factory and the send destination for a one-way operation, and send and receive destinations for a request-response operation. Typically, you would choose pre-configured if your system administrator had set up the configuration for you.
For Connection Mode, select between Use host client connection property, where you specify the host name, server channel and port, or Use client channel definition table (CCDT), where these values are specified in the table.
In the Data format section, select how the data will be serialized between the business object and the message. The default data bindings are Unstructured Text Message and Unstructured Binary Message for unstructured text and byte messages, and Serialized as XML and Serialized Java Object for XML and Java objects. In the case of XML, your wrapped data objects must be a complex type; they can not be a simple type.
The alternative is for you to provide your own data binding, in which case select User Supplied. The implementation has to conform to the MQ data binding interface. Click OK. The basic MQ binding is created and shown in the properties view when the Binding tab is selected.
You do not see a selection for a messaging domain such as point-to-point or publish-subscribe because the binding generator only supports point-to-point. The MQ JMS binding, however, does support publish-subscribe.
In the Request Message ID Options field, New Message ID lets the queue manager select a unique message ID for the request (default). Copy from SCA message sets the message ID to be the same as the one carried in the headers of the SCA message or create one if not found.
Set message type to MQMT_DATAGRAM or MQMT_REQUEST for request-response operation means you have the option of overriding the MessageType field.Override reply to queue of request message means you have the option of overriding the ReplyTo. The import will, by default, force the ReplyTo and MessageType fields to be appropriate values. Advanced users can switch this off, but you will have to use a mediation module to set the fields to whatever you want. Since you can easily break the import by getting these fields wrong, it is recommended you leave these options checked.
In the Response Correlation Schema field, Correlation ID copy from Request Message ID (default) means the response message's correlation ID will be set to the request message's message ID. Response Message ID copy from Request Message ID means the response message will have a message ID field set to the request message's message ID. Correlation ID copy from Request Correlation ID means the response message will have a correlation ID set to the request message's correlation ID.
The Response Message Correlation field is what we expect the receiving MQ application to do. If it does not do this the MQ import can not correlate requests and replies.