Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • org.apache.axis2.transport.jms.JMSListener
  • org.apache.axis2.transport.jms.JMSSender
Info

JMS messages can be easily configured using the WSO2 Message Broker. This message brokering system is based on JMS specifications and is thereby capable of communicating with any JMS client. WSO2 MB can be effectively used with WSO2 DSS in order to configure JMS queues and topics and to manage message routing, message stores and message processors.

The JMS transport implementation requires an active JMS server instance to be able to receive and send messages. We recommend using Apache ActiveMQ JMS server, but other implementations such as Apache Qpid and Tibco are also supported. You also need to put the client JARs for your JMS server in Carbon the product's classpath. In case of Apache ActiveMQ, you need to put the following JARs in the classpath:

  • activemq-core.jar
  • geronimo-j2ee-management_1.0_spec-1.0.jar
  • geronimo-jms_1.1_spec-1.1.1.jar

These JAR files can be obtained by downloading the latest version of Apache ActiveMQ (version 5.2.0 or later is recommended). Extract the downloaded archive and find the required dependencies in the $ACTIVEMQ_HOME/lib directory. You need to copy these JAR files over to $CARBON<PRODUCT_HOMEHOME>/repository/components/lib directory for Carbon the product to be able to pick them up at runtime.

...