Extending the JMS Nodes sample

The JMS nodes can be used as a consumer (JMSInput) or as a producer (JMSOutput) in both publish/subscribe and point-to-point messaging. You can change both message flows in the JMS Nodes sample to connect to another JMS provider.

To connect to another JMS provider, you must make the following changes:

  1. Redefine the administered objects in your JMS provider of choice, and save the bindings file in the directory on the computer on which the integration node is installed.
  2. Change the properties of the JMSInput node and the JMSOutput node to point to the directory that contains the bindings file. Do not point to the bindings file itself.
  3. Modify or remove the Mapping node if you do not plan to do message manipulation, or if you want to change the functions.
  4. Modify the Java driver code IP subscriber and add other files to fit your new scenario.
  5. Create a broker archive (BAR) file to contain your modified message flow.
  6. Deploy the BAR file to the broker.
  7. Run the modified sample code or use your own producers and consumers for the new flow.

Performance Harness for Java Message Service

If you want to extend the sample or test any JMS Node flow with WebSphere MQ, or any other JMS provider, then you might find the Performance Harness tool useful as a way to send and receive JMS messages. The tool also has the capability to send and receive WebSphere MQ messages, therefore, it is useful for testing JMS Node flows that include transformations to and from WebSphere MQ. The documentation for the tool contains examples of how to use it to send and receive messages to and from a JMS provider.

For information about the Performance Harness tool, see This link opens in a new window Performance harness.

Back to sample home