Aggregator

From:Afkham Azeez (aze...@wso2.com)List:org.wso2.carbon-dev

Were the review recommendations implemented ?

---- Sent from my phone On Aug 31, 2011 10:59 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:53 AM, Afkham Azeez <aze...@wso2.com> wrote:

Where are the crucible notes? Better have an architecture review as well.

+1

Crucible link https://wso2.org/crucible/cru/COMPONENT-54

---- Sent from my phone On Aug 31, 2011 10:28 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:11 AM, Afkham Azeez <aze...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 9:51 AM, Amila Maha Arachchi <ami...@wso2.com wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

Billing code needs lot of improvements. I am on support until next Tuesday. I'll try my best to do the improvements after that and present. If not I would like to request for one more week to do the refactoring.

How come the billing code that has been in development since last December suddenly need a "lot" of improvement? How did you suddenly come to realize this? What are these improvements? I'd suggest that you just present the code as it is for the review. If you remember, this review was

scheduled

1-2

weeks before the StratosLive launch and got delayed because of the release. I believe there was ample time to rectify the code.

Not suddenly. It was in the card for sometime. Although I started

working

on

it since February, my initial target was to get it working. I had to know the code.

This review was done on the scheduled date. You missed it because you were sick IIRC.

My concern is, the code needs design level changes. But I couldn't do them yet. Anyway, I'll present it as it is.

AmilaM.

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Afkham Azeez (aze...@wso2.com)List:org.wso2.carbon-dev

Were the review recommendations implemented ?

---- Sent from my phone On Aug 31, 2011 10:59 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:53 AM, Afkham Azeez <aze...@wso2.com> wrote:

Where are the crucible notes? Better have an architecture review as well.

+1

Crucible link https://wso2.org/crucible/cru/COMPONENT-54

---- Sent from my phone On Aug 31, 2011 10:28 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:11 AM, Afkham Azeez <aze...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 9:51 AM, Amila Maha Arachchi <ami...@wso2.com wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

Billing code needs lot of improvements. I am on support until next Tuesday. I'll try my best to do the improvements after that and present. If not I would like to request for one more week to do the refactoring.

How come the billing code that has been in development since last December suddenly need a "lot" of improvement? How did you suddenly come to realize this? What are these improvements? I'd suggest that you just present the code as it is for the review. If you remember, this review was

scheduled

1-2

weeks before the StratosLive launch and got delayed because of the release. I believe there was ample time to rectify the code.

Not suddenly. It was in the card for sometime. Although I started

working

on

it since February, my initial target was to get it working. I had to know the code.

This review was done on the scheduled date. You missed it because you were sick IIRC.

My concern is, the code needs design level changes. But I couldn't do them yet. Anyway, I'll present it as it is.

AmilaM.

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Afkham Azeez (aze...@wso2.com)List:org.wso2.carbon-dev

Were the review recommendations implemented ?

---- Sent from my phone On Aug 31, 2011 10:59 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:53 AM, Afkham Azeez <aze...@wso2.com> wrote:

Where are the crucible notes? Better have an architecture review as well.

+1

Crucible link https://wso2.org/crucible/cru/COMPONENT-54

---- Sent from my phone On Aug 31, 2011 10:28 AM, "Amila Maha Arachchi" <ami...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 10:11 AM, Afkham Azeez <aze...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 9:51 AM, Amila Maha Arachchi <ami...@wso2.com wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

Billing code needs lot of improvements. I am on support until next Tuesday. I'll try my best to do the improvements after that and present. If not I would like to request for one more week to do the refactoring.

How come the billing code that has been in development since last December suddenly need a "lot" of improvement? How did you suddenly come to realize this? What are these improvements? I'd suggest that you just present the code as it is for the review. If you remember, this review was

scheduled

1-2

weeks before the StratosLive launch and got delayed because of the release. I believe there was ample time to rectify the code.

Not suddenly. It was in the card for sometime. Although I started

working

on

it since February, my initial target was to get it working. I had to know the code.

This review was done on the scheduled date. You missed it because you were sick IIRC.

My concern is, the code needs design level changes. But I couldn't do them yet. Anyway, I'll present it as it is.

AmilaM.

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<

