This page walks you through the steps to follow when configuring WSO2 ESB's JMS transport with WSO2 Message Broker (WSO2 MB).
When you configure WSO2 ESB’s JMS transport with WSO2 MB, the recommended version of WSO2 MB to be used is WSO2 MB 3.0.0. We do not recommend the use of WSO2 MB 2.2.0 or lower.
Follow the steps below to configure the ESB's JMS transport with WSO2 MB 3.0.0
Setting up WSO2 MB
Download and install WSO2 MB. For instructions on how to download and install WSO2 MB, see Getting Started with WSO2 MB.
The unzipped WSO2 MB distribution folder will be referred to as
<MB_HOME>throughout the documentation.
It is not possible to start multiple WSO2 products with their default configurations simultaneously in the same environment. Since all WSO2 products use the same port in their default configuration, there will be port conflicts. Therefore, to avoid port conflicts, apply a port offset in the
<MB_HOME>/repository/conf/carbon.xmlfile by changing the offset value to 1. For example,
- Open a command prompt (or a shell in Linux) and go to the
- Start the Message Broker by executing
sh wso2server.sh(on Linux/OS X) or
Setting up WSO2 ESB
- If you have not already done so, see Getting Started with WSO2 ESB for details on installing and running WSO2 ESB.
To enable the JMS transport of WSO2 ESB to communicate with the Message Broker, edit the
<ESB_HOME>/repository/conf/axis2/axis2.xmlfile, find the commented
<transport receiver>block and uncomment it as shown below.
Also, uncomment the following
<transport sender>block for JMS in the same file:
For more information on the JMS configuration parameters used in the code segments above, see JMS Connection Factory Parameters.
- Copy the following JAR files from the
<MB_HOME>/clent-libdirectory to the
<ESB_HOME>/repository/conf/jndi.propertiesfile and make a reference to the running Message Broker as specified below:
Use carbon as the virtual host.
- Define a queue named
Comment out the topic, since it is not required in this scenario. However, in order to avoid getting the
javax.naming.NameNotFoundException:TopicConnectionFactoryexception during server startup, make a reference to the Message Broker from the
- Ensure that WSO2 Message Broker is running, and then open a command prompt (or a shell in Linux) and go to the
- Start the ESB server by executing sh wso2server.sh (on Linux/OS X) or wso2server.bat (on Windows).
Now you have instances of both WSO2 Message Broker and WSO2 ESB configured and running.