JBoss created a messaging bus called HornetQ. In 2015 the project was donated to Apache and is now a part of Apache ActiveMQ Artemis. This article will review how to connect to JBoss HornetQ v2.4 via the JMS remoting protocol.
HornetQ requires 17 jar files to be downloaded and added to your Boomi account. Instructions for loading jar files into your Boomi account can be found here. The links below are for Maven and the jars can be downloaded by clicking on jar next to Files. The two main jar files are jboss-remote-naming and hornetq-jms-client. The rest are dependencies.
Figure 1. Download jar files from Maven Repository.
hornetq-commons-2.4.7.Final.jar
hornetq-core-client-2.4.7.Final.jar
hornetq-jms-client-2.4.7.Final.jar
hornetq-journal-2.4.7.Final.jar
hornetq-native-2.4.7.Final.jar
jboss-ejb-client-1.0.13.Final.jar
jboss-jms-api_2.0_spec-1.0.0.Final.jar
jboss-logging-3.1.0.GA.jar
jboss-marshalling-1.3.0.GA.jar
jboss-marshalling-river-1.3.0.GA.jar
jboss-remote-naming-1.0.7.Final.jar
jboss-remoting-3.2.7.GA.jar
jboss-sasl-1.0.0.Final.jar
jgroups-3.3.4.Final.jar
netty-all-4.0.13.Final.jar
xnio-api-3.0.0.GA.jar
xnio-nio-3.0.7.GA.jar
Figure 2. JBoss HornetQ Custom Library.
Lastly, deploy the custom library, once all the jar files have been loaded into the Account Library and added to a Custom Library.
Figure 3. JBoss HornetQ Connection
Authentication: Used required authentication type
JMS Server Type: Generic JNDI
Connection Factory JNDI Lookup: jms/RemoteConnectionFactory
Initial Context Factory: org.jboss.naming.remote.client.InitialContextFactory
Provider URL: remote://<host>:<port>
Additional properties for disabling SSL. Only use these settings if SSL is disabled on the HornetQ server.
jboss.naming.client.remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
jboss.naming.client.connect.options.org.xnio.Options.SSL_STARTTLS=false
jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false
The article was originally posted at Boomi Community.