Creating a Java Message Service (JMS) broker

JMS messaging in HCL OneTest™ API supports publishing to destinations, topics, and queues, and each is managed by a separate transport. The configuration of all three, however, is identical. Only when you are selecting the different transports in a message editor do you see the option to publish/subscribe to a destination, topic, or queue.

The JMS transport is created when you create a physical JMS Broker resource in the Architecture School.

In Architecture School, you can create a resource in two ways:

Each physical JMS Broker resource represents a JMS transport that can be selected and configured later.