Using JMS in IBM App Connect Enterprise
Use IBM® App Connect Enterprise to connect to applications that send and receive messages that conform to the Java™ Message Service (JMS) standard.
You can use the built-in JMS nodes in IBM App Connect Enterprise to support the following operations:
- Receive a JMS message as input.
- Receive a JMS message in the middle of a message flow.
- Create a JMS message for output.
- Work with message flows that do not expect JMS messages.
All JMS messages must conform to the Java Message Service Specification version 1.1 or 2.0.
You can create message flows to receive messages from JMS destinations, and send messages to JMS destinations. These destinations are accessible through a connection to a JMS provider. In sending and receiving messages, the JMS nodes behave like JMS clients.
You can also use two transformation nodes, the JMSMQTransform node and the MQJMSTransform node, with the JMSInput, JMSReceive and JMSOutput nodes so that they can interact with nodes that expect a propagated message to contain an MQMD (and MQRFH2) header.
- The JMSMQTransform node takes the output of the JMSInput or JMSReceive node, and produces a message that can be handled by an MQOutput node.
- The MQJMSTransform node transforms a message with an MQMD (and optional MQRFH2) header into a message that is expected by the JMSOutput node.
If you want to change or add content to the headers in JMS messages, you can include a JMSHeader node in the message flow to modify fields without programming.
You can configure the JMS nodes to work with the IBM MQ JMS provider, WebSphere® Application Server, and all JMS providers that conform to the Java Message Service Specification version 1.1 or 2.0. IBM App Connect Enterprise supports Java 7(also known as Java 1.7).