This documentation is for WSO2 Enterprise Service Bus version 4.8.1 . View documentation for the latest release.

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

The following instructions describe how to set up the JMS transport with JBossMQ, the default JMS provider in JBoss Application Server 4.2. (JBossMQ was replaced by JBoss Messaging in JBoss Application Server 5.0.)

To configure the JMS transport with JBossMQ:

  1. Copy the following client libraries to the <ESB_HOME>/repository/components/lib directory.
    • <JBOSS_HOME>/lib/jboss­system.jar
    • <JBOSS_HOME>/client/jbossall­client.jar
  2. Enable the JMS transport listener by adding the following listener configuration to the <ESB_HOME>/repository/conf/axis2/axis2.xml file:

    <!­­ Configuration for JBoss 4.2.2 GA MQ ­­>
    <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
      <parameter name="MyQueueConnectionFactory" locked="false">
        <parameter name="java.naming.factory.initial" locked="false">org.jnp.interfaces.NamingContextFactory</parameter>
        <parameter name="java.naming.factory.url.pkgs" locked="false">org.jnp.interfaces:org.jboss.naming</parameter>
        <parameter name="java.naming.provider.url" locked="false">jnp://localhost:1099</parameter>
        <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">/ConnectionFactory</parameter>
        <parameter name="transport.jms.Destination" locked="true">queue/susaQueue</parameter>
  3. Enable the JMS transport sender by uncommenting the following line in the <ESB_HOME>/repository/conf/axis2/axis2.xml file:

    <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/>
  4. Start the ESB and ensure that the logs prints messages indicating that the JMS listener and sender are started and that the JMS transport is initialized.
  • No labels