WSO2 Unveils its Own IDE - Mitchell Pronschinske, DZone

Starting today, developers using WSO2's Apache-licensed SOA components will be able to add even more customization to their systems. That's because WSO2 now has their own IDE for developing, debugging, and deploying SOA services and composite applications on Carbon, their Equinox-influenced OSGi architecture on which WSO2's ESB, BPM engine, Governance registry, and other components are based.

The new release, called Carbon Studio IDE, reduces the complexity of building and integrating composite applications. This Eclipse-based tool allows developers to create a Carbon Application project (CApp) which encompasses the application and the server configurations. For example, a single project might encompass the configuration of a WSO2 ESB, the provision of a WSO2 Governance Registry, and BPEL for execution in the WSO2 Business Process Server.

It is then exported into a Carbon Archive (CAR) format, which simplifies the deployment of composite applications spanning multiple systems into a production environment. Each server the CAR is deployed to will extract only the relevant part of the application, allowing the application topology to become a reliable part of the CApp definition instead of being implied through a complex multi-server deployment process.

Carbon Studio also offers single-click testing for Java-based apps within the IDE. The debugging tools support Apache Axis2-based services, Apache Synapse mediators, registry handlers, and data validators.

“We have found that many of our customers are developing sophisticated applications that span the WSO2 Carbon product family, and they are taking advantage of the unique strengths of our platform when used as a whole,” said Dr. Sanjiva Weerawarana, founder and CEO of WSO2. “We’re now revving up our tooling support with WSO2 Carbon Studio—helping developers to organize, develop, test, and deploy these composite applications with greater ease than ever before. This illustrates WSO2’s commitment to continuously searching and destroying the hassles developers and IT staff may encounter, and helping businesses fully realize the contributions of SOA to the bottom line.”

It's a welcome change to SOA domains when developers can avoid the integration complexity and redundancy of traditional middleware platforms by having a shared and unified management console that provides a consistent set of enterprise-class management, security, clustering, logging, statistics, tracing, and other capabilities - and all of it as free open source.

WSO2 includes a comprehensive set of tools for supporting an SOA environment:

  • Apache Axis2 and JAX-WS Tooling: create open services from existing or new Java code.
  • Data Service Tooling: expose existing data sources as secure open services.

  • BPEL Tooling: create industry standard workflows and automated processes.

  • ESB Tooling: create flows and mediation based on the Apache Synapse / WSO2 ESB configuration model.

  • Gadget Editor: create gadgets and portal UIs using the OpenSocial / Google Gadget specification.
  • Registry Tooling: manage resources in the WSO2 Governance Registry.