http://twitter.com/afkham_azeez>

* linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Amila Maha Arachchi (ami...@wso2.com)List:org.wso2.carbon-dev

On Wed, Aug 31, 2011 at 10:11 AM, Afkham Azeez <aze...@wso2.com> wrote:

On Wed, Aug 31, 2011 at 9:51 AM, Amila Maha Arachchi <ami...@wso2.com>wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

Billing code needs lot of improvements. I am on support until next Tuesday. I'll try my best to do the improvements after that and present. If not I would like to request for one more week to do the refactoring.

How come the billing code that has been in development since last December suddenly need a "lot" of improvement? How did you suddenly come to realize this? What are these improvements? I'd suggest that you just present the code as it is for the review. If you remember, this review was scheduled 1-2 weeks before the StratosLive launch and got delayed because of the release. I believe there was ample time to rectify the code.

Not suddenly. It was in the card for sometime. Although I started working on it since February, my initial target was to get it working. I had to know the code.

This review was done on the scheduled date. You missed it because you were sick IIRC.

My concern is, the code needs design level changes. But I couldn't do them yet. Anyway, I'll present it as it is.

AmilaM.

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Afkham Azeez (aze...@wso2.com)List:org.wso2.carbon-dev

On Wed, Aug 31, 2011 at 9:51 AM, Amila Maha Arachchi <ami...@wso2.com>wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

Billing code needs lot of improvements. I am on support until next Tuesday. I'll try my best to do the improvements after that and present. If not I would like to request for one more week to do the refactoring.

How come the billing code that has been in development since last December suddenly need a "lot" of improvement? How did you suddenly come to realize this? What are these improvements? I'd suggest that you just present the code as it is for the review. If you remember, this review was scheduled 1-2 weeks before the StratosLive launch and got delayed because of the release. I believe there was ample time to rectify the code.

AmilaM.

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Asela Pathberiya (ase...@wso2.com)List:org.wso2.carbon-dev

On Tue, Aug 30, 2011 at 1:26 AM, James McLaughlin < ji...@stonewatercontrols.com> wrote:

Hello, We are using the User Management facilities in the ESB (3.0.1) to provide authentication and user administration for a remote client application. Adding and Authenticating users works no problem, and we are able to add claims when we add a User, but we are having some issues managing claims. How do we go about Adding, Updating and Deleting claims for a particular User after that User has been created? There doesn't seem to be an API supporting these operations in the ClaimManagementService.

There is a API for this, called "UserProfileMgtService" in Identity user profiles feature. This feature is not shipped with ESB by default and You need to install it using feature manager which can be found in ESB UI. Here you need to point to the p2 repository [1] and install 3.0.1 Identity User Profiles Feature.

[1] http://dist.wso2.org/p2/carbon/releases/3.0.0/

Thanks in advance,

Jim

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Janaka Ranabahu (jan...@wso2.com)List:org.wso2.carbon-dev

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Group B Gadget Repository - Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Noted

Thanks, Janaka

Group E Metering - AmilaM

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- Janaka Ranabahu Software Engineer WSO2 Inc.

Mobile +94 718370861 Email : jan...@wso2.com Blog : janakaranabahu.blogspot.com

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Nuwan Bandara (nuw...@wso2.com)List:org.wso2.carbon-dev

Hi

On Tue, Aug 30, 2011 at 9:59 PM, Tharindu Mathew <thar...@wso2.com> wrote:

On Tue, Aug 30, 2011 at 9:02 AM, Afkham Azeez <aze...@wso2.com> wrote:

Please organize the following reviews.

Group A BAM Event Receiver - Tharindu

Noted.

Group B Gadget Repository - Nuwan

Recent modifications to the gadget repository is done by RangaS, I prefer Ranga doing the code review rather than myself. however Ranga is not in Group B.

Regards, /Nuwan

Group C Authenticator Framework - Thilina

Group D Registry Indexing - Janaka

Group E Metering - AmilaM

-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **aze...@wso2.com* <aze...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*

-- Regards,

Tharindu

-- *Thanks & Regards,

Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware

http://nuwan.bandara.co * <http://www.nuwanbando.com/>

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Nuwan Bandara (nuw...@wso2.com)List:org.wso2.carbon-dev

