Tag Archives: WSO2 Business Activity Monitor

WSO2Con Insights – AlmavivA Adopts Lean Approach to Public Administration with WSO2

The Italian Ministry of Economy was looking for a complete transformation in data management by redefining and organizing its own data, so that information of millions of employees of the Italian Public Administration would be unique and certified.

The proposed system spelt the integration of two main IT systems in the Ministry; one that handles personal data, and a second that handles economic data, so that the system would have one single point of management, and serve applications regarding salaries and personal data as a self-service for the Italian public sector employees.

The Ministry approached AlmavivA Group, Italy’s number one Information and Communication Technology provider, for a solution. Guiseppe Bertone, Solution Architect at AlmavivA S.p.A. said during his session at WSO2Con 2014 EU, in Barcelona, Spain that AlmavivA designed and proposed an ad hoc master data management (MDM) solution for the Ministry, based on WSO2 products to manage the data of 2.6 million employees.

Picking the Best Product Solution

He said that there was a set criteria that AlmavivA and their client listed out prior to choosing the right products and platform for the project. Some of the critical features were interoperability with existing IT components, high modularity, optimized for performance, and most importantly, open source. Comparing pre-built product solutions available in the market, Bertone and his team made a decision to use WSO2 products for the entire solution.

“WSO2 products fit the requirement. You can enable only the components that you need, and leave the rest of it out, unlike in pre-built solutions,” he said.

He added that there were many redundant repositories within the Ministry IT systems; datasets needed to be optimized and integrated with external systems, and a migration workflow for the existing data had to be defined.

The reference architecture for the MDM solution included interface, events, security, and data quality components, as well as the repository layer, which consists of four databases; master data, metadata, historical data and reference data.

The AlmavivA project ‘Anagrafca Unica’, roughly translating to ‘Unique Repository’, was initiated in March 2012.

The WSO2 Advantage

The mapped reference architecture was a total solution platform based on a set of WSO2 products;

WSO2 Enterprise Service Bus (ESB) for interface services, the WSO2 Data Services Server (DSS) to access the repository layer and manage all life cycle services, WSO2 Identity Server (IS) as the security and identity component, WSO2 Message Broker (MB) for communication between applications, WSO2 Governance Registry (G-REG) to store configurations of all components, and the WSO2 Business Activity Monitor (BAM) to monitor services across the entire MDM solution. OracleDB is used as the repository layer.

With BAM being easily integrated to other WSO2 products, AlmavivA simply had to install only a specific BAM load inside each component, so that the statistics and real-time performance could be monitored. An additional console was added as an UI for the system’s custom procedures.

Another advantage of using WSO2 products was brought to light during the development stage; “Many aspects of WSO2 products can be simply configured from the web UI, or the developer studio for all WSO2 components. It’s really useful and easy to use,” explained Bertone.

In a covalent situation such as this, WSO2 deploys Carbon Apps. By creating a carbon app, a single file consisting of all components is created, so that once the file is deployed, the server knows which components to take, according to Bertone. “This is useful because once you have a system like this you can integrate it with an application cycle management solution already present in the customer environment, like we did,” he says. “We have now created a console where with a single click, the customer can pass from staging to production.”

AlmavivA is looking to expand Anagrafica Unica across the country to include all employees of the Italian Public Administration sector in the system, bringing the total user count to 3.5 million. Bertone and his team are also looking to serve data to external systems, such as the Ministry of Health, with more government institutions being added along the way.

For more information on AlmavivA’s development of the Master Data Management System, view the recording of Bertone’s WSO2Con EU presentation.

WSO2Con Insights – Algar Telecom Delivers Innovation Through Next-Gen Server-Side JavaScript Framework

As telecommunications continue to compete on service, they look at new ways to enrich the customer experience. For Algar Telecom, one of those ways is enabling customers to create their own Web applications using the popular JavaScript language.

At WSO2Con US 2013, Cesar William Alvarenga, front-end engineer at Algar Telecom, described how the company  is taking advantage of Jaggery, WSO2’s server-side JavaScript framework for composing Web applications.

Building on Initial Success

Before describing the company’s use of Jaggery, Alvarenga began by talking about the company’s first project using WSO2 software: Algar Telecom OCS (online charging system). OCS is used to charge customers in real-time, based on their service usage, and all mobile and fixed line traffic will run through this platform. The traffic is passed through WSO2 Enterprise Service Bus (ESB), transforming the data and integrating with legacy services.

