Monday Mar 31, 2008

Pluggability Rules

I came across and article from a Java Developers Journal e-mail titled "In the Future, the Desktop Will Become the Enterprise Front End - Enterprise Widgets: The Story So Far" that I found very interesting. It covers a bit of history of widgets on the desktop and how Apple first introduced the idea in 1983, but it was really the internet that enabled offerings like Konfabulator (Yahoo! Widgets) and Apple's own Dashboard.

It goes on to discuss the applicability of widgets in the enterprise but makes several observations that sound eerily familiar to those working on Open ESB:
"What is needed is an enterprise widget ecosystem. The ecosystem would have to be portable across the most common desktop operating systems and it would need to be backend agnostic."
"At the same time, however, the ability to link widgets together so that widgets can act as data feeds for other widgets ... is also important."
"For one thing each widget could evolve separately so that you could update functionality without having to do a huge application release. The narrow focus of widgets also makes testing, maintenance, and development a lot easier."
All of this is exactly what Open ESB is doing, just around an integration platform, rather than for desktop widgets.
  • There is an ecosystem developing components ranging from BPEL and XSLT Service Engines to RSS and XMPP Binding Components according to the JBI specification providing for portability across runtimes.
  • JBI enables the components to connect together in a standards based way so that a developer can say use any Binding Component to feed data to the Intelligent Event Processor Service Engine or any other combination one can think of.
  • Many of the components are being developed in a common community, and some in other communities or by other vendors, but all can evolve and mature on their own schedule, and because they plug in to a standards based platform they can be released or made available as they are ready without having to have a full release of everything else.
Our customers of the Java Composite Application Platform Suite will soon realize these benefits as our upcoming release aligns with the development taking place in Open ESB.

Pluggability rules!

Tuesday Feb 05, 2008

Open ESB Activity

I've blogged about Project Open ESB several times before (here, here, and here), but it is been awhile so I thought I'd give an update.

The community continues to grow with many Sun and non-Sun committers collaborating together, some individuals, and some representing companies and community partners. A few key partners that have contributed numerous components are Imola and Gestalt LLC (recently acquired by Accenture). Imola is working on CICS and CORBA Binding Components and Gestalt is working on RSS, SIP, UDDI, and XMPP Binding Components as well as Encoding Service Engine.

You will have noticed some interesting looking components in the list, probably not the typical type of adapters you'd expect to see for a traditional integration offering. But that is what is great about community and open-source development as well as a testament to what a platform built on an open standard like JBI enables. Anyone can build a component for whatever protocol, system, or function they desire and have it plug into the platform and benefit from everything else that also plugs into the platform. Additionally, this is an indication that "traditional integration" is changing to adapt to the "Web 2.0" world and protocols that it brings. Just think about the applications for incorporating RSS and XMPP into your integration or composite applications.

But it isn't just about components from community partners. Sun is building numerous components from BPEL 2.0 and XSLT Service Engines to a variety of Binding Components for JDBC, JMS, E-mail, SAP, and more. A particularly interesting new Service Engine is the Intelligent Event Processor that provides for receiving and processing real-time events to aggregate, correlate, and monitor them to support a variety of new applications built on an Event Driven Architecture. And because it is a JBI component, and can benefit from all the Binding Components as a way to receive events and send notifications and it doesn't have to have custom mechanisms for that.

There are many more components being developed so visit the site and take a look. We welcome all feedback so I encourage you to download a recent build, try it out, and collaborate with the community at what ever level you'd like.

Monday Aug 13, 2007

JBI Ecosystem Growing with CICS Binding Component

I came across a great article on JBI and CICS on written by our friends at Gruppo Imola.

Imola is a member of the Project Open ESB community and is developing several JBI components there including a CICS Binding Component which is the topic of the article they've written. But they've also worked on a CORBA Binding Component that is in a similar state of development to the CICS BC.




« July 2016