WSO2 BPS 2.1.0 Available for Download

The WSO2 Business Process Server(BPS) team is pleased to announce the release of 2.1.0 version of the Open Source Business Process server. WSO2 BPS 2.1.0 is based on WSO2 Carbon 3.2.0 which is the OSGi-based component framework allows the complete set of WSO2 products to leverage shared components, ensuring a consistent set of features between products, a consistent user experience, and reusing of identical components. You can find the release note for WSO2 BPS 2.1.0 from here.

Two fresh products; WSO2 MB and WSO2 CEP also were released with the existing set of products.

Few excerpts from the WSO2 BPS 2.1.0 release note...

• WSO2 Business Process Server (BPS) is an easy-to-use Open Source Business Process Server that executes business processes written following WS-BPEL standard. WS-BPEL is emerging as the defacto standard for composing multiple synchronous and asynchronous web services into collaborative and transactional process flows which increase the flexibility and agility of your Service Oriented Architecture. WSO2 BPS is powered by Apache ODE and available under Apache Software License v2.0. WSO2 BPS provides a complete Web based graphical console to deploy, manage and monitor business process and process instances.
  
• WSO2 BPS is developed on top of the revolutionary Carbon platform (Middleware a' la carte), and is based on the OSGi framework to achieve the better modularity for you SOA. Carbon platform contains lots of new features and many other optional components that can be used to customize or enhance the functionalities provided by BPS to suits you SOA needs. In addition to installing optional components you can uninstall unwanted features without any trouble.
  WSO2 team recently released 3.2.0 version of WSO2 Carbon platform which is the OSGi-based component framework allows the complete set of products to leverage shared components, ensuring a consistent set of features between products, a consistent user experience, and reusing of identical components.
  
• An open source product, WSO2 BPS is available under the Apache Software License (v2.0) . This includes all of the extra integration and management functionality as well.

Off-season Sri Padha(Adam's peak) hike

Recently five friends at WSO2 and I hiked-up Sri Padha(Adam's Peak) during the off-season. It was my 2nd hike to that mountain during the off-season. During the off-season the site was very much peaceful as usually pilgrims don't walk up the mountain due to heavy raining, strong wind, lightning and thick mist.
Adam's peak is an important pilgrimage site especially for Buddhists. Unlike in pilgrimage season (December to May), we had to take precautions and we had to prepare and bring all the food and stuff required up to the peak of the mountain. As there's no electricity until the peak of the mountain, we prepared for that as well. We climbed-up the mountain via a shorter path which is Hatton route and climbed-down via a longer path which is Rathnapura route. We started to climb-up the mountain around 2pm and it took around four hours. While climbing-up, it was raining all most all the time, but we didn't experience much of a wind. We were the only team to stay there for that night. And the next morning we worshiped and walked around the peak. We couldn't see the sun-rise due to thick mist. Only for few seconds we saw very far away mountains but those views were vanished in seconds when thick clouds covered the peak. Then we climbed-down via Rathnapura route and we experienced some strong wind. Though Rathnapura route was quite longer it was more beautiful as it was lead through a lush green jungle.

At the peak

Carbon 3.2.0 - One checkout One build in 3-4 hours

Recently I had a memory upgrade to my office laptop. So I felt to build very recently released WSO2 Carbon 3.2.0 branch and compare the build time while watching a movie :). Previously it took around 8-9 hours to build the complete carbon product stack which consist of around 4941kSLOC. But now it takes around 3-4 hours. During the build, I managed to keep the swap usage in a minimum level (maximum up-to 10MB) by configuring the JVM options such that Build system utilizes the maximum physical memory while underneath OS has enough physical memory left for its tasks. Normally in Ubuntu 10.04 (Kernel Linux 2.6.32-24-generic), from the moment physical memory is fully utilized, the swap space starts to increase continuously even though there's available physical memory after sometime. So swap usage doesn't decrease for a long time. So if the JVM options are not set properly overall performance get decreased drastically. Seems tuning JVM based on available physical memory can preserve a lot of CPU time.