Heshan's Blog

Sample client for Axis2 XMPP transport

2011-07-28T01:36:00.000-07:00

Following is a sample service client that demonstrates the use of Apache Axis2's XMPP transport.

1) Add the following to your axis2.xml

i) Register the tranport listener.

<transportReceiver name="xmpp" class="org.apache.axis2.transport.xmpp.XMPPListener">
  <!-- Account details for google talk -->
  <parameter name="GoogleServer">
     <parameter name="transport.xmpp.ServerUrl">talk.google.com</parameter>
     <parameter name="transport.xmpp.ServerAccountUserName">axis2.xmpp.account1</parameter>
     <parameter name="transport.xmpp.ServerAccountPassword">apacheaxis2</parameter>
     <parameter name="transport.xmpp.ServerType">transport.xmpp.ServerType.GoogleTalk</parameter>
  </parameter>
</transportReceiver>

ii) Register the transport sender.

<transportSender name="xmpp" class="org.apache.axis2.transport.xmpp.XMPPSender">
</transportSender>

2) Sample service client.

import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
import org.apache.axis2.transport.xmpp.util.XMPPConstants;
import org.apache.axis2.util.XMLPrettyPrinter;

public class XMPPSampleClient {
   public static void main(String[] args) {
 invokeTimeService();
}

private static void invokeTimeService() {
 String endPointUrl = "xmpp://synapse.demo.0@gmail.com/" + "TimeService";

 EndpointReference targetEPR = new EndpointReference(endPointUrl);
 try {
                       ConfigurationContext ctx =
                            ConfigurationContextFactory.createConfigurationContextFromURIs(
                                XMPPSampleClient.class.getResource("axis2.xml"), null);

  OMElement payload = getPayload();
  Options options = new Options();
  options.setProperty(XMPPConstants.XMPP_SERVER_TYPE, XMPPConstants.XMPP_SERVER_TYPE_GOOGLETALK);
  options.setProperty(XMPPConstants.XMPP_SERVER_URL, XMPPConstants.GOOGLETALK_URL);
  options.setProperty(XMPPConstants.XMPP_SERVER_USERNAME, "synapse.demo.0");
  options.setProperty(XMPPConstants.XMPP_SERVER_PASSWORD, "mailpassword");

  options.setTo(targetEPR);
  options.setAction("urn:getServerTime");
  ServiceClient sender = new ServiceClient(ctx,null);

  sender.setOptions(options);
  OMElement result = sender.sendReceive(payload);
  XMLPrettyPrinter.prettify(result, System.out);
 } catch (Exception e) {
  e.printStackTrace();
 }
}

private static OMElement getPayload() {
 OMFactory fac = OMAbstractFactory.getOMFactory();
 OMNamespace omNs = fac.createOMNamespace(
   "http://example.xmpp.transports.axis2.org/example1", "example1");
       return fac.createOMElement("getServerTime", omNs);
}
}

XSLT transformations with WSO2 ESB

2011-07-14T23:58:00.000-07:00

Recently I did some performance comparison on a new mediator that I have developed for WSO2 ESB for XSLT transformations.

Following 6 scenarios were taken into consideration for this benchmark;

1) SCENARIO-1 : Direct Service call to backend service (which is hosted at axis2 server) from the client.

2) SCENARIO-2 : Service Call to the backend service through a Pass through proxy (Using message realy)

3) SCENARIO-3 : Service call to the backend service through the XSLT transformation proxy (with xalan XSLT processor)

4) SCENARIO-4 : Service call to the backend service through the XSLT transformation proxy (with saxon XSLT processor)

5) SCENARIO-5 : Service call to the backend service through the XSLT transformation proxy (with saxon XSLT processor) - with patched XSLT mediator which is doing XML stream transformation (using message relay)

6) SCENARIO-6 : Service call to the backend service through the XSLT transformation proxy (with saxon enterprise edition XSLT processor) - with patched XSLT mediator which is doing XML stream transformation (using message relay)

Following are the configurations of the machines which were used in the performance benchmark. For more information refer the attached document named hardware-configuration-of-machines.txt

Hardware/Software configuration of the machines used

1) Configuration of the machine(32 bit) which was running the client (load testing tool used was java-bench):

OS : Debian GNU/Linux 6.0

CPU : Intel(R) Pentium(R) 4 CPU 2.80GHz

RAM : 1 GB

2) Configuration of the machine(64 bit) which was running the axis2 server which is hosting the service:

OS : Ubuntu 11.04

CPU : Genuine Intel(R) CPU T2400 @ 1.83GHz

RAM : 3 GB

3) Configuration of the machine(64 bit) which was running the WSO2 ESB:

OS : Debian GNU/Linux 6.0

CPU : Pentium(R) Dual-Core CPU E5400 @ 2.70GHz

RAM : 4 GB

Results/Observation

The time per request were measured for the XSLT transformations with the ESB and calculated the latency numbers. The message sizes used were 5k, 10k, 50k, 100k, 200k, 300k, 400k, 500k. The time per request were measured for the number of requests 10000, 11000, 12000, 13000, 14000, 15000. During the benchmarking session, I got the numbers for xalan as well as saxon XSLT processors. Since the primary concern of this benchmark was on latency, the concurrency level used was one.

i) Time per request

Request Size	Direct request (ms)	ESB -Pass through(Message relay) - Time per request(ms)	ESB (xalan) – Time per request (ms)	ESB (saxon) – Time per request (ms)	ESB patched (saxon) -– Time per request (ms)	ESB Patched (Saxon EE) Timer per request (ms)
5k	2.932	5.087	11.458	9.899	7.486	7.413
10k	4.564	6.332	16.73	15.387	11.145	10.473
50k	17.881	20.984	46.328	42.481	40.834	34.598
100k	34.691	37.339	83.554	79.325	71.151	62.992
200k	67.66	70.771	155.233	146.885	128.672	119.886
300k	100.661	103.945	233.79	213.84	186.985	177.184
400k	133.125	137.898	295.675	283.95	245.029	238.081
500k	166.008	169.460	364.027	356.182	302.779	297.676

ii) Latency

The latency was calculated by the following equation.

Latency = (Time per request through ESB - Direct request)

Request Size	ESB(Message relay) latency (ms)	ESB (xalan) latency (ms)	ESB (saxon) latency (ms)	ESB patched (saxon) latency (ms)	ESB patched (saxon-EE) latency (ms)
5k	2.155	8.526	6.967	4.554	4.481
10k	1.768	12.166	10.823	6.581	5.909
50k	3.103	28.447	24.6	22.953	16.717
100k	2.648	48.863	44.634	36.46	28.301
200k	3.111	87.573	79.225	61.012	52.226
300k	3.284	133.129	113.179	86.324	76.523
400k	4.773	162.55	150.825	111.904	104.956
500k	3.452	198.019	190.174	136.771	131.668

iii) Overhead

The overhead percentage introduced by the ESB is calculated by the following equation.

ESB Overhead = (Time per request through ESB - Direct request time)/(Direct request time) * 100 %

Request Size	ESB(Message relay) overhead(%)	ESB (xalan) overhead percentage (%)	ESB (saxon) overhead percentage (%)	ESB patched (saxon) overhead percentage (%)	ESB patched (saxon-EE) overhead percentage (%)
5k	73.49931787176	290.7912687585	237.619372442	155.3206002729	152.830832196453
10k	38.737949167397	266.5644171779	237.1384750219	144.1936897458	129.469763365469
50k	17.353615569599	159.0906548851	137.5761981992	128.3653039539	93.490296963257
100k	7.6331036868352	140.8520942031	128.661612522	105.0993052953	81.580236949065
200k	4.5979899497488	129.4309784215	117.0928170263	90.1744014189	77.188885604493
300k	3.2624353026495	132.2547957998	112.4357993662	85.7571452698	76.020504465483
400k	3.585352112676	122.103286385	113.2957746479	84.059342723	78.840187793427
500k	2.0794178593803	119.2828056479	114.5571297769	82.3881981591	79.314249915667

Observation

In case of scenarios 3 & 4, the only difference is the underlying XSLT processor used by the ESB is changed from the xalan to saxon. When comparing the performance numbers of xalan and saxon; saxon is showing a little performance improvement. Therefore, there is no significant gain with the use of saxon as opposed to xalan (which is the default XSLT processor shipped with the ESB).

In case of scenario 5, I developed a new mediator to do XSLT transformation by passing in the stream directly to the XSLT processor with the use of Message Relay.

Compared to scenarios 3 & 4, scenario 5 is showing a significant performance improvement.

The difference between scenario 5 and 6 is that the underlying saxon XSLT processor is changed from the community edition to enterprise edition. Compared to scenario 5, scenario 6 is showing a performance improvement.

Throughout this post I have talked about a transformation mediator which is supporting streaming. This will be available with the next release of the WSO2 ESB. This meadiator's name will be relayTransformer.

I will write a new post on this new mediator on some other time.

NOTE: This performance figures were calculated, inorder for me to get an idea about the performance gain of this new mediator. These figures were not calculated in an ideal environment. Therefore, if you try to compare these numbers with a performance benchmark that you might have done, it might not be comparable.

References

[1] - http://wso2.org/products/download/esb/java/4.0.0/wso2esb-4.0.0.zip

[2] - http://heshans.blogspot.com/search/label/ESB

[3] - http://wso2.org/project/esb/java/4.0.0/docs/samples/message_mediation_samples.html#Sample8

Changing the underlying XSLT processor of WSO2 ESB

2011-07-12T22:25:00.000-07:00

The default XSLT processor shipped in with WSO2 ESB is xalan. Let's assume that you need to change the xslt processor to saxon.

Following are the steps to set saxon as the XSLT processor.

1) Remove the xalan-2.7.0.wso2v1.jar from the following locations.
ESB_HOME/lib/xalan-2.7.0.wso2v1.jar
ESB_HOME/lib/endorsed/xalan-2.7.0.wso2v1.jar

2) Then add the Saxon home edition(saxon9he.jar) to the above mentioned locations.
ie.
ESB_HOME/lib/
ESB_HOME/lib/endorsed/

Saxon can be downloaded from [1].

3) Start the ESB server.

After changing the XSLT processor to Saxon, you can do your transformations with the use of Saxon parser.

[1] - http://saxon.sourceforge.net/

Local Transport implementation for WSO2 ESB

2011-06-21T03:52:00.000-07:00

Apache Axis2's non blocking local transport implementation is used to make internal service calls and transfer data within proxy services. The class org.apache.axis2.transport.local.NonBlockingLocalTransportSender implements the sender API. The transport does not have a receiver implementation and does not accept any configuration parameters as of now. This transport will work seamlessly against the ESB's Nhttp transport. This new transport is available with the latest [1] release of WSO2 ESB (ie. wso2esb-4.0.0). The binary distro can be downloaded from [2].

Scenario :

Inorder to demonstrate the use of local transport, let's consider following scenario. The ESB contains three proxy services. The stockquote client invokes the LocalTransportProxy. Then the message will be sent to the SecondProxy and then it will be sent to the StockQuoteProxy. The StockQuoteProxy will invoke the backend service and return the response to the client.

1) Without local transport

If you have a look at the above diagram you might notice that each call between proxy services are going through the network.

Synapse Configuration:

<definitions xmlns="http://ws.apache.org/ns/synapse">
<proxy xmlns="http://ws.apache.org/ns/synapse" name="LocalTransportProxy"
       transports="https http" startOnLoad="true" trace="disable">
    <target>
        <endpoint name="ep1">
            <address uri="http://localhost:9000/services/SecondProxy"/>
        </endpoint>
        <inSequence>
            <log level="full"/>
            <log level="custom">
                <property name="LocalTransportProxy" value="In sequence of LocalTransportProxy invoked!"/>
            </log>
        </inSequence>
        <outSequence>
            <log level="custom">
                <property name="LocalTransportProxy" value="Out sequence of LocalTransportProxy invoked!"/>
            </log>
            <send/>
        </outSequence>
    </target>
    <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
<proxy xmlns="http://ws.apache.org/ns/synapse" name="SecondProxy"
       transports="https http" startOnLoad="true" trace="disable">
    <target>
        <endpoint name="ep2">
            <address uri="http://localhost:9000/services/StockQuoteProxy"/>
        </endpoint>
        <inSequence>
            <log level="full"/>
            <log level="custom">
                <property name="SecondProxy" value="In sequence of Second proxy invoked!"/>
            </log>
        </inSequence>
        <outSequence>
            <log level="custom">
                <property name="SecondProxy" value="Out sequence of Second proxy invoked!"/>
            </log>
            <send/>
        </outSequence>
    </target>
    <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
<proxy xmlns="http://ws.apache.org/ns/synapse" name="StockQuoteProxy"
       startOnLoad="true">
    <target>
        <endpoint name="ep3">
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
        </endpoint>
        <outSequence>
            <log level="custom">
                <property name="StockQuoteProxy"
                          value="Out sequence of StockQuote proxy invoked!"/>
            </log>
            <send/>
        </outSequence>
    </target>
    <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
</proxy>
</definitions>

2) With local transport

In this sample, the communication between proxy services are done through the Local transport. Since Local transport calls are in-JVM calls, it will reduce the time taken for the communication between proxy services (will not introduce any network overhead).

Synapse Configuration:

<definitions xmlns="http://ws.apache.org/ns/synapse">
 <proxy xmlns="http://ws.apache.org/ns/synapse" name="LocalTransportProxy"
        transports="https http" startOnLoad="true" trace="disable">
     <target>
         <endpoint name="ep1">
             <address uri="local://localhost/services/SecondProxy"/>
         </endpoint>
         <inSequence>
             <log level="full"/>
             <log level="custom">
                 <property name="LocalTransportProxy" value="In sequence of LocalTransportProxy invoked!"/>
             </log>
         </inSequence>
         <outSequence>
             <log level="custom">
                 <property name="LocalTransportProxy" value="Out sequence of LocalTransportProxy invoked!"/>
             </log>
             <send/>
         </outSequence>
     </target>
     <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
 </proxy>
 <proxy xmlns="http://ws.apache.org/ns/synapse" name="SecondProxy"
        transports="https http" startOnLoad="true" trace="disable">
     <target>
         <endpoint name="ep2">
             <address uri="local://localhost/services/StockQuoteProxy"/>
         </endpoint>
         <inSequence>
             <log level="full"/>
             <log level="custom">
                 <property name="SecondProxy" value="In sequence of Second proxy invoked!"/>
             </log>
         </inSequence>
         <outSequence>
             <log level="custom">
                 <property name="SecondProxy" value="Out sequence of Second proxy invoked!"/>
             </log>
             <send/>
         </outSequence>
     </target>
     <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
 </proxy>
 <proxy xmlns="http://ws.apache.org/ns/synapse" name="StockQuoteProxy"
        startOnLoad="true">
     <target>
         <endpoint name="ep3">
             <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
         </endpoint>
         <outSequence>
             <log level="custom">
                 <property name="StockQuoteProxy"
                           value="Out sequence of StockQuote proxy invoked!"/>
             </log>
             <send/>
         </outSequence>
     </target>
     <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
 </proxy>
</definitions>

If you are interested in running this local transport sample, refer [3]. I am planning to do a performance benchmark against this local transport. Stay tuned for my followup post on local transport performance.

References

[1] - http://wso2.org/project/esb/java/4.0.0/doc

[2] - http://wso2.org/products/download/esb/java/4.0.0/wso2esb-4.0.0.zip

[3] - http://wso2.org/project/esb/java/4.0.0/docs/samples/transport_samples.html#Sample268

WSO2 Enterprise Service Bus 4.0.0 Released

2011-06-13T21:18:00.000-07:00

The WSO2 ESB team is pleased to announce the release of version 4.0.0 of the Open Source Enterprise Service Bus (ESB).

WSO2 ESB is a fast, lightweight and user friendly open source Enterprise Service Bus (ESB) distributed under the Apache Software License v2.0. WSO2 ESB allows system administrators and developers to easily configure message routing, intermediation, transformation, logging, task scheduling, fail over routing and load balancing. It also supports transport switching, eventing, rule based mediation and priority based mediation for advanced integration requirements. The ESB runtime is designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse mediation engine.

WSO2 ESB 4.0.0 is developed on top of the revolutionary WSO2 Carbon platform (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the ESB. Further, any existing features of the ESB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 ESB can be fully customized and tailored to meet your exact SOA needs.

You can download this distribution from http://wso2.org/downloads/esband give it a try.

Brand New Features in this Release

HTTP relay transport - Pure streaming HTTP transport based on Java NIO for ultra fast HTTP routing
Deployment synchronizer - Easily synchronize the configuration across a cluster of Carbon Servers
Message stores and processors - For advanced enterprise messaging and QoS enforcement (eg: in-order delivery, exactly once delivery)
Mediation templates - The concept of reusable functions to the ESB configuration language
Message broker - Built-in JMS provider/broker powered by Apache Qpid
FTPS support via file transport - Transfer files over SSH connections
Conditional router mediator - Implement advanced and complex routing logic at ease
URL rewrite mediator - Rewrite URLs and URL fragments efficiently
Custom XPath extensions - User defined custom XPath extensions support
New HL7 transport (optional) - Send and receive HL7 messages over MLLP and other transports
New eventing implementation - A powerful event broker with extensive support for WS-Eventing and topic management
Event mediator - Publish events to topics defined in the built-in event broker
LDAP user store - Built-in LDAP service based on Apache Directory Server
Dynamic registry keys and endpoint URL support - Construct registry lookup keys and endpoint URLs dynamically at mediation time

Enhancements in this Release

Improved Smooks mediator
Enhanced support for service chaining with the receiving sequence support in the send mediator
Improved weighted round robin algorithm for the load balance endpoint
Improvements to caching
Automatic schema imports from the WSDLs added to the registry (for proxy services)
Automatic schema imports from the schema files added to the registry (for validate mediator)
Support for setting properties at the endpoint level
Enhanced Enrich Mediator
Improved support for batch transfers in FIX transport
Validation support for the ESB configuration editor (source view)
Proxy service UI enhancements
Enhanced menu layouts
Local transport for fast in-VM service calls

Key Features of WSO2 ESB

Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
Non-blocking HTTP/S transports based on Apache HttpCore-NIO for ultra-fast execution and support for thousands of connections at high concurrency with constant memory usage.
Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS configurations ..)
Easily extendable via custom Java classes (mediator and command)/Spring configurations, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler.
Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
Lightweight, XML and Web services centric messaging model
Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Health Level-7 protocol)
Enhanced support for the VFS (File/FTP/SFTP), JMS, Mail transports with optional TCP/UDP transports and transport switching among any of the above transports
Support for message splitting & aggregation using the EIP and service callouts
Database lookup & store support with DBMediators with reusable database connection pools
WS-Eventing support with event sources and event brokering
Rule based mediation of the messages using the Drools rule engine
Transactions support via the JMS transport and Transaction mediator for database mediators
Internationalized GUI management console with user management for configuration development
Integrated monitoring support with statistics, configurable logging and tracing
JMX monitoring support and JMX management capabilities like, Graceful/Forceful shutdown/restart

