Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are several services in Adeptia Connect that require JMS Provider is used to connect to JMS Server. While creating JMS Providerserver. To connect to the JMS server, you need to specify the Provider Jar files , which are used to connect to JMS Server. There are several services of Adeptia Connect, which require JMS Provider to connect to JMS Server.while creating the JMS Provider. 

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

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

activemq-

all

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

Steps to create JMS Provider


Warning
titleImportant

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.

  1. Click Configure > ACCOUNTS > JMS Provider.  

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

  4.  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 Table 4.
    Click Upload Jars button to upload the driver jar files for the JMS Server.
  5. Anchor
    5
    5
    In the Provider Jar Files field, click Upload Jars.

    The Upload Jar Files screen is displayed.

     


    Info
    JMS Jar files are drivers, which are used to connect JMS Servers. There are specific jar files for different JMS Servers. These note that these jar files are not provided with the Adeptia Connect. Users should use Use the jar files that are available with the JMS Serversservers.


  6. Click the Browse button and select the required jar files. The path of the selected jar file is displayed in the Browse File field.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 list.
  8. Repeat the steps to upload additional jar files.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 screenProvider screen.
    The uploaded jar file(s) is displayed in the textbox  Provider Jar Files field.


    Info
    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 as specified by the JMS Provider in the textbox  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 field. For example, for Apache ActiveMQrunning ActiveMQ running on the same server, use tcp://localhost:61616.
  12. Enter the username and password required to connect to JMS Server in the textboxes UserName and Password respectively.
  13. Re-enter the password in the textbox Confirm Password

    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.

    Info

    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.


  14. To fetch the secrets from the Hashicorp Vault, do the followings:

    Info

    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. 

      Tip

      Each secret is maintained as a key-value pair in Hashicorp Vault.

      Image Added

    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.


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

  16. 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.
  17. Enter the JMS Provider Topic Connection Factory in the Topic Connection Factory field field. For example, in case of OpenJMSApache ActiveMQ, Topic Connection Factory is TopicConnectionFactory.
  18. The above example is only applicable in case of Apache MQ. If we use the Apache Active MQ as JMS Server then we can define

    In case the JMS Server, which 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, the enter those connection parameters and their values in the Additional Connection Parameters table.
    Image Removed

     

    . For example, you can enter the Topic and Queue

    name (which

    details that will be used in the Source/Target/Event

    ) in the Additional Connection parameter table

    .

    Image Added

     
  19. Expand Advanced Properties and select the project of the activity from in the drop-down list of  Project field.



  20. Click Save.

Anchor
JMS servers
JMS servers
Supported JMS servers

The following table lists the types of JMS Server servers 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 URLsURLs.

Server Type

JAR Files

JNDI Factory

URL

Apache Active MQ

activemq-

all

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


 
 


 

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



Panel
borderStylesolid
titleYou may be interested in...
What is new
Application architecture
Key terms
InstallDeploy
Usage scenarios