WSO2 Enterprise Service Bus (ESB), v1.0 Samples Setup Guide

Overview

The WSO2 ESB ships with a set of working examples that demonstrates some of the basic features and capabilities of itself. A set of sample clients and services are provided in addition to the sample configurations, and scripts are provided to execute the sample scenarios as explained below.

This document provides step-by-step instructions on how to install the pre-requisites, and set up the samples - generic instructions on how to start the sample server, deploy a service, and run the client.

Table of Contents

Pre-requisites

You will need a Java development kit / JRE version 1.4 or later and Apache Ant 1.5 or later, at a minimum, to try out the samples. Ant can be downloaded from http://ant.apache.org. The JMS examples can be executed against an ActiveMQ installation by default (or another JMS provider with configuration) and any HTTPS examples would require a JDK version 1.5 or later.

Note*: The samples and the documentation assumes that you are running the ESB in DEBUG mode. You can switch from the default INFO log messages to DEBUG log messages by changing the line "log4j.category.org.apache.synapse=INFO" as "log4j.category.org.apache.synapse=DEBUG" in the lib/log4j.properties file.

Understanding the Samples

The above diagram depicts the interactions between the clients, the ESB and services at a high level. The Clients are able to send SOAP/REST or POX messages over transports such as HTTP/HTTPS or JMS with WS-Addressing, WS-Security, or WS-Reliable messaging. They could send binary optimized content using MTOM or SwA or binary or plain text JMS messages. After mediation through the ESB, the requests are passed over to the sample services. The sample clients and services are explained below.

Using the Sample Clients

The sample clients can be executed from the samples/axis2Client directory through the provided Ant script. Simply executing 'ant' displays the available clients and some of the sample options used to configure them. The sample clients available are listed below:

1. Stock Quote Client

This is a simple SOAP client that could send stock quote requests, and receive and display the last sale price for a stock symbol.