Bugs Fixed in this Release

This release of WSO2 ESB comes with a number of bug fixes, both in the base framework and the ESB specific components. All the issues which have been fixed in ESB 4.0.0 are recorded at following locations:

Known Issues

All the open issues pertaining to WSO2 ESB 4.0.0 are reported at following locations:

How to Run

Extract the downloaded zip
Go to the bin directory in the extracted folder
Run the wso2server.sh or wso2server.bat as appropriate
Point your browser to the URL https://localhost:9443/carbon
Use "admin", "admin" as the username and password to login as an admin
If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
Sample configurations can be started by the wso2esb-samples script passing the sample number with the -sn option (Please have a look at the samples guide for more information, on running samples)

How to Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : carbon-dev@wso2.org | Subscribe | Mail Archive
User List : esb-java-user@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature requests regarding WSO2 ESB through the public ESB JIRA. You can use the Carbon JIRA to report any issues related to the Carbon base framework or associated Carbon components.

Discussion Forums

Alternatively, questions could be raised using the forums available.

WSO2 ESB Forum: Discussion forum for WSO2 ESB developers/users

Support

We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

For more information about WSO2 ESB please see http://wso2.com/products/enterprise-service-bus.

-- The WSO2 ESB Team --

Executing Groovy scripts using WSO2 ESB

2011-05-06T01:52:00.000-07:00

Following post will discuss how to execute a Groovy script using the WSO2 ESB's script mediator [1].

1) Download a distribution of the WSO2 ESB [2].

2) Extract the zip file. The directory created will be referred as ESB_HOME.

3) Go to the ESB_HOME/samples/axis2Server/src/SimpleStockQuoteService directory. Run "ant" to build the service. A service archive will be created at ESB_HOME/samples/axis2Server/repository/services. The generated service archive can be deployed at an Axis2 server.
eg. SimpleStockQuoteService.aar

4) Copy the groovy-all-1.1-rc-1.jar into ESB_HOME/repository/components/lib/.

5) Go to the ESB_HOME/bin and run the script which starts wso2server.
eg. wso2server.bat for windows environments
wso2server.sh for linux environments

6) Once the server stats, log into the Mangement Console using following credentials (following are the default username/password).
username: admin
password: admin

7) Add the following proxy to the Synapse configuration using the Source View tab.

<proxy xmlns="http://ws.apache.org/ns/synapse" name="groovyProxy" transports="https,http" statistics="disable" trace="disable" startOnLoad="true">
  <target>
     <inSequence>
        <script language="groovy">println "The current time is: ${new Date()}"</script>
        <send>
           <endpoint name="endpoint_urn_uuid_4ECE7CA834EC574477533951">
              <address uri="http://localhost:9000/services/SimpleStockQuoteService" />
           </endpoint>
        </send>
     </inSequence>
  </target>
</proxy>

8) Execute the client using the following command.

heshan@heshan-ThinkPad:~/Dev/wso2esb-4.0.0-SNAPSHOT/samples/axis2Client$ ant stockquote -Daddurl=http://localhost:8280/services/groovyProxy

9) Following message will be printed at ESB console.

The current time is: Fri May 06 14:00:40 IST 2011

References
[1] - http://wso2.org/project/esb/java/3.0.1/docs/mediators/script.html
[2] - http://wso2.org/downloads/esb

Friendly Basketball Match

2011-02-27T10:43:00.001-08:00

We (WSO2) played a friendly Basketball match against some of my friends at Colombo University. We played the match on 24th Thursday at British School's outdoor Basketball court. This was the second time that we met in a friendly match. Last year the Colombo University guys won the match and this time around we won the match.

When comparing our performance against our previous encounter, our team has improved a lot.

Since we had 2 games in 2 consecutive years, we are planning to take this ahead and have this friendly Basketball match as an annual event.

I should like to thank my junior match mates at Colombo University for coming there to play a match during a University vacation and the crowd for coming there to cheer us.

Handling a http-get request and invoking an external Web service with WSO2 ESB

2011-02-19T00:57:00.000-08:00

Following post will discuss how to handle a http-get request from WSO2 ESB and call a external web service. Inorder to clarify example clearly I am using a simple usecase described below. The relevant configuration files, steps to run the sample and the messages flowing through the system is shown below. I have labeled the messages in the diagram, inorder to show the contents of the messages.

Usecase
1. Client makes a rest-like http-get: GET /.../company/<id>
eg. curl "http://localhost:8280/services/ProxyA/company/IBM" -v
2. ESB service proxy picks the company id from the url
eg. IBM
3. ESB service makes a web service call to a external ws-service (SimpleStockQuoteService) and a spesific ws-method.
4. ESB service parses the ws-response and returns a plain xml result to the client.

Configuration Files
Following is the Synapse configuration which contains the sample proxy which handles the request.

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
    <parameter name="cachableDuration">15000</parameter>
</registry>
<proxy name="ProxyA" transports="https http" startOnLoad="true" trace="disable">
    <target>
        <inSequence>
            <enrich>
                <source type="inline">
                    <a xmlns=""/>
                </source>
                <target type="body" action="child"/>
            </enrich>
            <log level="full"/>
            <property name="company" expression="substring-after(get-property('To'),'company/')"/>
            <xslt key="xslt-transform-request">
                <property name="symbol" expression="get-property('company')"/>
            </xslt>
            <header name="Action" value="urn:getQuote"/>
            <log level="full"/>
            <send>
                <endpoint name="ep1">
                    <address uri="http://localhost:9000/services/SimpleStockQuoteService" format="soap11"/>
                </endpoint>
            </send>
        </inSequence>
        <outSequence>
            <property xmlns:ax21="http://services.samples/xsd" xmlns:ns="http://services.samples" name="response_symbol" expression="//ns:return/ax21:symbol/child::text()"/>
            <property xmlns:ax21="http://services.samples/xsd" xmlns:ns="http://services.samples" name="response_high" expression="//ns:return/ax21:high/child::text()"/>
            <property xmlns:ax21="http://services.samples/xsd" xmlns:ns="http://services.samples" name="response_low" expression="//ns:return/ax21:low/child::text()"/>
            <log level="custom">
                <property name="response symbol:" expression="get-property('response_symbol')"/>
                <property name="response high  :" expression="get-property('response_high')"/>
                <property name="response low   :" expression="get-property('response_low')"/>
            </log>
            <xslt key="xslt-transform-response">
                <property name="symbol" expression="get-property('response_symbol')"/>
                <property name="high" expression="get-property('response_high')"/>
                <property name="low" expression="get-property('response_low')"/>
            </xslt>
            <send/>
        </outSequence>
    </target>
</proxy>
<localEntry key="xslt-transform-request" src="file:repository/samples/resources/transform/request_transform.xslt"/>
<localEntry key="xslt-transform-response" src="file:repository/samples/resources/transform/response_transform.xslt"/>
<sequence name="fault">
    <log level="full">
        <property name="MESSAGE" value="Executing default 'fault' sequence"/>
        <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
        <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
    </log>
    <drop/>
</sequence>
<sequence name="main">
    <in>
        <log level="full"/>
        <filter source="get-property('To')" regex="http://localhost:9000.*">
            <send/>
        </filter>
    </in>
    <out>
        <send/>
    </out>
</sequence>
</definitions>

Following is the xslt transformation (request_transform.xslt) which transforms the request at the ESB.

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:param name="symbol"/>
<xsl:template match="/">
    <m0:getQuote xmlns:m0="http://services.samples">
        <m0:request>
            <m0:symbol><xsl:value-of select="$symbol"/></m0:symbol>
        </m0:request>
    </m0:getQuote>
</xsl:template>
</xsl:stylesheet>

Following is the xslt transformation (response_transform.xslt) which transforms the response at the ESB.

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:param name="symbol"/>
<xsl:param name="high"/>
<xsl:param name="low"/>
<xsl:template match="/">
    <m0:getQuote xmlns:m0="http://services.samples">
        <m0:response>
            <m0:company><xsl:value-of select="$symbol"/></m0:company>
    <m0:high><xsl:value-of select="$high"/></m0:high>
    <m0:low><xsl:value-of select="$low"/></m0:low>
        </m0:response>
    </m0:getQuote>
</xsl:template>
</xsl:stylesheet>

The contents of the messages flowing through the ESB
Request-A

