com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Configure with Tibco EMS

Owned by Former user (Deleted)
Last updated: Oct 10, 2016 by Former user (Deleted)
3 min read

This section describes how to configure the WSO2 ESB's JMS transport with Tibco EMS . Follow the steps below to set up and configure.

  1. Download and set up Tibco EMS in your environment.
  2. If you have not done so already, download and install WSO2 ESB as described in Installation Guide.
  3. Copy the Tibco EMS client jar files that are shipped with the distribution to the <ESB_HOME>/repository/components/extensions directory. 
    • tibcrypt.jar
    • tibjms.jar
    • tibjmsadmin.jar
    • tibjmsapps.jar
    • tibrvjms.jar
  4. WSO2 ESB does not have a default configuration script for TIBCO EMS. Therefore, add the following configuration to the <ESB_HOME>/repository/conf/axis2/axis2.xml file.

Setting up the JMS Listener 

<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
    <parameter name="TopicConnectionFactory" locked="false">
       <parameter locked="false" name="java.naming.factory.initial">
         com.tibco.tibjms.naming.TibjmsInitialContextFactory
       </parameter>
       <parameter locked="false" name="java.naming.provider.url">tcp://127.0.0.1:37222</parameter>
       <parameter locked="false" name="java.naming.security.principal">admin</parameter>
       <parameter locked="false" name="java.naming.security.credentials"/>
       <parameter locked="false" name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
       <parameter locked="false" name="transport.jms.JMSSpecVersion">1.0.2b</parameter>
       <parameter locked="false" name="transport.jms.ConnectionFactoryType">topic</parameter>
       <parameter locked="false" name="transport.jms.UserName">admin</parameter>
       <parameter locked="false" name="transport.jms.Password">admin</parameter>
       <parameter locked="false" name="transport.jms.CacheLevel">session</parameter>
    </parameter>
    <parameter locked="false" name="QueueConnectionFactory">
       <parameter locked="false" name="java.naming.factory.initial">
         com.tibco.tibjms.naming.TibjmsInitialContextFactory
       </parameter>
       <parameter locked="false" name="java.naming.provider.url">tcp://127.0.0.1:37222</parameter>
       <parameter locked="false" name="java.naming.security.principal">admin</parameter>
       <parameter locked="false" name="java.naming.security.credentials"/>
       <parameter locked="false" name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
       <parameter locked="false" name="transport.jms.JMSSpecVersion">1.0.2b</parameter>
       <parameter locked="false" name="transport.jms.ConnectionFactoryType">queue</parameter>
       <parameter locked="false" name="transport.jms.UserName">admin</parameter>
       <parameter locked="false" name="transport.jms.Password">admin</parameter>
       <parameter locked="false" name="transport.jms.CacheLevel">session</parameter>
    </parameter>
    <parameter name="default" locked="false">
       <parameter locked="false" name="java.naming.factory.initial">
          com.tibco.tibjms.naming.TibjmsInitialContextFactory
       </parameter>
       <parameter locked="false" name="java.naming.provider.url">tcp://127.0.0.1:37222</parameter>
       <parameter locked="false" name="java.naming.security.principal">admin</parameter>
       <parameter locked="false" name="java.naming.security.credentials"/>
       <parameter locked="false" name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
       <parameter locked="false" name="transport.jms.JMSSpecVersion">1.0.2b</parameter>
       <parameter locked="false" name="transport.jms.ConnectionFactoryType">queue</parameter>
       <parameter locked="false" name="transport.jms.UserName">admin</parameter>
       <parameter locked="false" name="transport.jms.Password">admin</parameter>
       <parameter locked="false" name="transport.jms.CacheLevel">session</parameter>
   </parameter>
</transportReceiver>

Setting up the JMS Sender

To enable the JMS transport sender, add the following JMS transport listener configuration in <ESB_HOME>/repository/conf/axis2/axis2.xml file.

<transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender">
   <parameter locked="false" name="QueueConnectionFactory">
      <parameter locked="false" name="java.naming.factory.initial">
         com.tibco.tibjms.naming.TibjmsInitialContextFactory
      </parameter>
      <parameter locked="false" name="java.naming.provider.url">tcp://127.0.0.1:37222</parameter>
      <parameter locked="false" name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
      <parameter locked="false" name="transport.jms.JMSSpecVersion">1.0.2b</parameter>
      <parameter locked="false" name="transport.jms.ConnectionFactoryType">queue</parameter>
   </parameter>
</transportSender>

  For details on the JMS configuration parameters used in the code segments above, see JMS Connection Factory Parameters.

You now have instances of Tibco EMS and WSO2 ESB configured, up and running. Next, see JMS Usecases for implementation details of various JMS use cases.

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.