ant stockquote [-Dsymbol=IBM|MSFT|SUN|..]
  [-Dmode=quote | customquote | fullquote | placeorder | marketactivity]
  [-Daddurl=http://localhost:9000/soap/SimpleStockQuoteService]
  [-Dtrpurl=http://localhost:8080] [-Dprxurl=http://localhost:8080]
  [-Dpolicy=../../repository/conf/sample/resources/policy/policy_1.xml]

The client is able to operate in the following modes, and send the payloads listed below as SOAP messages:

Note : See samples/axis2Client/src/samples/common/StockQuoteHandler.java for sample responses expected by the clients.

Smart Client Mode:

The 'addurl' property sets the WS-Addressing EPR, and the 'trpurl' sets a transport URL for a message. Thus by specifying both properties, the client can operate in the 'smart client' mode, where the addressing EPR could specify the ultimate receiver, while the transport URL set to the ESB ensures that any necessary mediation takes place before the message is delivered to the ultimate reciver.

e.g: ant stockquote -Daddurl=<addressingEPR> -Dtrpurl=<esb>

Gateway / Dumb Client Mode:

By specifying only a transport URL, the client operates in the 'dumb client' mode, where it sends the message to the ESB and depends on the ESB rules for proper mediation and routing of the message to the ultimate destination.

e.g: ant stockquote -Dtrpurl=<esb>

Proxy Client Mode:

In this mode, the client uses the 'prxurl' as an HTTP proxy to send the request. Thus by setting the 'prxurl' to the ESB, the client could ensure that the message would reach the ESB for mediation. The client could optionally set a WS-Addressing EPR if required.

e.g: ant stockquote -Dprxurl=<esb> [-Daddurl=<addressingEPR>]

Specifying a Policy

By specifying a WS-Policy using the 'policy' property, QoS aspects such as WS-Security could be enforced on the request. The policy specifies details such as timestamps, signatures, and encryption. See Apache Axis2 and Apache Rampart documentation for more information.

2. Generic JMS Client

The JMS client is able to send plain text, plain binary content, or POX content by directly publishing a JMS message to the specified destination. The JMS destination name should be specified with the 'jms_dest' property. The 'jms_type' property could specify 'text', 'binary' or 'pox' to specify the type of message payload.

The plain text payload for a 'text' message can be specified through the 'payload' property. For binary messages, the 'payload' property would contain the path to the binary file. For POX messages, the 'payload' property will hold a stock symbol name to be used within the POX request for stock order placement request.

e.g.,

ant jmsclient -Djms_type=text -Djms_dest=dynamicQueues/JMSTextProxy -Djms_payload="24.34 100 IBM"
ant jmsclient -Djms_type=pox -Djms_dest=dynamicQueues/JMSPoxProxy -Djms_payload=MSFT
ant jmsclient -Djms_type=binary -Djms_dest=dynamicQueues/JMSFileUploadProxy
                     -Djms_payload=./../../repository/conf/sample/resources/mtom/asf-logo.gif

Note: The JMS client assumes the existence of a default ActiveMQ (4.1.0 or above) installation on the local machine.

3. MTOM / SwA Client

The MTOM / SwA client can send a binary image file as a MTOM or SwA optimized message, and receive the same file again through the response and save it as a temporary file. The 'opt_mode' can specify 'mtom' or 'swa' respectively for the above mentioned optimizations. Optionally, the path to a custom file can be specified through the 'opt_file' property, and the destination address can be changed through the 'opt_url' property if required.

e.g. ant optimizeclient -Dopt_mode=[mtom | swa]

Starting the Sample Services

The sample services ship with a pre-configured Axis2 server, and demonstrates in-only and in-out SOAP/REST or POX messaging over HTTP/HTTPS and JMS transports using WS-Addressing, WS-Security, and WS-Reliable Messaging. It also handles binary content using MTOM and SwA.

The sample services can be found in the samples/axis2Server/src directory and can be built and deployed using Ant from each service directory.

user@host:/tmp/wso2esb-1.0/samples/axis2Server/src/SimpleStockQuoteService$ ant
Buildfile: build.xml
...
build-service:
   ....
      [jar] Building jar: /tmp/wso2esb-1.0/samples/axis2Server/repository/services/SimpleStockQuoteService.aar

BUILD SUCCESSFUL
Total time: 3 seconds

To start the Axis2 server, go to the samples/axis2Server directory and execute the axis2server.sh or axis2server.bat script. This starts the Axis2 server with the HTTP transport listener on port 9000 and HTTPS on 9002 respectively. To enable JMS transport, you will need to set up and start a JMS provider. An ActiveMQ 4.0.1 or later JMS server on the local machine is supported by default, and can be easily enabled by uncommenting the JMS transport from the conf/axis2.xml

The Sample services are as follows:

1. SimpleStockQuoteService

This service has four operations, getQuote (in-out), getFullQuote(in-out), getMarketActivity(in-out) and placeOrder (in-only). The getQuote operation will generate a sample stock quote for a given symbol. The getFullQuote operation will generate a history of stock quotes for the symbol for a number of days, and the getMarketActivity operation returns stock quotes for a list of given symbols. The placeOrder operation will accept a one way message for an order.

2. SecureStockQuoteService

This service is a clone of the SimpleStockQuoteService, but has WS-Security enabled and an attached security policy for signing and encrypting messages.

3. MTOMSwASampleService

This service has three operations: uploadFileUsingMTOM(in-out), uploadFileUsingSwA(in-out) and oneWayUploadUsingMTOM(in-only), and also demonstrates the use of MTOM and SwA. The uploadFileUsingMTOM and uploadFileUsingSwA operations accept a binary image from the SOAP request as MTOM and SwA, and returns this image back again as the response, while the oneWayUploadUsingMTOM saves the request message to the disk.

Starting Sample ESB Configurations

To start the WSO2 ESB with the sample default configuration, execute the wso2-esb.bat or wso2-esb.sh script found in the /bin directory. This starts up an instance of the ESB using the Synapse and Axis2 configuration files located in the conf directory. The repository/conf/samples directory contains the sample configurations available as synapse_sample_<n>.xml files. To start a specific sample configuration of the ESB, use the '-sample <n>' switch as follows:

wso2-esb.bat -sample <n>
wso2-esb.sh -sample <n>

Setting up JMS

The samples used in this guide assumes the existence of a local ActiveMQ (4.1.0 or higher) installation, which is properly installed and started.

To enable the JMS transport, you need to uncomment the JMS transport listener configuration. If you are using a JMS provider other than ActiveMQ, this configuration should be updated to reflect your environment. Once uncommented, the default configuration should be as follows. To enable JMS for the ESB, the conf/axis2.xml must be updated. To enable JMS support for the sample Axis2 server, the samples/axis2Server/repository/conf/axis2.xml file must be updated.

    <!--Uncomment this and configure as appropriate for JMS transport support, after setting up your JMS environment (e.g. ActiveMQ)-->
    <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
        </parameter>

        <parameter name="myQueueConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
        </parameter>

        <parameter name="default" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter>
        </parameter>
    </transportReceiver>

Configuring the ESB for Script Mediator Support

The Script Mediator is a Synapse extension, and thus all pre-requisites for all BSF supported scripting languages may not be bundled by default with the ESB distribution. Before you use some script mediators, you may need to manually add the required .jar files to the lib directory, and optionally perform other installation tasks as may be required by the individual scripting language. This is detailed in the following sections.

JavaScript Support

The JavaScript/E4X support is enabled by default and comes ready-to-use with the WSO2 ESB distribution.

Ruby Support

For Ruby support, you need to download the 'jruby-complete.jar' from the Maven repository for JRuby, and copy it into the 'lib' folder of Synapse . Download the JRuby JAR.