GET /services/ProxyA/company/IBM HTTP/1.1
User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
Host: 127.0.0.1:8281
Accept: */*

Request-B

POST /services/SimpleStockQuoteService HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
SOAPAction: "urn:getQuote"
Transfer-Encoding: chunked
Host: 127.0.0.1:9001
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO

113
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:envelope soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:body>
     <m0:getquote m0="http://services.samples">
        <m0:request>
           <m0:symbol>IBM</m0:symbol>
        </m0:request>
     </m0:getQuote>
  </soapenv:Body>
</soapenv:Envelope>0

Response-C

HTTP/1.1 200 OK
Content-Type: text/xml; charset=UTF-8
Date: Sat, 19 Feb 2011 08:50:01 GMT
Transfer-Encoding: chunked
Connection: Keep-Alive

40a
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:envelope soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:body>
     <ns:getquoteresponse ns="http://services.samples">
        <ns:return ax21="http://services.samples/xsd" xsi="http://www.w3.org/2001/XMLSchema-instance" type="ax21:GetQuoteResponse">
           <ax21:change>-2.7502820955517455</ax21:change>
           <ax21:earnings>13.682776182003703</ax21:earnings>
           <ax21:high>159.3075652956029</ax21:high>
           <ax21:last>154.1201005301602</ax21:last>
           <ax21:lasttradetimestamp>Sat Feb 19 14:20:01 IST 2011</ax21:lastTradeTimestamp>
           <ax21:low>158.77156450332262</ax21:low>
           <ax21:marketcap>-4211789.232304155</ax21:marketCap>
           <ax21:name>IBM Company</ax21:name>
           <ax21:open>161.05685744490376</ax21:open>
           <ax21:peratio>24.219012038564948</ax21:peRatio>
           <ax21:percentagechange>1.913224112346585</ax21:percentageChange>
           <ax21:prevclose>-143.75117257844414</ax21:prevClose>
           <ax21:symbol>IBM</ax21:symbol>
           <ax21:volume>6450</ax21:volume>
        </ns:return>
     </ns:getQuoteResponse>
  </soapenv:Body>
</soapenv:Envelope>0

Response-D

HTTP/1.1 200 OK
Content-Type: application/xml; charset=UTF-8
Date: Sat, 19 Feb 2011 08:50:01 GMT
Transfer-Encoding: chunked

bc
<m0:getquote m0="http://services.samples">
<m0:response>
  <m0:company>IBM</m0:company>
  <m0:high>159.3075652956029</m0:high>
  <m0:low>158.77156450332262</m0:low>
</m0:response></m0:getQuote>0

Steps to run the sample
1) Download WSO2 ESB [1].

2) Start wso2esb using the startup scripts.
eg: ./wso2server.sh

3) Login to the WSO2 Management console.

4) Copy the attached xslt files (ie. request_transform.xslt, response_transform.xslt) to wso2esb-3.0.1/repository/samples/resources/transform directory.

5) Go to Source View and paste the Synapse configuration to it and hit update.

6) Start the Axis2 server and deploy the SimpleStockQuoteService if not already done.
i) Run the ant script to build the SimpleStockQuoteService. It is residing in wso2esb-3.0.1/samples/axis2Server/src/SimpleStockQuoteService directory.
ii) Then run the simple axis2Server shipped in with the wso2esb. This can be done by the running the axis2Server startup script inside wso2esb-3.0.1/samples/axis2Server/ directory.
eg: ./axis2server.sh

7) Execute the following curl command.
eg: curl "http://localhost:8280/services/ProxyA/company/IBM" -v

Then you will be getting the following response.
eg:


* About to connect() to localhost port 8280 (#0)
*   Trying ::1... connected
* Connected to localhost (::1) port 8280 (#0)
> GET /services/ProxyA/company/IBM HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
> Host: localhost:8280
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/xml; charset=UTF-8
< Date: Thu, 10 Feb 2011 07:54:46 GMT
< Transfer-Encoding: chunked
<
* Connection #0 to host localhost left intact
* Closing connection #0
<m0:getQuote xmlns:m0="http://services.samples"><m0:response><m0:company>IBM</m0:company><m0:high>-81.16785748190335</m0:high><m0:low>85.09674577550493</m0:low></m0:response></m0:getQuote>

References
[1] - http://wso2.org/downloads/esb
[2] - http://wso2.org/project/esb/java/3.0.1/docs/

Became a Committer for Apache Synapse

2011-01-30T05:18:00.000-08:00

I earned committership for Apache Synapse ESB project :)

Apache Synapse Enterprise Service Bus (ESB) - 2.0.0 Released

2011-01-11T03:58:00.000-08:00

Overview

The Apache Synapse ESB is a robust, lightweight and highly scalable and distributed open source Enterprise Service Bus (ESB). It supports SOAP Web services as well as Legacy services over transports such as JMS, Apache VFS File systems, Mail etc, and SOAP, REST/POX, plain text and binary message payloads. (Please see http://synapse.apache.org for more details)

Installation Prerequisites

Apache Synapse requires a J2SE runtime of version 1.5.x or later. Running the samples also requires Apache Ant 1.7.x or later. Although Synapse would run with a JDK > 1.5.x, the Script mediator may not properly function on these JDKs. Building Synapse from source requires JDK 1.5.x or later, and Apache Maven 2.1.0 or later

Quick start
Please see the http://synapse.apache.org/Synapse_Quickstart.html guide

Building the Samples
Please see the documents http://synapse.apache.org/Synapse_Samples.html and http://synapse.apache.org/Synapse_Samples_Setup.html

Synapse configuration language
Please see the document http://synapse.apache.org/Synapse_Configuration_Language.html

Extending Synapse
Please see the document http://synapse.apache.orgs/Synapse_Extending.html

Known Issues and limitations

SYNAPSE-180 Does not support throttling by concurrency within a cluster
SYNAPSE-186 Does not support HTTP some of the REST operations (such as put/delete etc)
SYNAPSE-181 Does not yet support JTA transactions
SYNAPSE-330 Does not yet support load balancing with session affinity using SOAP sessions
SYNAPSE-280 Does not preserve CDATA sections within payloads
SYNAPSE-307 The XSLT mediator will not report errors encountered in a provided stylesheet
The Synapse JMS implementation supports JMS 1.0.2b, however due to licensing issues we includethe JMS 1.1 spec JAR from Apache Geronimo (geronimo-jms_1.1_spec-1.1.jar) instead. If you have any issues with JMS 1.0.x, please download the Sun JMS 1.0.2b JAR and replace supplied JAR from Geronimo.

Frequently asked questions

How can I change the default logging level of Synapse? Edit the lib/log4j.properties and set the line "log4j.category.org.apache.synapse=INFO" to "log4j.category.org.apache.synapse=DEBUG" and restart Synapse.
If you get an error related to WS-Security or when using it, check to ensure that your JDK uses the "Unlimited Strength Jurisdiction Policy Files". These could be downloaded from http://java.sun.com/javase/downloads/index_jdk5.jsp Refer to the associated documentation for instructions on how to install it to your JDK.
If you encounter issues with your JDK related to XML processing, try placing the Xerces jar files xercesImpl-2.8.0.jar and xml-apis-1.3.03.jar in your /jre/lib/endorsed/ directory.

Reporting Problems

Please use the Apache JIRA system (http://issues.apache.org/jira/browse/SYNAPSE) to report issues

You may also join the: synapse-dev mailing list by sending email to dev-subscribe@synapse.apache.org

synapse-user mailing list by sending email to user-subscribe@synapse.apache.org

New features in the Synapse 2.0.0 release

New, fine-grained configuration model
Hot deployment and hot update support for configuration artifacts
Priority based mediation support
Comprehensive eventing capabilities with WS-Eventing support
Secure vault for encrypting passwords in configuration files
File locking support in the VFS transport for concurrent polling
URLRewrite medaitor for fast and simple URL rewriting
Synapse configuration observer API
Multiple identity support in the HTTPS transport
Enhanced JMX monitoring support for the NHTTP transport
Dead letter channel implementation (experimental)
Synapse XAR Maven plugin for generating configuration artifacts

SFTP file transer with WSO2 ESB.

2011-01-05T23:12:00.000-08:00

The VFS transport implementation is based on Apache Commons VFS implementation. VFS (Virtual File System) transport implementation is a module which belongs to the Apache Synapse project. It has a set of service level parameters that needs to be specified for each service.

VFS service level parameters and their descriptions can be found in [1] and the endpoint formats can be found in [2].

Following is a sftp sample for ESB 3.0.1. It copies a file from one sftp location to another sftp folder. SFTPVFSProxy is the proxy service which copies file from one sftp location to another.

If you need further information or need help troubleshooting this sample refer [5].


<proxy name="SFTPVFSProxy" transports="vfs" startOnLoad="true" xmlns="http://ws.apache.org/ns/synapse">
     <target>
         <inSequence>
             <log level="full"/>
             <property name="File" expression="fn:concat('test-', get-property('transport', 'FILE_PATH'))" scope="default"/>
             <property name="transport.vfs.ReplyFileName" expression="fn:concat(fn:substring-after(get-property('MessageID'), 'urn:uuid:'), '.xml')" scope="transport"/>
             <property name="OUT_ONLY" value="true"/>
             <send>
                 <endpoint name="endpoint_urn_uuid_A1546EFFD75FC9CCED785986339425964585275">
                     <address uri="vfs:sftp://heshan:password@10.101.1.112/home/heshan/out"/>
                 </endpoint>
             </send>
         </inSequence>
     </target>
     <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
     <parameter name="transport.PollInterval">15</parameter>
     <parameter name="transport.vfs.MoveAfterProcess">vfs:sftp://heshan:password@10.101.1.112/home/heshan/original</parameter>
     <parameter name="transport.vfs.FileURI">vfs:sftp://heshan:password@10.101.1.112/home/heshan/in/test.xml</parameter>
     <parameter name="transport.vfs.MoveAfterFailure">vfs:sftp://heshan:password@10.101.1.112/home/heshan/original</parameter>
     <parameter name="transport.vfs.FileNamePattern">.*.xml</parameter>
     <parameter name="transport.vfs.ContentType">application/xml</parameter>
     <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
</proxy>

Following is the XML file (test.xml) that is being moved.


<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
  <soapenv:Body>
      <getQuote xmlns="http://services.samples">
          <request>
              <symbol>IBM</symbol>
          </request>
      </getQuote>
  </soapenv:Body>
</soapenv:Envelope>

If you are interested in trying out more VFS samples, refer [3] and [4].

[1] - http://wso2.org/project/esb/java/3.0.1/docs/transports/transports-catalog.html#VfsTrp
[2] - http://commons.apache.org/vfs/filesystems.html#SFTP
[3] - http://wso2.org/project/esb/java/3.0.1/docs/samples/transport_samples.html#Sample254
[4] - http://wso2.org/project/esb/java/3.0.1/docs/samples/transport_samples.html#Sample255
[5] - http://wso2.org/library/tutorials/2011/01/sftp-file-transer-wso2-esb

Debug Carbon server when it is started as a daemon

2010-11-23T22:32:00.000-08:00

WSO2 Carbon Server can be run as a daemon on Unix/Linux systems. Say for instance that you need to remote debug the server when it is started as a daemon. This blogpost will be discussing $subject.

1) Open up the wrapper.conf file.


heshan@heshan-ThinkPad:~/Dev/customer/wso2esb-3.0.1/bin$ vim ../repository/conf/wrapper.conf

2) Add following entries to the wrapper.conf.


wrapper.java.additional.20=-Xdebug
wrapper.java.additional.21=-Xnoagent
wrapper.java.additional.22=-Djava.compiler=NONE
wrapper.java.additional.23=-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005

3) Start the ESB as a daemon.


heshan@heshan-ThinkPad:~/Dev/customer/wso2esb-3.0.1/bin$ ./wso2server.sh start
Starting WSO2 ESB v3.0.1...

4) Start the debugger.

5) Monitor the log.


heshan@heshan-ThinkPad:~/Dev/customer/wso2esb-3.0.1/bin$ tail -f ../repository/logs/wrapper.log
INFO   | jvm 1    | 2010/11/24 11:35:09 |   object space 84224K, 76% used [0x00007fbfcff20000,0x00007fbfd3e0dff0,0x00007fbfd5160000)
STATUS | wrapper  | 2010/11/24 11:35:09 | <-- Wrapper Stopped STATUS | wrapper  | 2010/11/24 11:45:46 | --> Wrapper Started as Daemon
WARN   | wrapper  | 2010/11/24 11:45:46 | ------------------------------------------------------------------------
WARN   | wrapper  | 2010/11/24 11:45:46 | The JVM is being launched with a debugger enabled and could possibly be
WARN   | wrapper  | 2010/11/24 11:45:46 | suspended.  To avoid unwanted shutdowns, timeouts will be disabled,
WARN   | wrapper  | 2010/11/24 11:45:46 | removing the ability to detect and restart frozen JVMs.
WARN   | wrapper  | 2010/11/24 11:45:46 | ------------------------------------------------------------------------
STATUS | wrapper  | 2010/11/24 11:45:46 | Launching a JVM...
INFO   | jvm 1    | 2010/11/24 11:45:46 | Listening for transport dt_socket at address: 5005
INFO   | jvm 1    | 2010/11/24 11:45:56 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2010/11/24 11:45:56 |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2010/11/24 11:45:56 |
INFO   | jvm 1    | 2010/11/24 11:45:56 | [2010-11-24 11:45:56,845]  INFO - Main Initializing system...

Now you have successfully debugged the Carbon Server, when it is started as a daemon.

WSO2 Basketball finals 2010

2010-10-29T21:13:00.000-07:00

QUALIFYING MATCHES

The 3rd annual WSO2 Basketball tournament was held over the month of October. We had 4 teams and 6 qualifying matches leading up to the finals. Wild Boars and Legions were the teams with the leading scores and they were chosen to be in the finals. When comparing with last 2 years, this time around every team had a balanced set of players. It can be seen by results of the preliminary round matches, where 3 teams had won 2 out of 3 matches they faced. Therefore, we had to choose the finalists by getting the accumulated scores of each team.

THE TEAMS
The Legions were led by our CEO, Dr. Sanjiva Weerawarna and the Wild Boars were led by our VP of Engineering, Samisa Abeysinghe.


====================================================
Legions              |         Wild Boars       |
====================================================
Amal Rangana            |Amila Suriyarachchi       |
Chamara Silva           |Asanka Abeysinghe (VC)    |
Chanaka Jayasena        |Asela Pathberiya          |
Danushka Menikkumbura   |Deependra Ariyadewa       |
Flora Ariyapala         |Dimuthu Leelarathne       |
Gayani Rajanayake       |Hasmin Abdul Cader        |
Isuru Suriarachchi      |Heshan Suriyarachchi      |
Janath Sivayoganathan   |Milinda Lakmal Pathirage  |
Kalpani Wanigaratne     |Nandika Jayawardana       |
Mahesh Marcus           |Rajika Kumasiri           |
Sanjiva Weerawarana (C) |Samisa Abeysinghe (C)     |
Srinath Perera          |Sumedha Rubasinghe        |
Tharindu Mathew         |Udeshika Ratnavira        |
Thilina Buddika         |Thilanga Pitigala         |
Waruna Ranasinghe       |Anjana Fernando           |
Miyuru Daminda          |Yasith Nakandana          |
Kasun Indrasiri         |Lavi De Silva             |
Gayani Marasinghe       |Sanjaya Vithanagama       |
Pavithra Madurangi      |Denis Perera              |
Arjuna Samaraweera      |Shammi Jayasinghe         |
Asiri Rathnayake        |P.K.A. Thilini Ishaka     |
Eshara Kalpanie Fonseka |Kathiravelu Pradeeban     |
Janaka Ranabahu         |Udayanga Wickramasinghe   |
Sarasi Madushika        |Pradeep Fernando          |
Nirdesha Munasinghe     |Hasini Gunasinghe         |
Charith Wickramarachchi |Hasini Yatawatte          |
Dinusha Dilrukshi       |Sanjeewa Mallalgoda       |
Manisha Ellaperuma      |                          |
Meeyoni Fernando        |                          |
====================================================

THE FINAL
It was a rain hit final and we played in our usual outdoor Basketball court - the car-park ;). Eventhough it was raining we could see the crowd standing around the court and cheering for their favourites.

The Legions started playing very aggressively from the word go and they were determind to not let the Championship slip away from them. Wildboars on the other hand was equal to the task and did not want to repeat the 2009 finals (in which WBs became runners up). It was an evenly contested match and The Legions were leading at half time whisle. Although they were leading, the Wild Boars were not too far behind (I can't recall the half-time score).

Then we started the second half. In the second half Wild Boars caught up to Legions score. I remember a point where the scores were levelled at 36-all. From this point onwards, non of the two teams didn't let the other take the lead for more than 2 points. It was showing the symptoms of going for an extra time ending.

FINAL WORKOUT
As the game progressed, I was getting the feeling that the game should be finished by now. So I asked Pumika who was near the stop clock, "how much time left?". She told me 30 seconds. I instantly thought of getting a timeout, but since we had the ball in our hand and we were attacking, I didnt want to take a timeout. (At that point if I took a timeout, it will inturn let the Legions know of the stop clock. Therefore, I opted not to take a timeout :) )

Asanka was controlling the ball at that time. I shouted at him "SHOOT! SHOOT!" (BTW, the scores were levelled at this point, 42-all). I don't know whether he heard my screms in the middle of the roar from the crowd. Anjana, Ude and I, was guarded by the defenders. Asanka, cleverly dribbled towards the baseline, which resulted in two defenders going towrds him to guard his move. That move, freed Samisa (the defender that should guard Samisa was now defending Asanka). Then Asanka passed the ball back to Samisa, who hit a long range 2 pointer to seal the win for the Wild Boars. That marked the end of a nail biting final. A final which I will remember for a long time. :)

Hats off to Legions for giving such a good game and in my book, both the teams were winners that night. They both fought hard to win the Championship. If you have a look back at the Legions past performances, this is a significant improvement from their side.

SCORE SHEETS


==============================================================
Date                     |    Teams                     |Score
==============================================================
Wednesday 6th 4.00 pm    | Cloud bots Vs. Titans        |31:53
Thursday 7th 4.00 pm     | Legion Vs. Wild Boars        |23:34
Tuesday 12th 4.00 pm     | Titans Vs. Wild Boars        |33:28
Thursday 14th 4.00 pm    | Cloud bots Vs. Legion        |22:54
Tuesday 19th 4.00 pm     | Cloud bots Vs. Wild Boars    |34:61
Thursday 21st 4.00 pm    | Titans Vs. Legion            |29:40
Tuesday 26th 4.00 pm     | Cloud bots Vs. Titans        |41:72
Thursday 28th 7.00 pm    | Wild Boars Vs. Legions       |44:42
==============================================================

OBSERVAIONS
Piyumika was the main person responsible for organizing this year's tournament. She had given attention to detail in organizing this very successful event which everyone enjoyed very much. I take this opportunity to thank (on behalf of all the players) Piyumika and her team for making this a memorable night. Specially the idea to bring in a face painter added color to the event :).

I take the this opportunity to thank the crowd (who came to cheer for us or against us) who supported the players throughout this tournament. If it wasn't for ya'll it wont be an entertaining tournament like this.

As Isuru pointed out the other day, we did not have any serious injuries (broken bones, torn muscles, etc:) ) during this tournament. That means we are starting to play real Basketball and we have moved away from playing the Rugby+Basketball [2] hybrid, that we were used to play :D.

I am finishing off this post with an extract from a Fort Minor song.

This is ten percent luck, twenty percent skill
Fifteen percent concentrated power of will
Five percent pleasure, fifty percent pain
And a hundred percent reason to remember the name

Related Posts
[1] - http://heshans.blogspot.com/2008/10/internship-wso2.html
[2] - http://heshans.blogspot.com/2009/10/basketball-wso2-how-to-survive.html

Pictures courtesy of Chinthana Wilmuna.

Generate custom Error messages with WSO2 ESB

2010-10-25T05:41:00.000-07:00

In this blogpost we will be looking at how to generate a soap fault using the makefault mediator. In addition to that I will show how to embed a custom message within that soap fault. Inorder to achieve this goal we will be using the makefault mediator and a script mediator.

The Synapse configuration used:


<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
<localEntry key="detailsTransformScript" src="file:repository/samples/resources/script/detailTransform.js"/>
<sequence name="myFaultHandler">
    <property name="uniqueKey" value="123" scope="default" type="STRING"/>
    <property name="customErrorCode" value="8719" scope="default" type="STRING"/>
    <property name="customErrorText" value="Issue has " scope="default" type="STRING"/>
    <property name="customTime" expression="get-property('SYSTEM_DATE')" scope="default" type="STRING"/>
    <script language="js" key="detailsTransformScript" function="transformDetail"/>
    <log level="custom">
        <property name="Detail" expression="get-property('customErrorDetail')"/>
    </log>
    <makefault version="soap11">
        <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/>
        <reason expression="get-property('ERROR_MESSAGE')"/>
        <detail expression="get-property('customErrorDetail')"/>
    </makefault>
    <send/>
</sequence>
<sequence name="fault">
    <log level="full">
        <property name="MESSAGE" value="Executing default "fault" sequence"/>
        <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
        <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
    </log>
    <drop/>
</sequence>
<sequence name="main" onError="myFaultHandler">
    <in>
        <switch xmlns:m0="http://services.samples" source="//m0:getQuote/m0:request/m0:symbol">
            <case regex="MSFT">
                <send>
                    <endpoint name="endpoint_urn_uuid_F3FC39CF93F681A11649593938524451942754528">
                        <address uri="http://bogus:9000/services/NonExistentStockQuoteService"/>
                    </endpoint>
                </send>
            </case>
            <case regex="SUN">
                <send>
                    <endpoint name="endpoint_urn_uuid_F3FC39CF93F681A1164959398253284-1608236576">
                        <address uri="http://localhost:9009/services/NonExistentStockQuoteService"/>
                    </endpoint>
                </send>
            </case>
        </switch>
        <drop/>
    </in>
    <out>
        <send/>
    </out>
</sequence>
</definitions>

The javascript file used in the script mediator:


 function transformDetail(mc) {
     var symbol = mc.getPayloadXML()..*::Code.toString();
     var errorCode = mc.getProperty("customErrorCode");
     var errorText = mc.getProperty("customErrorText");
     var time = mc.getProperty('customTime');
     mc.setProperty("customErrorDetail", <AppErrorCode><TimeStamp>{time}</TimeStamp><ErrorCode>{errorCode}</ErrorCode><ErrorText>{errorText}</ErrorText></AppErrorCode>);
  }

Instructions to run the sample.
1) Copy the attached javascript file to ESB_HOME/repository/samples/resources/script/ directory.

2) Startup the ESB instance. Copy the attached synapse configuration to source view of the Management UI and hit update.

3) Start the Axis2 server and deploy the SimpleStockQuoteService if not already done.

4) Execute the client using following command.


ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=MSFT

5) Monitor the response message with TCPMon.


HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Host: 127.0.0.1:8281
SOAPAction: "urn:getQuote"
Date: Thu, 21 Oct 2010 09:52:23 GMT
Transfer-Encoding: chunked

338
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
     <wsa:MessageID>urn:uuid:952C448142FB1B1FE925278283667424-1166645935</wsa:MessageID>
     <wsa:Action>urn:getQuote</wsa:Action>
     <wsa:RelatesTo>urn:uuid:6DDD0BCE4CDCFB5AFD1287654743750</wsa:RelatesTo>
  </soapenv:Header>
  <soapenv:Body>
     <soapenv:Fault>
        <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
        <faultstring>Connection refused or failed for : bogus:9000, IO Exception occured : bogus</faultstring>
        <detail>
<AppErrorCode>
<TimeStamp>10/21/10 3:22 PM</TimeStamp>
<ErrorCode>8719</ErrorCode>
<ErrorText>A custom issue has occured</ErrorText>
</AppErrorCode></detail>
     </soapenv:Fault>
  </soapenv:Body>
</soapenv:Envelope>0

As you can see we have added a custom details element which is containing some information that you would like to generate.

Further Reading

[1] - Refer transport ERROR codes in https://svn.apache.org/repos/asf/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/SynapseConstants.java

[2] - Property Mediator section of the WSO2 ESB Configuration language
http://wso2.org/project/esb/java/3.0.1/docs/configuration_language.html#property

[3] - WSO2 ESB error handling samples.
http://wso2.org/project/esb/java/3.0.1/docs/samples/message_mediation_samples.html#Sample4
http://wso2.org/project/esb/java/3.0.1/docs/samples/message_mediation_samples.html#Sample5

[4] - We are having built in Error Codes for transport related errors. Say for instance that you need to handle an error related to an XML format error. That kind of issues can be resolved by using fault handlers.
eg: If a sequence fail in an XSLT transformation phase due to to an XML format error, you can register a fault handler for a sequence to handle it. For more information read Error Handling with Sequences and Proxy Services .

Send HTML format email from WSO2 ESB

2010-10-19T17:02:00.000-07:00

1. Enable mail transport sender and transport listener in the axis2.xml.


<transportSender name="mailto" <transportSender name="mailto" class="org.apache.axis2.transport.mail.MailTransportSender">
        <parameter name="mail.smtp.host">smtp.gmail.com</parameter>
        <parameter name="mail.smtp.port">587</parameter>
        <parameter name="mail.smtp.starttls.enable">true</parameter>
        <parameter name="mail.smtp.auth">true</parameter>
        <parameter name="mail.smtp.user">synapse.demo.0</parameter>
        <parameter name="mail.smtp.password">mailpassword</parameter>
        <parameter name="mail.smtp.from">synapse.demo.0@gmail.com</parameter>
</transportSender>

<transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener"/>

2. Register the ApplicationXMLFormatter as the formatter for text/html content type in the axis2.xml


&lt:messageFormatter contentType="text/html" class="org.apache.axis2.transport.http.ApplicationXMLFormatter"/>

3. In the mediation sequence, set the messageType property as well as the ContentType property to text/html (Setting both parameters is crucial to get this working. The messageType parameter is looked up by the mail transport to select the correct formatter. The other property is used by the formatter to set the right content type on the outgoing message.)

The sample proxy configuration is attached for your reference.


<proxy name="StockQuoteProxy" transports="http" xmlns="http://ws.apache.org/ns/synapse">
    <target>
       <inSequence>
          <property name="Subject" value="Custom Subject for Response" scope="transport"/>
         <property name="messageType" value="text/html" scope="axis2"/>
         <property name="ContentType" value="text/html" scope="axis2"/>
         <property name="OUT_ONLY" value="true"/>
   <script language="js"><![CDATA[
        mc.setPayloadXML(<h1>WSO2 ESB Rocks!</h1>);
   ]]></script>
          <log level="full"/>
          <send>
             <endpoint>
                <address uri="mailto:test@test.com"/>
             </endpoint>
          </send>
       </inSequence>
    </target>
</proxy>

4. To test the sample, simply send a request to the sample proxy service using the sample Axis2 client. That will send an e-mail with in-line HTML content to the target endpoint.

eg.


wso2esb-3.0.0/samples/axis2Client$ ant stockquote -Daddurl=http://localhost:8280/services/StockQuoteProxy

WSO2 ESB wins gold award at NBQSA 2010

2010-10-08T01:05:00.000-07:00

WSO2 ESB won the gold award in NBQSA 2010. I am proud to be a member of the ESB team. :)

Build WSO2 Stratos ESB from source

2010-09-30T02:05:00.000-07:00

Following blogpost will discuss how to build WSO2's Stratos ESB (aka Cloud ESB) from source.

1. First build carbon trunk upto features. Please follow my earlier post on building WSO2 ESB from source.

2. Checkout WSO2 Stratos source.


svn co https://svn.wso2.org/repos/wso2/trunk/stratos

Then following directories/files will be checked into your file system.


.
|-- build
|-- components
|-- features
|-- pom.xml
|-- samples
|-- services
`-- setup

3. Build Stratos components project.


heshan@heshan-laptop:~/Dev/trunk/stratos/components$ mvn clean install -Dmaven.test.skip=true

4. Build Strtos features project.


heshan@heshan-laptop:~/Dev/trunk/stratos/features$ mvn clean install -Dmaven.test.skip=true

5. Build Stratos Manager.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/manager$ mvn clean install -Dmaven.test.skip=true

6. Build Stratos ESB.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/esb$ mvn clean install -Dmaven.test.skip=true

7. Run the setup script.


heshan@heshan-laptop:~/Dev/trunk/stratos/setup$ ./setup.sh

8. Create the necessary databases.


mysql>CREATE DATABASE stratos_db;

mysql>CREATE DATABASE WSO2CARBON_DB;

mysql>CREATE DATABASE billing;

Create users and give necessary user-permssions.


mysql>CREATE USER 'wso2stratos'@'localhost' IDENTIFIED BY 'wso2stratos';
mysql>GRANT ALL ON *.* TO 'wso2stratos'@'localhost';

mysql>CREATE USER 'billing'@'localhost' IDENTIFIED BY 'billing';
mysql>GRANT ALL ON *.* TO 'billing'@'localhost';

Create tables.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/manager/modules/distribution/target/wso2stratos-manager-1.0.0-SNAPSHOT/dbscripts$ mysql -u root -p < billing-mysql.sql billing

9. Start the Stratos Manager.
NOTE: Server should be started with -Dsetup option in the first time.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/manager/modules/distribution/target/wso2stratos-manager-1.0.0-SNAPSHOT/bin$ ./wso2server.sh -Dsetup

10. Start Stratos ESB.
NOTE: Server should be started with -Dsetup option in the first time.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/esb/modules/distribution/target/wso2stratos-esb-1.0.0-SNAPSHOT/bin$ ./wso2server.sh -Dsetup

11. Stop the above servers. Then startup the both the servers again without -Dsetup option.


heshan@heshan-laptop:~/Dev/trunk/stratos/services/manager/modules/distribution/target/wso2stratos-manager-1.0.0-SNAPSHOT/bin$ ./wso2server.sh
heshan@heshan-laptop:~/Dev/trunk/stratos/services/esb/modules/distribution/target/wso2stratos-esb-1.0.0-SNAPSHOT/bin$ ./wso2server.sh

12. Create a Tenent by logging into the Stratos Manager. Then using the credentials obtained, you can log into the Stratos ESB.

Migrate Synapse Configuration from 1.2 to 2.0

2010-09-10T22:18:00.000-07:00

The current namespace of the synapse-2.0 trunk is http://synapse.apache.org/ns/2010/04/configuration. The earlier namespace of synapse-1.2 was http://ws.apache.org/ns/synapse. Therefore you may encounter some errors, when running a synapse configuration of a 1.2 release against a trunk build(ie. synapse-2.0.0-SNAPSHOT). Since the Synapse configuration has undergone some configuration changes, merely changing the namespace of the the old synapse configuration wont help you to solve your problem.

That's why Synapse ships a migration tool for migrating a 1.2 configuration to a 2.0 configuration. Ruwan has written the xslt transformation for the above. You can find it in the Synapse trunk.

Recently I had to update the Synapse sample configurations of WSO2 ESB's trunk. This tool made my life a lot easier during the migration process. I modified the sample migrator to suit my purpose. I am sharing the code here, if you need to migrate the synapse configurations in bulk.


import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.stream.StreamResult;
import javax.xml.transform.stream.StreamSource;
import java.io.FileReader;
import java.io.FileWriter;
import java.io.IOException;

/**
*
*/
public class ConfigurationMigrator {

