Skip navigation
Toggle Sidebar

JMS Connector

Note: Before working with the JMS connector, you should be familiar with general Process Development

The JMS Connector is designed in such a way that it is able to be configure to work with any JMS (v1.1) messaging provider. It allows you to send and receive messages from JMS queues or topics. The connector has support for transactions, durable/non-durable topic subscriptions, configurable receive timeouts, message selectors and custom message properties.

In most cases, each JMS provider is going to have provider specific jars that are needed for the messaging to work. The JMS Connector supports this by allowing users to place any required jars in the ../<Atom install root>/userlib/jms directory. If the directory doesn't exist, create it and make sure that it is reachable by the Atom (i.e. the permissions are correct). The JMS Connector will inspect this directory and use any jar files it finds.

Connector Configuration

Configuring a connector to communicate with your JMS provider requires the setup of two different components:

This design allows for reusability of the components, which contain connection settings such as user name, password, etc. Once your connection and connector operation are built, you will need to set up your connector within the process model. When your connector is configured properly within your process, Boomi AtomSphere will be able to map to and from virtually any system using the JMS connector to send and receive data from your JMS provider.

JMS Connection (Boomi AtomSphere)
JMS Operation (Boomi AtomSphere)

Adaptavist Theme Builder Powered by Atlassian Confluence