Hi Dimuthu,

You can add, <component> <framework-configuration> <bypass> <authentication> <link>/index.jsp</link> </authentication> </bypass> </framework-configuration> ...... </component>

inside component.xml; we have done that in dashboard.ui pages.

Regards, /Nuwan

On Tue, Aug 30, 2011 at 7:22 PM, Dimuthu Leelarathne <dimu...@wso2.com>wrote:

Hi,

Does anyone know how to skip authentication for a set of jsps that doesn't have a menu item (other than modifying CarbonSecuredHttpContext) ?

The component.xml has <skip-authentication></skip-authentication> inside menu.

thanks, dimuthul

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

-- *Thanks & Regards,

Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware

http://nuwan.bandara.co * <http://www.nuwanbando.com/>

_______________________________________________ Carbon-dev mailing list Carb...@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

From:Amila Suriarachchi (ami...@wso2.com)List:org.wso2.architecture

On Wed, Aug 31, 2011 at 11:34 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote:

On Wed, Aug 31, 2011 at 10:34 AM, Amila Suriarachchi <ami...@wso2.com>wrote:

On Tue, Aug 30, 2011 at 2:59 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote:

Hi Folks,

Today we had a discussion on the WSO2 SAP adapter. We briefly went through what we already have and discussed some new ideas.

Participants: Sanjiva, Kasun, Hiranya

Points discussed:

1. Current BAPI transport uses a custom XML representation of BAPI. This means the user has to do a lot of XSLT/XPath stuff even to invoke a simple BAPI. 2. Look into using BSF/JavaScript to directly invoke the JCo API from the mediation level. 3. Get rid of the BAPI/IDoc endpoint model which uses an external properties file. Instead, introduce a new endpoint format where all the relevant SAP parameters can be defined within the endpoint itself. 4. Look into developing a tooling layer in CStudio using JCo. This should be able to connect to a SAP system, browse available BAPIs and generate the necessary transformations (XSLT/Smooks) - Also look for any existing Eclipse tools for SAP 5. BAPI listener can be used to replace a legacy SAP system without breaking existing SAP clients - So we need this 6. Move the source to public SVN - Person who builds the source should provide the JCo library - Check whether we can configure Maven to build the component only when the JCo library is present 7. Write some articles around the SAP adapter

Isn't is possible to implement BAPI using a custom deployer like in DataServices.

So that we can use a custom deployment descriptor file (like .dbs) to specify parameters and it is exposed as a proper web service using a WSDL. The other advantage of this is that it can be used in a BPEL process as well.

We have that too.

ok. Then why need to have two implementations? ESB can invoke this either using send mediator or call back mediator.

thanks, Amila.

Thanks, Hiranya

thanks, Amila.

Please add if I've missed anything.

Thanks

-- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

-- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Waruna and I’ll be doing a post-conference tutorial session on “Advanced Concepts in WS-BPEL” in WSO2 Con 2011.Summary of the session is as follows.BPEL is the de-facto standard for modeling executable Web services orchestrations. It is an XML-based language used for the definition and execution of business, as well as scientific work flows using Web services. WSO2 Business Process Server (WSO2 BPS) and Apache Orchestration Director Engine(ODE) are two WS-BPEL compliant business process executable work-flow engines, which support composition of Web services by orchestrating service interactions.In this tutorial, Warauna and I will elaborate on some advanced concepts in WS-BPEL 2.0 and extensibility in WSO2 BPS likefault handling compensation handling event processing    selective event processing multiple event processing concurrent event processing message correlation parallel processing Introduction to ODE extensions Future improvements with extensions

From WSO2 BPS 2.1.0 onwards, we have introduced a new sample guide and documentation which explain some of the basic concepts involved in WS-BPEL 2.0. You can find the documentation over here .Also we have introduced few samples for complex BPEL scenarios likeCompensation handlers - SampleCompensationHandlersThis samples demonstrates a flight reservation process with the functionality of with a basic compensation handler will work. Also it involves the which are required in compensation handling. Event-handlers - SampleEventHandlers This sample has an event-handler implementation is capable verifying the functionality and reliability of construct. Asynchronous processes SampleAsynchronousProcessThis sample contains two processes. One acts as a client (Async-Client.zip) for the server (Async-Server.zip). Message correlation is used to maintain the asynchronous interaction between client and server.    We will add the documentation to explain those scenarios as well. You can find those other samples over here. Some of the already available guides on samples areIf ForEach While Repeat until Flow and Links Pick Synchronous and Asynchronous Service Invocations Fault Handling Split XslTransform