“Today we are processing over 200,000 transactions per day and this number will increase every day,” Alvarenga said. “The performance of the ESB is agreeable and it supports our telecommunication requirements.”

Algar Telecom also uses WSO2 products to support its Coreo platform, which is used to deliver a range of applications. For example, Alvarenga noted, an application could let a user send in the airport and flight number and receive the flight information—all using SMS.

Currently Algar Telecom deploys WSO2 ESB and WSO2 Business Activity Monitor (BAM) across the Coreo platform, Alvarenga explained. WSO2 ESB is used to create an interface between all the Coreo modules and transform the data, while the company uses WSO2 BAM to collect and present all of the platform’s data. The company is now testing Jaggery to facilitate Web app development.

The Jaggery Advantage

“Web developers love JavaScript, but typically must alternate between two languages when they want to build applications on the server side,” Alvarenga said. “Using Jaggery allows our developers to work strictly with JavaScript to build Web applications across the Coreo platform.”

With Jaggery, users can generate HTML and they can exchange messages with JSON, Alvarenga observed; “Another benefit is you can reduce the number of layers in your solution. You can access directly the ESB or database for example, and this helps the developer to build a small solution, accessing directly the main services.”

Working in JavaScript using Jaggery also supports Algar Telecom’s vision of a mobile platform that inherently supports Web-native applications.

“I think the future evolution shows that the mobile platform will support these Web  applications,” Alvarenga said, “Today we have some operating systems that support only this type of application, like Ubuntu phone, HP WebOS. Tizen from Linux, and Firefox OS from Mozilla. Using Jaggery, you have a lot of functionality, so if you know JavaScript, for the server-side application, you don’t have to do much. It’s very easy.

Alvarenga wrapped up by providing a detailed explanation of how Jaggery is used with the Coreo platform—using the Jaggery template to generate HTML for the user, granting access to the user with Jaggery and an OAuth module, executing the application using the WS-Request module, and using the ActiveMQ module to get the result back to the user.

For more information about how Algar Telecom is using Jaggery and other WSO2 solutions to develop web and mobile applications, view Alvarenga’s WSO2Con 2013 presentation here.

We Head to Strata 2014 This Week

This week we head to Strata 2014 taking place in Santa Clara, CA. The O’Reilly event for the data community kicks off tomorrow, where WSO2 is a Exabyte sponsor. I will be presenting the talk “Tracking a Soccer Game with Big Data”  on Wednesday the 12th of February at 4.50 p.m.

My session is based on the annual DEBS event processing challenge last year which included a data set generated by a real soccer match in which sensors were placed in the soccer ball and players’ shoes.  We used complex event processing (CEP) and MapReduce based technologies for this challenge to track and process data, achieving throughput in excess of 100,000 events/sec. I will detail how we extended the solution to conduct batch processing using business activity monitoring (BAM) using the same framework, enabling users to obtain both instant analytics as well as more detailed batch processing based results.

Late last year we released WSO2 Complex Event Processor (CEP) 3.0 and WSO2 Business Activity Monitor (BAM) 2.4. Working together, the integrated WSO2 products provide the industry’s first solution for enabling data streams to be analyzed simultaneously in real-time (with WSO2 CEP 3.0) and via batch processing (with WSO2 BAM 2.4). As a result, enterprises have unprecedented flexibility for analyzing the vast streams of events coming into the organization to gain valuable insights into their business.

See here for more details about the WSO2 Platform for big data analytics or sign up for the upcoming webinar series where we will examine how IT professionals can collect, analyze and visualize big data in real-time models and off-line decision support models using WSO2 BAM and WSO2 CEP.

As a special give-away at Strata, we hope to give out the latest Apple Mac Pro to one lucky winner who drops by our booth! So if you are planning on attending the conference, come on over to booth #901. I’ll be happy talk about how you can address your big data challenges too.

– Dr. Srinath Perera, Director of Research at WSO2

WSO2 Products: Summer Release Round-up

Couple of weeks ago, CTO Paul Fremantle and Tech Evangelist Chris Haddad, conducted a webinar on the innovative advancements of the WSO2 Carbon middleware and WSO2 Stratos cloud platforms. Here are some highlights from their presentation

  • WSO2 Carbon core 4.0 released with many improvement and new features
    • Enhanced Deployment Synchronizer
    • Deployment performance improvements
    • Managements and worker node separation
    • JDK 1.7 support
    • Better integration with Tomcat 7
    • Upgrading Equinox SDK (OSGI Runtime) to v3.7
    • P2 Repository: Features grouped by product
    • Multi Tenancy in Carbon
