Kafka

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.

To use Apache Kafka, you need to create a Kafka account and define a Kafka listener and a target. Kafka messages can be consumed and published by a template, transaction, or process flow. 

Creating Kafka Account

Kafka account is used to connect with Kafka Server. While creating Kafka account, you need to specify the Provider Jar files, which are used to connect to Kafka Server. 

1. Click Configure > ACCOUNTS > Kafka.  

2. Click Create Kafka account. 
3. In Create Kafka Account window, do the following:
   1. In the Name and Description fields, enter the name and description for the new Kafka account respectively.
   2. In the Broker field, enter the URL of the Kafka brokers, foe example, host1:port1,host2:port2.

   3. In the Security Protocol field, enter the protocol used to communicate with brokers.

      The supported protocols are PLAINTEXT and SSL.
      
      In case you select SSL, you need to select a Keystore in the Select Keystore field.

   4. 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..).
      

      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.

       

   5. In the Select Project field, select the project.
   6. Click Save.
   
   
   

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

2. Click Upload Jars button to upload the driver jar files for the JMS Server. The UploadJar 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.

3. Click the Browse button and select the required jar files. The path of the selected jar file is displayed in the Browse File field.
4. Click the Upload JAR button. The file name is displayed in under the heading File Names list.
5. Repeat the steps to upload additional jar files.

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

7. 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.
8. Enter the URL of the JMS Server in the URL field. For example, for Apache ActiveMQrunning on the same server, use tcp://localhost:61616.
9. Enter the username and password required to connect to JMS Server in the textboxes UserName and Password respectively.
10. Re-enter the password in the textbox Confirm Password.
11. 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.

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

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

14. Expand Advanced Properties and select the project of the activity from the drop-down list of Project.
    
    
    
    
15. 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

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

Services

Account

Listener

Activate/Deactivate Kafka Listener

Target

Using Kafka in a Template

Using Kafka in a Process Flow

Publish Process Flow to Consume messages from Kafka Server

QuickBooks is the #1 rated small business accounting software.

QuickBooks features several innovative functions such as remote access capabilities, remote payroll assistance and outsourcing, electronic payment functions, online banking and reconciliation, mapping features through integration with Google Maps, marketing options through Google, and improved e-mail functionality through Microsoft Outlook and Outlook Express. In addition, you can import data from Excel spreadsheets, use additional employee time to track, and make use of pre-authorization of electronic funds.

For more information, click here.

Field (Account) Information

While configuring the Source or Destination of a Template or Transaction, you need to create an account to configure your application with Adeptia Connect. While creating an account, you need to specify the location from where Adeptia Connect will access the data.

Click  to add an account.