  private static final String MIGRATOR_XSLT_PATH
          = "modules/migrator/src/main/resources/synapse-configuration-migrator.xslt";

  public static int confgNumber [] = new int []
              {0,1,2,3,4,5,6,7,8,9,10,11,
              50,51,52,53,54,55,56,57,58,
              100,101,102,
              150,151,152,153,154,155,
              200,201,202,
              250,251,252,253,254,255,256,257,258,259,
              260,261,262,264,265,
              300,
              350,351,352,353,354,
              360,361,362,363,
              370,371,372,
              380,381,
              390,391,
              400,420,430,
              500,501,502,503,504,
              550,551,
              600,601,602,603,604,605,606,
              652,654};

  public static void doTransform(String xmlFile, String xslFile, String outFile)
          throws TransformerException, IOException {

      FileReader xslFileReader = new FileReader(xslFile);
      StreamSource xslStreamSource = new StreamSource(xslFileReader);

      FileReader xmlFileReader = new FileReader(xmlFile);
      StreamSource xmlStreamSource = new StreamSource(xmlFileReader);

      FileWriter outFileWriter = new FileWriter(outFile);
      StreamResult outStreamResult = new StreamResult(outFileWriter);

      TransformerFactory transformerFactory = TransformerFactory.newInstance();
      Transformer transformer = transformerFactory.newTransformer(xslStreamSource);

      transformer.transform(xmlStreamSource, outStreamResult);
      outFileWriter.flush();
  }

  public static void migrateAllConfigs(String source, String destination){
      System.out.println("\n\t#######################################################");
      System.out.println("\t#      Apache Synapse - Configuration Migration       #");
      System.out.println("\t#######################################################");

      System.out.println("\n[INFO] Migration STARTED");

      for (int aConfgNumber : confgNumber) {
          try {
              System.out.println("[INFO]Migrating synapse configuration : " + aConfgNumber);
              doTransform(source + aConfgNumber + ".xml", MIGRATOR_XSLT_PATH, destination + aConfgNumber +".xml");

          } catch (TransformerException e) {
              handleException("Migration FAILED\n\t" + e.toString());
          } catch (IOException e) {
              handleException("Migration FAILED\n\t" + e.toString());
          }
      }

      System.out.println("[INFO] Migration COMPLETED");

  }

  public static void main(String args[]) {
      migrateAllConfigs("/home/heshan/Dev/trunk/carbon/products/esb/modules/samples/src/main/conf/synapse/synapse_sample_",
              "/tmp/synapse-config/synapse_sample_");
  }

  private static void handleException(String message) {
      System.out.println("[ERROR] " + message);
  }
}

WSO2 Enterprise Service Bus (ESB) 3.0.1 Released

2010-09-09T21:19:00.000-07:00

The WSO2 ESB team is pleased to announce the release of version 3.0.1 of the Open Source Enterprise Service Bus (ESB).

WSO2 ESB 3.0.1 is developed on top of the revolutionary WSO2 Carbon platform (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the ESB. Further, any existing features of the ESB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 ESB can be fully customized and tailored to meet your exact SOA needs.

You can download this distribution from http://wso2.org/downloads/esb and give it a try.

How to Run

Extract the downloaded zip
Go to the bin directory in the extracted folder
Run the wso2server.sh or wso2server.bat as appropriate
Point your browser to the URL https://localhost:9443/carbon
Use "admin", "admin" as the username and password to login as an admin and create a user account
Assign the required permissions to the user through a role
If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
Sample configurations can be started by the wso2esb-samples script passing the sample number with the -sn option (Please have a look at the samples guide for more information, on running samples)

New Features of WSO2 ESB 3.0.1

There are no new features in this release. This is a bug fix release. See the section "Bugs Fixed in WSO2 ESB 3.0.1" for more information.

Key Features of WSO2 ESB

Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
Non-blocking HTTP/S transports based on Apache HttpCore-NIO for ultrafast execution and support for thousands of connections at high concurreny with constant memory usage.
Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS configurations ..)
Easily extendable via custom Java classes (mediator and command)/Spring configurations, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler.
Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
Lightweight, XML and Web services centric messaging model
Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Health Level-7 protocol)
Enhanced support for the VFS (File/FTP/SFTP), JMS, Mail transports with optional TCP/UDP transports and transport switching among any of the above transports
Support for message splitting & aggregation using the EIP and service callouts
Database lookup & store support with DBMediators with reusable database connection pools
WS-Eventing support with event sources and event brokering
Rule based mediation of the messages using the Drools rule engine
Transactions support via the JMS transport and Transaction mediator for database mediators
Internationalized GUI management console with user management for configuration development
Integrated monitoring support with statistics, configurable logging and tracing
JMX monitoring support and JMX management capabilities like, Graceful/Forceful shutdown/restart

Bugs Fixed in This Release

This release of WSO2 ESB comes with a number of bug fixes, both in the base framework and the ESB specific componenents. All the issues which have been fixed in ESB 3.0.1 are recorded at following locations:

Known Issues

Endpoint UI does not support selecting already existing endpoints as child endpoints when creating load balance/failover endpoints
HTTP GET requests performed on an endpoint that has a trailing '/' character, do not work properly
SOAP tracer does not work when the message relay is activated
The sequence editor and the built-in XML editors do not work properly on Google Chrome

All the open issues pertaining to WSO2 ESB 3.0 are reported at following locations:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : carbon-dev@wso2.org | Subscribe | Mail Archive
User List : esb-java-user@wso2.org | Subscribe | Mail Archive

Reporting Issues

WSO2 encourages you to report issues and your enhancement requests for the WSO2 ESB using the public JIRA.

You can also watch how they are resolved, and comment on the progress..

Discussion Forums

Alternatively, questions could be raised using the forums available.

WSO2 ESB Forum : Discussion forum for WSO2 ESB developers/users

Support

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

For more information about WSO2 ESB please see http://wso2.com/products/enterprise-service-bus.

-- The WSO2 ESB Team --

Win a free trip to WSO2 Con

2010-09-02T01:19:00.000-07:00

The sponsorship includes:

* Return air ticket, including international!
* 5 nights hotel accommodation
* Ground transport
* US $50 per Diem
* Free pass to WSO2Con 2010
* Free pass to two day special Technical Workshop
* Invitation to VIP Gala Dinner Celebration
* Invitation to WSO2 5 Year Celebration Party

For more information visit [1].

[1] - http://wso2.org/wso2con2010-sponsorship

WSO2 Con 2010

2010-09-01T23:28:00.000-07:00

WSO2 Con 2010 will be held at HNB Towers, Colombo on 14th and 15th September. For more information visit WSO2Con website.

Sending UTF-16 messages through Synapse

2010-07-20T18:05:00.000-07:00

When fixing SYNAPSE-662 and SYNAPSE-670, I had to send UTF-16 messages to the SimpleStockQuoteService to verify the fixes. Following are the sample configuration and client code that I used to verify the fixes.

1. Start the Synapse ESB with the following configuration.


<definitions xmlns="http://ws.apache.org/ns/synapse">
   <switch source="//m0:getQuote/m0:request/m0:symbol" xmlns:m0="http://services.samples/xsd">
       <case regex="IBM">
           <!-- the property mediator sets a local property on the *current* message -->
           <property name="symbol" value="Great stock - IBM"/>
       </case>
       <case regex="MSFT">
           <property name="symbol" value="Are you sure? - MSFT"/>
       </case>
       <default>
           <!-- it is possible to assign the result of an XPath expression as well -->
           <property name="symbol"
                 expression="fn:concat('Normal Stock - ', //m0:getQuote/m0:request/m0:symbol)"
                 xmlns:m0="http://services.samples/xsd"/>
       </default>
   </switch>

   <log level="custom">
       <!-- the get-property() XPath extension function allows the lookup of local message properties
           as well as properties from the Axis2 or Transport contexts (i.e. transport headers) -->
       <property name="symbol" expression="get-property('symbol')"/>
       <!-- the get-property() function supports the implicit message headers To/From/Action/FaultTo/ReplyTo -->
       <property name="epr" expression="get-property('To')"/>
   </log>

   <!-- Send the messages where they are destined to (i.e. the 'To' EPR of the message) -->
   <send/>
</definitions>

2. Start the Axis2 server and deploy the SimpleStockQuoteService.

3. Use the following axis2 client (which generates a UTF-16 message) to invoke the service.


package org.wso2.esb;

import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axis2.AxisFault;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;

import java.lang.*;

public class MyClient {
   public static OMElement createPayload(){
       OMFactory fac = OMAbstractFactory.getOMFactory();
       OMNamespace omNs = fac.createOMNamespace("http://services.samples", "ns");
       OMElement method = fac.createOMElement("getQuote", omNs);
       OMElement value1 = fac.createOMElement("request", omNs);
       OMElement value2 = fac.createOMElement("symbol", omNs);

       value2.addChild(fac.createOMText(value1, "IBM"));
       value1.addChild(value2);
       method.addChild(value1);
       return method;
   }

   public static void main(String args[]){
       OMElement payload = createPayload();
       ServiceClient serviceclient;

       ConfigurationContext configurationContext = null;
       try {        
           configurationContext = ConfigurationContextFactory.
                  createConfigurationContextFromFileSystem("/home/heshan/Dev/trunk/synapse/modules/distribution/target/synapse-2.0.0-SNAPSHOT/samples/axis2Client/client_repo",
                          "/home/heshan/Dev/trunk/synapse/modules/distribution/target/synapse-2.0.0-SNAPSHOT/samples/axis2Client/client_repo/conf/axis2.xml");

          serviceclient = new ServiceClient();
          Options opt = new Options();

          opt.setTo(new EndpointReference ("http://localhost:8281/services/StockQuote"));
          opt.setAction("urn:getQuote");
    opt.setProperty(org.apache.axis2.Constants.Configuration.CHARACTER_SET_ENCODING,"UTF-16");
          opt.setSoapVersionURI(org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);
          serviceclient.setOptions(opt);

          OMElement ome = serviceclient.sendReceive(payload);
          System.out.println("The output is : " + ome);

       } catch (AxisFault axisFault) {
           axisFault.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.

       }

   }
}

Extend the Axis2 Framework to Support JVM Based Scripting Languages

2010-07-14T11:03:00.000-07:00

This article explains how to extend the Axis2 framework to support Java Virtual Machine (JVM) based scripting languages such as Jython, JRuby, etc. It provides a high level overview of the subject, covering some key concepts of Apache Axis2 and how it can be used to come up with an extension to a JVM based scripting language. After going through this article, a developer will be able to extend the Axis2 framework to support the JVM based scripting language of his or her choice.

If you are interested, read the full article on InfoQ.com.

I take this opportunity to thank Nandika for doing the technical review and Charles Humble for doing the editorial review.

Build WSO2 ESB from source

2010-06-22T21:24:00.000-07:00

This post will discuss how to build WSO2 ESB[1] from the WSO2 Carbon[2] trunk.

1) Checkout WSO2 Carbon project's trunk.


heshan@heshan-laptop:~/Dev/trunk/$ svn co https://svn.wso2.org/repos/wso2/trunk/carbon

Following directories/files would be checked-out to your file system.


carbon
|-- components
|-- core
|-- dependencies
|-- features
|-- orbit
|-- pom.xml
|-- products

2) Build the dependencies for ESB project.


heshan@heshan-laptop:~/Dev/trunk/carbon/dependencies$ mvn clean install -Dproduct=esb

Then the following dependencies will be built. If you encounter any build errors, try and build each project one at a time :)


dependencies
|-- abdera
|-- axiom
|-- axis2
|-- wss4j
|-- carbon-p2-plugin
|-- commons/caching
|-- commons/eventing
|-- commons/throttle
|-- commons/xkms
|-- p2
|-- rampart
|-- rhino
|-- sandesha
|-- savan
|-- synapse
|-- transports
|-- commons-vfs

Carbon Dependencies :-

Carbon platform makes use of already existing open source projects rather than trying to re-invent the wheel. We use popular and matured open source projects like apache axiom, axis2, synapse etc which fuel the very heart of the carbon platform. Dependencies contains all these open source projects that the carbon platform makes use of adding more value to them.

3) Build Carbon Orbit for ESB project.


heshan@heshan-laptop:~/Dev/trunk/carbon/orbit$ mvn clean install -Dproduct=esb

Carbon Orbit :-
WSO2 Carbon uses OSGi as its underlying modularization technology. But Many 3rd party open source libraries does not exists in osgi form (ie. in osgi bundle form). Therefore to introduce them to the carbon platform, we wrap-around them to make them proper OSGI bundles (They will be useful to any OSGI environment like felix, knoplerfish etc). Carbon-orbit project contains all these third party bundles.

4) Build Carbon Core for ESB project.


heshan@heshan-laptop:~/Dev/trunk/carbon/core$ mvn clean install -Dproduct=esb

Carbon Core :-
This is where we create the base for our platform. Everything runs on top of this base. From the simple OSGi framework to the UI framework, all the critical technologies for the platform are implemented here.

5) Build Carbon Components for ESB project.


