DUSHAN 'S VIEW

Implement an effective Digital Platform using WSO2 Integration - WSO2 Con 17

2017-01-19T18:05:00.002-08:00

Distributed Transaction (XATransaction) For JMS Trasnport- WSO2 ESB 5.0.0

2016-11-16T10:48:00.000-08:00

Distributed Transaction (XATransaction) For JMS Trasnport- WSO2 ESB 5.0.0

Distributed transactions plays a major role in today's business world. It adds a very important functionality to your system, which you will only see in a system crash. Having good transactional support in your system will definitely save your business in a system crash.

Distributed JMS transaction

An external transaction manager manages the coordination of the transaction. Designing and using JMS distributed transactions is more complex than using local JMS transactions.

The transaction manager is the primary component of the distributed transaction infrastructure and distributed JMS transactions are managed by the XAResource enabled transaction manager in the J2EE application server. Also note that you need to check if your message broker supports XA transactions.

XA two-phase commit process

The two-phase commit consists of the following steps:

Immediately after the transaction begins, the transaction manager invokes start() on the JMS XA resource, which indicates that the resource should initialize a new transaction. The JMS XA resource now generates a new transaction ID and sends it over the network to the remote broker.

The JMS XA resource now forwards all of the operations that arise during a JMS session (for example, messages, acknowledgments, and so on) to the remote broker.

On the broker side, the received operations are not performed immediately. Because the operations are happening in a transaction context and the transaction is not yet committed, the broker buffers all of the operations in a transaction store (held in memory, initially). Messages held in the transaction store are not forwarded to JMS consumers.

In a two-phase commit process, the first phase of completing the transaction is where the transaction manager invokes prepare() on all of the participating XA resources. At this stage, the JMS XA resource sends the prepare() operation to the remote broker.

On the broker side, when the transaction store receives the prepare() operation, it writes all of the buffered operations to disk. Hence, after the prepare phase, there is no longer any risk of losing data associated with this transaction branch.

The second phase of completing the transaction is where the transaction manager invokes commit() on all of the participating XA resources. The JMS XA resource sends the commit() operation to the remote broker.

On the broker side, the transaction store marks this transaction as complete. The pending operations are now executed and any pending messages can now be forwarded to JMS consumers.

Please follow documentation to configure WSO2 esb with activemq browser.

XA transaction example.

ESB listen to message queue and send that message to multiple queues. if something went wrong in sending the message to one of those queues, the original message should be rollbacked to Listening queue and none of the queues should receive the message. The entire transaction should be rollbacked.

The following example code shows the configuration of ESB which listen to a JMS queue and consume messages as well as to send messages to multiple JMS queues in transactional manner.

<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="JMSListenerProxy"
       transports="https http jms"
       startOnLoad="true">
   <description/>
   <target>
      <inSequence>
         <property name="OUT_ONLY" value="true"/>
         <log level="custom">
            <property name="MESSAGE_ID_A" expression="get-property('MessageID')"/>
         </log>
         <log level="custom">
            <property name="BEFORE" expression="$body"/>
         </log>
         <property name="MESSAGE_ID_B"
                   expression="get-property('MessageID')"
                   scope="operation"
                   type="STRING"/>
         <property name="failureResultProperty"
                   scope="default"
                   description="FailureResultProperty">
            <result xmlns="">failure</result>
         </property>
         <enrich>
            <source clone="true" xpath="$ctx:failureResultProperty"/>
            <target type="body"/>
         </enrich>
         <log level="custom">
            <property name="AFTER" expression="$body"/>
         </log>
         <property name="BEFORE1" value="ABCD" scope="axis2" type="STRING"/>
         <callout serviceURL="jms:/ActiveMQPublisher1?transport.jms.ConnectionFactoryJNDIName=XAConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;transport.jms.DestinationType=queue;transport.jms.TransactionCommand=begin">
            <source type="envelope"/>
            <target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                    xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                    xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
         </callout>
         <callout serviceURL="jms:/ActiveMQPublisher2?transport.jms.ConnectionFactoryJNDIName=XAConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;transport.jms.DestinationType=queue">
            <source type="envelope"/>
            <target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                    xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                    xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
         </callout>
         <callout serviceURL="jms:/ActiveMQPublisher3?transport.jms.ConnectionFactoryJNDIName=XAConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;transport.jms.DestinationType=queue;transport.jms.TransactionCommand=end">
            <source type="envelope"/>
            <target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                    xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                    xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
         </callout>
         <drop/>
      </inSequence>
      <faultSequence>
         <log level="custom">
            <property name="Transaction Action" value="Rollbacked"/>
         </log>
         <callout serviceURL="jms:/ActiveMQPublisherFault?transport.jms.ConnectionFactoryJNDIName=XAConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;transport.jms.DestinationType=queue;transport.jms.TransactionCommand=rollback">
            <source type="envelope"/>
            <target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                    xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                    xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
         </callout>
      </faultSequence>
   </target>
   <parameter name="transport.jms.ContentType">
      <rules>
         <jmsProperty>contentType</jmsProperty>
         <default>application/xml</default>
      </rules>
   </parameter>
   <parameter name="transport.jms.Destination">MyJMSQueue</parameter>
</proxy>

To place a message into a JMS queue, execute following command from /samples/axis2Client directory.

ant stockquote -Dmode=placeorder -Dtrpurl="jms:/MyJMSQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.ContentTypeProperty=Content-Type&transport.jms.DestinationType=queue"

You should be able to observe ESB consumes messages from MYJMSQueue and sends to multiple queues. To check rollback functionality provide unreachable host name to any destination queue and save the configurations. You should be able to observe ESB fault sequence getting invoked and failed message delivered to configured destination within fault sequence

Anyway,

The problem with XA is it can be a bit slow; as the XA protocol requires multiple syncs to disk to ensure it can always recover properly under every possible failure scenario. This adds significant cost (in terms of latency, performance, resources and complexity). Also quite a few EJB servers and databases don't actually properly support XA

So a good optimisation is to use regular JMS transactions - with no XA - and just perform some duplicate message detection in your code to check you have not already processed the message. (ref ActiveMQ)

Amazon API GW integration with WSO2 IS for OAuth 2.0 token validation

2016-10-14T15:03:00.001-07:00

In this blog thought of discussing another interesting topic which is relate token validation and how you can register a custom Authorizers via lambda functions to the Amazon API Gateway and use WSO2 Identity Server as authorization server.

So, Following steps will guide you on how to use WSO2 IS as a custom authorize for Amazon APIs.

Setup WSO2 Identity Server

We will be generating tokens in WSO2 IS and using them to call APIs configured in Amazon API Gateway Preparing WSO2 IS And Generating tokens
When testing WSO2 IS for Amazon API Gateway, we used OAuth 2.0 Token Introspection API. You need host (introspect.war) that you need to deploy in IS.
The source for this is found in [1]

Extract the downloaded zip file to a convenient file location. This distributed folder (by default the folder name is wso2is-5.2.0 ) will be referred to as throughout the document.
Copy introspect.war file to /repository/deployment/server/webappslocation. In order to generate an access token we need to create an Oauth2 application and get client credentials from there
Start the server and login to the management console with admin:admin credentials. Steps to start the product are in [2]. Also you can find the complete installation guide in [3] Note : In order to be accessed by Amazon Gateway Lambda function, this up and running Identity Server should be hosted with a public URL 4. In the main menu in management console, click “Add” under Service Provider

Give a Service Provider name and click Register. You will see the Service Provider
Configuration page.
Expand Inbound Authentication Configuration panel.
Expand the OAuth/OpenID Connect Configuration and click Configure.
Fill in the form that appears. For the Allowed Grant Types you can disable the ones you do not require or wish to block.
Use following request to generate tokens with password grant type

Replace and values with admin. Replace with Base64 encoded values

curl -k -d
"grant_type=password&username=<USERNAME>&password=<PASSWORD>&scope=<SCOPE>" -H
"Authorization: Basic <ENCODED_KEY>" -H "Content-Type:
application/x-www-form-urlencoded"
https://<IS_HOST>t:<IS_HTTPS_PORT>/oauth2/token

will have a response similar to,

curl -k -d "grant_type=password&username=admin&password=admin&scope=default " -H
"Authorization: Basic
X1ZpREJUMWJUSHF5eXFfR1Y0UWJoc0V6X1IwYTpLdzIxV1JPRmYyeTc4RGViMXY0UGpoRkdydGhq" -H
"Content-Type: application/x-www-form-urlencoded"
https://localhost:9443/oauth2/token
This will have a response similar to,
{
 "scope": "default"
 "token_type": "Bearer"
 "expires_in": 956
 "refresh_token": "23444-dff-32b0-b4cf-7dc7d8fd8205"
 "access_token": "455533ed-d222-3b0e-9512-fec0b94c1592"
}

We will use this access_token value when invoking APIs in AWS side.

Configuring Amazon API Gateway

Goto Lambda console in Amazon API Gateway and create new Lambda function.

This function should call Token Introspection API of WSO2 IS Server. I have attached a sample lambda function (Lambda.js) which is calling this API. You can copy the source of this file and

console.log('starting lambda');
var http = require('http');
exports.handler = function(event, context) {
    var tkn = event.authorizationToken;
 var postData = 'token='+tkn;
 console.log(postData);

 var options = {
   hostname: 'ip.address',
   port: 9763,
   path: '/introspect',
   method: 'POST',
   headers: {
     'Content-Type': 'application/x-www-form-urlencoded'
   }
 };

 var req = http.request(options, (res) => {
   console.log(`STATUS: ${res.statusCode}`);
   console.log(`HEADERS: ${JSON.stringify(res.headers)}`);
   res.setEncoding('utf8');
   res.on('data', (chunk) => {
     console.log(`BODY: ${JSON.stringify(chunk)}`);
  validationReq(chunk,event,context);
   });
   res.on('end', () => {
     console.log('No more data in response.');
   });
 });

 req.on('error', (e) => {
   console.log(`problem with request: ${e.message}`);
 });

 // write data to request body
 req.write(postData);
 req.end();

}

var validationReq = function (obj,evt,ctx) {
    console.log(obj);
    obj = JSON.parse(obj);

    var bool = obj['active'];
 if(bool) {
     console.log('Token verified');
     ctx.succeed(generatePolicy('user', 'Allow', evt.methodArn));
 } else {
     ctx.fail("Unauthorized");
 }
 
}


