Integrating new components into a middleware stack can be a time consuming ordeal – one that Middleware vendor WSO2 seeks to address in its release of the Carbon 3.0 platform this week.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
The company’s updated SOA platform has an interesting feature called the Component Manager. Through a checkbox-styled UI, a developer or architect can start with the basic core and click to add more than 150 functionality components. For example, you can add mediation to the Web Services Application Server with a click and the Component Manager automatically acquires, installs and provisions the feature in the runtime.
I am sure users will appreciate having one less reason to deal with installers and file systems. But as this feature probably is meant for installing WSO2 components on WSO2 middleware, I can’t help but wonder if it would integrate well with the multi-vendor, best-of-breed middleware systems we see in many enterprises.
There were a host of other updates to the platform. WSO2 has added in WS-Discovery to automatically find service endpoints, as well as enhanced governance registry integration across the platform. The company’s ESB now has a graphical dashboard to monitor runtimes and provide analytics. The governance registry now works with the WSO2 Gadget Server, which provides tools for impact analysis on services and registry resources.
WSO2 is known for its lightweight, open-source approach to middleware and has built its platform on OSGi. Analysts often talk of OSGi as the next wave for enterprise application environments. While some say it is still overly complex to use, OSGi’s approach to componentization lets developers update elements in the runtime without taking systems offline.