heshan@heshan-laptop:~/Dev/trunk/carbon/components$ mvn clean install -Dproduct=esb

Carbon Components :-
Components module contains the main functionalities that are introduced by each and every product in addition to to the core level features. Among the close to 100 components each adds value to the product in a different way than the next. Some will enhance the security while some may just provide vital tools to monitor the health of the system.

6) Build Carbon Features for ESB project.


heshan@heshan-laptop:~/Dev/trunk/carbon/features$ mvn clean install -Dproduct=esb

Carbon Features :-
Equinox P2 has been integrated with WSO2 Carbon platform to enable provisioning capabilities. This enables you to extend or enhance your carbon platform with more functionalities or just strip out the irrelevant features which suits your context.

7) Build WSO2 ESB product.


heshan@heshan-laptop:~/Dev/trunk/carbon/products/esb$ mvn clean install

Carbon Product :-
Products module contains all the products ranging from ESB to BRS.

8) When the build is successful move to target folder inside esb project.


heshan@heshan-laptop:~/Dev/trunk/carbon/products/esb/modules/distribution/target$ ls
pom-transformed.xml  wso2esb-3.0.0-SNAPSHOT  wso2esb-3.0.0-SNAPSHOT-docs.zip  wso2esb-3.0.0-SNAPSHOT.zip

Then unzip the SNAPSHOT.


heshan@heshan-laptop:~/Dev/trunk/carbon/products/esb/modules/distribution/target$ unzip wso2esb-3.0.0-SNAPSHOT.zip

Start the ESB server


heshan@heshan-laptop:~/Dev/trunk/carbon/products/esb/modules/distribution/target/wso2esb-3.0.0-SNAPSHOT/bin$ ./wso2server.sh

Now you have successfully built and started a WSO2 ESB build from Carbon trunk.

References
[1] - http://wso2.com/products/enterprise-service-bus/
[2] - http://wso2.com/products/carbon/

NOTE: If you need to build any other Carbon based product, repeat the above steps by replacing the product name to the relevant product.

mvn version used for testing this was:


heshan@heshan-laptop:~$ mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-19 00:40:27+0530)
Java version: 1.6.0_03
Java home: /home/heshan/Installations/jdk1.6.0_03/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" arch: "i386" Family: "unix"

Setting up and configuring WSO2 Stratos Services

2010-06-17T23:24:00.000-07:00

In this screen-cast, Shankar walks you through the steps required to setting up a domain in WSO2 Stratos, configuring and customizing it according to your requirement.

Meeting CIO Challenges with WSO2 Stratos

2010-06-17T23:16:00.000-07:00

Call MS SQL Server SPs from WSO2 ESB

2010-05-28T23:26:00.000-07:00

This post will be focusing on MS SQL Server Stored Procedures(SP) and follow up my article titled "How to call database stored procedures from WSO2 ESB" on WSO2 OxygenTank.

You may think "why is he writing a separate post addressing MS SQL Server?". The reason is that; when calling MS SQL Server SPs, you need to slightly modify the mediator configuration in order to successfully call a SP.

Now let's dig in to "how to do this".

Setting up MS SQL database server
1. Install and setup MS SQL Server.

2. Create a sample database in MS SQL Server.
Following sql statments cab be used to create the same enviornment discussed in the above article.

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
IF NOT EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[company]') AND type in (N'U'))
BEGIN
CREATE TABLE [dbo].[company](
[compName] [varchar](10) NULL,
[id] [varchar](10) NULL,
[price] [decimal](18, 0) NULL,
[location] [varchar](10) NULL
) ON [PRIMARY]
END
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
IF NOT EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[getCompany]') AND type in (N'P', N'PC'))
BEGIN
EXEC dbo.sp_executesql @statement = N'
CREATE procedure [dbo].[getCompany] @compname varchar(10) as
select * from company where compName = @compname
'
END
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
IF NOT EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[updateCompany]') AND type in (N'P', N'PC'))
BEGIN
EXEC dbo.sp_executesql @statement = N'
CREATE procedure [dbo].[updateCompany] @compPrice decimal, @compName varchar(10) as
update company set price = @compPrice where compName = @compName
'
END

Setting up ESB server
1. Download latest version of WSO2 ESB from http://wso2.org/downloads/esb. This tutorial will be demonstrated upon the latest release of the WSO2 ESB. ie. WSO2 ESB-3.0.0.

2. Install it as a standalone server. Install location will be referred to as ESB_HOME from here onwards.

3. When using MS SQL Server, ms-sql-jdbc.jar should be added to the ESB classpath(i.e. ESB_HOME/repository/components/lib/).

4. Start WSO2ESB using the startup scripts.
eg. wso2server.bat for windows environments
wso2server.sh for linux environments

5. Open a web browser and navigate to https://localhost:9443/

6. Login to ESB. The default username/password will be admin/admin. Go through the User Interface and get yourself familiarized with WSO2 ESB environment.

ESB configuration
Following is the Synapse configuration used to call the MS SQL Stored Procedure. Pay close attention on 'how the SP query is written inside the mediator' :).

<definitions xmlns="http://ws.apache.org/ns/synapse">

<sequence name="main">
<in>
    <send>
        <endpoint>
            <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
        </endpoint>
    </send>
</in>

<out>
    <log level="custom">
        <property name="text"
                  value="** Reporting to the Database **"/>
    </log>

    <dbreport>
        <connection>
            <pool>
<url>jdbc:sqlserver://10.100.1.200:1433;databaseName=ESB_SP_SAMPLE</url>
<user>sa</user>
<password>test</password>
<driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver>
            </pool>
        </connection>
        <statement>
            <sql>{ call updateCompany(?,?) }</sql>
            <parameter expression="//m0:return/m1:last/child::text()"
                       xmlns:m0="http://services.samples" xmlns:m1="http://services.samples/xsd" type="DOUBLE"/>
            <parameter expression="//m0:return/m1:symbol/child::text()"
                       xmlns:m0="http://services.samples" xmlns:m1="http://services.samples/xsd" type="VARCHAR"/>
        </statement>
    </dbreport>
    <log level="custom">
        <property name="text"
                  value="** Looking up from the Database **"/>
    </log>
    <dblookup>
        <connection>
            <pool>
<url>jdbc:sqlserver://10.100.1.200:1433;databaseName=ESB_SP_SAMPLE</url>
<user>sa</user>
<password>test</password>
<driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver>
            </pool>
        </connection>
        <statement>
            <sql>{ call getCompany(?) }</sql>
            <parameter expression="//m0:return/m1:symbol/child::text()"
                       xmlns:m0="http://services.samples" xmlns:m1="http://services.samples/xsd" type="VARCHAR"/>
            <result name="stock_prize" column="price"/>
        </statement>
    </dblookup>
    <log level="custom">
        <property name="text"
                  expression="fn:concat('Stock Prize - ',get-property('stock_prize'))"/>
    </log>
    <send/>
</out>
</sequence>

</definitions>

Running the sample.
1. Start the WSO2 ESB server with the attached synapse configuration named dbreport_synapse_config.xml.

2. Start the Axis2 server and deploy the SimpleStockQuoteService if not already done.

3. Run the client.

ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=WSO2

SOA Summer School - 2010

2010-05-19T21:08:00.000-07:00

Summer School will focus on Service Oriented Architecture (SOA) concepts, technologies, and best practices. In addition to that, this year's Summer School sessions will be including insights into proven techniques for cloud deployments, business process management (BPM), complex event processing (CEP) , business rules processing and more.

Summer School 2010 runs for two months starting 10^th June and ending on 29^th July. Do you know what's the best news about Summer School is ? IT'S ABSOLUTELY FREE ! :) yes, free as in open source ;)

If you are interested, you can register here.

Call database stored procedures from WSO2 ESB

2010-05-11T08:22:00.000-07:00

Stored procedure is a powerful mechanism to interact with a relational database. It allows business logic to be embedded inside database as an API. Stored procedure is stored in a precompiled format within the database itself resulting in faster execution speed.

WSO2 Enterprise Service Bus is capable of calling database Stored Procedures via the db mediators. If your application uses stored procedures and you want to expose them to outside business systems, WSO2 ESB is the answer that you were looking for.

Read the full article on OT.

The WSO2 Enterprise Service Bus (ESB) 3.0.0 Released

2010-05-02T21:14:00.000-07:00

The WSO2 ESB team is pleased to announce the release of version 3.0.0 of the Open Source Enterprise Service Bus (ESB).

WSO2 ESB 3.0.0 is developed on top of the revolutionary WSO2 Carbon platform (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the ESB. Further, any existing features of the ESB which are not required to your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 ESB can be fully customized and tailored to meet your exact SOA needs.

You can download this distribution from http://wso2.org/downloads/esb and give it a try.

How to Run

Extract the downloaded zip
Go to the bin directory in the extracted folder
Run the wso2server.sh or wso2server.bat as appropriate
Point your browser to the URL https://localhost:9443/carbon
Use "admin", "admin" as the username and password to login as an admin and create a user account
Assign the required permissions to the user through a role
If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
Sample configurations can be started by the wso2esb-samples script passing the sample number with the -sn option (Please have a look at the samples guide for more information, on running samples)

New Features of WSO2 ESB 3.0.0

Priority based mediation through priority executors
WS-Discovery support and dynamic endpoint discovery
Message Relay for efficient pass through of messages
Component manager to install and uninstall features (provisioning support)
Common Internet File System (CIFS) support through the VFS transport
File locking functionality in the VFS transport to support concurrent polling
Smooks mediator for efficient message transformation
Enrich mediator for smart message manipulation
OAuth mediator for 2-legged OAuth support
Default endpoint UI
Hot deploy and hot update configuration elements (sequences, endpoints, proxy services etc)
Transport level statistics collection and monitoring
POX security support
Dependency detection and alerting for mediation configuration elements
Mediation statistics API and custom mediation statistics consumers
Multiple certificate/identity support in the NHTTP transport sender
Improved logging capabilities for the NHTTP transport
Templates based proxy service development in the UI
Dashboard to monitor server environment and runtime
Easy creation and management capabilities for dynamic sequences and endpoints
Pagination to service management, endpoint management and sequence management UIs
Obtaining resources like WSDL's through web proxy servers

Key Features of WSO2 ESB

Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
Non-blocking HTTP/S transports based on Apache HttpCore-NIO for ultrafast execution and support for thousands of connections at high concurreny with constant memory usage.
Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS configurations ..)
Easily extendable via custom Java classes (mediator and command)/Spring configurations, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler.
Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
Lightweight, XML and Web services centric messaging model
Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Health Level-7 protocol)
Enhanced support for the VFS (File/FTP/SFTP), JMS, Mail transports with optional TCP/UDP transports and transport switching among any of the above transports
Support for message splitting & aggregation using the EIP and service callouts
Database lookup & store support with DBMediators with reusable database connection pools
WS-Eventing support with event sources and event brokering
Rule based mediation of the messages using the Drools rule engine
Transactions support via the JMS transport and Transaction mediator for database mediators
Internationalized GUI management console with user management for configuration development
Integrated monitoring support with statistics, configurable logging and tracing
JMX monitoring support and JMX management capabilities like, Graceful/Forceful shutdown/restart

Bugs Fixed in This Release

This release of WSO2 ESB comes with a number of bug fixes, both in the base framework and the ESB specific componenents. All the issues which have been fixed in ESB 3.0.0 are recorded at following locations:

Known Issues

Endpoint UI does not support selecting already existing endpoints as child endpoints when creating load balance/failover endpoints
HTTP GET requests performed on an endpoint that has a trailing '/' character, do not work properly
SOAP tracer does not work when the message relay is activated
The sequence editor and the built-in XML editors do not work properly on Google Chrome

All the open issues pertaining to WSO2 ESB 3.0 are reported at following locations:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : carbon-dev@wso2.org | Subscribe | Mail Archive
User List : esb-java-user@wso2.org | Subscribe | Mail Archive

Reporting Issues

WSO2 encourages you to report issues and your enhancement requests for the WSO2 ESB using the public JIRA.

You can also watch how they are resolved, and comment on the progress..

Discussion Forums

Alternatively, questions could be raised using the forums available.

WSO2 ESB Forum : Discussion forum for WSO2 ESB developers/users

Support

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support.

For more information about WSO2 ESB please see http://wso2.com/products/enterprise-service-bus.

-- The WSO2 ESB Team --

Mediator to support Database stored procedure

2010-04-30T10:35:00.001-07:00

Following blogpost shows how to use Apache Synapse's dblookup mediator to support a mysql database stored procedure.

Setting up mysql database server
1. Install mysql server.

heshan@heshan-laptop:~$ apt-get install mysql

2. Connect to mysql server.

heshan@heshan-laptop:~$ mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 300
Server version: 5.0.75-0ubuntu10.3 (Ubuntu)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

3. Create a sample databasae

mysql>CREATE DATABASE comp;

4. Create a table using the following statement.

mysql>CREATE TABLE company(name varchar(10), id varchar(10), price double);

5. Inserts some data using following statements

mysql>INSERT INTO company VALUES ('IBM','c1',3.7563);
mysql>INSERT INTO company VALUES ('SUN','c2',3.2554);
mysql>INSERT INTO company VALUES ('MSFT','c3',0.0);

6. Create a Stored Procedure.

mysql>CREATE PROCEDURE getCompany(compName VARCHAR(10)) SELECT name, id, price FROM company WHERE name = compName;

7.Add mysql-connector-java-5.1.12-bin.jar to the classpath. This can be done by putting the jar into the Synapse lib directory.

Running the Synapse sample
1. Save the following synapse-configuration as synapse_sample_364.xml to the samples folder.

SYNAPSE_HOME/repository/conf/sample/synapse_sample_364.xml

2. Synapse configuration.

<!-- SYNAPSE_HOME/repository/conf/sample/synapse_sample_364.xml -->
<definitions xmlns="http://synapse.apache.org/ns/2010/04/configuration">

<sequence name="myFaultHandler">
   <makefault response="true">
       <code value="tns:Receiver" xmlns:tns="http://www.w3.org/2003/05/soap-envelope"/>
       <reason expression="get-property('ERROR_MESSAGE')"/>
   </makefault>
   <send/>
   <drop/>
</sequence>

<sequence name="main" onError="myFaultHandler">
   <in>
       <log level="custom">
           <property name="text"
                     value="** Looking up from the Database **"/>
       </log>
       <dblookup>
           <connection>
               <pool>
                   <driver>com.mysql.jdbc.Driver</driver>
                   <url>jdbc:mysql://localhost/comp</url>
                   <user>root</user>
                   <password>admin</password>
               </pool>
           </connection>
           <statement>
               <sql>call getCompany(?)</sql>
               <parameter expression="//m0:getQuote/m0:request/m0:symbol"
                          xmlns:m0="http://services.samples" type="VARCHAR"/>
               <result name="company_id" column="id"/>
           </statement>
       </dblookup>

       <switch source="get-property('company_id')">
           <case regex="c1">
               <log level="custom">
                   <property name="text"
                             expression="fn:concat('Company ID - ',get-property('company_id'))"/>
               </log>
               <send>
                   <endpoint>
                       <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
                   </endpoint>
               </send>
           </case>
           <case regex="c2">
               <log level="custom">
                   <property name="text"
                             expression="fn:concat('Company ID - ',get-property('company_id'))"/>
               </log>
               <send>
                   <endpoint>
                       <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
                   </endpoint>
               </send>
           </case>
           <case regex="c3">
               <log level="custom">
                   <property name="text"
                             expression="fn:concat('Company ID - ',get-property('company_id'))"/>
               </log>
               <send>
                   <endpoint>
                       <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
                   </endpoint>
               </send>
           </case>
           <default>
               <log level="custom">
                   <property name="text" value="** Unrecognized Company ID **"/>
               </log>
               <makefault response="true">
                   <code value="tns:Receiver"
                         xmlns:tns="http://www.w3.org/2003/05/soap-envelope"/>
                   <reason value="** Unrecognized Company ID **"/>
               </makefault>
               <send/>
               <drop/>
           </default>
       </switch>
       <drop/>
   </in>

   <out>
       <send/>
   </out>

</sequence>

</definitions>

3. Start the Synapse configuration numbered 364.

i.e. synapse -sample 364

4. Start the Axis2 server and deploy the SimpleStockQuoteService if not already done.

5. Run the client.

ant stockquote -Daddurl=http://localhost:9000/soap/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dsymbol=IBM

6. Voila, you have invoked a database stored procedure.

Running Synapse ESB's Script Mediator with include option

2010-04-27T00:51:00.000-07:00

Apache Synapse ESB's Script Mediator can be used for message mediation. Sample 350 of Synapse samples is demonstrating how this Script Mediator can be used in a real world scenario.

Suppose the script you specified is calling a function of another script. Then the latter script should also be included in the script mediator configuration. It's done using the <include> element. The key attribute of the <include> element can be specified with the script program statements stored in a separate file, which is referenced via the local or remote registry entry. Following example shows how it can be done.

<script key="string" language="string" [function="script-function-name"]>
  <include key="string"/>
</script>

I am using the same example used in Sample 350 to demonstrate this scenario.

1) Replace the stockquoteTransform.js with the following javascript.


// stockquoteTransform.js
function transformRequest(mc) {
transformRequestFunction(mc);
}

function transformResponse(mc) {
transformResponseFunction(mc);
}

2) Add the following sample.js file to SYNAPSE_HOME/repository/samples/resources/script


// sample.js
function transformRequestFunction(mc) {
var symbol = mc.getPayloadXML()..*::Code.toString();
mc.setPayloadXML(
 <m:getquote m="http://services.samples">
    <m:request>
       <m:symbol>{symbol}</m:symbol>
    </m:request>
 </m:getquote>);
}

function transformResponse(mc) {
var symbol = mc.getPayloadXML()..*::symbol.toString();
var price = mc.getPayloadXML()..*::last.toString();
mc.setPayloadXML(
 <m:checkpriceresponse m="http://services.samples/xsd">
<m:code>{symbol}</m:code>
<m:price>{price}</m:price>
 </m:checkpriceresponse>);
}

