Dzone hosts an interview to Frank Kieviet, OpenESB Community Manager, about OpenESB, Java CAPS, Glassfish and future directions. It is a good summary of the present status, how difficult has been to get the former SeeBeyond suite as opensource and where it aims to go in the next few months.
From my point of view the OpenESB suite still lacks two major components:
- A SOA Governance solution. A good registry / repository is an important side component of any ESB, at present Sun should at least establish a commercial partnership with other vendors about that, the strategy here seems a bit confusing and no clear message is available for consulting partners and end customers. My opinion is that OpenESB needs to partner with solutions having a similar dual opensource / commercial license, a closed-source only registry product could lead to difficult sales propositions.
- A ESB management and monitoring console. The ESB Console project is very late, even if it seems a version 1.0 will be released within this year. Any ESB needs robust and easy monitoring and this can't be sold by suggesting users to build their own through JMX or other APIs.
So far, lacking an integrate offering from Sun, I am evaluating myself some third parties Governance solutions to suggest to my customers, some are quite nice and works well with OpenESB and Java CAPS.


5 commenti:
Have you looked at Mule Galaxy for the SOA governance piece? (www.mulesource.org)
Not yet, so far I have experimented with WSO2 Registry which seems a very interesting product. I will have a look at Galaxy anyway. Thanks.
Both of the product are nice, but the question is how to integrate them into SOA environment in OpenESB.
By this I mean publishing to registry and deploying from registry. Anybody experienced with it ?
Ivan, what do you mean by "deploying from registry"?
I mean to deploy to production. To complete SOA Governence circle. Imagine Developer creates web service. Publish it to the registry. Then manager can evaluate product and it approved. Then it goes to production. So I mean deploy like to deploy web service deliverables into target production container.
Post a Comment