JMS Provider

There are several services in Adeptia Connect that require JMS Provider to connect to JMS server. To connect to the JMS server, you need to specify the Provider Jar files while creating the JMS Provider. 

This section describes how to create a JMS Provider activity using the following details:

JMS Server Type

Apache Active MQ

Transfer Type

Secure

Provider JAR Files

activemq-core-5.7.0.jar, geronimo-j2ee-management_1.1_spec-1.0.1.jar

JNDI Factory

org.apache.activemq.jndi.ActiveMQInitialContextFactory

URL

tcp://localhost:61616

User Name

MyUserName

Password

Mypassword

Queue Connection Factory

QueueConnectionFactory

Topic Connection Factory

TopicConnectionFactory

Important

As the bundled Amazon Corretto JRE has been upgraded from Java version 8 to version 17 in AC v3.7.2, the JMS provider that connects to Apache Active MQ JMS server now uses the two jars activemq-core-5.7.0.jar, and geronimo-j2ee-management_1.1_spec-1.0.1.jar. Thus, you need to update any existing JMS provider that connects to Apache Active MQ JMS server to use these two jars.

Steps to create JMS Provider

  1. Click Configure > ACCOUNTS > JMS Provider.  

  2. Click Create JMS Provider
  3. Enter the name and description for the new JMS Provider in the Name and Description fields respectively.



  4.  Select the server type from the drop-down list of JMS Server Type.


    To know more on the JMS Server types supported by Adeptia Connect and their corresponding JAR files, JNDI Factory and URLs, refer Table 4.
  5. Click Upload Jars button to upload the driver jar files for the JMS Server. The Upload Jar Files screen is displayed.


    JMS Jar files are drivers, which are used to connect JMS Servers. There are specific jar files for different JMS Servers. These jar files are not provided with the Adeptia Connect. Users should use the jar files that are available with the JMS Servers.
  6. On the Upload Jar Files screen, click Choose File and select the geronimo-j2ee-management_1.1_spec-1.0.1.jar
  7. Click the Upload JAR button. The file name is displayed in under the heading File Names.
  8. Repeat the steps 6 and 7 to select and upload the activemq-core-5.7.0.jar. 
  9. Click the Finish button to return to the Create JMS Provider screen. The uploaded jar file(s) is displayed in the Provider Jar Files field.

    If required, you can also unload the JAR files. To unload jars files, click the Unload JAR button.
  10. Enter the JNDI Factory class name in the JNDI Factory field. For Example, in case of Apache ActiveMQ, the value is org.apache.activemq.jndi.ActiveMQInitialContextFactory.
  11. Enter the URL of the JMS Server in the URL field. For example, for Apache ActiveMQ running on the same server, use tcp://localhost:61616.
  12. Enter the username and password required to connect to JMS Server in the Userame and Password fields respectively.
  13. Re-enter the password in the Confirm Password field.
  14. Enter the JMS Provider Queue connection Factory in the Queue Connection Factory field. For example, in case of Apache ActiveMQ, Queue Connection Factory is QueueConnectionFactory.
  15. Enter the JMS Provider Topic Connection Factory in the Topic Connection Factory field. For example, in case of OpenJMS, Topic Connection Factory is TopicConnectionFactory.
  16. Enter the connection parameters and their values in the Additional Connection Parameters table if the JMS server that you are trying to connect to requires additional connection parameters. For example, you can enter the Topic and Queue details that will be used in the Source/Target/Event.


     
  17. Expand Advanced Properties and select the project of the activity in the Project field.



  18. Click Save.


The following table lists the types of JMS Server supported by Adeptia Connect and their corresponding JAR Files, JNDI Factory, and URL.
Table 4: JMS Server Types and corresponding JAR Files, JNDI Factory Names and URLs

Server Type

JAR Files

JNDI Factory

URL

Apache Active MQ

activemq-core-5.7.0.jar
geronimo-j2ee-management_1.1_spec-1.0.1.jar

org.apache.activemq.jndi.ActiveMQInitialContextFactory

tcp://localhost:61616

OpenJMS

openjms-0.7.7-beta-1.jar, 
penjms-common-0.7.7-beta-1.jar, 
openjms-net-0.7.7-beta-1.jar, 
openjms-tools-0.7.7-beta-1.jar, 
jndi-.2.1.jar, 
concurrent-1.3.4.jar, 
spice-jndikit-1.2.jar, 
derby-10.1.1.0.jar

org.exolab.jms.jndi.InitialContextFactory

tcp://localhost:3035

OracleAQ

aqapi.jar,ojdbc6.jar

oracle.jms.AQjmsInitialContextFactory

jdbc:oracle:thin:@{hostname}:{port}:{sid}

Oracle Weblogic

wlfullclient.jar

weblogic.jndi.WLInitialContextFactory

t3://localhost:7001

IBM WebSphere

com.ibm.mq.commonservices.jar, 
com.ibm.mq.defaultconfig.jar, com.ibm.mq.headers.jar, com.ibm.mq.jar, 
com.ibm.mq.jmqi.jar, com.ibm.mq.jms.Nojndi.jar, com.ibm.mqjms.jar, 
connector.jar, 
dhbcore.jar

com.ibm.mq.jms.Nojndi


 


Version of JAR files may vary depending on version of the JMS Servers you are using.