“The Carbon platform is your reconfigurable modular middleware. Recently we’ve seen lots more customers actually wanting to de-couple different parts of a product to vertically scale while at the same time horizontally scaling. This capability is proving to be a major benefit of the Carbon platform.”
– Paul Fremantle  
“We are rapidly evolving all of our products simultaneously on top of single cohesive code base. This is unparalleled in the industry to have such coordinated releases on a single platform.”
– Chris Haddad
  • WSO2 Stratos 2.0 Platform as a Service will include
    • Support for multiple languages and runtimes
    • Support for more IaaS providers (vmWare, EC2, OpenStack, CloudStack, Rackspace etc.) via Jcloud
    • Enhanced manageability
“We are embracing a heterogeneous environment were you can run PHP in the cloud environment and take advantage of the rich set of PaaS foundation services that Stratos offers. Also you can plug-in any application server or asynchronous  server and cloud-ify  the application environment by having an mechanism that ties back into the pass foundation and Startos controller services.”
– Chris Haddad
“The key differentiator for Startos is its inherent multi-tenancy. There are other PaaS offering that have the polyglot language support but what they don’t have is the concept and modeling of multi-tenancy. That plus the richness of the set of Stratos services that the cartridges have available to you make us really stand out.”
– Paul Fremantle

You can watch the full recording of the webinar here: http://wso2.org/library/webinars/2012/09/wso2-carbon-wso2-stratos-summer-release-roundup

 – Hasmin AbdulCader, Director, Communications

WSO2 Platform for API Management

One of the niceties of mainframes was the simplicity of a single API for the users.  After years of evolution towards a decentralized model we still find this pattern appearing, even among SOA implementations that span many subsystems and service platforms.

I discussed the need for unified APIs in my previous blog posts [1],[2], and explained how you can build using the WSO2 middleware platform.

Presenting entire subsystems, which may include legacy systems, databases, and internal and external services as a single unified API makes integration easier for a partner (further decoupling detailed knowledge of the subsystems), and is increasingly used for internal users such as business processes, business rules and mashups. A unified API hides a variety of transports and systems behind a single, consistent, API.

With the introduction of unified API, API management and monitoring becomes an important factor.  Different formats and protocols like SOAP/HTTP, JSON, XML/HTTP, JMS can be exposed across the range of services. A centralized configuration change at the ESB layer enables different protocols or enables QoS features across the API.  Features such as usability, the security, governance can be managed in a single location, as can enterprise features like scalability and high-availability. Monitoring provides a single point for assessing the usage and health of the system.

As I described in my previous posts, the WSO2 Enterprise Service Bus (ESB) provides the a simple yet powerful and highly performant system upon which to implement a unified API and select the various QoS characteristics. WSO2 ESB supports all the popular security standards required for integration and leverages WSO2 Carbon clustering features for scalability and high-availability out of the box.

The WSO2 Governance Registry builds the required governance framework for the unified API by providing a repository for policies and API metadata – even for API documentation – and adds the ability to share, version, analyze dependencies and policy conformance, and manage lifecycles of this metadata.  The WSO2 Governance Registry helps you define the and manage the QoS of your API, and works in conjunction with the ESB to assess and enforce the defined policies.

Monitoring – a key part of runtime governance – is accomplished by deploying the WSO2 Business Activity Monitor (BAM) to collect, summarize, and report on the API usage.  Or you can use the JMX support in the WSO2 ESB and other WSO2 Carbon products to tie into third-party monitoring tools.

Certain services need to go beyond simple monitoring. When we looked at the business requirements of our API management customers, billing and metering, isolated runtimes for specific consumers/consumer groups, as well as customization or overriding of the API for specific consumers emerged. We have found multi-tenancy to be a powerful answer for those requirements, and is available in the WSO2 cloud platform, WSO2 Stratos. With WSO2 Stratos you can easily expose your API in the cloud or as part of the SaaS offerings you provide.

In summary, both essential and extended features for API implementation and management are provided by WSO2 middleware platform, making it a great choice for meeting both your business and technical requirements.

Asanka Abeysinghe, Director of Solutions Architecture
Asanka’s blog: http://asanka.abeysinghe.org/