var generatePolicy = function(principalId, effect, resource) {
    var authResponse = {};
    console.log(resource);
    authResponse.principalId = principalId;
    if (effect && resource) {
        var policyDocument = {};
        policyDocument.Version = '2012-10-17'; // default version
        policyDocument.Statement = [];
        var statementOne = {};
        statementOne.Action = 'execute-api:Invoke'; // default action
        statementOne.Effect = effect;
        statementOne.Resource = resource;
        policyDocument.Statement[0] = statementOne;
        authResponse.policyDocument = policyDocument;
    }
    return authResponse;
}

Copy it as the Lambda function code. Note that you have to replace <host_name of publiclyhosted wso2 is> and <port of publicly hosted wso2 is> values with actual host and port before using it.

Save the Lambda function.

Follow Configure Custom Authorizer Using the API Gateway Console in [1] When creating the custom authorizer, make sure you give Lamba Region and Lambda Function details according to the function you created in Step 1.

After above configurations are done, you should have an API deployed in Amazon API
Gateway which is configured to use the custom authorizer which calls WSO2 IS to authorize.
Invoke this API giving the access_token obtained from WSO2 IS as the Identity token source header value you configured when above step.

Note:- How Please refer OAuth 2.0 Token Introspection API for WSO2 Identity Server to understand how introspect API calls would validate the access tokens and responses

Empty token
curl -k -H 'Content-Type: application/x-www-form-urlencoded' -X POST --data 'token=' https://localhost:9443/introspect
Response: {"active":false}

Invalid token: 
curl -k -H 'Content-Type: application/x-www-form-urlencoded' -X POST --data 'token=Bjhk98792k9hkjhk' https://localhost:9443/introspect 
Response: {"active":false,"token_type":"bearer"}

Get a valid token: 
curl -v -X POST --basic -u client_id:client_secret -H "Content-Type: application/x-www-form-urlencoded;charset=UTF-8" -k -d "grant_type=client_credentials" https://localhost:9443/oauth2/token Validate the token:
curl -k -H 'Content-Type: application/x-www-form-urlencoded' -X POST --data 'token=99f0a7092c71a6e772cbcf77addd39ea' https://localhost:9443/introspect 
   Response: 
   { "username":"admin@carbon.super", 
     "nbf":3272, 
     "active":true, 
     "token_type":"bearer", 
     "client_id":"LUG28MI5yjL5dATxQWdYGhDLSywa" 
   }

[1] https://github.com/facilelogin/aratuwa/tree/master/api-security/org.wso2.carbon.identity.oauth.introspection
[2] https://docs.wso2.com/display/IS520/Running+the+Product
[3] https://docs.wso2.com/display/IS520/Installation+Guide
[4] http://docs.aws.amazon.com/apigateway/latest/developerguide/use-custom-authorizer.html

IoT Use case WSO2

2016-06-11T15:15:00.002-07:00

In this blog, I thought of discussing kind of an interesting use case which involves communicating and managing alerts though the concept IoT (Internet Of Things)

The use case which I'm describing involve WSO2 middleware stack, before that lets try to understand use case first.

Story
A organization called 'Amber Shopping complex' who is well reputed organization doing clothing business. Then recently their management decided to enhance the client experience and planning to bring more user friendly environment when a buyer enters in to the shop complex. So the concept is 'Amber' publish advertisement on TV, News Papers asking to download newly developed mobile application. Since 'Amber' is so popular, all most all its buyer have download the mobile application.
Then, once users movies different parts of the shopping complex, the mobile device sending the notification to the 'Amber Shopping IT genius', so what will be happening after that you will be amazed.

Client going to buy shirts (which he has already search through mobile device), he received alters from to the mobile application asking his choices, and new arrivals to the store.
Client walking pass TV display guess what, the TV display suddenly personalizing and start to show what he has preferred in the past and choices available and locations (Digital Signage)
Client go to different section "let say" kid toys section, client received alerts to his mobile devices, the new toys arrived and prices

... and many more other cool stuff...

Let assume how we can achieve above use case, to accomplish this use case we are using
WSO2 Iot Server , WSO2 CEP, WSO2 MB, WSO2 ESB,WSO2 APIM,WSO2 DAS

I know most of you may already aware others products other than WSO2 Iot server (which of cause yet to be released officially by WSO2), so let me give you a small introduction what WSO2 Iot Server (which is still at Alpha state), if anyone interest they could join to the beta program.

What is IoT server ?

"WSO2 IoT Server (IoTS) is the core of WSO2's Open IoT Platform. It provides the capabilities required by device manufacturers and enterprises to build a complete IoT architecture around their connected device offering. Device manufactures are able to manage the device architecture from the server-side using WSO2 IoTS, extend the IoTS to any device type, and support other protocols and data formats as it runs on top of WSO2 Connected Device Management Framework (WSO2 CDMF).
WSO2 IoTS offers customizable and advanced IoT device analytics via WSO2 Data Analytics Server that include predictive analytics using machine learning capabilities. It also supports edge computing devices, policy-based edge analytics, and pre-built instant visualization for sensor readings using live data streams gathered from devices.
Take a look at the WSO2 IoT Server presentation on Your foundation for the Internet of things to expand your knowledge on IoTS. This is a great place for you to start if you are new to WSO2 IoTS."

If you need more information please visit [1]

Now lets try to see how we could overcome the given use case, please see the below diagram which show complete interaction or solution architecture, that can be implemented to overcome the given use case.

Solution Architectural View

Following diagram illustrating the complete interaction from device registration and alerting model would work

Flow

What we need to understand here is the role which WSO2 Iot server plays, i.e how it interacts with different modules to complete the user interaction, specially we have to isolate use experience for that, it is must that have to maintain a device in which client use along side with some other information.

On the other hand, the for intercommunication,such as mobile devices to message broker we thought of using mqtt protocal (pub/sub)

Why we need MQTT? ref [2]

MQTT was developed by Andy Stanford-Clark (IBM) and Arlen Nipper (Eurotech; now Cirrus Link) in 1999 for the monitoring of an oil pipeline through the desert. The goals were to have a protocol, which is bandwidth-efficient and uses little battery power, because the devices were connected via satellite link and this was extremely expensive at that time.
The protocol uses a publish/subscribe architecture in contrast to HTTP with its request/response paradigm.Publish/Subscribe is event-driven and enables messages to be pushed to clients. The central communication point is the MQTT broker, it is in charge of dispatching all messages between the senders and the rightful receivers. Each client that publishes a message to the broker, includes a topic into the message. The topic is the routing information for the broker. Each client that wants to receive messages subscribes to a certain topic and the broker delivers all messages with the matching topic to the client. Therefore the clients don’t have to know each other, they only communicate over the topic. This architecture enables highly scalable solutions without dependencies between the data producers and the data consumers.

CEP role
CEP (Complex event processor) plays equally important role in this design with its real time analysis capability while alerting other sub modules such as if client move one place to another, mobile device publishes GPS detail and CEP engine keep analyzing them and sends alerts to ESB, where it interact with other sub-modules. (please read [3] for more information)

Finally
If you need to write such requirement from the sketch, it would require a thousand lines of codes may be much more complicated interaction between system. But with above of cause with minimal effort you can simply build the integration layer.

[1]https://docs.wso2.com/display/IoTS100/WSO2+IoT+Server
[2] http://www.hivemq.com/blog/how-to-get-started-with-mqtt
[3] http://wso2.com/library/blog-post/2013/11/understanding-complex-event-processing-(cep)-operators-with-wso2-cep-(siddhi)/

Troubleshoot and understanding Puppet deployment

2016-05-30T11:15:00.001-07:00

Following blog, I will try to describe the steps that you may need to follow up in order to setup a WSO2 product cluster quick time using Puppet scripts.
Basically, thought this is straight forward you may have to spent few minutes or some time few hours to get firm to your self. Because if you just start to work these environments thing gonna be bit difficult. In this blog I try to target people who just started to work with puppet and of cause they may be face similar issues.

For the ease of understanding, we have divided the instructions into 3 Tasks.

    Step 1. Setup two instances
    Step 2. Setup Puppet Master and puppet agent
    Step 3. Perform a catalog run to configure product instance

First of all lets try to understand puppet directory structure [1],basically, hiera structure defines the variable and parameters per environment per platform per product such as how it should populate while under module, the templates of each products defined with .erp

If you refer below structure, you will notice something called 'hiera', the term we are using With Hiera, you can externalize your systems' configuration data and easily understand how those values are assigned to your servers. With that data separated from your Puppet code, you then can encrypt sensitive values, such as passwords and keys [2]

Once you navigate, please try to understand the project structure, in this case we are trying to prepare 'dev' environment, so understanding hiera model is important.

lets see how hiera.yaml definition looks

:hierarchy:
    - "node/%{::clientcert}"
    - "wso2/%{::product_name}/%{::product_version}/%{::platform}/%{::product_profile}"
    - "wso2/%{::product_name}/%{::product_version}/%{::platform}/default"
    - "osfamily/%{::osfamily}"
    - "vm_type/%{::vm_type}"
    - "platform/%{::platform}"
    - wso2/common
    - common
:backends:
    - yaml
:yaml:
    :datadir: "/etc/puppet/hieradata/dev"

In above structure, it would explain how hiera would travel through, then extract variables to prepare the platform that you are running.

Let assume I need to run api-store profile (APIM having store,publisher,gateway,key manager), then once I initiate the product profile from puppet agent (which I will explain later), when puppet agent communicates with puppet master, it would go through above mentioned hierarchy to resolve variables i.e
api-store.yaml --> default.yaml--> common.yaml --> (root common) -->common.yaml

However, first of all we should install puppet do refer [3], follow the steps given

Sometimes you will not succeeded straightforward (As I was struggle for a while to establish connection between puppet agent and master, therefore if you have any trouble please do refer[4])

From my personal experience,the most common issue you will face

err: Could not request certificate: No route to host - connect(2)
Exiting; failed to retrieve certificate and waitforcert is disabled

I would say, if you need to resolve this, you don't need to fiddle around much

There are few steps you need to verify,

Step-1
Please make sure /etc/hosts files of both nodes as given below, make sure you gave puppet master host name correctly

Puppet master
/etc/hosts
127.0.0.1 localhost
127.0.0.1 puppet puppetmaster

/etc/hostname
puppetmaster

Puppet Agent
/etc/hosts
127.0.0.1      localhost
[IP-address of puppetmaster]     puppetmaster
[IP-address of agent]      [Agent-hostage]

Step-2

