Supporting Different Transports

Follow the steps mentioned below to add support for each transport type

MQTT Transport

Download MQTT client library (mqtt-client-0.4.0.jar).
Add the JAR to the <PRODUCT_HOME>/repository/components/lib/ directory.

Kafka Transport

Download Apache Kafka server.

This guide uses Kafka 2.10-0.8.2.1 version.
Copy the following client JAR files from <KAFKA_HOME>/libs/ directory to <PRODUCT_HOME>/repository/components/lib/ directory.

- kafka_2.10-0.8.2.1.jar
- zkclient-0.3.jar
- scala-library-2.10.4.jar
- zookeeper-3.4.6.jar
- metrics-core-2.2.0.jar
- kafka-clients-0.8.2.1.jar

The above jars are the client jars for Kafka 2.10-0.8.1. If you want to use the client jars for Kafka_2.10-0.9.0.1 or Kafka_2.11-0.9.0.1, the following needs to be done.

Copy the following client JAR files from <KAFKA_HOME>/lib/ directory to <PRODUCT_HOME>/repository/components/lib/ directory.
- kafka_2.11-0.9.0.1.jar
- kafka-clients-0.9.0.1.jar
- metrics-core-2.2.0.jar
- scala-library-2.11.7.jar
- scala-parser-combinators_2.11-1.0.4.jar
- zkclient-0.7.jar
- zookeeper-3.4.6.jar
Download the jass.conf file and save it in the <PRODUCT_HOME>/repository/conf/identity directory.

Kafka_2.10-0.9.0.1 is backward compatible. Therefore, you can use Kafka_2.10-0.8.2.1 client jars to connect with Kafka_2.10-0.9.0.1.

SMS Transport

Download and copy following libraries to <PRODUCT_HOME>/repository/components/lib/ directory.
- axis2-transport-sms-1.0.0.jar
- jsmpp-2.1.0.jar

JMS Transport

Follow the steps to configure Apache ActiveMQ message broker

Install Apache ActiveMQ JMS.

This guide uses ActiveMQ versions 5.7.0 - 5.9.0. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to Apache ActiveMQ Documentation.
Add the following ActiveMQ JMS-specific JAR files to the <PRODUCT_HOME>/repository/components/lib/ directory.
- <ACTIVEMQ_HOME>/lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar
- <ACTIVEMQ_HOME>/lib/activemq-core-x.x.x.jar (for 5.7.0 and below)
- <ACTIVEMQ_HOME>/lib/hawtbuf-1.9.jar (for 5.8.0 and above)
- <ACTIVEMQ_HOME>/lib/activemq-client-x.x.x.jar (for 5.8.0 and above)

Follow the steps to configure Apache Qpid message broker

Install JMS-Qpid Broker and JMS-Qpid Client.

This guide uses Apache Qpid version 0.32. For more instructions on Apache Qpid go to Qpid documentation.
Add the following Qpid JMS-specific JAR files to <PRODUCT_HOME>/repository/components/lib/ directory.
- <QPID-CLIENT_HOME>/lib/geronimo-jms_1.1_spec-1.1.1.jar
- <QPID-CLIENT_HOME>/lib/qpid-client-0.32.jar
- <QPID-CLIENT_HOME>/lib/qpid-common-0.32.jar

Follow the steps to configure WSO2 Message Broker (MB)

Download and install WSO2 Message Broker. For instructions on WSO2 MB, go to Message Broker documentation.

This guide uses WSO2 Message Broker (MB) version 3.1.0.
Add the following JMS -specific JAR files to <PRODUCT_HOME>/repository/components/lib/ directory.
- <MB_HOME>/client-lib/andes-client-3.1.1.jar
- <MB_HOME>/client-lib/log4j-1.2.13.jar
- <MB_HOME>/client-lib/slf4j-1.5.10.wso2v1.jar
- <MB_HOME>/client-lib/geronimo-jms_1.1_spec-1.1.0.wso2v1.jar

Follow the steps to configure TIBCO EMS Server

Download and install TIBCO Enterprise Message Service. For more information on installing, go to TIBCO documentation.

This guide uses TIBCO EMS Server version 8.2.0 V7
Add the following JMS -specific JAR files to <PRODUCT_HOME>/repository/components/lib/ directory.
- <TIBCO_EMS_HOME>/lib/jms-2.0.jar
- <TIBCO_EMS_HOME>/lib/tibjms.jar
You need to remove the line javax.jms in launch.ini file which is located in <CEP_HOME>/repository/conf/etc to avoid OSGI package path conflicts as below.

org.osgi.framework.system.packages=javax.accessibility,\
javax.activity,\
...
javax.imageio.stream,\
javax.management,\
...