I will be presenting this year as well at WSO2Con about the WSO2 Stratos Cloud Middleware Platform as well as WSO2 StratosLive Platform-as-a-Service.Here is the abstract of my talk."More enterprises are recognizing the opportunity to extend the reach and cost-efficiency of their applications by delivering them as software-as-a-service (SaaS). However, the approach to deploying in the cloud and the choice of either cloud middleware software or a platform-as-a-service (PaaS) can significantly affect the success of a SaaS implementation.WSO2 Stratos is a complete enterprise-ready cloud middleware platform designed to extend SOAs to the cloud, and it is the software that powers the WSO2 StratosLive PaaS. By providing WSO2 Carbon products as services over public, private, and hybrid cloud infrastructure, WSO2 Stratos offers an ideal platform for SaaS developers to create, manage and run enterprise-class applications and services with all the inherent benefits of a true cloud-native environment.In this session, we will be looking at the WSO2 Stratos cloud middleware platform and the benefits it offers in developing, testing, deploying and managing cloud-native applications."

Did you messed up after new Ubuntu installation. Its really annoyed(with new side menu bar). i was able to fix this and get back my lovely ubntu UI. Here are the steps.01. Type settings on search window(from menu search)02. Go to login screen and click on itYou will see following window       Then unlock it by giving your password. Then select Ubuntu classic.yes you have done it. now you have to logout and re login. Thats it :)

Throttling is the key to making multitenancy a reality in cloud computing. Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. Many cloud computing offerings are multi-instance, and not multitenant, as they lack the core platform capabilities to support true multitenancy. However, to realize pay-as-you-go model of cloud computing, you need throttling as a key ingredient of the cloud platform. This article explains, what, why & how of throttling in a cloud computing environment. Throttling is about controlling the usage of Network bandwidth Data storage CPU usage I/O operations Throttling can be done to keep track of current usage of cloud computing subscribers – aka tenants, help in billing them and also help with determining to scale up or down the resources based on the usage of those by tenants.   Technorati Tags: Cloud Computing

Latest, wiki based, WSO2 Enterprise Service Bus Documentation is now available online. The purpose of this documentation is to provide you with complete procedures for installing, configuring and implementing solutions with WSO2 ESB. The documentation topics are provided on separate pages. All pages are organized into a hierarchy of parent and child pages. To find a specific topic in a particular section, click on the topic name in the Table of Contents which is located on the left of every page. This TOC reflects a physical (tree) structure of pages in the "Enterprise Service Bus" space. This documentation is expected to be updated for each release. The documentation is equipped with clear images, loads of samples, crystal clear explanations of various routing and message mediation constructs. The good news is that, we are already working on more product documentation. We will soon have other WSO2 products with this level of complete and comprehensive documents.   Technorati Tags: SOA,ESB,Service Bus

Apache Hadoop is a great framework for scalable computing This blog lists out the steps to build Hadoop source from a checkout from the trunk. I'm working on Mac OS X, so most the steps would apply to *nix users as well, with minor differences.Check out the source  You can checkout the source using the following command:svn checkout http://svn.apache.org/repos/asf/hadoop/common/trunk/ hadoop-trunk Use Maven 3 I was using Maven 2.2.1. If you start to build with a version earlier than 3, Hadoop with the use of the enforcer plugin stops the build (kudos to that) saying you need Maven 3.A "mvn -version" will help you here to identify which maven version you are using.Install protobuf Now, if you build everything will build except for the map-reduce module. For that, or specifically for YARN (inside map-reduce), you need to get protobuf.It's available here: http://code.google.com/p/protobuf/downloads/listFor this you need gcc. On a Mac OS X, the easiest way to do this is to just install Xcode (available on your Mac OS X install disk, under optional).Now run a 'configure', then a 'make', followed by a 'make install', and you should have protobuf in your system.Complete the build Now, you should be able to do a complete build of the whole hadoop source, including the map-reduce project.Use the following command : mvn clean install -P -cbuildHere we use the additional options to stop compiling the native code. The native code refers to, quoting Arun C. Murthy, 'The native code, in this context, is the C executable used to launch the containers (tasks) by the NodeManager. The short summary of the executable is that it's a setuid executable used to ensure that the unix process runs as the actual user who submitted the job, not as the unix user of the NodeManager.'A thanks goes out to Ravi Theja, Praveen Sripathi and Arun Murthy for the help on the map-reduce mailing list. Hope the post helped you to build Hadoop, without running into any road blocks.