Verify at puppet agent the puppet.conf file under /etc/puppet/, the only thing you need to focus [agent] tag and verify the server mapping as highlighted below

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post

[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY

[agent]
server=puppetmaster

Step3
Then at puppet master, /puppet/hieradata/dev/wso2/common.yaml, please check following entry

# Host mapping to be made in etc/hosts
wso2::hosts_mapping:
localhost:
    ip_address: 127.0.0.1
    hostname: localhost
puppetmaster :
    ip_address : [puppet-master-ip]
    hostname : puppetmaster
pub.am.wso2.com :
    ip_address : [agent-ip]
    hostname : [agent-hostname]

** Make to give correct information under host name, as these gonna replace /etc/hosts mapping during run time, else thing gonna break up while scripts running

Step4
Check puppet.conf under puppet master "puppet/puppet.conf", please make sure it has "autosign=true" which required for certification signing for proper master-agent communication

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
#factpath=$vardir/lib/facter
templatedir=$confdir/templates
dns_alt_names=puppetmaster,puppet
hiera_config = /etc/puppet/hiera.yaml

[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
autosign=true

If you verify above given steps carefully, you should execute following command;

Puppet Master

puppet cert clean —all
service puppetmaster restart
** If you need to see whats going inside puppet master, then you can start "puppet master --no-daemonize --debug"

Puppet Agent

"find /var/lib/puppet/ssl -name '*.pem' -exec rm {} \;" (to clean up invalid certificates)
puppet agent -t —debug (to establish master-agent connection)

Puppet Agent run time
Once verify above, then just run setup.sh, which should start to deploy agent profile while communicating with master

deployment.cofig

product_name=wso2am   // defines the product type
product_version=1.10.0 //define the product version
product_profile=default //defines the profiles
environment=dev // the environment
vm_type=openstack
platform=default

setup.sh

#!/bin/bash
echo "#####################################################"
echo "                   Starting cleanup "
echo "#####################################################"
ps aux | grep -i wso2 | awk {'print $2'} | xargs kill -9
#rm -rf /mnt/*
sed -i '/environment/d' /etc/puppet/puppet.conf
echo "#####################################################"
echo "               Setting up environment "
echo "#####################################################"
rm -f /etc/facter/facts.d/deployment_pattern.txt
mkdir -p /etc/facter/facts.d

while read -r line; do declare $line; done < deployment.conf
echo "reading...."
echo product_name=$product_name product_version=$product_version product_profile=$product_profile
echo product_name=$product_name >> /etc/facter/facts.d/deployment_pattern.txt
echo product_version=$product_version >> /etc/facter/facts.d/deployment_pattern.txt
echo product_profile=$product_profile >> /etc/facter/facts.d/deployment_pattern.txt
echo vm_type=$vm_type >> /etc/facter/facts.d/deployment_pattern.txt
echo environment=$environment >> /etc/facter/facts.d/deployment_pattern.txt
echo platform=$platform >> /etc/facter/facts.d/deployment_pattern.txt

echo "reading end"

echo "#####################################################"
echo "                    Installing "
echo "#####################################################"

puppet agent --enable
puppet agent -vt
puppet agent --disable

Please use [5] to download the puppet-master module which I have used to config, but there you have to copy JDK, products etc

[1]
├── LICENSE
├── README.md
├── hiera.yaml
├── hieradata
│   └── dev
│       ├── common.yaml
│       ├── platform
│       │   └── kubernetes.yaml
│       ├── vm_type
│       │   └── docker.yaml
│       └── wso2
│           ├── common.yaml
│           ├── wso2am
│           │   ├── 1.10.0
│           │   │   ├── default
│           │   │   │   ├── api-key-manager.yaml
│           │   │   │   ├── api-publisher.yaml
│           │   │   │   ├── api-store.yaml
│           │   │   │   ├── default.yaml
│           │   │   │   ├── gateway-manager.yaml
│           │   │   │   └── gateway-worker.yaml
│           │   │   └── kubernetes
│           │   │       ├── api-key-manager.yaml
│           │   │       ├── api-publisher.yaml
│           │   │       ├── api-store.yaml
│           │   │       ├── default.yaml
│           │   │       ├── gateway-manager.yaml
│           │   │       └── gateway-worker.yaml
├── manifests
│   └── site.pp
├── modules
│   ├── java
│   │   ├── LICENSE
│   │   ├── Modulefile
│   │   ├── README.markdown
│   │   ├── manifests
│   │   │   ├── init.pp
│   │   │   └── setup.pp
│   │   ├── metadata.json
│   │   ├── spec
│   │   │   ├── spec.opts
│   │   │   └── spec_helper.rb
│   │   └── tests
│   │       └── init.pp
│   ├── wso2am
│   │   ├── README.md
│   │   ├── files
│   │   │   ├── configs
│   │   │   │   └── repository
│   │   │   │       └── components
│   │   │   │           ├── dropins
│   │   │   │           └── lib
│   │   │   ├── patches
│   │   │   │   └── repository
│   │   │   │       └── components
│   │   │   │           └── patches
│   │   │   ├── system
│   │   │   └── wso2am-1.10.0.zip
│   │   ├── manifests
│   │   │   └── init.pp
│   │   ├── metadata.json
│   │   └── templates
│   │       ├── 1.10.0
│   │       │   ├── bin
│   │       │   │   ├── ciphertool.sh.erb
│   │       │   │   └── wso2server.sh.erb
│   │       │   ├── password-tmp.erb
│   │       │   └── repository
│   │       │       └── conf
│   │       │           ├── api-manager.xml.erb
│   │       │           ├── axis2
│   │       │           │   └── axis2.xml.erb
│   │       │           ├── carbon.xml.erb
│   │       │           ├── datasources
│   │       │           │   ├── am-datasources.xml.erb
│   │       │           │   └── master-datasources.xml.erb
│   │       │           ├── identity
│   │       │           │   └── identity.xml.erb
│   │       │           ├── registry.xml.erb
│   │       │           ├── security
│   │       │           │   ├── cipher-text.properties.erb
│   │       │           │   └── cipher-tool.properties.erb
│   │       │           ├── tomcat
│   │       │           │   └── catalina-server.xml.erb
│   │       │           └── user-mgt.xml.erb

[2] http://www.linuxjournal.com/content/using-hiera-puppet
[3] https://github.com/wso2/puppet-modules/wiki/Use-WSO2-Puppet-Modules-in-puppet-master-agent-Environment
[4] http://suhan-opensource.blogspot.com/2014/10/puppet-master-agent-communication-errors.html
[5] https://www.dropbox.com/s/6sljlbj1bop46lx/puppet.zip?dl=0

WSO2 ESB Accessing application/x-www-form-urlencoded Data

2016-05-27T13:04:00.004-07:00

Problem:

I want to pass application/x-www-form-urlencoded data to the ESB:

curl -v -X POST 'http://myhost/myapi/stuff' -d 'myvar=hello' -H "Content-Type: application/x-www-form-urlencoded"

...and then be able to receive each form variable in my ESB API .

To get a given variable, I'm doing this:

<resource methods="POST" uri-template="/stuff">
      <inSequence>
         <property name="myvar" expression="//xformValues//myvar/text()"></property>
...

Then I'm storing that in an argument:

<args>
   <arg evaluator="xml" expression="$ctx:myvar"></arg>
</args>

Then I'm later trying to stuff it in a payload with $1.

I know that the issue is with the property line:

<property name="myvar" expression="//xformValues//myvar/text()"></property>

...because if I store a literal value in the line, it will work.

I do have the messageReceiver configured in the axis.xml:

<messageFormatter contentType="application/x-www-form-urlencoded"
    class="org.apache.axis2.transport.http.XFormURLEncodedFormatter"/>
<messageFormatter contentType="multipart/form-data"

And, I have the messageBuilder configured in the axis.xml file:

<messageBuilder contentType="application/x-www-form-urlencoded"
    class="org.apache.synapse.commons.builders.XFormURLEncodedBuilder"/>

ANSWER : Just use

`<property name="myvar" expression="//myvar/text()"/>`

e.g
wire logs

[2016-05-27 12:59:22,160] DEBUG - wire >> "POST /foo123 HTTP/1.1[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "User-Agent: curl/7.37.1[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "Host: 192.168.56.1:8280[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "Accept: */*[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "Authorization: Basic QU93ZmJQRW5YcXVDVnhIS1ZZT2ZlVFQxT01NYTpEeGpBY3dodFB5Wm5JTU9CZmJEakRHc21FQjBh[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "Content-Type: application/x-www-form-urlencoded;charset=UTF-8[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "Content-Length: 135[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "[\r][\n]"
[2016-05-27 12:59:22,161] DEBUG - wire >> "grant_type=authorization_code&code=291a24141f1e3332baf9799c4c378033&redirect_uri=https://identity.qa.example.com/playground2/oauth2.jsp"
[2016-05-27 12:59:22,163] DEBUG - LogMediator Start : Log mediator
[2016-05-27 12:59:22,163]  INFO - LogMediator To: /foo123, MessageID: urn:uuid:c20f24d4-668d-447e-9de0-dbe5885b6d16, Direction: request
[2016-05-27 12:59:22,164] DEBUG - LogMediator End : Log mediator
[2016-05-27 12:59:22,164] DEBUG - LogMediator Start : Log mediator
[2016-05-27 12:59:22,164]  INFO - LogMediator payload = <mediate><code>291a24141f1e3332baf9799c4c378033</code><redirect_uri>https://identity.qa.example.com/playground2/oauth2.jsp</redirect_uri><grant_type>authorization_code</grant_type></mediate>,code = 291a24141f1e3332baf9799c4c378033
[2016-05-27 12:59:22,164] DEBUG - LogMediator End : Log mediator
[2016-05-27 12:59:22,165] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2016-05-27 12:59:22,165] DEBUG - wire << "Authorization: Basic QU93ZmJQRW5YcXVDVnhIS1ZZT2ZlVFQxT01NYTpEeGpBY3dodFB5Wm5JTU9CZmJEakRHc21FQjBh[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Host: 192.168.56.1:8280[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Content-Type: application/x-www-form-urlencoded;charset=UTF-8[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Accept: */*[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Date: Fri, 27 May 2016 19:59:22 GMT[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Server: WSO2-PassThrough-HTTP[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "91[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "code=291a24141f1e3332baf9799c4c378033&redirect_uri=https%3A%2F%2Fidentity.qa.example.com%2Fplayground2%2Foauth2.jsp&grant_type=authorization_code[\r][\n]"
[2016-05-27 12:59:22,166] DEBUG - wire << "0[\r][\n]"
[2016-05-27 12:59:22,167] DEBUG - wire << "[\r][\n]"

API

<api xmlns="http://ws.apache.org/ns/synapse" name="foo123" context="/foo123">
   <resource methods="POST">
      <inSequence>
         <log></log>
         <property name="payload" expression="//mediate"></property>
         <property name="code" expression="//mediate/code"></property>
         <log level="custom" separator=",">
            <property name="payload" expression="$ctx:payload"></property>
            <property name="code" expression="$ctx:code"></property>
         </log>
         <respond></respond>
      </inSequence>
   </resource>
</api>
 

WSO2 IS SSO with .NET application

2016-05-11T12:40:00.001-07:00

In this blog, I would like to discuss another common case which, I couldn't find many entries in explaining how to integrate WSO2 Identity Server with .NET web application.

There are different types of 3rd party components available but out of that thought of demonstrating the demo with Component Space [1] which provides a comprehensive framework to implement SSO solutions and the demonstration was prepared with using those references.

I will use some steps (with images) to demonstrate how easily could integrate, the sample code can be download [3] and you could easily open up .NET IDE so, you can customize it according to your preference.

First, you should register .NET web application you have written as a service provider, you can customize SP parameters such as assertion encryption, SLO settings according to your preference. (I would assume at this point you may have covered fundamentals of WSO2 Identity server, such as registering Sevice Provide (SP), Identity Provider (IP) and other basic fundamentals, if not recommendation is to go through [2]

Then, you have to customize the SSO web app settings under web.config

<configuration>
  <appSettings>
    <add key="idpssoURL" value="https://localhost:9443/samlsso" />
    <add key="idpArtifactResponderURL" value="http://localhost:51394/SAML2IdentityProvider/SAML/ArtifactResponder.aspx" />
    <add key="idpLogoutURL" value="https://localhost:9443/samlsso" />
 </appSettings>
<connectionStrings/>

Once you do all the required modifications at SSO web app, then when deploying to IIS server, during initial startup it would ask the way SSOSAMLRequest should have generated, this is customizable, which means you don't need to expose to the actual client but for development perspective, you can play around with different options available.

The next step would be, when you click "continue" button, it would direct you to IS SSO login page as depicted below.

Then once you log in successfully, it would show the welcome page as given below.

[1] https://docs.wso2.com/display/IS500/Samples
[2] http://www.componentspace.com/SAMLv20.aspx
[3] https://www.dropbox.com/s/jfik1852xdhf342/SAML2ServiceProvider.zip?dl=0

WSO2 Gateway (WSO2 GW) -Alpha

2015-10-31T14:35:00.003-07:00

WSO2 Gateway (WSO2 GW) is an ultra high performance, lightweight and configuration-driven message gateway based on
standard gateway pattern. It aims to encapsulate messaging between source and target systems that are built with
disparate technologies, protocols, and standards. While it includes messaging between two systems, message mediation
can be controlled by configuring WSO2 GW’s mediation logic.

Download Aplha

Key Features

* Ultra high performance and low latency HTTP/S messaging.

* Supports thousands of concurrent connections/clients.

* Header-based routing using Apache Camel as the message mediation engine.

* Defines REST services/APIs using Camel REST DSL.

* Lightweight and stateless service orchestration.

* Load balancing and failover messaging.

* Error handling support.

Getting Started

By configuring the [camel-context.xml](https://github.com/wso2/product-gw/blob/master/product/carbon-home/repository/conf/camel/camel-context.xml) (which can be found in `$CARBON_HOME/repository/conf/camel/camel-context.xml`)
we can achieve camel routing.

Sample camel configuration for Header-based routing

<route id="http-routes">
<from uri="wso2-gw:/default"/>
<choice>
<when>
<simple>${header.routeId} regex 'r1'</simple>
<to uri="wso2-gw:http://localhost:9000/services/SimpleStockQuoteService"/>
</when>
<when>
<simple>${header.routeId} regex 'r2'</simple>
<to uri="wso2-gw:http://localhost:9002/service/SimpleStockQuoteService"/>
</when>
<otherwise>
<to uri="wso2-gw:http://localhost:9004/SimpleStockQuoteService"/>
</otherwise>
</choice>
</route>
```

Sample request to route to localhost:9000
curl http://localhost:9090/default -H __"routeId:r1"__

If we don't have any routeId header the request will be routed to the localhost:9004 (i.e to otherwise)

Sampel REST configuration

Following is a sample rest interface definition
```
<rest path="/gw">
<get uri="/news">
<to uri="direct:getNews"/>
</get>
<get uri="/news/{id}">
<to uri="direct:getNewsById"/>
</get>
</rest>
```

and follwoing is the corresponding routes
```
<route>
<from uri="direct:getNews"/>
<to uri="wso2-gw:http://jsonplaceholder.typicode.com/posts"/>
</route>
<route>
<from uri="direct:getNewsById"/>
<recipientList>
<simple>wso2-gw:http://jsonplaceholder.typicode.com/posts/${header.id}</simple>
</recipientList>
</route>
```

when we invoke the request `http://localhost:9090/gw/news`
it will be routed to `http://jsonplaceholder.typicode.com/posts`

similarly `http://localhost:9090/gw/news/24` will be routed to `http://jsonplaceholder.typicode.com/posts/24`

Connecting IBM MQ with WSO2 ESB via SSL (Mutual Authentication)

2015-06-15T15:40:00.002-07:00

Thought of writing this blog because very recently we a had use-case to demonstrate this particular features, but not like other MQ, IBM MQ gave us a hard time to figure out and fix the puzzle. On the other hand WSO2 ESB to MQ connection via SSL quite important and the most trick part is to learn the materials provided by IBM, this blog covers connecting IBM MQ 8.0 with Fix pack released for MQ SSL related issues MQ 8.0.0.2 please find the detail [2][4]

First tricky part is to define a certificate repository correctly best way learn this is to study [1], please find the key repository detail I have configured.

Once you do that, next most important part is setting key repositories to MQ connection managers, you need to give the path in which the key repository has stored

Then you need to follow the same procedure to create connection with .binding [3]
Once do that you need to provide the SSL cipher spec which suppose to use there are few algorithms but remember that with IBM MQ 8.0 onwards SSL V3 support is deprecated thus you need to use the latest java client libraries to connect the queue.
Please read [5] the changes that accommodated in IBM MQ 8.0

There were lots of class loader issues, it was due to MQ 7.0.0 client libraries conflict and we have created new OSGI jar bundle to resolve this puzzle, please find the latest jars which you must put in ESB dropping folder and make sure only those two jars only required for connect latest MQ 8.0 otherwise you will get tons of connection related issues.
Then when you start ESB you need to include the cipher spec as environment variable, please make sure to modify wso2servers.sh with

-DCMQC.SSL_CIPHER_SUITE_PROPERTY="SSL_RSA_WITH_3DES_EDE_CBC_SHA" \

[1] http://www.ibm.com/developerworks/websphere/library/techarticles/0510_fehners/0510_fehners.html

[2] http://www-01.ibm.com/support/docview.wss?uid=swg24039436

[3] http://nandikajayawardana.blogspot.com/2015/03/configuring-ibm-mq-with-wso2-esb.html

[4] https://www.ibm.com/developerworks/community/blogs/messaging/entry/bitesize_blogging_mq_v8_fix_pack_8_0_0_2_mq_classes_now_support_tls_with_the_oracle_jre?lang=en

[5] http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.pro.doc/q001060_.htm

NTLM Authentication WSO2 ESB (Developer Testing)

2015-05-08T20:53:00.002-07:00

NTLM ?

Thought of writing this blog as I got few queries on how ESB can be configured to communicate services which are secured with NTLM (which is also is known as Windows Authentication), please refer [1] to learn more information on NTLM
When comes with WSO2 ESB we do not have OOTB approach to resolve this puzzle, we have tried to add pass-through support for NTLM. But, there seems to be inherent technical problems in NTLM standard it self preventing it to work through a proxy.

NTLM is connection oriented, based on connection state. It authenticates the connection - not really the end user.

Kerberos is the preferred choice to connect through proxy servers than NTLM, due to the connection-based nature of NTLM.

When a client needs to authenticate itself to a proxy or server using the NTLM scheme then the following 4-way handshake takes place

1: C -> S GET ...

2: S -> C 401 Unauthorized
WWW-Authenticate: NTLM

3: C -> S GET ...
Authorization: NTLM <type-1-message>

4: S -> C 401 Unauthorized
WWW-Authenticate: NTLM <type-2-message>

5: C -> S GET ...
Authorization: NTLM <type-3-message>

6: S -> C 200 Ok

This manifests itself states that the network connection must be kept alive during the second part of the handshake,i.e. between the receiving of the type-2 message from the server (step 4) and the sending of the type-3 message (step 5). Each time the connection is closed this second part (steps 3 through 6) must be repeated over the new connection (i.e. it's not enough to just keep sending the last type-3 message).

Also, once the connection is authenticated, the Authorization header need not be sent anymore while the connection stays open, no matter what resource is accessed.

Microsoft also emphasizes that NTLM requires implicit end-to-end state and will not work through a proxy server.

So how we have overcome

since we need to maintain "NTLM is connection oriented, based on connection state.", the solution we came is to use Class Mediator and CalloutMediator approach

Ok, lets start from the beginning, (for novice users this might helpful as I will go through setting up NTLM service from VM which has Windows 7)

Setup NTLM service in Windows

(Assume you have installed IIS service from windows features), Then need to enable Windows Authentication

Then you need to navigate to IIS admin service and enable Windows authentication for a selected site

Since this a developer testing, I will create a WCF service and host the created service under IIS

When you try to deploy the created WCF service from Microsoft Visual Studio few errors can be thrown and there are solutions being discussed under [2][3]

Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

The authentication schemes configured on the host ('IntegratedWindowsAuthentication') do not allow those configured on the binding 'BasicHttpBinding' ('Anonymous'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this application through the IIS management tool, through the ServiceHost.Authentication.AuthenticationSchemes property, in the application configuration file at the element, by updating the ClientCredentialType property on the binding, or by adjusting the AuthenticationScheme property on the HttpTransportBindingElement

If you successfully deploy service then when accessing the service it should look as

If you enter invalid Windows Credentials result would be

Successful invocation will results as

Setup WSO2 ESB

HttpClient has improved NTLM support please refer [4] for the relevant technical detail
Written simple client to test NTLM communication, client can be found from here

Invalid Request

And we have written a class mediator by referring the same NTLMClient i.e NTLMMediator, and once download you need to compile to OSGI jar then need to place at ESB_HOME/repository/components/dropins then restart server.
Since we do use proxy and Callout mediator approach the synapse configuration looks like give below.

If you setup everything correctly and when invoke ESB proxy then it will return result as

You could give a try on this. Its a very basic developer test for NTLM and can be enhanced many ways based on requirements.

[1] https://msdn.microsoft.com/en-us/library/windows/desktop/aa378749%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
[2] http://stackoverflow.com/questions/9794985/iis-this-configuration-section-cannot-be-used-at-this-path-configuration-lock
[3] http://stackoverflow.com/questions/15264969/make-wcf-service-integratedwindowsauthentication
[4] https://hc.apache.org/httpcomponents-client-ga/ntlm.html

Federated Authentication-Configure WSO2 IS with Salesforce

2015-03-17T17:59:00.001-07:00

This article will discuss how we could configure WSO2 Identity server with salesforce for Federated Authentication

You should create a salesforce developer account from https://developer.salesforce.com/
Once you login to developer account you need to navigate, Identity providers under Security console tab

Then you must download Salesforce public certificate and the Identity provide meta-information which is required for IDP configuration WSO2 IS

<md:entitydescriptor entityid="https://wso2idc-dev-ed.my.salesforce.com" validuntil="2025-03-18T00:16:43.800Z" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata">
   <md:idpssodescriptor protocolsupportenumeration="urn:oasis:names:tc:SAML:2.0:protocol">
      <md:keydescriptor use="signing">
         <ds:keyinfo>
            <ds:x509data>
               
            </ds:x509data>
         </ds:keyinfo>
      </md:keydescriptor>
      <md:nameidformat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:nameidformat>
      <md:singlesignonservice binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" location="https://wso2idc-dev-ed.my.salesforce.com/idp/endpoint/HttpPost">
      <md:singlesignonservice binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" location="https://wso2idc-dev-ed.my.salesforce.com/idp/endpoint/HttpRedirect">
   </md:singlesignonservice></md:singlesignonservice></md:idpssodescriptor>
</md:entitydescriptor>

You will find POST and HTTP re-directing IDP urls are at the meta-information which required when configuring WSO2 Identity Provider.

Then you need to create a Connected app, you need to provide almost similar entries when creating connected app, specially pay special attention on ACS URL and Issuer URL

Then create a user profile and add connected app where only the user who has the profile will allow to authenticate via SSO

Start Identity server then configure Identity Provider as shown below, you need to import salesforce public certificate obtained in earlier steps as below.

Configure Service provider as shown below,

Inbound configuration should be as below

Then deploy travolocity app , setup SSO then click login page

Identity Server 5.0 User Account Recovery / User Account lock and unlocking

2015-02-23T11:16:00.002-08:00

This article I'm gonna discuss about account registration methods, for the demo purpose I am going to use WSO2 IS 5.0.0 , InfomationRecovery sample (shared here with) which is hosted in Tomcat

Setting up IS 5.0.0

Update below parameters wso2is-5.0.0\repository\conf\security\identity-mgt.properties

Identity.Listener.Enable=true
Notification.Sending.Enable=true
Notification.Expire.Time=7200
Notification.Sending.Internally.Managed=true
Authentication.Policy.Enable=true
Authentication.Policy.Account.Lock.On.Failure=true
Authentication.Policy.Account.Lock.On.Failure.Max.Attempts=2
Authentication.Policy.Account.Lock.Time=2

You need to configure the email sender and here we use the axis transport Sender. Following configureation needs to be done in the axis2.xml file located in the Identity Server installation under <is_home>/repository/conf/axis2 directory. Uncomment the following and give your email details.

<transportsender class="org.apache.axis2.transport.mail.MailTransportSender" name="mailto">
<parameter name="mail.smtp.from">wso2demomail@gmail.com</parameter> 
        <parameter name="mail.smtp.user">wso2demomail@gmail.com</parameter> 
        <parameter name="mail.smtp.password">mailpassword</parameter> 
        <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> 
</transportsender>

You also can configure the email format and confirmation code urls in the email-admin-config.xml under <is_home>/repository/conf/email directory. For password recovery sending email you need to have a email template type as “passwordReset”. Following shows a sample configuration.

Start IS server
Map Account Recovery Clam as given below

Start Tomcat or any Application server, deploy war file (project can be found from here)
Click user registration

Configure IS for SP please see image

Once click from Registration will be direct to SSO page

Recover password if forgot..

SAML2 bearer tokens with OAuth2 tokens in WSO2 API Manager

2015-02-17T18:26:00.000-08:00

Most of enterprise applications use SAML2 to engage a third-party identity provider to grant access to systems that are only authenticated against the enterprise application. These enterprise applications might need to consume OAuth-protected resources through APIs, after validating them against an OAuth2.0 authentication server. However, an enterprise application that already has a working SAML2.0 based Single Sign On infrastructure between itself and the IDP prefers to use the existing trust relationship, even if the OAuth authorization server is entirely different from the IDP. The SAML2 Bearer Assertion Profile for OAuth2.0 helps leverage this existing trust relationship by presenting the SAML2.0 token to the authorization server and exchanging it to an OAuth2.0 access token and then use that OAuth token to get access to APIs.

Ground work Understanding how this process can be implemented

Setup IDP in WSO2 Identity server (Uses IS 5.0.0)

Now need to request SAML token for the user, for that have created a script as follows, make sure the SAML request being signed using the public certificate.

#!/bin/bash

#saml assertion issuer

ISSUER="SAML_ASSERTION_TEST_ISSUER"

#ISSUER="localhost"

#saml2_assertion_subject

SUBJECT="saman123"

#saml2_assertion_recipient

RECIPIENT="https://localhost:9444/oauth2/token/"

#saml2_asseertion_audience_restriction

AUDIENCE="https://localhost:9444/oauth2/token/"

#path to JKS store file

JKS_PATH="/Users/dushan/workspace/poc/apikeym/apim17/wso2is-5.0.0/repository/resources/security/wso2carbon.jks"

java -jar SAML2AssertionCreator/SAML2AssertionCreator.jar $ISSUER $SUBJECT $RECIPIENT $AUDIENCE $JKS_PATH wso2carbon wso2carbon wso2carbon

You can download SAML2AssertionCreator project from here

Exchange SAML token to Access Token

curl -k -d "grant_type=urn:ietf:params:oauth:grant-type:saml2-bearer&assertion=<SAML_ASSERTION obtained from above step >&scope=PRODUCTION" -H "Authorization: Basic <base 64[consumer_key:consumer_secret] of desired API, Content-Type: application/x-www-form-urlencoded" https://localhost:8243/token

Setting Proxy with mod_proxy with Basic Authorization

2015-02-17T06:11:00.000-08:00

Install mod_proxy and setup reverse proxy in Apache Webserver

Follow the given below steps.
Note: In all given below example replace the value of ServerAdmin,ServerName & ServerAlias as per your server information

Step 1: Install the module

sudo apt-get install libapache2-mod-proxy-html

Step 2: Installing the dependency libxml2-dev

apt-get install libxml2-devStep 3: Load the module

a2enmod proxy proxy_http

Step 4: Create the Virtual Host in apache configuration file . If your configuration is located in conf.d you have to do changes in that file. I am giving example with default setting in Apache Webserver in Ubuntu

vi /etc/apache2/sites-enabled/000-default

Step 5: Following configuration allows user to access http service but it requires user to provide credentials, which is stored at /var/www/.htpasswd

<VirtualHost *:80>
ServerName 192.168.56.102
SSLEngine off
ProxyPass /foo/ http://192.168.56.1:8280/
<Proxy *>
Order Allow,Deny
Allow from all
AuthType Basic
AuthName "Authenticated proxy"
AuthUserFile /var/www/.htpasswd
Require valid-user
</Proxy>
</VirtualHost>

Step 6: Accessing https services, which requires to generate key pair of wso2carbon server and store as SSLCertificateFile/SSLCertificateKeyFile

generate key pair from wso2carbon.jks

keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12 -deststoretype PKCS12 -srcalias <jkskeyalias> -deststorepass <password> -destkeypass <password>
Export certificate.

openssl pkcs12 -in keystore.p12 -nokeys -out cert.pem
Export unencrypted private key.

openssl pkcs12 -in keystore.p12 -nodes -nocerts -out key.pem

Optional disabling CN check.

SSLProxyCheckPeerName off
SSLProxyCheckPeerCN off<VirtualHost *:443>
SSLProxyEngine On
SSLCertificateFile /home/dushan/cert.pem
SSLCertificateKeyFile /home/dushan/key.pem

SSLProxyCheckPeerName off
SSLProxyCheckPeerCN off
# CacheDisable *

SSLEngine on
ProxyPass /foo/ https://192.168.56.1:8243/

<Proxy *>
Order Allow,Deny
Allow from all
AuthType Basic
AuthName "Authenticated proxy"
AuthUserFile /var/www/.htpasswd
Require valid-user
</Proxy>

</VirtualHost>

Secure File Transfer with VFS (ESB FTP+SSL certificates)

2015-02-08T17:37:00.004-08:00

Hello, everyone this post I would discuss a new feature that enables us to share files between ESB and FTP server where FTP server establish connection through SSL certificates. will go step by step discussing how you could prepare FTP server to enable SSL and then share files between ESB

Generating KeyPair

openssl genrsa -des3 -out dushan.key 1024
openssl req -new -x509 -days 365 -key dushan.key -out dushan.crt
Import certificate to ESB client-trust store

keytool -import -alias stan -keystore client-truststore.jks -file dushan.crt

Used Filezilla client and server to demonstrate this scenario,

You can configure VFS transport with https://docs.wso2.com/pages/viewpage.action?pageId=26838852
Proxy Configuration looks as below

Please notice the configuration (special notations) 'vfs.ssl.keystore' ,'vfs.ssl.truststore' ,'vfs.ssl.tspassword','vfs.ssl.kspassword'

<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="VFSProxy"
       transports="vfs"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence>
         <property name="OUT_ONLY" value="true"/>
         <property name="transport.vfs.ReplyFileName"
                   expression="fn:concat(fn:substring-after(get-property('MessageID'), 'urn:uuid:'), '.csv')"
                   scope="transport"/>
         <property name="messageType" value="text/plain" scope="axis2"/>
         <property name="ClientApiNonBlocking" scope="axis2" action="remove"/>
         <send>
            <endpoint>
               <address uri="vfs:ftps://dushan:12345@192.168.56.102/test?vfs.ssl.keystore=/Users/dushan/workspace/onlinesupport/ESB/wso2esb-4.8.1/repository/resources/security/wso2carbon.jks&amp;vfs.ssl.truststore=/Users/dushan/workspace/onlinesupport/ESB/wso2esb-4.8.1/repository/resources/security/client-truststore.jks&amp;vfs.ssl.kspassword=wso2carbon&amp;vfs.ssl.tspassword=wso2carbon&amp;vfs.ssl.keypassword=wso2carbon"/>
            </endpoint>
         </send>
         <drop/>
      </inSequence>
   </target>
   <parameter name="transport.PollInterval">10</parameter>
   <parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
   <parameter name="transport.vfs.FileURI">file:///Users/xx/in</parameter>
   <parameter name="transport.vfs.MoveAfterProcess">file:///Users/xx/processed</parameter>
   <parameter name="transport.vfs.MoveAfterFailure">file:///Users/xx/fail</parameter>
   <parameter name="transport.vfs.FileNamePattern">.*.csv</parameter>
   <parameter name="transport.vfs.ContentType">text/plain</parameter>
   <parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
   <description>Custom file reader proxy for CAP mainframe file. This will perform transformation to DP v2 structure and store data into Vertica</description>
</proxy>


Fail to add public certificates  would result errors as follows



... 16 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
 at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
 at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
 at sun.security.validator.Validator.validate(Validator.java:260)
 at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
 at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231)
 at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
 at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1421)
 ... 27 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Transaction ESB + DSS

2014-06-27T03:08:00.003-07:00

This particular synapse configuration demos , when transaction failure scenario when box_carring is enabled.

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="TransactionProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log/>
<log level="custom">
<property name="M2" value="************HITTING Transaction PROXY************"/>
</log>
<header name="Action" value="urn:begin_boxcar"/>
<property name="setCookieHeader"
expression="$trp:Set-Cookie"
scope="default"
type="STRING"/>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body>
<dat:begin_boxcar/>
</soapenv:Body>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<call>
<endpoint>
<address uri="http://localhost:9764/services/Persons_DataService.SOAP11Endpoint/"/>
</endpoint>
</call>
<property name="setCookieHeader"
expression="$trp:Set-Cookie"
scope="default"
type="STRING"/>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body>
<dat:insert_Persons_operation>
<dat:PersonID>1</dat:PersonID>
<dat:LastName>test</dat:LastName>
<dat:FirstName>test22</dat:FirstName>
</dat:insert_Persons_operation>
</soapenv:Body>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="custom">
<property name="JSESSIONID" expression="get-property('setCookieHeader')"/>
</log>
<property name="Cookie"
expression="$trp:Set-Cookie"
scope="transport"
type="STRING"/>
<header name="Action" value="urn:urn:insert_Persons_operation"/>
<call>
<endpoint>
<address uri="http://localhost:9764/services/Persons_DataService.SOAP11Endpoint/"
format="soap11"/>
</endpoint>
</call>
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body>
<dat:insert_Persons_operation>
<dat:PersonID>2</dat:PersonID>
<dat:LastName>mmm</dat:LastName>
<dat:FirstName>mmmmm</dat:FirstName>
</dat:insert_Persons_operation>
</soapenv:Body>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<log level="custom">
<property name="JSESSIONID" expression="get-property('setCookieHeader')"/>
</log>
<property name="Cookie"
expression="$ctx:setCookieHeader"
scope="transport"
type="STRING"/>
<header name="Action" value="urn:urn:insert_Persons_operation"/>
<call>
<endpoint>
<address uri="http://localhost:9764/services/Persons_DataService.SOAP11Endpoint_invalid/"
format="soap11"/>
</endpoint>
</call>
<switch source="$axis2:HTTP_SC">
<case regex="2[0-9][0-9]">
<payloadFactory media-type="xml">
<format>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:dat="http://ws.wso2.org/dataservice">
<soapenv:Header/>
<soapenv:Body>
<dat:end_boxcar/>
</soapenv:Body>
</soapenv:Envelope>
</format>
<args/>
</payloadFactory>
<property name="Cookie"
expression="get-property('setCookieHeader')"
scope="transport"
type="STRING"/>
<header name="Action" value="urn:end_boxcar"/>
<call>
<endpoint>
<address uri="http://localhost:9764/services/Persons_DataService.SOAP11Endpoint/"
format="soap11"/>
</endpoint>
</call>
</case>
<case regex="404">
<property name="ERROR_CODE" value="600404"/>
<property name="ERROR_MESSAGE" value="Not Found"/>
</case>
<case regex="400">
<property name="ERROR_CODE" value="600400"/>
<property name="ERROR_MESSAGE" value="Bad Request"/>
</case>
<case regex="500">
<property name="ERROR_CODE" value="600500"/>
<property name="ERROR_MESSAGE" value="Internal Server Error"/>
</case>
</switch>
<filter source="$axis2:HTTP_SC" regex="^[^2][0-9][0-9]">
<then>
<makefault version="soap11">
<code expression="get-property('ERROR_CODE')"/>
<reason expression="get-property('ERROR_MESSAGE')"/>
<detail/>
</makefault>
</then>
</filter>
<respond/>
</inSequence>
<outSequence>
<drop/>
</outSequence>
</target>
<description/>
</proxy>

Data Service Server

<data description="multiple services per each table" enableBatchRequests="false" enableBoxcarring="true" name="Persons_DataService" serviceNamespace="http://ws.wso2.org/dataservice" serviceStatus="active">
<config id="default">
<property name="carbon_datasource_name">mysql</property>
</config>
<query id="insert_Persons_query" useConfig="default">
<sql>INSERT INTO Persons(PersonID,LastName,FirstName) VALUES(?,?,?)</sql>
<param name="PersonID" ordinal="1" paramType="SCALAR" sqlType="INTEGER" type="IN"/>
<param name="LastName" ordinal="2" paramType="SCALAR" sqlType="STRING" type="IN"/>
<param name="FirstName" ordinal="3" paramType="SCALAR" sqlType="STRING" type="IN"/>
</query>
<query id="select_all_Persons_query" useConfig="default">
<sql>SELECT PersonID, LastName, FirstName FROM Persons</sql>
<result element="PersonsCollection" rowName="Persons">
<element column="PersonID" name="PersonID" xsdType="xs:integer"/>
<element column="LastName" name="LastName" xsdType="xs:string"/>
<element column="FirstName" name="FirstName" xsdType="xs:string"/>
</result>
</query>
<operation name="insert_Persons_operation">
<call-query href="insert_Persons_query">
<with-param name="PersonID" query-param="PersonID"/>
<with-param name="FirstName" query-param="FirstName"/>
<with-param name="LastName" query-param="LastName"/>
</call-query>
</operation>
<operation name="select_all_Persons_operation">
<call-query href="select_all_Persons_query"/>
</operation>
</data>

Logs
====
[2014-07-29 14:30:28,609] DEBUG - wire >> "[\r][\n]"
[2014-07-29 14:30:28,610] INFO - LogMediator JSESSIONID = JSESSIONID=98D714A6825F25D333E87A1389C005DB; Path=/; HttpOnly
[2014-07-29 14:30:28,616] DEBUG - wire << "POST /services/Persons_DataService.SOAP11Endpoint_invalid/ HTTP/1.1[\r][\n]"
[2014-07-29 14:30:28,616] DEBUG - wire << "Cookie: JSESSIONID=98D714A6825F25D333E87A1389C005DB; Path=/; HttpOnly[\r][\n]"
[2014-07-29 14:30:28,616] DEBUG - wire << "Content-Type: text/xml[\r][\n]"
[2014-07-29 14:30:28,616] DEBUG - wire << "SOAPAction: "urn:urn:insert_Persons_operation"[\r][\n]"
[2014-07-29 14:30:28,617] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2014-07-29 14:30:28,617] DEBUG - wire << "Host: localhost:9764[\r][\n]"
[2014-07-29 14:30:28,617] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2014-07-29 14:30:28,617] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2014-07-29 14:30:28,617] DEBUG - wire << "[\r][\n]"
[2014-07-29 14:30:28,618] DEBUG - wire << "18d[\r][\n]"
[2014-07-29 14:30:28,618] DEBUG - wire << "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dat="http://ws.wso2.org/dataservice"><soapenv:Header></soapenv:Header><soapenv:Body><dat:insert_Persons_operation><dat:PersonID>2</dat:PersonID><dat:LastName>mmm</dat:LastName><dat:FirstName>mmmmm</dat:FirstName></dat:insert_Persons_operation></soapenv:Body></soapenv:Envelope>[\r][\n]"
[2014-07-29 14:30:28,618] DEBUG - wire << "0[\r][\n]"
[2014-07-29 14:30:28,618] DEBUG - wire << "[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "HTTP/1.1 500 Internal Server Error[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "Date: Tue, 29 Jul 2014 18:30:28 GMT[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "Connection: close[\r][\n]"
[2014-07-29 14:30:28,624] DEBUG - wire >> "Server: WSO2 Carbon Server[\r][\n]"
[2014-07-29 14:30:28,625] DEBUG - wire >> "[\r][\n]"
[2014-07-29 14:30:28,625] DEBUG - wire >> "1d5[\r][\n]"
[2014-07-29 14:30:28,625] DEBUG - wire >> "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault xmlns:axis2ns6="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>axis2ns6:Client</faultcode><faultstring>The service cannot be found for the endpoint reference (EPR) http://localhost:9764/services/Persons_DataService.SOAP11Endpoint_invalid/</faultstring><detail></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>[\r][\n]"
[2014-07-29 14:30:28,626] DEBUG - wire >> "0[\r][\n]"
[2014-07-29 14:30:28,626] DEBUG - wire >> "[\r][\n]"
[2014-07-29 14:30:28,630] DEBUG - wire << "HTTP/1.1 500 Internal Server Error[\r][\n]"
[2014-07-29 14:30:28,631] DEBUG - wire << "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[2014-07-29 14:30:28,631] DEBUG - wire << "Date: Tue, 29 Jul 2014 18:30:28 GMT[\r][\n]"
[2014-07-29 14:30:28,631] DEBUG - wire << "Server: WSO2-PassThrough-HTTP[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "165[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode xmlns:axis2ns44="http://schemas.xmlsoap.org/soap/envelope/">axis2ns44:600500</faultcode><faultstring>Internal Server Error</faultstring><detail></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>[\r][\n]"
[2014-07-29 14:30:28,632] DEBUG - wire << "0[\r][\n]"
[2014-07-29 14:30:28,633] DEBUG - wire << "[\r][\n]"

TCP Transport in Proxy WSO2 ESB

2014-04-10T09:18:00.001-07:00

Its simple you need do following steps

First make sure you have enabled transport reciver for tcp in axis2.xml (repository/conf/axis2/axis2.xml)

<transportReceiver name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportListener" />
<transportSender name="tcp" class="org.apache.axis2.transport.tcp.TCPTransportSender"/>

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="TCPProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="full"/>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<parameter name="transport.tcp.port">6789</parameter>
<parameter name="transport.tcp.contentType">application/xml</parameter>
<description/>
</proxy>

import java.io.*;
import java.net.*;

class TCPClient {
String host = "localhost";
int port = 6789;
Socket socket = null;

public static void main(String args[]) throws Exception {
String name = "Amani";
TCPClient client = new TCPClient();
// String message =
// "<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">\n" +
// "<soapenv:Header/>\n" +
// "<soapenv:Body>\n" +
// " <p:greet xmlns:p=\"http://greet.service.amani.org\">\n" +
// " <in>" +
// name +
// "</in>\n" +
// " </p:greet>\n" +
// "</soapenv:Body>\n" + "</soapenv:Envelope>";
client.SendToServer("<test></test>");
client.close();
}

TCPClient(String _host, int _port) throws Exception {
host = _host;
port = _port;
socket = new Socket(host, port);
}

TCPClient() throws Exception {
socket = new Socket(host, port);
}

void SendToServer(String msg) throws Exception {
// create output stream attached to socket
PrintWriter outToServer = new PrintWriter(new OutputStreamWriter(socket.getOutputStream()));
// send msg to server
outToServer.print(msg + '\n');
outToServer.flush();
}

String RecieveFromServer() throws Exception {
// create input stream attached to socket
BufferedReader inFromServer =
new BufferedReader(
new InputStreamReader(
socket.getInputStream()));
// read line from server
String res = inFromServer.readLine(); // if connection closes on server
// end, this throws
// java.net.SocketException
return res;
}

void close() throws IOException {
socket.close();
}
}

STILL WSO2 ESB THE FASTEST ON EARTH

2014-02-18T09:54:00.002-08:00

WSO2 ESB team released the latest benchmark ESB Performance Round 7.5 , the result tests are based on the previous serious of performance test carried by different vendors.The main idea of this article is to provide the facts that WSO2 ESB still holding the position as the fastest message mediation engine with with minimum latency.

The test cases were executed by categorizing the sections, such as Passthough Invocation, Content Base Routing (CBR),Content Header Base Routing (CHBR), and Security scenarios.

The test cases were designed to measure the throughput (TPS) under different concurrences with different size of messages and to get more visualization aspect, we did a summery graph and out of different vendors such as Ultra ESB,Teland ESB, It was clearly visualize that WSO2 outcomes others by considerable margin when the average calculated.

And also when considering the individual scenarios; WSO2 ESB performed well without seen any exception or any payload corruptions and to verify this further more; WSO2 team run corruption checker and also used Jmeter response assertion to make sure there won't be any corruption under different high concurrences.

Nevertheless Surprisingly, we did observe improvements of Mule ESB, which we have noted that it performs well over Ultra ESB for some use cases such as CBR, CHBR

Anyway, the main fact that this article trying to bid, the claims made by some vendors by arguing the default pack which does the payload corruption,but yes we did identified such claim but, never with the default setting , it was with the StreamXpath where this was due to a very negligible error which we have fixed in no time.

Why we did ESB Performance round 7.5 ?

The main reason why WSO2 did this because as professional,we need to make sure that WSO2 ESB is the strongest and the well performed ESB available in the market and we need to make sure that we did answer the questions raised by ESB PERFORMANCE ROUND 7.

When considering the OPEN source nature I think WSO2 ESB is the only ESB that has much features that allow different users to

try them freely and the source is open and they could see anything, and WSO2 welcomes the open community ideas, and again WSO2 ESB do not have any sort of hidden code which not sharable or available under different license.

Finally, I know this would hurt few guys/organizations because they put such effort by spending days and nights to QA other vendors products and written article by highlighting issues/errors which they found as disaster, I Know we will see a Performance Round 8, sooner rather than later because the guys who claims to be the champions now are in at 3rd place so they need to bring their act to gather and need response faster, I think they should now need to plan different execution scenarios for the next round such as JSON, JSON Path evaluation, and we know RESTful invocations are now becoming the huge topic and people waiting to see ESB's performance in JSON related usecases.But the bottom-line is still WSO2 ESB will hold the leading position.. bet my word...! Enjoy...

The WSO2 Enterprise Service Bus (ESB) 4.8.1 Released!

2014-02-04T03:11:00.002-08:00

WSO2 ESB team is pleased to announce the release of version 4.8.1 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.8.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.com/products/enterprise-service-bus/ 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
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)

Enhancements in WSO2 ESB 4.8.1

HL7 Message Store Implementation with Console for message audit and replay
Thread Pooled HL7 Server Endpoints
Improvements for working with Invalid HL7 Messages
Enhancing FAST XSLT Mediator.
cApp deployment enhacements and stabilizing class mediator hot deployment.

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) and optimization switching (MTOM/SwA).
API facilitating building REST APIs
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, 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
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.8.1 are recorded at following locations:

Fixed ESB specific issues

Known Issues

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

WSO2 ESB 4.8.1 component issues

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : dev@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 on http://stackoverflow.com.

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 --

Invoking Secure Service (UT enabled) Via Non Secure Client -Part 2

2013-11-21T01:13:00.001-08:00

Enabling policy

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="NonSecureProxyPolicy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="full">
<property name="INNNNN" value="***********INNNN sequence proxy2***********"/>
</log>
<send>
<endpoint>
<address uri="https://localhost:8243/services/SecureService">
<enableSec policy="conf:/security-policy/UT-Policy1"/>
</address>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<description/>
</proxy>

Rampart policy

<wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UTOverTransport">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Lax/>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
</wsp:Policy>
</sp:TransportBinding>
<sp:SignedSupportingTokens xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:UsernameToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"/>
</wsp:Policy>
</sp:SignedSupportingTokens>
<rampart:RampartConfig xmlns:rampart="http://ws.apache.org/rampart/policy">
<rampart:user>dushan</rampart:user>
<rampart:timestampPrecisionInMilliseconds>true</rampart:timestampPrecisionInMilliseconds>
<rampart:timestampTTL>300</rampart:timestampTTL>
<rampart:timestampMaxSkew>300</rampart:timestampMaxSkew>
<rampart:timestampStrict>false</rampart:timestampStrict> <rampart:passwordCallbackClass>org.wso2.samples.pwcb.PWCBHandler</rampart:passwordCallbackClass>
<rampart:nonceLifeTime>300</rampart:nonceLifeTime>
</rampart:RampartConfig>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>

Invoking Secure Service (UT enabled) Via Non Secure Client -Part 1

2013-11-21T00:42:00.002-08:00

When client would require to invoke Secure Services via Non secure services, one possible solution is to enable encrypt the basic headers and them to the Authorization header in transport scope then to invoke the given service

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="NonSecureProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<log level="full">
<property name="INNNNN" value="***********INNNN sequence proxy2***********"/>
</log>
<property name="Authorization"
expression="fn:concat('Basic ', base64Encode('dushan:dushan'))"
scope="transport"/>
<send>
<endpoint>
<address uri="https://localhost:8243/services/SecureService/getQuote"
format="pox"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<description/>
</proxy>

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="SecureService"
transports="https"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<send>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<enableSec/>
<policy key="conf:/repository/axis2/service-groups/SecureService/services/SecureService/policies/UTOverTransport"/>
<description/>
</proxy>

[2013-11-21 14:12:30,620] DEBUG - wire >> "[\r][\n]"
[2013-11-21 14:12:30,636] DEBUG - wire << "POST /services/SimpleStockQuoteService/getQuote HTTP/1.1[\r][\n]"
[2013-11-21 14:12:30,637] DEBUG - wire << "Authorization: Basic ZHVzaGFuOmR1c2hhbg==[\r][\n]"
[2013-11-21 14:12:30,637] DEBUG - wire << "Accept-Encoding: gzip,deflate[\r][\n]"
[2013-11-21 14:12:30,638] DEBUG - wire << "Content-Type: application/xml[\r][\n]"
[2013-11-21 14:12:30,638] DEBUG - wire << "SOAPAction: urn:getQuote[\r][\n]"
[2013-11-21 14:12:30,638] DEBUG - wire << "Transfer-Encoding: chunked[\r][\n]"
[2013-11-21 14:12:30,638] DEBUG - wire << "Host: localhost:9000[\r][\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << "[\r][\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << "fe[\r][\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << "<ser:getQuote xmlns:ser="http://services.samples">[\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << " [\n]"
[2013-11-21 14:12:30,639] DEBUG - wire << " <ser:request>[\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << " [\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << " <xsd:symbol xmlns:xsd="http://services.samples/xsd">11</xsd:symbol>[\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << " </ser:request>[\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << " </ser:getQuote>[\r][\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << "0[\r][\n]"
[2013-11-21 14:12:30,640] DEBUG - wire << "[\r][\n]"
[2013-11-21 14:12:30,644] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2013-11-21 14:12:30,644] DEBUG - wire >> "Content-Type: application/xml; charset=UTF-8[\r][\n]"
[2013-11-21 14:12:30,645] DEBUG - wire >> "Date: Thu, 21 Nov 2013 08:42:30 GMT[\r][\n]"
[2013-11-21 14:12:30,645] DEBUG - wire >> "Transfer-Encoding: chunked[\r][\n]"
[2013-11-21 14:12:30,645] DEBUG - wire >> "Connection: Keep-Alive[\r][\n]"
[2013-11-21 14:12:30,645] DEBUG - wire >> "[\r][\n]"
[2013-11-21 14:12:30,647] DEBUG - wire >> "368[\r][\n]"
[2013-11-21 14:12:30,647] DEBUG - wire >> "<ns:getQuoteResponse xmlns:ns="http://services.samples"><ns:return xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ax21:GetQuoteResponse"><ax21:change>4.423747490453758</ax21:change><ax21:earnings>13.080465575691782</ax21:earnings><ax21:high>183.72455511877618</ax21:high><ax21:last>177.25933516401494</ax21:last><ax21:lastTradeTimestamp>Thu Nov 21 14:12:30 IST 2013</ax21:lastTradeTimestamp><ax21:low>-176.6775010130566</ax21:low><ax21:marketCap>1797692.482250683</ax21:marketCap><ax21:name>11 Company</ax21:name><ax21:open>183.25648908841202</ax21:open><ax21:peRatio>-17.898897366819455</ax21:peRatio><ax21:percentageChange>-2.6156190500725063</ax21:percentageChange><ax21:prevClose>-169.12812629695176</ax21:prevClose><ax21:symbol>11</ax21:symbol><ax21:volume>5447</ax21:volume></ns:return></ns:getQuoteResponse>[\r][\n]"
[2013-11-21 14:12:30,648] DEBUG - wire >> "0[\r][\n]"
[2013-11-21 14:12:30,648] DEBUG - wire >> "[\r][\n]"
[2013-11-21 14:12:30,655] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]"
[2013-11-21 14:12:30,655] DEBUG - wire << "Content-Type: application/xml[\r][\n]"
[2013-11-21 14:12:30,656] DEBUG - wire << "Date: Thu, 21 Nov 2013 08:42:30 GMT[\r][\n]"
[2013-11-21 14:12:30,656] DEBUG - wire << "Server: WSO2-PassThrough-HTTP[\r][\n]"
[2013

Callout Meditor to Invoke REST Services

2013-11-20T04:16:00.002-08:00

Following configuration allows you to invoke RESTful services via CalloutMeditator

P.N you need to change axis2_client.xml Required to add JSON message formatter in ESB_470_HOME/samples/axis2Client/client_repo/conf/axis2.xml

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
name="CalloutProxy"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<property name="enableREST"
value="true"
scope="axis2-client"
type="BOOLEAN"/>
<property name="messageType"
value="application/json"
scope="axis2-client"
type="STRING"/>
<property name="contentType"
value="application/json"
scope="axis2-client"
type="STRING"/>
<callout serviceURL="http://localhost:9001/services/SimpleStockQuoteService"
action="urn:getQuote"
initAxis2ClientOptions="false">
<source xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
<target xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
</callout>
<property name="RESPONSE" value="true"/>
<header name="To" action="remove"/>
<send/>
<drop/>
</inSequence>
</target>
<description/>
</proxy>

Wire logs

log4j.logger.httpclient.wire.header=DEBUG
log4j.logger.httpclient.wire.content=DEBUG

logs seen in console

[2013-11-20 17:38:18,840] INFO - CarbonUIServiceComponent Mgt Console URL : https://10.100.1.122:9443/carbon/
[2013-11-20 17:39:39,459] DEBUG - header >> "POST /services/SimpleStockQuoteService HTTP/1.1[\r][\n]"
[2013-11-20 17:39:39,468] DEBUG - header >> "Content-Type: application/json; charset=UTF-8[\r][\n]"
[2013-11-20 17:39:39,469] DEBUG - header >> "Accept-Encoding: gzip,deflate[\r][\n]"
[2013-11-20 17:39:39,469] DEBUG - header >> "User-Agent: Axis2[\r][\n]"
[2013-11-20 17:39:39,469] DEBUG - header >> "Host: localhost:9001[\r][\n]"
[2013-11-20 17:39:39,469] DEBUG - header >> "Transfer-Encoding: chunked[\r][\n]"
[2013-11-20 17:39:39,469] DEBUG - header >> "[\r][\n]"
[2013-11-20 17:39:39,480] DEBUG - content >> "27[\r][\n]"
[2013-11-20 17:39:39,480] DEBUG - content >> "{"getQuote":{"request":{"symbol":"?"}}}"
[2013-11-20 17:39:39,480] DEBUG - content >> "[\r][\n]"
[2013-11-20 17:39:39,480] DEBUG - content >> "0"
[2013-11-20 17:39:39,480] DEBUG - content >> "[\r][\n]"
[2013-11-20 17:39:39,480] DEBUG - content >> "[\r][\n]"

Upcoming ESB features (Call Meditor and Connectors)

2013-09-26T10:38:00.004-07:00

ESB 4.8.0 about to be released soon, in my previous blog I discussed how you can configure, iterate and aggregate ,there have been numerous changers accommodated in 4.8.0 to simplify the configuration, some of the enhancements we have done listed below.

Call Mediator (Non Blocking callout mediator) probably but almost retiring CalloutMediator (which is blocking)
Loopback Mediator
Response Mediator

additionally more information to be followed related to the CLOUD CONNECTOR usecases within next few weeks ......

<proxy xmlns="http://ws.apache.org/ns/synapse"
name="CallIterator"
transports="https,http"
statistics="disable"
trace="disable"
startOnLoad="true">
<target>
<inSequence>
<iterate xmlns:m1="http://services.samples"
xmlns:m2="http://services.samples/xsd"
id="callItr"
expression="//m1:getQuotes/m1:getQuote">
<target>
<sequence>
<call>
<endpoint>
<address uri="http://localhost:9001/services/SimpleStockQuoteService"/>
</endpoint>
</call>
</sequence>
</target>
</iterate>
<log level="full">
<property name="MESSAGE" value="##1"/>
</log>
<property name="ECNCLOSING_ELEMENT" scope="default">
<wrapper xmlns=""/>
</property>
<aggregate id="callItr">
<completeCondition>
<messageCount min="-1" max="-1"/>
</completeCondition>
<onComplete xmlns:m1="http://services.samples"
expression="//m1:getQuoteResponse"
enclosingElementProperty="ECNCLOSING_ELEMENT">
<log level="full">
<property name="MESSAGE" value="##2"/>
</log>
</onComplete>
</aggregate>
<loopback/>
</inSequence>
<outSequence>
<respond/>
</outSequence>
</target>
<description/>
</proxy>

response..

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<wrapper>
<ns:getQuoteResponse xmlns:ns="http://services.samples">
<ns:return xsi:type="ax21:GetQuoteResponse" xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ax21:change>-2.282072032481502</ax21:change>
<ax21:earnings>-8.184245817709384</ax21:earnings>
<ax21:high>161.1255146837517</ax21:high>
<ax21:last>153.9460060122943</ax21:last>
<ax21:lastTradeTimestamp>Thu Sep 26 23:05:24 IST 2013</ax21:lastTradeTimestamp>
<ax21:low>-153.68705428915268</ax21:low>
<ax21:marketCap>3698159.0880708937</ax21:marketCap>
<ax21:name>DLL Company</ax21:name>
<ax21:open>-151.72501736767938</ax21:open>
<ax21:peRatio>25.8716132214498</ax21:peRatio>
<ax21:percentageChange>1.562593376583845</ax21:percentageChange>
<ax21:prevClose>-146.04388234836802</ax21:prevClose>
<ax21:symbol>DLL</ax21:symbol>
<ax21:volume>16230</ax21:volume>
</ns:return>
</ns:getQuoteResponse>
<ns:getQuoteResponse xmlns:ns="http://services.samples">
<ns:return xsi:type="ax21:GetQuoteResponse" xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ax21:change>-2.50201581759645</ax21:change>
<ax21:earnings>13.910655333381875</ax21:earnings>
<ax21:high>-173.9913159476355</ax21:high>
<ax21:last>178.2282964042608</ax21:last>
<ax21:lastTradeTimestamp>Thu Sep 26 23:05:24 IST 2013</ax21:lastTradeTimestamp>
<ax21:low>184.07373157820325</ax21:low>
<ax21:marketCap>-8690349.18328286</ax21:marketCap>
<ax21:name>SAMSUG Company</ax21:name>
<ax21:open>187.00563796447824</ax21:open>
<ax21:peRatio>24.27282100627226</ax21:peRatio>
<ax21:percentageChange>1.5129014962405416</ax21:percentageChange>
<ax21:prevClose>-165.37863329594103</ax21:prevClose>
<ax21:symbol>SAMSUG</ax21:symbol>
<ax21:volume>17238</ax21:volume>
</ns:return>
</ns:getQuoteResponse>
<ns:getQuoteResponse xmlns:ns="http://services.samples">
<ns:return xsi:type="ax21:GetQuoteResponse" xmlns:ax21="http://services.samples/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ax21:change>3.776274828469344</ax21:change>
<ax21:earnings>12.080383538265115</ax21:earnings>
<ax21:high>-169.48473541292884</ax21:high>
<ax21:last>173.1940035266614</ax21:last>
<ax21:lastTradeTimestamp>Thu Sep 26 23:05:24 IST 2013</ax21:lastTradeTimestamp>
<ax21:low>179.34173748130962</ax21:low>
<ax21:marketCap>3.542581699105626E7</ax21:marketCap>
<ax21:name>IBM Company</ax21:name>
<ax21:open>-170.07540506338606</ax21:open>
<ax21:peRatio>-19.16117019602173</ax21:peRatio>
<ax21:percentageChange>2.001801348105515</ax21:percentageChange>
<ax21:prevClose>188.64383481623557</ax21:prevClose>
<ax21:symbol>IBM</ax21:symbol>
<ax21:volume>8286</ax21:volume>
</ns:return>
</ns:getQuoteResponse>
</wrapper>
</soapenv:Body>
</soapenv:Envelope>

The WSO2 Enterprise Service Bus (ESB) 4.7.0 Released!

2013-07-03T19:44:00.001-07:00

WSO2 ESB team is pleased to announce the release of version 4.7.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.7.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.com/products/enterprise-service-bus/ 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
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)

Brand New in This Release

Comprehensive REST integration support with HTTP Endpoints
JSON support for Payload Factory Mediator
SSL Tunneling Support
SSL Profiles for inbound and outbound scenarios
Inbound Connection Throttling support for Pass-Thru and NHTTP transports
CRL/OCSP Certificate Revocation Verification

Enhancements in WSO2 ESB 4.7.0

Enhanced Message Stores and Processors for Guaranteed Delivery and Rate Matching Scenarios
High Performance Multitenant REST APIs support with Pass-Thru Transport
Stabilizing Registry Based Deployment Synchronizer
Invoking Sequences and Proxy Service from Scheduled Tasks
HL7 Enhancements to support Application-Acknowledgement and Auto-Acknowledgement scenarios
Transport Header manipulation in Header Mediator
Enhancement on Content Negotiation in RESTful integration(ie: POX with text/xml)
JMS MapMessage compatibility for JMS Transport