This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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

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 <ESB_HOME>/repository/components/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 <ESB_HOME>/repository/conf/etc/launch.ini file.

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

5. Enable the JMS Listener and Sender in <ESB_HOME>/repository/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 ESB.   

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

  • No labels