Any WSO2 product like WSO2 BPS, WSO2 AS, WSO2 ESB etc is based on WSO2 Carbon platform. One inherent characteristic of this platform is, it's easily front-end and back-end separated. As well this is an interesting deployment pattern which is very useful in many scenarios. In this post what I tried to do is monitor two WSO2 back-end server instances (ESB and BPS) via a single front-end server instance.Table of ContentWhat's front-end(FE) and back-end(BE) separation? Advantages Tested Environment How to separate FE and BE features of a product Configure ports to connect FE and BE How to compose a FE of two products Configurations steps to connect FE and BE What's front-end and back-end separation?Carbon products can be separated as the backend components that runs the middleware logic and the frontend that contains the GUI to manage, monitor and control the instance. Suppose a WSO2 product is a set of features containing front-end (FE), back-end (BE) and common (Com.) features as follows. Then we can separate the product into FE and BE segments as follows.+AdvantagesThis pattern is helpful to keep the backend binary size limited and to provide facility to render the console in a remote machine. By using a single frontend deployment can connect to multiple backends by changing the backend url in the management console. This will help to manage multiple products/ multiple instances of the same product by using a single console. Tested EnvironmentHere again what I’m going to do is depicted as follows.I’m gonna monitor two WSO2 product BE instances (ESB and BPS), via a single FE instance which composed of ESB FE and BPS FE. Here I’m using ESB 3.0.1 and BPS 2.0.1. Note - The reason for specifically using these versions is both products should be released based on the same carbon core (here it’s Carbon 3.0.1), in order to mix features of different products in each other.How to separate FE and BE features of a productSeparating FE and BE features of a WSO2 carbon product is works out of the box. It’s supported via the product management console.Let’s see how to create a WSO2 ESB BE. Creating a WSO2 BPS BE is also the same. Creating a WSO2 ESB FE is same except the step 5.Start ESB Go to https://10.100.0.23:9443/carbon In the Web console goto Configure -> Features in the left-side menu  Goto Settings tab, and add the repository http://dist.wso2.org/p2/carbon/releases/3.0.0/ .This repo based on Carbon version used in the ESB. refer - http://wso2.org/projects/carbon/provisioning-wso2-carbon-with-equinox-p2 Adding repository... Finished adding repository Goto “Installed Features” tab. Select “All Console Features”. Select “Uninstall”. If you need to separate out the BE features, select “All Server Features”. While uninstalling... Finished Then re-start the server. Once you’re done the Web-UI console will look like below. Configure ports to connect FE and BEIt’s essential to avoid port conflicts, as now there can be several server instances trying to grab the same ports. We can do this by modifying the ports used formanagement console http and https transport listeners- $CARBON-HOME/repository/conf/mgt-transports.xml http and https transport listeners - $CARBON-HOME/repository/conf/axis2.xml Change the server url in carbon.xml such that FE points to BE.https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/ How to compose a FE of two productsWe need a server instance consisted of ESB FE and BPS FE. For that what we can do is adding BPS features to WSO2 ESB product and removing BPS and ESB BE features (i.e all server features) from it. In current carbon, only FE features can be installed. But the released versions only feature groups can be installed.Or we can do the other way around as well. Here the easiest way is to add the BPS features to ESB product as there’s only one feature (BPEL Feature) to add as follows. Configurations steps to connect FE and BENow after that we can start three servers. i.e - BPS BE ESB BE BPS FE +ESB FE Then via FE-only server instance’s management UI we can monitor and manage the both BE server instances by changing the Server URL in the login page.

