Here are some settings required for working with the following popular endpoints:
How to configure JMS for ActiveMQ without SSL
Configuring JMS for ActiveMQ
Property Name | Property Value |
---|
java.naming.factory.initial | org.apache.activemq.jndi.ActiveMQInitialContextFactory |
java.naming.provider.url | tcp://localhost:61616
|
topic.jms/topic/dataTopic | TOPIC.DATATOPIC |
topic.jms/topic/controlTopic | TOPIC.CONTROLTOPIC |
queue.jms/queue/dataQueue | QUEUE.DATAQUEUE |
queue.jms/queue/controlQueue | QUEUE.CONTROLQUEUE |
connectionFactoryNames | connFact |
How to Configure JMS for Connecting to ActiveMQ via SSL
Configuring JMS for Connecting to Active MQ via SSL
- Add Active MQ server's certificate to plex's trust store.
Attach the .bindings file that is created by the Active MQ SME and is provided with the server's certificate.
The Connection Factory property fetches the value from the .bindings file.
Provide all the necessary JAR files belonging to the Active MQ client, or it might fail to validate.
Each version of the Active MQ client uses different JRE levels. If the version of Active MQ is 5.15.10, use the 5.15.10 JRE files.
Include the following JAR files while configuring the account:
- activemq-all-5.15.10.jar
- commons-logging-1.2.jar
- commons-codec-1.9.jar
- httpclient-4.5.2.jar
- httpcore-4.4.4.jar
- xtream-1.4.11.1.jar
- Upload these libraries(JAR files) to the Shared project for the JMS account.
Configure the following JVM options, and then start the JCC.
Property Name | Property Value |
---|
java.naming.factory.initial | org.apache.activemq.jndi.ActiveMQInitialContextFactory |
java.naming.provider.url | https://<machine_name>:8443 |
How to configure JMS for ApolloMQ
Configuring JMS for ApolloMQ
Property Name | Property Value |
---|
java.naming.factory.initial | org.apache.activemq.jndi.ActiveMQInitialContextFactory |
java.naming.provider.url | tcp://localhost:61613
|
topic.jms/topic/dataTopic | topic.dataTopic |
topic.jms/topic/controlTopic | topic.controlTopic |
queue.jms/queue/dataQueue | queue.dataQueue |
queue.jms/queue/controlQueue | queue.controlQueue |
connectionFactoryNames | connFact |
Note: ApolloMQ is REST based. It can be configured using Web Console. While creating a topic/queue, we must provide just name. This name is used both as the property name and property value.
How to set up JMS for JBoss HornetQ without SSL
Configuring JMS for JBoss HornetQ
Configuring the HornetQ Account
Update the Account popup with the following settings:
Label | Required. Enter a label for the new account. Default value: None. |
---|
Username | Enter the username associated with your HornetQ account. Default value: None. |
---|
Password | Enter the password associated with the username entered in the Username field. Default value: None. |
---|
Connection Factory | Required. This is the Java Naming and Directory Interface (JNDI) name for the JMS connection factory. you can find this information in the configuration file associated with the HornetQ installation.
Default value: None. |
---|
JNDI Properties | Required. Enable you to specify details, such as the JNDI server name, which will enable SnapLogic to connect to HornetQ. You need to configure these are pairs of Property Name and Property Value. These properties and values must be configured as shown below:
|
---|
Property Name | Required. This is the name of the JNDI property required for JNDI to work. These names can be picked up from the JNDI configuration file. Default value: None. |
---|
Property Value | Required. This is the location of the package that contains information related to this property. Default value: None. |
---|
Jar files | Required. These are the JAR files that must be present; else HornetQ will not work. Default value: None. The typical list of JAR files associated with HornetQ are as follows. These files are available once HornetQ is installed on your server. You need to navigate to the directory where you installed HornetQ and upload these files to SLDB:
|
---|
How to set up JMS for JBoss HornetQ via SSL
Configuring JMS for Connecting to HornetQ via SSL
- Import HornetQ server's certificate to plex's trust store by using the following command:
-import -file ~/client.cer -keystore broker.ts1 -storepass
- Attach the hornetq-configuration.xml file that is created by the HornetQ SME and is provided with the server's certificate.
Edit the hornetq-configuration.xml file that you imported from the server.
Edit connectors.
Edit acceptors.
In the JMS.xml file, add one Connection Factory.
The Connection Factory property fetches the value from the JMS.xml file.
- Optionally, create a simple pipeline with a File Reader Snap to verify that you can access the .xml file.
Provide all the necessary JAR files belonging to the HornetQ client, or it might fail to validate.
Each version of the HornetQ client uses different JRE levels. If the version of HornetQ is 1.8, use the 1.8 JRE files.
The typical list of JAR files associated with HornetQ are as follows. These files are available once you install HornetQ on your server. You need to navigate to the directory where you installed HornetQ and upload these files to SLDB:
- Upload these libraries(JAR files) to the Shared project for the JMS account.
How to set up a JMS account for IBM WebSphere MQ without SSL
Configuring JMS for IBM WebSphere MQ
Property Name | Property Value |
---|
java.naming.factory.initial | com.sun.jndi.fscontext.RefFSContextFactory |
java.naming.provider.url | file:///home/ubuntu/JNDI-Directory |
java.naming.security.authentication | none |
hostname | 127.0.0.1 |
port | 1414 |
queueManager | qManager |
channel | mqCientConnChannel |
transportType | 1 |
clientReconnectTimeout | 2 |
clientReconnectOptions | 0 |
Jar Files
Include the following JAR files while configuring the account:
- com.ibm.mq.defaultconfig.jar
- com.ibm.mq.postcard.jar
- providerutil.jar
- fscontext.jar
- com.ibm.mq.traceControl.jar
- com.ibm.mqjms.jar
- com.ibm.mq.jmqi.jar
- com.ibm.mq.pcf.jar
- com.ibm.mq.headers.jar
- bcpkix-jdk15on.jar
- bcprov-jdk15on.jar
- com.ibm.mq.tools.ras.jar
- com.ibm.mq.commonservices.jar
- com.ibm.mq.jar
- com.ibm.mq.allclient.jar
How to set up a JMS account for IBM WebSphere MQ via SSL
Configuring JMS for Connecting to IBM WebSphere MQ via SSL
- Add IBM MQ server's certificate in plex's trust store.
Attach the .bindings file that iscreated by the WebSphere MQ SME and is provided with theserver's certificate.
The Connection Factory property fetches the value from the .bindings file.
- Optionally, create a simple pipeline with a File Reader Snap to verify that you can access the .bindings file.
Provide all the necessary JAR files belonging to the WebSphere MQ client, or it might fail to validate.
Each version of the WebSphere MQ client uses different JRE levels. If the version of WebSphere MQ is 1.8, use the 1.8 JRE files.
The typical list of JAR files associated with WebSphere MQ are as follows. These files are available once you install WebSphere MQ on your server. Navigate to IBMMQ/MQServer/lap/jre/ibm-java-x86_64-80/jre/lib, where you installed WebSphere MQ, and upload these files to SLDB:
- Upload these libraries(JAR files) to the Shared project for the JMS account.
- Configure the following JVM options, and then start the JCC.
com.ibm.mq.cfg.useIBMCipherMappings: false
javax.net.ssl.trustStore: <Path of the truststore containing the server certificate>
javax.net.ssl.trustStorePassword - <truststore password>
Property Name | Property Value |
---|
java.naming.factory.initial | com.sun.jndi.fscontext.RefFSContextFactory |
java.naming.provider.url | file:///home/ubuntu/JNDI-Directory |
java.naming.security.authentication | none |
hostname | 127.0.0.1 |
port | 1414 |
queueManager | qManager |
channel | mqCientConnChannel |
transportType | 1 |
clientReconnectTimeout | 2 |
clientReconnectOptions | 0 |