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 types of messaging. You can easily change both message flows in the JMS Nodes sample to connect to another JMS provider.
To connect to another JMS provider, you would need to make the following changes:
- Redefine the administered objects in your JMS provider of choice,
and save the bindings file in a directory on the computer on which the
broker is installed.
- Change the properties of the JMSInput node and the JMSOutput node to point to
the directory where the new bindings file is. Do not point to the
bindings file itself.
- Modify or remove the Compute node and the ESQL code if you do not
plan to do message manipulation, or if you want to change the functionality.
- Modify the Java driver code IP subscriber and add other files to
fit
your new scenario.
- Create a broker archive (BAR) file to contain your modified
message flow.
- Deploy the BAR file to the broker.
- 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 indeed test any JMS Node flow with MQ, or any other JMS Provider, then you may find the following tool useful as a simple way to send and receive JMS messages. The tool also has the capabilities to send and receive WebSphere MQ messages so is ideal to test JMS Node flows which include transformations to/from Websphere MQ. The documentation for the tool contains examples of how to run it to send/receive messages to/from a JMS Provider.
Performance harness
Back to sample home