JMS V2 connection: ActiveMQ Classic

By enabling ActiveMQ Classic, the JMS V2 connector can connect to the ActiveMQ Classic provider.

To enable ActiveMQ Classic, upload the following JAR files into your account library (Settings > Development Resources > Account Libraries), add those files to a JMS type Custom Library component, and deploy the component to the appropriate basic runtime, runtime cluster, runtime cloud, or environment.

• activemq-broker.jar — located in the <activemq_home>/lib directory.

• activemq-client.jar — located in the <activemq_home>/lib directory.

• geronimo-spec-j2ee-management.jar — located in the <activemq_home>/lib directory.

Upload the JAR files into your Integration account library (Settings > Development Resources > Account Libraries). For more information, refer to Creating a Custom Library component, and Custom library deployment considerations to deploy the appropriate basic runtime, runtime cluster, runtime cloud, or environment. Uploaded or imported files first pass through a virus scanner. The upload or import results in an error if it detects a virus, and then rejects the file. If an error persists, contact Boomi Support.

note

Uploaded or imported files pass through a virus scanner first. If the scan detects a virus, you receive an error message, and the scan rejects the file. If an error persists, contact Boomi Support.

Communication Options tab

Server Type - Select ActiveMQ Classic to see default settings specific to ActiveMQ Classic are available.

Connection Factory JNDI Lookup - Set to ConnectionFactory.

Initial Context Factory - A text field where users can input their JNDI initial context factory object into.

Provider URL - A text field where users can input the URL to point to your ActiveMQ Classic server to.

JMS Properties - (Optional) Used to add JMS property names and values.