JBI defines a standard container in which components from multiple vendors and various integration technologies can interact.
But it is not (yet?) supported by major JavaPlatform technologies like WebSphere (from IbmCorporation) nor WebLogic (from BEA). And not relevant for BigIron legacy applications, nor found common grounds with the MicrosoftWay. This observation came from ZapThink?.
It is said IBM not interested in multivendor environments, and BEA wants prominence for its solution built on the OpenSource Beehive that it promotes.
"JBI will drive the shape of ESBs much like the EJB spec helped drive the shape of app servers four to five years ago. In short, JBI will provide to ESB and integration what EJB has provided for app servers and business logic,"
JBI proposes to eliminate vendor specific integration solutions by defining a standards based Integration framework. The JBI API proposes to have a Standard environment where integration components from multiple vendors will reside and be offered as services to clients. These components provide specific services, which can be combined to form specific integration solutions. The services provided by the JBI are based on WSDL and web services.
The key components of the Java Business Integration framework are Service Engines (SE), Binding component (BC) and the Normalized message service (NMS).