JMS Provider is used to connect to JMS Server. While creating JMS Provider, 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.

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-all-5.7.0.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

Go to ACCOUNTS and click Manage Objects.
Click ACCOUNTS > JMS Provider.
Click Create JMS Provider. The Create JMS Provider screen is displayed.
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 Table 4.
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.
Click the Browse button and select the required jar files. The path of the selected jar file is displayed in the Browse File field.
Click the Upload JAR button. The file name is displayed in under the heading File Names list.
Repeat the steps to upload additional jar files.
Click the Finish button to return to the Create JMS Provider screen. The uploaded jar file(s) is displayed in the textbox Provider Jar Files.

If required, you can also unload the JAR files. To unload jars files, click the Unload JAR button.
Enter the JNDI Factory class name as specified by the JMS Provider in the textbox JNDI Factory. 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 ActiveMQrunning on the same server, use tcp://localhost:61616.
Enter the username and password required to connect to JMS Server in the textboxes UserName and Password respectively.
Re-enter the password in the textbox Confirm 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 OpenJMS, Topic Connection Factory is TopicConnectionFactory.
In case the JMS Server, which you are trying to connect, requires additional connection parameters, the enter those connection parameters and their values in the Additional Connection Parameters table.

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 the Topic and Queue name (which will be used in the Source/Target/Event) in the Additional Connection parameter table.
Expand Advanced Properties and select the project of the activity from the drop-down list of Project.
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-all-5.7.0.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.

Browser not supported