Versions Compared
Version | Old Version 8 | New Version 9 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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 |
Warning | ||
---|---|---|
| ||
For an existing JMS Provider to work, you need to edit it and replace the uploaded jars with 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 files. To upload new jars, refer to step 5 through 9jar. 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.
Info 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.Anchor 5 5 The Upload Jar Files screen is displayed.
Info 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.Info 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.
- Enter the username and password required to connect to JMS Server in the UserName and Password fields respectively.
- Re-enter the password in the Confirm Password field.
- 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.
Anchor | ||||
---|---|---|---|---|
|
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 | |
OpenJMS | openjms-0.7.7-beta-1.jar, | org.exolab.jms.jndi.InitialContextFactory | |
OracleAQ | aqapi.jar,ojdbc6.jar | oracle.jms.AQjmsInitialContextFactory | jdbc:oracle:thin:@{hostname}:{port}:{sid} |
Oracle Weblogic | wlfullclient.jar | weblogic.jndi.WLInitialContextFactory | |
IBM WebSphere | com.ibm.mq.commonservices.jar, | com.ibm.mq.jms.Nojndi |
Info |
---|
Version of JAR files may vary depending on version of the JMS Servers you are using. |
Panel | ||||
---|---|---|---|---|
| ||||
What is new |