This is very basic usage of ESB and you can do many things inside this proxy service(Calling few actual web services, mediate message, logging, ,message reformat). I used this example to just demonstrate how we can use ESB with BlackBerry client. WSO2 Strstos WSO2 Stratos is the most complete, enterprise-grade, open PaaS, with support for more core services than any other available PaaS today. The open nature of WSO2 Stratos makes it the perfect environment for hosting companies, ISVs and System Integrators to build and customize Industry-specific PaaS and SaaS platforms for vertical markets; for example, creating a Mobile PaaS for telecom companies.The WSO2 StratosLive Java PaaS, hosted by WSO2, enables developers to instantly provision and pay for just the middleware services they use. Enterprises can use the WSO2 StratosLive to host business process flows between business partners as well as implement cloud-based services that access internal systems.Developers get all the benefits of the complete WSO2 Carbon enterprise middleware platform and the multi-tenant, elastic WSO2 Stratos cloud middleware platform without the hassles of setting up machines and middleware WSO2 ESB WSO2 ESB is unique Enterprise Service Bus from the ground up relying on innovative Carbon technology to give you a smooth start-to-finish project experience you cannot find elsewhere. Easy configuration through an intuitive graphical interface allows you to get started – and into production – much faster. Lean, high-performance design conserves resources through maximum efficiency. Built on the WSO2 Carbon OSGi platform: adding new capabilities as you need them is a snap. http://wso2.com/wp-content/themes/wso2ng-v3/images/stratoslive-diagram.gif In this post i will describe how to deploy a simple proxy service in stratoslive and how we can invoke it by BlackBerry mobile device. First we need to setup eclipse IDE(Which use widely in enterprise level to develop BlackBerry Applications) to develop BlackBerry Apps. In my previous post i have describe this topic clearly you will find it here. First we will see how we can deploy simple proxy service with StratosLive. First to https://stratoslive.com/ . you can create new account freely.Then login to the system go to ESB home page. See the figure   Figure : Services Home WSO2 StratosLive Then click on source view to edit configurations. Figure : Edit window for edit source of Configuration Typically the ESB is deployed between the actual client and a backend service implementation to mediate the message flow in between. Thus WSO2 ESB can accept a message on behalf of the actual service, perform authentication, validation, transformation, logging, routing based on the content etc. and then decide the destination target endpoint for the message and direct it to an actual service implementation.We have to write configuration for those operations. These configuration are written using the Synapse configuration language which is a simple and easy to learn domain specific language based on XML. It is always recommended to use the graphical wizards and tools provided in the WSO2 ESB management console to setup the mediation configuration, thus avoiding having to write XML configurations manually. But for this simple configuration we will use XML writing method. See following configuration. <?xml version="1.0" encoding="UTF-8"?>                                                                 mc.setPayloadXML(             <greeting>Hello World</greeting>             );                                                                                     There you will see EchoProxy which is use to set set XML Payload to response message.if you need you can do some thing more inside this proxy(Do Authentication check, send request to actual web service/data service and send response back). Yo have to copy this configuration to your configuration and update Next go to services and you will see deployed proxy service as follows   figure : Deployed services window to view Proxy Services Deployed Then click on the service and you will see following window. There you can edit your service/ generate WSDL/ Try service etc... Then click on try it and test your service by sending request. you will see the response with greeting message   Figure : Service home window Edit and modify the service Now we have created our proxy service successfully now we will see how we can invoke this by BlackBerry.First setup your Eclipse IDE using this guideline document. Then download esb_client source code for here.Unzip it and open with eclipse ide. You have to set your proxy service url properly in the code.for me it was http://esb.stratoslive.wso2.com:8280/services/t/sanjeewa.info/EchoProxy" In blackBerry mobile devices before send request to some url we have to append some part to it. It must contain [deviceside=true;apn=Apnkey]. When i developed my first application in 2009 i found simple solution for this.I was able to store some known apns with relative Mobile Network Code(MNC) and Mobile Country Code (MCC). and retrive them when necessary.you will see more information on MCC/MNC here[http://en.wikipedia.org/wiki/Mobile_Network_Code]. I have written separate post how to use that method, click here[http://sanjeewamalalgoda.blogspot.com/2009/09/run-blackberry-application-without-apn.html] to view it. I used same method for this example. Here we will do simple http get() to that proxy service and get greeting message. you will see very basic UI for service invocation. Then build project and run it on blackberry Device simulator. Go to downloads for your Mobile device.You will see SendT program click on it you will see the following window                                       Then Click on left button and press send request.Then you will see the status and response message as shown below                  so you can modify ESB configuration and client source code as you need for different kind of usages. if you need to test this program with actual device copy cod,jad or jar file to your mobile device using BlackBerry Desktop Software [http://us.blackberry.com/apps-software/desktop/]. And install program to your device. Source Code for BlackBerry Client: http://www.speedyshare.com/files/30054360/download/proxy%20service%20test%20BB%20client%20src.zip

