This documentation is for WSO2 Enterprise Integrator version 6.2.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc
Skip to end of metadata
Go to start of metadata

This page describes how to configure the WSO2 JMS transport with  IBM® WebSphere® Application Server.

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 Integration profile, edit the <EI_HOME>/conf/axis2/axis2.xml file.
  • To enable the JMS transport in other profiles, edit the <EI_HOME>/wso2/<PROFILE_HOME>/conf/axis2/axis2.xml file. <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 <EI_HOME>/wso2/business-process/conf/axis2/axis2.xml file

1. Set up IBM WebSphere Application Server according to the instructions provided by IBM.

2. Create a JMS queue (e.g., samplequeue) and a JMS connection factory (e.g., QueueConnectionFactory) as described in the topics under Setting Up JMS in IBM WebSphere Application Server in the IBM documentation.  

3. Copy the following libraries from <WEBSHPERE_HOME>/java/lib directory to <EI_HOME>/lib directory.

  •    com.ibm.ws.runtime.jar
  •    com.ibm.ws.admin.client_7.0.0.jar
  •    com.ibm.ws.sib.client.thin.jms_7.0.0.jar
  •    com.ibm.ws.webservices.thinclient_7.0.0.jar
  •    bootstrap.jar

 4. Add the following entries to the <EI_HOME>/conf/etc/launch.ini file.

javax.jms,\
javax.rmi.CORBA,\

5. Enable the JMS Listener and Sender in <EI_HOME>/conf/axis2/axis2.xml by un-commenting the following lines of code. 
 

JMS Listener
   <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
       <parameter name="myQueueConnectionFactory" locked="false">
            <parameter name="java.naming.factory.initial" locked="false">com.ibm.websphere.naming.WsnInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url" locked="false">iiop://localhost:2809</parameter>
            <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
            <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
            <parameter name="transport.jms.Destination">samplequeue</parameter>
       </parameter>
 
        <parameter name="default" locked="false">
            <parameter name="java.naming.factory.initial" locked="false">com.ibm.websphere.naming.WsnInitialContextFactory</parameter>
            <parameter name="java.naming.provider.url" locked="false">iiop://localhost:2809</parameter>                           
            <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
            <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
            <parameter name="transport.jms.Destination">samplequeue</parameter>
       </parameter>
   </transportReceiver>
JMS Sender
<transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/> 
For details on the JMS configuration parameters used in the code segments above, see JMS Connection Factory Parameters.


6. Start IBM WebSphere Application Server and WSO2 EI.   

You now have instances of IBM WebSphere Application Server and WSO2 EI configured and running. Next, see JMS Usecases for implementation details of various JMS use cases.

  • No labels