3) Update the synapse configuration with the following configuration.


<definitions xmlns="http://ws.apache.org/ns/synapse">
<localEntry key="stockquoteScript" src="file:repository/conf/sample/resources/script/stockquoteTransform.js"/>
<localEntry key="sampleScript" src="file:repository/samples/resources/script/sample.js"/>

<in>
 <!-- transform the custom quote request into a standard quote request expected by the service -->
 <script language="js" key="stockquoteScript" function="transformRequest">
 <include key="sampleScript"/>
<script>
 <send>
     <endpoint>
         <address uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
     </endpoint>
 </send>
</in>
<out>
 <!-- transform the standard response back into the custom format the client expects -->
 <script language="js" key="stockquoteScript" function="transformResponse"/>
     <include key="sampleScript"/>
<script>
 <send/>
</out>
</definitions>

4) Start the Synapse ESB with the above configuration. Deploy the SimpleStockQuote service (which is shipped with Synapse) on SimpleAxisServer. Then invoke the client giving the following command.


ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dmode=customquote

5) It will yield the following result.

   [java] Custom :: Stock price = $161.76045110619708

6) For more information.

WSO2 ESB articles - http://wso2.org/library/esb
Apache Synapse - http://synapse.apache.org/

Recursively remove .svn files

2010-04-05T23:27:00.000-07:00

Following command can be used to recursively remove .svn files.

Following command can be used to list out .svn files.


find . -type d -name .svn

Following command can be used to remove all .svn files.

 
rm -rf `find . -type d -name .svn`

Using Event Broker in WSO2 Carbon to generate Events

2010-04-02T18:40:00.000-07:00

Following code/configuration show what are required to make use of the event broker in carbon to generate events. In the following example we are looking at how to generate an email notification.

1). Declarative Service Component to obtain the service URL.


import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.engine.AxisConfiguration;
import org.apache.axis2.engine.ListenerManager;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.AxisFault;
import org.apache.log4j.*;
import org.osgi.service.component.ComponentContext;
import org.osgi.framework.BundleContext;
import org.wso2.carbon.utils.ConfigurationContextService;
import org.wso2.carbon.utils.NetworkUtils;
import org.wso2.carbon.eventing.broker.services.EventBrokerService;

import java.net.SocketException;

/**
* @scr.component name="org.wso2.carbon.health.service" immediate="true"
* @scr.reference name="configuration.context.service"
* interface="org.wso2.carbon.utils.ConfigurationContextService" cardinality="1..1"
* policy="dynamic" bind="setConfigurationContextService" unbind="unsetConfigurationContextService"
* @scr.reference name="listener.manager.service"
* interface="org.apache.axis2.engine.ListenerManager" cardinality="0..1" policy="dynamic"
* bind="setListenerManager" unbind="unsetListenerManager"
* @scr.reference name="eventbroker.service"
* interface="org.wso2.carbon.eventing.broker.services.EventBrokerService"
* cardinality="1..1" policy="dynamic" target="(name=HealthMonitorEventBroker)"
* bind="setHealthMonitorEventBrokerService" unbind="unsetHealthMonitorEventBrokerService"
*/
public class HealthMonitorEventingServiceComponent {
  private static Log log = LogFactory.getLog(HealthMonitorEventingServiceComponent.class);

  private boolean configurationDone = false;

  private ConfigurationContextService configurationContextService = null;

  private ListenerManager listenerManager = null;

  private boolean initialized = false;

  private static EventBrokerService healthMonitorEventBrokerService = null;

  private String endpoint = null;

  private static BundleContext bundleContext = null;

  static Logger logger = Logger.getLogger(HealthMonitorEventingServiceComponent.class);

  Logger rootLogger = LogManager.getRootLogger();

  protected void activate(ComponentContext context) {
      bundleContext = context.getBundleContext();
  }

   public static BundleContext getBundleContext() {
      return bundleContext;
  }

  private void initializeAppender() {
      if (listenerManager == null || healthMonitorEventBrokerService == null) {
          return;
      }
      System.out.println("Carbon Health Monitor started!");

      rootLogger.addAppender(new JiraAppender());
      log.info("Jira appender added to the root logger");
      // Setting level of root logger
      //rootLogger.setLevel(Level.DEBUG);

      addAppenders();
      rootLogger.error("This log message is used to trigger the JiraAppender");
  }

  public void addAppenders() {
      SimpleLayout layout = new SimpleLayout();
      FileAppender appender = null;
      try {
          appender = new FileAppender(layout, "/tmp/output1.txt", false);
      } catch (Exception e) {
          logger.error(e);
      }

      rootLogger.addAppender(appender);
      logger.debug("DEBUG message 2");
      logger.debug("DEBUG message 3");
      log.info("Appender added to the logger");
  }

  protected void deactivate(ComponentContext context) {
  }

  protected void setConfigurationContextService(ConfigurationContextService configurationContextService) {
      this.configurationContextService  = configurationContextService;
  }

  protected void unsetConfigurationContextService(ConfigurationContextService configurationContextService) {
  }

  protected void setHealthMonitorEventBrokerService(EventBrokerService healthMonitorEventBrokerService) {
      this.healthMonitorEventBrokerService = healthMonitorEventBrokerService;
      initializeAppender();
  }

  protected void unsetHealthMonitorEventBrokerService(EventBrokerService healthMonitorEventBrokerService) {
      this.healthMonitorEventBrokerService = null;
  }

  protected void setListenerManager(ListenerManager listenerManager) {
      this.listenerManager = listenerManager;
      initialize();
      initializeAppender();
  }

  protected void unsetListenerManager(ListenerManager listenerManager) {
      this.listenerManager = null;
  }

  private void initialize() {
      ConfigurationContext serverConfigurationContext = configurationContextService.getServerConfigContext();
      if (!configurationDone && listenerManager != null) {
          String host = null;
          try {
              host = NetworkUtils.getLocalHostname();
          } catch (SocketException e) { }
          if (serverConfigurationContext != null) {
              AxisConfiguration config = serverConfigurationContext.getAxisConfiguration();
              if (config != null && config.getTransportIn("http") != null &&
                      config.getTransportIn("http").getReceiver() != null) {
                  try {
                      EndpointReference[] eprArray = config.getTransportIn("http")
                              .getReceiver().getEPRsForService("HealthMonitorEventingService",
                                      host);
                      if (eprArray != null && eprArray[0] != null) {
                          endpoint = eprArray[0].getAddress();
                      }
                  } catch (AxisFault e) { }
              }
          }
          configurationDone = true;
      }
  }

  public static EventBrokerService getHealthMonitorEventBrokerService() {
      return healthMonitorEventBrokerService;
  }
}

2). Generating Events.


OMFactory fac = OMAbstractFactory.getOMFactory();
Event<OMElement> event = new Event<OMElement>(zipElement);     
event.setTopic("/mail-sending/mail");
OMElement topic = EventBrokerUtils.buildTopic(fac,event);
EventBrokerUtils.generateEvent(event.getMessage(), topic, HealthMonitorEventingServiceComponent.getHealthMonitorEventBrokerService());

3). The services.xml for the service.


<serviceGroup>
  <service name="HealthMonitorEventingService" targetNamespace="http://eventing.registry.carbon.wso2.org">
      <transports>
          <transport>http</transport>
      </transports>
      <description>
          Health Monitor Eventing Service
      </description>
      <messageReceivers>
          <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"
              class="org.wso2.carbon.eventing.broker.receivers.CarbonEventingMessageReceiver"/>
          <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"
              class="org.wso2.carbon.eventing.broker.receivers.CarbonEventingMessageReceiver"/>
      </messageReceivers>
      <parameter name="enableSubscribe" locked="true">true</parameter>
      <operation name="Subscribe" mep="http://www.w3.org/ns/wsdl/in-out">
          <actionMapping>http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe</actionMapping>
      </operation>
      <parameter name="enableRenew" locked="true">false</parameter>
      <!--operation name="Renew" mep="http://www.w3.org/ns/wsdl/in-out">
          <actionMapping>http://schemas.xmlsoap.org/ws/2004/08/eventing/Renew</actionMapping>
      </operation-->
      <parameter name="enableUnsubscribe" locked="true">false</parameter>
      <!--operation name="Unsubscribe" mep="http://www.w3.org/ns/wsdl/in-out">
          <actionMapping>http://schemas.xmlsoap.org/ws/2004/08/eventing/Unsubscribe</actionMapping>
      </operation-->
      <parameter name="enableGetStatus" locked="true">false</parameter>
      <!--operation name="GetStatus" mep="http://www.w3.org/ns/wsdl/in-out">
          <actionMapping>http://schemas.xmlsoap.org/ws/2004/08/eventing/GetStatus</actionMapping>
      </operation-->
      <operation name="Publish" mep="http://www.w3.org/ns/wsdl/in-out">
          <actionMapping>http://ws.apache.org/ws/2007/05/eventing-extended/Publish</actionMapping>
      </operation>

      <parameter name="eventBrokerInstance" locked="true">HealthMonitorEventBroker</parameter>
  </service>
  <parameter name="hiddenService" locked="true">true</parameter>
</serviceGroup>

4). Event Broker configuration


<eventBroker xmlns="http://wso2.org/ns/2009/09/eventing">
  <eventStream name="HealthMonitorEventBroker">
      <subscriptionManager class="org.wso2.carbon.eventing.impl.EmbeddedRegistryBasedSubscriptionManager">
          <parameter name="topicHeaderName">topic</parameter>
          <parameter name="topicHeaderNS">http://wso2.org/ns/2009/09/eventing/notify</parameter>
          <parameter name="subscriptionStoragePath">/carbon/eventing/registry</parameter>
      </subscriptionManager>
      <!-- Uncomment to to RemoteRegistryBasedSubscriptionManager -->
      <!--subscriptionManager class="org.wso2.carbon.eventing.impl.RemoteRegistryBasedSubscriptionManager">
          <parameter name="topicHeaderName">topic</parameter>
          <parameter name="topicHeaderNS">http://wso2.org/ns/2009/09/eventing/notify</parameter>
          <parameter name="subscriptionStoragePath">/carbon/eventing/registry</parameter>
          <parameter name="registryURL">http://remote-ip:port/registry/</parameter>
          <parameter name="username">username</parameter>
          <parameter name="password">password</parameter>
      </subscriptionManager-->
      <!--<eventDispatcher>org.wso2.carbon.registry.eventing.RegistryEventDispatcher</eventDispatcher>-->
      <eventDispatcher>org.wso2.carbon.eventing.broker.CarbonEventDispatcher</eventDispatcher>
      <notificationManager class="org.wso2.carbon.eventing.broker.CarbonNotificationManager">
          <parameter name="minSpareThreads">25</parameter>
          <parameter name="maxThreads">150</parameter>
          <parameter name="maxQueuedRequests">100</parameter>
          <!-- Keep Alive time in nano seconds -->
          <parameter name="keepAliveTime">1000</parameter>
          <!-- Specify path of security policy file to enable security. -->
          <!--parameter name="securityPolicy">policypath</parameter-->

          <!-- Parameters specific to the Registry Event Broker configuration -->
          <!-- Set this as false to disable displaying of registry URL in notification e-mails -->
          <parameter name="showRegistryURL" locked="true">true</parameter>
      </notificationManager>
  </eventStream>
</eventBroker>

I have used the above method to generate email notifications within the Carbon Health Monitor component which I developed. More info on Health Monitor component will be discussed later.

Convert String to a InputStream

2010-04-02T18:30:00.000-07:00

Following code snippet show how to $subject.


import java.io.UnsupportedEncodingException;
import java.io.ByteArrayInputStream;
import java.io.InputStream;

public class StringSample {
       public static void main(String[] args) {
           String textInput = "Convert String to InputStream";
           try {
               InputStream is = new ByteArrayInputStream(textInput.getBytes("UTF-8"));
           } catch (UnsupportedEncodingException e) {
               e.printStackTrace();
           }
       }
}

Programmetically add Log4J Appenders

2010-04-02T17:36:00.000-07:00

Following code snippet shows how to programmetically add log4j Appenders to your java code.


import org.apache.log4j.ConsoleAppender;
import org.apache.log4j.FileAppender;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.PatternLayout;
import org.apache.log4j.SimpleLayout;

public class SampleLoggingAppender {
    static Logger logger = Logger.getLogger(SampleLoggingAppender.class);

    public static void main(String args[]) {
        SimpleLayout layout = new SimpleLayout();
        FileAppender fileAppender = null;
        try {
            fileAppender = new FileAppender(layout, "log.txt", false);
        } catch (Exception ignored) {
        }

        ConsoleAppender consoleAppender = new ConsoleAppender(new PatternLayout());

        logger.addAppender(fileAppender);
        logger.addAppender(consoleAppender);
        logger.setLevel(Level.DEBUG);

        logger.debug("DEBUG");
        logger.info("INFO");
        logger.warn("WARN");
        logger.error("ERROR");
        logger.fatal("FATAL");
    }
}

Transport Statistics Component for WSO2 ESB

2010-03-28T19:57:00.000-07:00

Transport Statistics component shows statistics related to Transports and it will be available with the WSO2 Carbon Iridium (version 3.0.0) release. It displays the Transports which are implementing

the interface org.apache.axis2.transport.base.ManagementSupport. These transport statistics include bytes received, bytes sent, faults receiving, faults sending,last reset time, max size received, max size sent, messages received, messages sent, metrics window, min size received, min size sent, queue size, timeouts receiving, timeouts sending.

Viewing Transport Statistics

In the navigator, under Monitor, click Transport Statistics. The Transport Statistics page appears.

Figure 1: Transport Statistics

The entry page lists down all the exposed Tranports which have implemented the ManagementSupport interface (Figure 1). The graph gives an aggregated view of the bytes received/ bytes sent vs time for all transports.

Click on a link to view the relevant statistics which relates to a transport (Figure 2). The graph gives a drilled down view of the bytes received/ bytes sent vs time for a specific transport.

Each link will take you to a new page that displays the transport statistics exposed by JMX. These data are the data which is shown in the jconsole and we are giving an aggregated view of the transport stats.

Figure 2: Transport Statistics for HTTP transport

These transport statistics include bytes received, bytes sent, faults receiving, faults sending, last reset time, max size received, max size sent, messages received, messages sent, metrics window, min size received, min size sent, queue size, timeouts receiving, timeouts sending.

This is the first component that I developed for WSO2 ESB. During the development stages of this component I had the chance of learning Ajax and applying them to this component, which is showing a screenshot of the statistics at a given point of time.

https://svn.wso2.org/repos/wso2/branches/carbon/3.0.0/components/transport-statistics

Restore a Registry Resource stored in a file to WSO2 Registry

2010-03-27T08:54:00.000-07:00

Following code snippet shows, how to programmetically restore a Registry Resourece written in to a file, back to WSO2 Registry using RemoteRegistry. This is a follow-up to an earlier blogpost.


import org.wso2.carbon.registry.app.RemoteRegistry;
import org.wso2.carbon.registry.core.exceptions.RegistryException;

import java.net.URL;
import java.net.MalformedURLException;
import java.io.FileWriter;
import java.io.FileReader;
import java.io.IOException;

public class RemoteRegistrySampleTest {
  public static void main(String[] args) {
      System.setProperty("javax.net.ssl.trustStore", "CARBON_HOME/resources/security/client-truststore.jks");
      System.setProperty("javax.net.ssl.trustStorePassword", "wso2carbon");
      System.setProperty("javax.net.ssl.trustStoreType", "JKS");

      RemoteRegistry esb2xRemoteRegistry = null;
      try {
          esb2xRemoteRegistry = new RemoteRegistry(new URL("https://localhost:9443/registry"),
                  "admin", "admin");
          esb2xRemoteRegistry.restore("/esb-resources", new FileReader("/home/heshan/Dev/wso2_heshan/temp/registry.xml"));
      } catch (RegistryException e) {
          e.printStackTrace();
      } catch (MalformedURLException e) {
          e.printStackTrace();
      } catch (IOException e) {
          e.printStackTrace();
      }

  }
}

Backup WSO2 Registry Resource to a file

2010-03-27T07:26:00.000-07:00

Following code snippet shows, how to programmetically backup WSO2 Registry Resource to a file using RemoteRegistry.


import org.wso2.carbon.registry.app.RemoteRegistry;
import org.wso2.carbon.registry.core.exceptions.RegistryException;

import java.net.URL;
import java.net.MalformedURLException;
import java.io.FileWriter;
import java.io.FileReader;
import java.io.IOException;

public class RemoteRegistrySampleTest {
  public static void main(String[] args) {
      System.setProperty("javax.net.ssl.trustStore", "CARBON_HOME/resources/security/client-truststore.jks");
      System.setProperty("javax.net.ssl.trustStorePassword", "wso2carbon");
      System.setProperty("javax.net.ssl.trustStoreType", "JKS");
    
      RemoteRegistry esb2xRemoteRegistry = null;
      try {
          esb2xRemoteRegistry = new RemoteRegistry(new URL("https://localhost:9443/registry"),
                  "admin", "admin");
          esb2xRemoteRegistry.dump("/esb-resources", new FileWriter("/home/heshan/Dev/wso2_heshan/temp/registry.xml"));
      } catch (RegistryException e) {
          e.printStackTrace();
      } catch (MalformedURLException e) {
          e.printStackTrace();
      } catch (IOException e) {
          e.printStackTrace();
      }

  }
}

Remove Line Breaks From a Java String

2010-03-02T01:08:00.000-08:00

Following code snippet shows how to remove line termination characters from a String.


import java.util.regex.*;

public class ClassA {
   public static void main(String args []) {
   String inputText = "sdfsdfsf\nsdfsdfsd";
   String inputText2 = "var trpListenerGr\naphDivId = #trpLi\nstenerGraph2\n";
   RemoveLineTerminationCharacterss(inputText);
   System.out.println("-------------------------------");
   RemoveLineTerminationCharacterss(inputText2);

   }