StratosLive comes with its own billing system to bill the tenants for using the cloud. Lets have a look at the bill generation process of StratosLive. Shown below is a simple diagram to explain the base entities involved in bill generation. There can be multiple billing engines in your environment. In StratosLive there are two of them. One is for scheduled bill generation (monthly invoice) and the other is for on-demand bill generation (interim invoice). Both these engines use a single billing database. Each of these engines have a set of handlers to be executed. These handlers can be configured via the billing-config.xml. These handlers are executed by the engine at the time of bill generation. Shown below is segment from the billing-config.xml multitenancy-billing-rules.drl email-billing-notifications.xml What are the data used in bill generation?Subscription details – subscriptions of the user for the duration considered in the bill generation. There is a subscription entry for each usage plan which the user was subscribed to during the billing periodUsage details – Usage details of the user for the month of bill generation. This includes bandwidth usage (webapp bandwidth, service bandwidth and registry bandwidth) and registry storage of the user.Pricing strategy – This defines how users are going to be charged for subscription and overusage. Shown below is a sample xml file which defines the pricing strategy. 10 10 0 25 0.1 2000 0.1 When does bill generation happen? As I mentioned previously, monthly invoice is generated by a scheduled task. This is achieved via Synapse scheduled tasks. When the billing manager is started (i.e. when the server starts), bill generation task is scheduled for the billing engine. This task scheduling can be configured via the billing-config.xml. Lets go through the bill generation step-by-step. Billing engine for scheduled bill generation executes the following set of handlers. 1.SubscriptionFeedingHandler – Retrieves the subscription entries relevant to the bill generation period. For each subscription, relevant user's usage data also retrieved. Subscription entries are added to the BillingEngineContext to be used by other handlers. 2.SubscriptionTreeBuildingHandler – Goes through all the subscription in the context and arrange the subscriptions of same customer together. Creates invoices and assigns the subscriptions to them. Fills some data of the invoice such as invoice dates, payments falling under the billing period. 3.RuleHandler – Rules are used to calculate the subscription fees. Rule handler executes the rules over the billing engine context. This will assign a subscription fee for all the subscriptions in the contex. 4.InvoiceCalculationHandler – Over usage charges are calculated by this handler according to the pricing strategy define in a xml file. Total cost, total payments an carried forward values are also calculated. At this moment, there is a complete invoice for all the customers in the memory. 5.Finalizing Handler – This handler takes care of storing the invoices in the billing database. 6.EmailSendingHandler - After generating and storing the invoices, customers have to be notified. It is done by the email sending handler. When this is done you receive an email notifying you about the invoice.Diagram below gives an idea on what happens in the first four handlers. Scheduled vs. On-demand bill generation These two operations are carried out by two billing engines Scheduled generation executes two additional handlers than the on-demand generation. They are the finalizing handler and the email sending handler. When the invoice is generated on-demand, it is not stored in the database (because it is only for presenting to the user). No email notification is necessary because the invoice shown in the UI. That is the reason for FinalizingHandler and EmailSendingHandler not needed for on-demand bill generation. Flexibility The whole bill generation process is execution of set of handlers. If you want to add something new to the flow, you can simply write a handler. Then you need to mention that handler in the billing-config.xml for it to be executed by the engine. Billing component will be further improved to calculate all the costs via rules. Then it will be super easy to make changes in cost items and pricing because only what we need is to edit the rule file. This avoids any code level change when it comes to changes in calculating the cost which is a huge advantage.