Kafka messages sometimes remain unprocessed by a JMS source for unexplained reasons. To ensure that all the Kafka messages are consumed and published successfully Adeptia Connect integrates Apache Kafka using which the application components can create, send, receive, and read messages using reliable communication.
...
Click Configure > ACCOUNTS > Kafka.
- Click Create Kafka account.
- In Create Kafka Account window, do the following:
- In the Name and Description fields, enter the name and description for the new Kafka account respectively.
- In the Broker field, enter the URL of the Kafka brokers, foe example, host1:port1,host2:port2.
In the Security Protocol field, enter the protocol used to communicate with brokers.
Tip The supported protocols are PLAINTEXT and SSL.
In case you select SSL, you need to select a Keystore in the Select Keystore field.In the Addon Configuration window, enter the Add On Configurations to be used in back end for performing operation on Kafka server (e.g. param1=value,param2=value..).
Note Here you can use properties which are not listed on this Kafka account creation interface, for example, you may need to use a property called Serializer that converts the data to bytes. You can find the properties available at this location. - In the Select Project field, select the project.
- Click Save.
...
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.
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.
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.
- Expand Advanced Properties and select the project of the activity from the drop-down list of Project.
- Click Save.
...
Server Type | JAR Files | JNDI Factory | URL |
Apache Active MQ | activemq-all-5.7.0.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 |
|
Version of JAR files may vary depending on version of the JMS Servers you are using.
...