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.

Steps to create a JMS Provider to connect to the Apache Active MQ server

The JMS provider being created here uses the Apache Active MQ server details furnished in the following table.

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 v4.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.

Click Configure > ACCOUNTS > JMS Provider.
Click Create JMS Provider.
Enter the name and description for the new JMS Provider in the textboxes Name and Description fields respectively.
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 to this section.
In the Provider Jar Files field, click Upload Jars.
The Upload Jar Files screen is displayed.

note that these jar files are not provided with Adeptia Connect. Use the jar files that are available with the JMS servers.
On the Upload Jar Files screen, click Choose File and select the geronimo-j2ee-management_1.1_spec-1.0.1.jar.
Click the Upload JAR button.
The file name is displayed in under the heading File Names.
Repeat the steps 6 and 7 to select and upload the activemq-core-5.7.0.jar.
Click the Finish 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.
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.
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.
Follow the steps below based on whether you want to fetch the secrets from the Hashicorp Vault or you want to enter the secrets manually.

To use Hashicorp Vault, you must enable Config Management feature and you may also need to do project mapping. For more details, refer to this page.
To fetch the secrets from the Hashicorp Vault, do the followings:

You can choose to use Hashicorp Vault for all or a specific field that need to contain secret.
1. In the Username field, enter the variable in the following format:
  ${Vault:<Key1>}
  Where, <Key1> is the key assigned to the username in the Hashicorp Vault.
  
  Each secret is maintained as a key-value pair in Hashicorp Vault.
2. Select the Use Vault checkbox next to the Password field if you want to use Vault for retrieving the password.
3. In the Password field, enter the variable in the following format:
  ${Vault:<Key2>}
  Where, <Key2> is the key assigned to the password in the Hashicorp Vault.
To enter the secrets manually, do the followings:
1. In the Username field, enter the username to connect to JMS Server.
2. In the Password field, enter the password.
3. In the Confirm Password field, re-enter the password.
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.
Enter the JMS Provider Topic Connection Factory in the Topic Connection Factory field. For example, in case of Apache ActiveMQ, Topic Connection Factory is TopicConnectionFactory.
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.
Expand Advanced Properties and select the project of the activity in the Project field.
Click Save.

Supported JMS servers

The following table lists the types of JMS servers supported by Adeptia Connect and their corresponding JAR Files, JNDI Factory, 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.

You may be interested in...

Supported JMS servers

What is newApplication architectureKey termsDeployUsage scenarios

What is new
Application architecture
Key terms
Deploy
Usage scenarios

Browser not supported