Put a Message in an Inbound Queue

This use case describes how to create an integration that uses the IBM MQ Series JMS Adapter to put a message in an inbound queue (for this example, named INQ). From the inbound queue, the message is consumed as a text message and published to an outbound topic (for this example, named TOPIN).

1. Configure the IBM MQ Series JMS Adapter on the Connections page.
2. Create the an application-driven integration. This is the first of two integrations you create. The second is described in the second use case. See Use a Topic to Subscribe to a Message.
3. Add the IBM MQ Series JMS Adapter as a trigger connection in the integration.
   The Adapter Endpoint Configuration Wizard is displayed.
4. On the Basic Info page, Queue for the Destination Type is selected.
5. On the Configuration page, the following details are specified for this use case. Your selections can vary.
   • A queue of your choice for the Destination Name (for this example, INQ is selected).
   • TextMessage for the Message Type value.
   • JMSPriority=8 for the Message Selector value. This means that only messages with a priority of 8 are consumed.
   • Yes for the Do you want to specify the structure for the payload value.
   • A schema of your choice for the Schema File value (for this example, singleString.xsd is selected).
6. On the Headers page, JMSType for the standard header and department for the custom header are selected.
7. Add the IBM MQ Series JMS Adapter as an invoke connection in the integration.
8. On the Basic Info page, Topic for the Destination Type value is selected.
9. On the Configuration page, the following details are specified for this use case:
   • TOPIN for the Destination Name value.
   • TextMessage for the Message Type value.
   • Priority [0 - 9] for the Message Selector value.
   • Yes for the Do you want to specify the structure for the payload value.
   • singleString.xsd for the Schema File value.
10. On the Headers page, JMSPriority and JMSType for the standard headers and department for the custom header are selected. These headers are captured from the inbound queue and assigned to the outbound topic.
11. In the mapper, the following mappings are specified:
    • Source JMSType element is mapped to the target JMSType element.
    • Source JMSProperty department element is mapped to the target JMSProperty department element.
    • Target JMSPriority element is manually set to 4. When the message is received in the inbound queue, a check is made to see if the JMSPriority is 8. If it is, it is set to a JMSPriority of 4 to show the setting of the JMS headers for the outbound topic.