Follow the steps below to configure the JMS transport of the ESB profile with the Broker profile.
From the below configurations, do the ones in the axis2.xml file based on the profile you use as follows:
- To enable the JMS transport in the ESB profile, edit the
- To enable the JMS transport in other profiles, edit the
<PROFILE_HOME>refers to the main directory of the profile inside the WSO2 EI distribution. For example, to enable the JMS transport in the Business Process profile, edit the
To enable the JMS transport of the ESB profile to communicate with the Broker profile, edit the
<EI_HOME>/conf/axis2/axis2.xmlfile, find the commented
<transport receiver>block and uncomment it as shown below.
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.
and make a reference to the running Broker profile 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 Broker profile from the
For instructions on configuring the JMS transport in a cluster of the WSO2 EI Broker profile, see Running the Broker instances.
- Ensure that the Broker profile is running, and then open a command prompt (or a shell in Linux) and go to the
- Start the WSO2 EI server by executing the following commands:
sh integrator.sh(on Linux/OS X) or
Now, you have both the Broker and the ESB profile of WSO2 EI configured and running with the JMS transport enabled.