   public static String RemoveLineTerminationCharacterss(String inputText){
   Pattern p;
   Matcher m;
   System.out.println(" Input Text : " + inputText);
   p = Pattern.compile("\n");
   m = p.matcher(inputText);
   String str = m.replaceAll("");
   System.out.println(" OUtput Text: " + str);
   return str;
   }
}

WSO2 SOA Workshop NYC

2010-02-21T22:31:00.000-08:00

The full-day interactive workshop will show you how to build your own solutions with industry acclaimed best practices and patterns. It will also discuss real SOA deployment issues such as security, interoperability and moving to the Cloud.

Paul Fremantle, Founder and CTO, WSO2 and Asanka Abeysinghe, Lead Solutions Architect will be presenting at the workshop.

For more details and to register visit:
http://wso2.com/events/2010-feb-nyc-soa-workshop/

Convert the SOAP message to a plain text mail

2010-02-21T22:17:00.000-08:00

How to convert a SOAP to a plain text mail using an Enterprise Service Bus (ESB).

SCENARIO:

Imagine a scenario where you are using the mail transport in WSO2 ESB. You need to convert the SOAP message to a plain text mail(without any XML in it). Read the full article here.

WSO2 Enterprise Service Bus 2.1.3 Released!

2010-02-02T22:15:00.000-08:00

The WSO2 ESB team is pleased to announce the release of version 2.1.3 of the Open Source Enterprise Service Bus (ESB). This is an enhanced and improved release of the WSO2 ESB 2.1.2 which went out on November 2009.

WSO2 ESB is a lightweight and easy-to-use Open Source Enterprise Service Bus (ESB) available under the Apache Software License v2.0. WSO2 ESB allows administrators to simply and easily configure message routing, intermediation, transformation, logging, task scheduling, load balancing, failover routing, event brokering, etc.. The runtime has been designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse core.

WSO2 ESB 2.1.3 is developed on top of the revolutionary Carbon platform (Middleware a' la carte), and is based on the OSGi framework to achieve the better modularity for your SOA architecture. This also contains a lots of new features and many other optional components to customize the behavior of the server. Further, if you do not want any of the built in features, you can uninstall those features without any trouble. In other words, this ESB can be customized to your SOA needs.

You can download this distribution from http://wso2.org/downloads/esb and give it a try.

How to Run

Extract the downloaded zip
Go to the bin directory in the extracted folder
Run the wso2server.sh or wso2server.bat as appropriate
Point your browser to the URL https://localhost:9443/carbon
Use "admin", "admin" as the username and password to login as an admin and create a user account
Assign the required permissions to the user through a role
If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
Samples configurations can be started by the wso2esb-samples script passing the sample number with the -sn option, please have a look at the samples guide for more information, on running samples

New Features of WSO2 ESB 2.1.3

This ESB release is based on the award winning WSO2 Carbon "Middleware a' la carte", an OSGi based SOA platform, version 2.0.3 by WSO2 Inc.
HTTP binary relaying support for ultra fast mediation via the ESB
New mediation statistics viewer
API for accessing mediation statistics at runtime
Enhanced remote registry support
Ability to edit dynamic sequences saved in the registry from the UI editor
Rule based mediation powered by Drools
Fine grained autherization for services via the Entitlement mediator
Enhanced WS-Eventing support and Event Sources making it an even broker
Enhanced AJAX based sequence, endpoint and proxy service editors
Enhanced permission model with the user management
Enhanced REST/GET and other HTTP method support
P2 based OSGi provisioning support, for optional features like service management, runtime governance and so on..
Many bug fixes, UI enhancements and usability improvements

Key Features of WSO2 ESB

Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
Non-blocking HTTP/S transports based on Apache HttpCore for ultrafast execution and support for thousands of connections at high concurreny with constant memory usage.
Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS, Configurations ..)
Easily extendable via custom Java class (mediator and command)/Spring mediators, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler.
Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
Lightweight, XML and Web services centric messaging model
Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Helth Level-7 protocol)
Enhanced support for the VFS(File/FTP/SFTP)/JMS/Mail transports with optional TCP/UDP transports and transport switching for any of the above transports
Support for message splitting & aggregation using the EIP and service callouts
Database lookup & store support with DBMediators with reusable database connection pools
WS-Eventing support with event sources and event brokering
Rule based mediation of the messages using the Drools rule engine
Transactions support via the JMS transport and Transaction mediator for database mediators
Internationalized GUI management console with user/permission management for configuration development and monitoring support with statistics, configurable logging and tracing
JMX monitoring support and JMX management capabilities like, Gracefull/Forcefull shutdown/restart

Get Involved

Help us improve this product by reporting any issues you many have: WSO2 ESB JIRA.

You can also watch how they are resolved, and comment on the progress.

Contact Us

Get in touch with the product team via the mailing lists:

Developer List : esb-java-dev@wso2.org | Subscribe | Mail Archive
User List : esb-java-user@wso2.org | Subscribe | Mail Archive

To subscribe to the above mailing lists see http://wso2.org/mail

Alternatively, questions can also be raised in the forum: http://wso2.org/forum/187

Support

For more details and to take advantage of this unique opportunity please visit http://wso2.com/support

For more information about WSO2 ESB please see http://wso2.com/products/enterprise-service-bus or visit the WSO2 Oxygen Tank developer portal for addition resources.

Thank You!
The WSO2 ESB team

How to apply a patch

2010-01-21T21:37:00.000-08:00

1). Take the svn diff of the changes you made and save it to a file.

$svn diff > ~/Desktop/carbon.patch021

2). Apply the saved patch to the source.

$patch -p 0 < ~/Desktop/carbon.patch021

3). Commit the changes.

$svn commit

Access JMX MBean information through RMI

2010-01-20T03:48:00.000-08:00

This is a follow up to my earlier post.

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

import javax.management.remote.JMXServiceURL;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.*;
import javax.management.openmbean.CompositeData;
import java.lang.management.ManagementFactory;
import java.net.MalformedURLException;
import java.io.IOException;
import java.util.Set;

public class JmxReport {
private static final Log log = LogFactory.getLog(JmxReport.class);

public static void logJmxInfo() {
   // Operating System MXBean
   log.info("Operating system architecture : " + ManagementFactory.getOperatingSystemMXBean().getArch());
   log.info("Available processors          : " + ManagementFactory.getOperatingSystemMXBean().getAvailableProcessors());
   log.info("Operating system name         : " + ManagementFactory.getOperatingSystemMXBean().getName());
   log.info("System load average           : " + ManagementFactory.getOperatingSystemMXBean().getSystemLoadAverage());
   log.info("Operating system version      : " + ManagementFactory.getOperatingSystemMXBean().getVersion());

   // Memory MXBean
   log.info("Heap memory usage             : " + ManagementFactory.getMemoryMXBean().getHeapMemoryUsage().toString());
   log.info("Non-heap memory usage         : " + ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().toString());

   // Class loading MXBean
   log.info("Loaded class count            : " + ManagementFactory.getClassLoadingMXBean().getLoadedClassCount());
   log.info("Total loaded class count      : " + ManagementFactory.getClassLoadingMXBean().getTotalLoadedClassCount());
   log.info("Unloaded class count          : " + ManagementFactory.getClassLoadingMXBean().getUnloadedClassCount());
}

public static void getJmxStatisticsViaRmi() {
   try {
       String jmxAgentName = "org.apache.synapse";
       MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();

       JMXConnector c = JMXConnectorFactory.newJMXConnector(createConnectionURL("heshan-laptop", 1099), null/*map*/);
       c.connect();
       Object o = c.getMBeanServerConnection().getAttribute(new ObjectName("java.lang:type=Memory"), "HeapMemoryUsage");
       CompositeData cd = (CompositeData) o;
       System.out.println(cd.get("committed"));

       Object object2 = c.getMBeanServerConnection().getObjectInstance(new ObjectName("org.apache.synapse:Type=Transport,ConnectorName=nio-http-listener"));
       Object lastResetTime = c.getMBeanServerConnection().getAttribute(new ObjectName("org.apache.synapse:Type=Transport,ConnectorName=nio-http-listener"), "LastResetTime");
       System.out.println("lastResetTime : " + lastResetTime.toString());

       ObjectName objName = new ObjectName("org.apache.synapse:Type=Transport,ConnectorName=nio-http-listener");
       Set set2 = mbs.queryNames(objName, null);
       for (Object o2 : set2) {
           log.info("  :: " + o2.toString());
       }
   } catch (MalformedObjectNameException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (InstanceNotFoundException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (MalformedURLException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (IOException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (ReflectionException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (AttributeNotFoundException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   } catch (MBeanException e) {
       e.printStackTrace();  //To change body of catch statement use File | Settings | File Templates.
   }
}

private static JMXServiceURL createConnectionURL(String host, int port) throws MalformedURLException {
   JMXServiceURL serviceURL = new JMXServiceURL("rmi", "", 0, "/jndi/rmi://" + host + ":" + port + "/synapse");
/* To monitor JMX info of Carbon Platform need to enable jmx port @ carbon.xml
   The link is service:jmx:rmi:///jndi/rmi://10.100.1.143:9999/server 
*/
   return serviceURL;
}

public static void main(String args[]) {
   getJmxStatisticsViaRmi();
}
}

Programmetically access JMX MBean information

2010-01-20T03:22:00.001-08:00


import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import java.lang.management.ManagementFactory;

public class JmxReport {
private static final Log log = LogFactory.getLog(JmxReport.class);

public static void logJmxInfo() {
    // Operating System MXBean
    log.info("Operating system architecture : " + ManagementFactory.getOperatingSystemMXBean().getArch() );
    log.info("Available processors          : " + ManagementFactory.getOperatingSystemMXBean().getAvailableProcessors() );
    log.info("Operating system name         : " + ManagementFactory.getOperatingSystemMXBean().getName() );
    log.info("System load average           : " + ManagementFactory.getOperatingSystemMXBean().getSystemLoadAverage() );
    log.info("Operating system version      : " + ManagementFactory.getOperatingSystemMXBean().getVersion() );

    // Memory MXBean
    log.info("Heap memory usage             : " + ManagementFactory.getMemoryMXBean().getHeapMemoryUsage().toString() );
    log.info("Non-heap memory usage         : " + ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().toString() );

    // Class loading MXBean
    log.info("Loaded class count            : " + ManagementFactory.getClassLoadingMXBean().getLoadedClassCount() );
    log.info("Total loaded class count      : " + ManagementFactory.getClassLoadingMXBean().getTotalLoadedClassCount() );
    log.info("Unloaded class count          : " + ManagementFactory.getClassLoadingMXBean().getUnloadedClassCount() );


}

public static void main(String args[]) {
    logJmxInfo();
}
}

Resolving permission issue with Tomcat

2010-01-20T02:41:00.000-08:00

When you download and start running catalins.sh, you might get following error.

The BASEDIR environment variable is not defined correctly
This environment variable is needed to run this program

To resolve this;
1) Check $CATALINA_HOME and $JAVA_HOME set properly.

2) Check whether the relevant files in $CATALINA_HOME/bin have necessary permissions required for execution.


$ chmod u+x catalina.sh
$ chmod +x ./setclasspath.sh
$ chmod +x ./startup.sh
$ chmod +x ./shutdown.sh

My 500LKR haircut

2009-12-10T05:18:00.000-08:00

This incident took place on Monday. Although it is not that much of a significant incident I thought of writing a blogpost because of the funny nature of it. On Monday, I thought of getting a haircut. I was having a chat with my buddy Pandula before going to the Saloon. When I mentioned about the haircut, he asked "hey man, are you still going to that shitty place to get an haircut. You should increase your standard of living cos now that you are employed and ....." he went on preaching. In my defense this so called "shitty Saloon" was the one which I have been going to for the last 5 years after moving to Borella. Although it did not have many luxurious facilities, I could get a haircut+head massage for 140/= (including the 20/= tip).

After Pandula's comment I was a bit embarrassed and thought of going to a better Saloon. After going in I told the barber the way in which I need my hair to be trimmed. He did it. At the end of the haircut I asked the barber how much is for the haircut. He said 150/=. I thought "Somebody have to pay for these fancy lights and equipment" and said "ok cool". Then I told him to give me a head massage(a statement which I would regret later).

This bugger gave me a head massage for 20 minutes. Normally in my old place the barber would give it for 5 mins. I thought that this guy was having some short term memory loss in understanding time durations. After everything was done, I asked him how much for the haircut? He said 500/=. My first reaction was that I heard it wrong and I asked the same question again to get the same answer back. Then I asked "Damn.... you charged 350/= for a head massage?". Although I had 2000/= with me at that time; under any circumstance I would not pay for a haircut that much.

I told him "I am having 300/= with me right now and out of it I have to buy a dinner packet for 100/=. I can only give you 200/=." He had no other option but to accept my proposition. [IMO barber had another extreme option. He could have asked me to cut hair of the customers until he recovers my charge (just like people are asked to wash plates in "siwari", when they are unable to pay for the food that they have eaten :)). I guess he did not have faith in me - having a pair of scissors on my hand ]. Therefore I gave him 200/= and got myself out of that place. That was the last time that I would step on that place.

Ironically the Saloon's name was "Sayonara" :) meaning 'goodbye'. 'siy-oh-nah-rah' would be the best matching name that anybody could come up with, for a Saloon like that :D

WSO2 Cloud Platform

2009-11-23T22:17:00.000-08:00

Last week, WSO2 launched their Cloud Platform, for extending SOA into cloud computing.

Wso2 Cloud Public 2009 11 16

View more documents from Sanjiva Weerawarana.

Apache Asia Roadshow 2009

2009-11-23T22:06:00.000-08:00

Apache Asia Roadshow 2009 will hit Colombo from the 3^rd - 5^th of December. You can register for the event here. Don't miss out this opportunity.

Cloud Computing

2009-11-23T22:02:00.000-08:00

Here's a very interesting video on cloud computing

Use mail transport in ESB to convert the SOAP message to a plain text mail

2009-11-05T01:54:00.000-08:00

Scenario:
Imagine a scenario where you are using the mail transport in ESB. You need to convert the SOAP message to a plain text mail(without any XML in it). This blogpost is written to address it.

How To:
Following steps will guide you to get your scenario up and running.

1) Uncomment the mail TransportSender and TransportReceiver from axis2.xml


<transportSender name="mailto" class="org.apache.axis2.transport.mail.MailTransportSender">
   <parameter name="mail.smtp.host">smtp.gmail.com</parameter>
   <parameter name="mail.smtp.port">587</parameter>
   <parameter name="mail.smtp.starttls.enable">true</parameter>
   <parameter name="mail.smtp.auth">true</parameter>
   <parameter name="mail.smtp.user">synapse.demo.0</parameter>
   <parameter name="mail.smtp.password">mailpassword</parameter>
   <parameter name="mail.smtp.from">synapse.demo.0@gmail.com</parameter>
</transportSender>

<transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener">
</transportReceiver>

2) Add the following line to axis2.xml's MessageFormatters.


<messageFormatter contentType="text/plain" class="org.apache.axis2.format.PlainTextFormatter"/>

3) Build the SimpleStockQuote service (which is residing inside the samples). Run sample axis2Server.

4) Use the attached proxy configuration.


<!-- Using the mail transport -->
<definitions xmlns="http://ws.apache.org/ns/synapse">
 <proxy name="StockQuoteProxy" transports="mailto">

     <parameter name="transport.mail.Address">synapse.demo.1@gmail.com</parameter>
     <parameter name="transport.mail.Protocol">pop3</parameter>
     <parameter name="transport.PollInterval">5</parameter>
     <parameter name="mail.pop3.host">pop.gmail.com</parameter>
     <parameter name="mail.pop3.port">995</parameter>
     <parameter name="mail.pop3.user">synapse.demo.1</parameter>
     <parameter name="mail.pop3.password">mailpassword</parameter>
     <parameter name="mail.pop3.socketFactory.class">javax.net.ssl.SSLSocketFactory</parameter>
     <parameter name="mail.pop3.socketFactory.fallback">false</parameter>
     <parameter name="mail.pop3.socketFactory.port">995</parameter>
     <parameter name="transport.mail.ContentType">application/xml</parameter>

     <target>
         <inSequence>
             <property name="senderAddress" expression="get-property('transport', 'From')"/>
             <log level="full">
                 <property name="Sender Address" expression="get-property('senderAddress')"/>
             </log>

             <send>
                 <endpoint>
                     <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
                 </endpoint>
             </send>
         </inSequence>
         <outSequence>
             <property name="Subject" value="Custom Subject for Response" scope="transport"/>
       <property name="messageType" value="text/plain" scope="axis2-client"/>
<script language="js"><![CDATA[
               mc.setPayloadXML(<ns:text xmlns:ns="http://ws.apache.org/commons/ns/payload">Plain text received!</ns:text>);
    ]]></script>
             <header name="To" expression="fn:concat('mailto:', get-property('senderAddress'))"/>
             <log level="full">
                 <property name="message" value="Response message"/>
                 <property name="Sender Address" expression="get-property('senderAddress')"/>
             </log>
             <send/>
         </outSequence>
     </target>
     <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
 </proxy>
</definitions>

5) Send an email to synapse.demo.1@gmail.com

6) You will receive the response in plain text.

Exposing a non-secured service with security using ESB

2009-10-21T01:27:00.000-07:00

This article explains how to expose a non-secure service as a secured service using WSO2 ESB. The unsecured service is SimpleStockQuoteService. The strategy taken up is to secure SimpleStockQuoteService throught a secured proxy. A proxy service is written to enable username token authentication and logging of messages. Steps specified in the article demonstrates how to get this scenario up and running. [Read the full article for more info]

My article on IBM Developer Works

2009-10-11T21:21:00.000-07:00

It was one of my dreams to publish an article in IBM dW. Last week one of my articles got published in the IBM developerWorks. A special thank goes out to Chris Walden (Web Development Editor) of developerWorks who made this happen.

Basketball @ WSO2 : How to Survive

