Technology Partnership Agreement - Web Service Monitoring Solutions Can Be Easily Plugged Into WSO2's Products

    A new technology partnership agreement was announced by WSO2, Inc. and SoapKnox, Inc. SoapKnox will deliver a mechanism by which their Real-Time Web Service Monitoring solutions can be easily plugged into WSO2's products.

    By amplifying the functionality of WSO2's management console, users will have the possibility to monitor Web Services from directly within WSO2's management console. This means that WSO2's users will now have an option of using SoapKnox's solutions that will enable them to monitor Web services running inside WSO2 products. WSO2 products include WSO2 Web Services Application Server (WSO2 WSAS) and WSO2 Enterprise Service Bus (WSO2 ESB). SoapKnox has also agreed to provide a pre-packaged version of WSO2 WSAS and WSO2 ESB with the monitoring solution built in for ready use.

    The WSO2 team is comprised of individuals instrumental in establishing Web services and SOAP standards, and longtime contributors to the Apache open source project. In addition, SoapKnox is developing comprehensive, multi platform, end to end Real-Time Web Services Monitoring solutions. SoapKnox's unified monitoring architecture offers users a way to monitor Web services developed in both Java as well as .NET platform through a single monitoring console.

    WSO2 offers an open source middleware stacks, built on Apache Axis2, that is optimized for Web services and SOA. The company's flagship products, WSO2 Web Services Application Server (WSAS) and Enterprise Service Bus (ESB), were released earlier this year. SoapKnox a USA based company was founded in 2006 and is developing Real-Time Web Service Monitoring solutions to monitor Web Services developed in both Java as well as .NET platform.

The current state of Monitoring can be summarized as follows, as the WebServices Journal states:

   1. End-to-end monitoring and performance- management tools and technology are still evolving.
   2. A proactive strategy is desired, as opposed to reactive monitoring and performance management.
   3. Usage and existence of "island or silo management" and summing up, i.e., monitoring the individual components of an application and summing them up for the end result.

Typical reactions to production problems vary from "it's their system/API/Web service... not ours!" to "the database is extremely slow" to "the network is congested" to "everything is fine, just reboot your machine." Bottom line: in the absence of an end-to-end monitoring tool, no group is willing to take responsibility.