JSR-208 Spec (JBI) Released for Public Review!

by David A. Chappell

Related link: http://jcp.org/en/jsr/detail?id=208



The JSR 208 EG has just released a public draft of the JBI spec for review. The 30 day review will close on April 4th with the last seven days also being a JCP EC ballot.

The full spec can be downloaded from -
http://jcp.org/en/jsr/detail?id=208

Here is an excerpt from the spec which describes the purpose of JBI –

“Enterprise application integration (EAI) and business-to-business integration (B2B) solutions have traditionally required the use of non-standard technologies to create functional systems. This has required end users to either “lock in” to a single vendor of such technologies, or create their own. Each approach has disadvantages. No single vendor can cover the vast functional space of EAI and B2B (consider the thousands of applications and protocols to be supported). This leaves users of integration technologies in the uncomfortable position of selecting less than ideal solutions to their integration problems, and paying dearly for them.

Java™ Business Integration (JBI) seeks to address this problem by creating a standards-based architecture for integration solutions. This infrastructure allows third-party components to be “plugged in” to a standard infrastructure, and allows those components to interoperate in a predictable, reliable fashion despite being produced by separate vendors. It is anticipated that this ability to interoperate will create a multivendor “ecosystem” which will give rise to large pool of integration-related technologies that can be sourced by end users. In addition, this ecosystem will foster new innovations in integration technologies, since it will permit innovators to concentrate on a particular technology or problem area, without having to worry about providing all the other pieces needed to build a complete integration solution.”

I would also like to add, as we at Sonic are often fond of saying, that JBI will help drive the shape of ESBs much like the EJB spec drove the shape of appservers in the late 90’s. JBI will add an additional degree of standardization and pluggable interoperability to a key architectural component of the ESB, which is the ESB Service Container.

For more information on the synergy between JBI and ESB, here are a few links to articles –

SOA Integration Java Specs Due Midyear
Integration Developer News
January 18, 2005
http://www.idevnews.com/IntegrationNews.asp?ID=150

The New Integration Standard: How Java Business Integration and the ESB Will Truly Standardize Integration
Business Integration Journal
http://www.bijonline.com/PDF/Chappell%20oct.pdf

For those who like to listen and watch a narrated slideshow rather than just read, here is a replay of a session I did at JavaPro Live! on the subject -
http://www.ftponline.com/javapro/2004_10/online/chappell/

For those of you who have been following along on the progression of the spec, here is a summary of changes made to this specification since Sept 2004 when we published the Early Draft Review –

- The Normalized Message Service has been renamed Normalized Message Router (NMR). The messaging model has been reworked to allow bindings and engines to work as service providers, consumers, or both. There are no longer separate DeliveryChannel types for bindings and engines.
- The management chapter has been rewritten. It previously used a use case-driven set of illustrations of system management. It now uses functional definitions of the JBI-provided management pieces, and how they interact with management tools as well as the JBI components being managed.
- The three separate framework chapter have been consolidated into one, reflecting the convergence of bindings and engines in the NMR.
- The the separate binding and engine packages have been combined into one javax.jbi.component package.
- A new "component" interface has been added, and the component-provided interfaces refactored to use it
- All JavaDocs for all JBI-defined APIs and SPIs are included in this specification.

Cheers,
Dave