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

Using the ESB as a JMS Producer

This section describes how to configure the ESB Profile of WSO2 Enterprise Integrator (WSO2 EI) to send messages to a JMS Queue.

 

Follow the steps below to configure the ESB Profile of WSO2 EI to accept messages via HTTP, and send them to JMS queue.  

  1. Configure the ESB Profile of WSO2 EI with Apache ActiveMQ and set up the JMS Sender. For instructions, see Configure with ActiveMQ . 

  2. Start WSO2 EI Tooling and create a proxy service with the following configuration. See Creating a Proxy Service for instructions.

    <proxy xmlns="http://ws.apache.org/ns/synapse" name="StockQuoteProxy" transports="http">
        <target>
            <inSequence>
                <property action="set" name="OUT_ONLY" value="true"/>
                <send>
                    <endpoint>
                        <address uri=""/> <!-- Specify the JMS connection URL here -->
                    </endpoint>
                </send>
            </inSequence>
            <outSequence/>
        </target>
        <publishWSDL uri="file:samples/service-bus/resources/proxy/sample_proxy_1.wsdl"/>
    </proxy>

    Proxy service configuration

    The OUT_ONLY property is set to true, which indicates that the message exchange is one-way. To send a message to a JMS queue, you should define the JMS connection URL as the endpoint address (which should be invoked via the Send mediator). There are two ways to specify the endpoint URL:

    • Specify the JNDI name of the JMS queue and the connection factory parameters in the JMS connection URL as shown in the exampe below. Values of connection factory parameters depend on the type of the JMS broker.

      When the broker is ActiveMQ
      jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue
      When the broker is WSO2 Message Broker
      jms:/StockQuotesQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&amp;java.naming.provider.url=conf/jndi.properties&transport.jms.DestinationType=queue


    • If you have already specified the endpoint's connection factory parameters (for the JMS sender configuration) in the axis2.xml file (stored in the <EI_HOME>/conf/axis2/ directory), the connection URL in the proxy service should be as shown below. In this example, the endpoint URL of the proxy service refers the relevant connection factory in the axis2.xml file:

      When the broker is ActiveMQ
      jms:transport.jms.ConnectionFactory=QueueConnectionFactory
      When the broker is WSO2 Message Broker
      jms:/StockQuotesQueue?transport.jms.ConnectionFactory=QueueConnectionFactory

    Be sure to replace the '&' character in the endpoint URL with '&amp;' to avoid the following exception:

    com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'java.naming.factory.initial' at [row,col {unknown-source}
  3. Send a message to the ESB by executing the following command from the <EI_HOME>/samples/axis2Client folder.

    ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy -Dmode=placeorder -Dsymbol=WSO2

    You can view the ActiveMQ queue by accessing the ActiveMQ management console using the URL http://0.0.0.0:8161/admin and using admin as both the username and password.

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