2009-10-03T05:26:00.000-07:00

It's been a while since I wrote a blogpost that relates to sports. Since annual basketball tournament at wso2 is coming up next week, I thought it would be the perfect time to write a blogpost on WSO2 basketball. The ideas & views expressed below can be a KnowledgeBase for anyone joining wso2 or newbie who wants to play basketball @ wso2.

Wso2 folks dont have a permanent basketball court to play basketball. Instead they have transformed the car park into a basketball court. It is car-park by day and basketball court by night. We have portable baskeball posts, so we move em to the car-park in the evening. The court is not having the ideal dimensions of a standard basketball court; it is due to the limited space available in the car park.

We started playing basketball @ wso2 around 1 year back and we followed it up with a inter-house basketball tournament, which was a blast. It was a very successful event and everyone enjoyed it a lot(apart from the people who got injured while playing lol). Now 1 year has elapsed since the introduction of basketball to wso2 and IMO I say that we are playing a different flavor of basketball.

Basketball is having several flavors ranging from Streetball to Slamball. Wso2's basketball has evolved into a unique flavor apart from these. I'd say it is a hybrid of both basketball and rugby :D. I'd like to call it RugBBall. Since I said that this would be a KB item, following are some tips to be successful(or survive lol) @ basketball court, during practice sessions.

You should be able to tolerate elbow shots and slaps, cos these arn't fouls :)

Dont ever argue with guys on "whether it was a foul or not". You could never win that argument :). Therefore it's better to carry on with the game without arguing.

After a practice session you'd feel like if you were scratched by a kitten and tackled by a NFL linebacker lol.

Those are the fun facts to know before you enter into the bb court.

I will follow this post up with a pre-tournament analysis of the wso2's inter-house basketball teams. So stay tuned ;) .

Create ZIP archieve from multiple files

2009-09-10T23:13:00.000-07:00

Following code snippet shows how to create a zip archieve from multiple files.

import java.util.zip.*;
import java.util.Iterator;
import java.util.List;
import java.util.ArrayList;
import java.io.*;

public class ZipDemo {
    static int BUFFER_SIZE = 1024;
    static String zipArchieveName = "allfiles.zip";

    public static void main(String args[]) {
        try {
            // Reference to the file we will be adding to the zipfile
            BufferedInputStream origin = null;

            // Reference to zip file
            FileOutputStream dest = new FileOutputStream(zipArchieveName);

            // Wrap our destination zipfile with a ZipOutputStream
            ZipOutputStream out = new ZipOutputStream(new BufferedOutputStream(dest));

            // Create a byte[] buffer that we will read data from the source
            // files into and then transfer it to the zip file
            byte[] data = new byte[BUFFER_SIZE];

            List files = new ArrayList();
            files.add("/tmp/systemInfo.txt");
            files.add("/tmp/osgiInfo.txt");
            files.add("/tmp/errorInfo.txt");

            // Iterate over all of the files in list
            for (Iterator i = files.iterator(); i.hasNext();) {
                // Get a BufferedInputStream that we can use to read the source file
                String filename = (String) i.next();
                System.out.println("Adding: " + filename);
                FileInputStream fi = new FileInputStream(filename);
                origin = new BufferedInputStream(fi, BUFFER_SIZE);

                // Setup the entry in the zip file
                ZipEntry entry = new ZipEntry(filename);
                out.putNextEntry(entry);

                // Read data from the source file and write it out to the zip file
                int count;
                while ((count = origin.read(data, 0, BUFFER_SIZE)) != -1) {
                    out.write(data, 0, count);
                }

                // Close the source file
                origin.close();
            }

            // Close the zip file
            out.close();
        }
        catch (Exception e) {
            e.printStackTrace();
        }
    }
}

How to add a Log4j Appender to WSO2 Carbon

2009-08-31T23:11:00.000-07:00

1) Write a java class and extend AppenderSkeleton. Add the logic to the append(LoggingEvent e) method.

public class JiraAppender extends AppenderSkeleton {
    protected void append(LoggingEvent loggingEvent) {
        if (loggingEvent.getLevel().toString().equalsIgnoreCase("INFO")) {
            System.out.println("INFO invoked!");
        }
    }

    public boolean requiresLayout() {
        return false; 
    }

    public void close() {
    }
}

2) Modify the log4j.properties file located at

/carbon-platform-2.0.1/carbondistribution/carbon-home/lib/log4j.properties

a) Add the following entry to the log4j.properties file.

# CARBON_JIRA is set to be a MemoryAppender using a PatternLayout.
log4j.appender.CARBON_JIRA=org.wso2.carbon.utils.JiraAppender
log4j.appender.CARBON_JIRA.layout=org.apache.log4j.PatternLayout
log4j.appender.CARBON_JIRA.layout.ConversionPattern=[%d] %5p - %x %m%n
log4j.appender.CARBON_JIRA.threshold=DEBUG

b) Update the log4j.properties file with the following entry.

log4j.rootLogger=INFO, CARBON_CONSOLE, CARBON_LOGFILE, CARBON_MEMORY, CARBON_SYS_LOG, CARBON_JIRA

log4j.logger.org.apache.axis2.wsdl.codegen.writer.PrettyPrinter=ERROR, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA
log4j.logger.org.apache.axis2.clustering=DEBUG, CARBON_CONSOLE, CARBON_LOGFILE, CARBON_JIRA
log4j.logger.org.apache=INFO, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA
log4j.logger.org.apache.catalina=WARN
log4j.logger.org.apache.tiles=WARN
log4j.logger.org.apache.coyote=WARN
log4j.logger.org.hibernate=ERROR, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA
log4j.logger.org.mortbay=ERROR, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA
log4j.logger.net.sf=ERROR
log4j.logger.org.wso2=INFO
log4j.logger.org.apache.axis2.enterprise=FATAL, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA
log4j.logger.de.hunsicker.jalopy.io=FATAL, CARBON_LOGFILE, CARBON_MEMORY, CARBON_JIRA

WSO2 Carbon Articles

2009-08-25T23:02:00.001-07:00

Following are a list of useful articles on WSO2 Carbon.

Getting Started with WSO2 Carbon

How Stuff Works – WSO2 Carbon

OSGi Tutorials

2009-08-24T05:03:00.000-07:00

Following are a list of OSGi tutorials which I found useful.

How to build OSGi bundles using Maven Bundle Plugin - Part1

Introduction to OSGI

Apache Felix OSGi Tutorial

OSGi for Beginners

Server Side OSGi

Hello, OSGi, Part 1: Bundles for beginners

Hello, OSGi, Part 2: Introduction to Spring Dynamic Modules

Hello, OSGi, Part 3: Take it to the server side

Building OSGi bundles using Maven Bundle Plugin

2009-08-23T23:26:00.000-07:00

I came across a good article by Sameera on "How to build OSGi bundles using Maven Bundle Plugin". It gives detailed infromation on how to use maven bundle plugin to generate OSGi bundles. In this blogpost, I will demonstrate how a sample can be run. If you are hungry for more information read the above article.

1) Download and extract the samples.

2) Build the sample01

mvn clean install

3) Download Equinox.
eg: org.eclipse.osgi_3.5.0.v20090520.jar

4) Run the jar file using following command.

java -jar org.eclipse.osgi_3.5.0.v20090520.jar -console

5) In the command prompt execute following command.

osgi> ss
Framework is launched.

id    State       Bundle
0    ACTIVE      org.eclipse.osgi_3.5.0.v20090520

6) Install the bundle

osgi>  install file:/home/heshan/Documents/Work/OSGi/maven_bundle_plugin_samples_0/sample01/target/sample01-1.0.0.jar
Bundle id is 1

osgi> ss
Framework is launched.

id    State       Bundle
0    ACTIVE      org.eclipse.osgi_3.5.0.v20090520
1    ACTIVE      org.wso2.mbp.sample01_1.0.0

7) Use the following commands to start and stop the bundles.

osgi> start 1
Hello World!!!

osgi> stop 1
Goodbye World!!!

Building WSO2 Carbon from source

2009-08-18T23:14:00.000-07:00

You can use following steps to successfully build, WSO2 Carbon from source;

1. Checkout commons. Then build caching, eventing, throttle, xkms modules.

2. Build carbon.

3. Build carbon-orbit.

4. Build synapse.

5. Build rhino.

6. Build carbon-components.

Second "First Day" @ WSO2

2009-08-17T10:07:00.000-07:00

Today was my first day at WSO2. I joined as a Software Engineer. This was in fact my second "first day" at WSO2. My first "first day" was in February 2008, when I joined WSO2 as an undergraduate intern.

Good Bye UCSC

2009-08-16T11:45:00.000-07:00

Past week was my last week at UCSC. I had my final year project defense last week and it was the last commitment that I had towards my university. The only other thing that we have to do is organize the Research Symposium. It will be held on 25th August.

UCSC had been my second-home for last 4 years and have some wonderful memories associated with it. It groomed me of becoming the person that I am today and I am forever grateful to University of Colombo and UCSC.

GSoC: Experience

2009-08-16T07:06:00.000-07:00

This was my second consecutive year as a Google Summer of Code student. During past 3 months I learned a lot of things. I discussed these in an earlier posts. In a nutshell;

1) I worked with a mentor (Matt Boersma) from a different time zone. This was the first time that I worked with a mentor from a different timezone. Our time difference was nearly 12 hours. We preferred email over chat since it was more conveinent for us.

2) It was a privilege to work as a summer of code student for Python Software Foundation (PSF). All the people who were mentoring me helped me a lot, ranging from shaping up the application (project proposal) to development.

3)It was a greatopportunity for me to work with experienced developers.

I would like to take this opportunity to thank my mentor Matt Boersma and Jython community for helping me to make my project a success. I would also take this opportunity to thank my co-mentors Jim Baker and Frank Wierzbicki.

I would like to state that it was a privilege and a honor to be selected as a GSoC student for a second time and thank Google for organizing a program like this. I am looking forward to participating in next year's GSoC as a mentor. :)

GSoC: Update

2009-08-15T10:39:00.000-07:00

During the development phase, I came across some problems. This is a follow up to my earlier posts. You can have a look at them here.

1) One problem is the way the API is designed to define the XML payload. I designed the WSF/Jython API in such a way that it is comparable with the WSF/Ruby implementation. Therefore WSF/Jython API should adhere to the API specified by WSF/Ruby.

When generating code using Axis2's code generation framework, you should generate it in a such a way that it should support XML object model(preferably in the case of axis2 - apache axiom). Therefore it would be better if the API supported axiom, inorder to use the code generation part. Consider the following example.

from org.wso2.wsf.jython.jythonwsclient import *

req_payload_string = "<deduct><var1>1.8</var1><var2>4.87594</var2></deduct>"
LOG_FILE_NAME = "/home/heshan/IdeaProjects/MRclient/src/python_client.log"
END_POINT = "http://localhost:8070/axis2/services/annotationScript/deduct"

try:
client = WSClient({}, LOG_FILE_NAME)
req_message = WSMessage(req_payload_string, {"to" :END_POINT})
print " Sending OM      : " , req_payload_string
res_message = client.request(req_message)
print " Response Message: " , res_message

except WSFault, e:
e.printStackTrace();

In above code snippet, the payload is set as a string. i.e.


req_payload_string = "<deduct><var1>1.8</var1><var2>4.87594</var2></deduct>"

What should be done is to keep the above feature intact with the API and do a feature addition that will support Apache Axiom.

2) Therefore, the existing WSF/Jython codebase should be modified to support axiom for Jython (should look into this further).

3) Modify the existing codebase to include the code generation part. Having said that there should be more work done to seamlessly integrate this(code-generation part) to WSF/Jython code. More coding have to be done on code generation module for Jython.

4) In a earlier post I said of modifying the Python deployer to support Contract First approach. This happens in the server-side code generation. It's a problem that I am still having.

5) In the same post I said that

0nly generate the client code and use the existing WSF/Jython's client API. Then before running the client code you can add the WSF/Jython client-side jar to the class path.

Now it seems like the best option out of the two options mentioned in the above post.

[The above arguments are my opinions and may subject to change.]

The Last Lecture: Achieving Your Childhood Dreams

2009-07-31T09:36:00.000-07:00

UCSC Research Symposium

2009-07-31T09:24:00.000-07:00

A gallant display of research prowess awaits unveiling as the country’s premiere Computer Science and Information Technology research community stages the biggest event of the year - the UCSC Research Symposium 2009. With the memories of the inaugural UCSC Research Symposium in 2008 that revolutionized the undergraduate Computer Science research in Sri Lanka, the University of Colombo School of Computing (UCSC) expands this year’s event into new bounds, embracing cutting-edge research in both quantitative and qualitative disciplines.

Date:
Tuesday, 25th of August 2009
8.00 AM to 5.00 PM

Venue:
Prof V.K. Samaranayake Auditorium,
University of Colombo School of Computing,
Colombo 7,

Sri Lanka

GSoC: How to integrate with existing code base

2009-07-10T21:04:00.000-07:00

This post will contain my arguments on "How to integrate this project to the existing WSF/Jython code base". This is a followup to my last post.

1. Modify the Python deployer to support Contract First approach.

2. To support Contract First approach you need to be able to generate a skeleton and a message receiver for your service. The generic message receiver that I have already written may not work because it works only on a limited schema structure.

3. Another way to look at the above argument(2) may be; only generate the client code and use the existing WSF/Jython's client API. Then before running the client code you can add the WSF/Jython client-side jar to the class path.

The above arguments are my opinion(for now) on integrating the gsoc code to existing code base. The above arguments may subject to change.

GSOC: Problems faced during development

2009-07-05T07:32:00.000-07:00

Earlier I said that I would be writing a blog post on the problems which I encountered during the development phase of my GSoC project. Here I am compiling them to a list. Some points in the list may not directly be problems but important things which came across during the process.

1. Had a problem with building axis2. This was overcome when I found a workaround for this. (This was a hard issue to regenerate because this will only happen occasionally.)

2. There were lot of dependencies inside axis2's code generation framework. Some dependencies were not set by the build script. Therefore had to manually add the dependencies and run the code. When it gives a compilation error stating a dependency is not there, had to set the dependencies. This took some time :).

3. Had to take some time to understand the existing code base and the architecture of the code generation framework.

4. Learned to work with XSLTs.

5. Another important point to note is that the WSF/Jython distribution, now needs some additional libraries to successfully run. You may have wondered "why is this happening?". As you may already know WSF/Jython is built on top of Apache Axis2. The new releases of Axis2 are having more dependencies towards other liblaries/jars (eg. wsdl4j, etc). Since I no longer work for WSO2, I do not have the access writes to change the build script for WSF/Jython. As soon as I get there, I would remember to revise the build script. Until then you could do a small workaround:)

Download Axis2 standard binary distribution. Then extract it. Add the jars which are residing in the lib folder, to the classpath. Then you could carry on with your work.

6. How to integrate this project to the existing WSF/Jython development. (I will present my arguments on this on a new post)

Mr. Lakshman Kadiragamar's Lesson

2009-06-29T22:29:00.000-07:00

In 2005, almost fifty years after he left Oxford, Mr. Lakshman Kadiragamar's portrait was unveiled at the Oxford Union. This was a great honour bestowed by the Oxford Union on only 15 others in its 183 year history.

Mr Kadirgamar had this to say about that event;

'......I would like to, if I may, to assume that I could share the honour with the people of my country, Sri Lanka . I had my schooling there, my first university was there, I went to Law College there and by the time I came to Oxford as a postgraduate student, well, I was relatively a matured person. Oxford was the icing on the cake … but the cake was baked at home ......(applause) .'

This is indeed true. People appreciate only the icing on the cake not where it was baked first.

Design for Jython Extension for Axis2

2009-06-27T01:29:00.000-07:00

In a earlier post I said that I am coming up with a Jython extension for Axis2. This will be a code generation tool for jython. This will use existing infrastructure in Axis2 to support Contract First Web services in Jython. What I am planning to do is to integrate this code generation tool into WSF/Jython. Then WSF/Jython will be able to support both, contract-first and code-first approaches. Thus, making the life easier for the Jython developer :).

The code generation engine calls the extensions one by one and then calls a component what is known as the Emitter. Emitter is the actual component that does the significant bit of work in the code generation process. Emitters are usually language dependent and hence one language has one emitter associated with it. Therefore there should be an emitter to support Jython code generation. This simple yet powerful architecture is shown in the above illustration.

The Emitter processes the WSDL and builds a object model. The object model is simply an XML file which contains the object model of the WSDL with respect to Axis2 information model (ie. axis service, axis operation, axis message, etc). The template is a XSLT file which contains information on how the code should be generated. Then the built object model is parsed against the template to build the jython source code.

wsdl2java Code Generation

2009-06-27T01:01:00.000-07:00

Axis2's wsdl2java code generation tool can be used to auto-generate programming language code for a given WSDL file. It can either generate code to invoke a Web service, or it can auto-generate the skeleton code that will adhere to the specification described within the WSDL file so that the generated code can be deployed as a Web service.

$HOME = Small Miracle

2009-06-27T00:46:00.000-07:00

My $HOME sweet home - Sri Lanka :).

Axis2 Code Generator

2009-06-26T23:57:00.000-07:00

This is a follow up to my earlier post. What I am planning to do is to come up with a mechanism to generate jython code for a given WSDL. For this purpose I am planning to use Axis2's Code Generation module.

When you consider a SOAP processing engine, one of the key value additions will be code generation based on WSDL. It is normally considered as a tool and importance of it can be seen as;

User convenience - Code generation tool helps users, to use the framework in easy and efficient way.
Make use of the framework to it's full potential.

Now let's have a look at the architecture of Axis2 Code generator.

The tool's architecture is pretty straight forward. The core processes the WSDL and builds a object model. Then the built object model is parsed against the template to build the source code.

King of Pop - MJ

2009-06-26T22:59:00.001-07:00

Michael Jackson died yesterday. He was considered the King of Pop and a megastar of music industry. Despite all accusations, he is one of those people who really made a difference. RIP MJ.