Evaluate Java's business integration features

Today, the number of network service specifications and the expansion of XML metadata are growing at an astonishing rate. Although the standards and norms publicly proposed by large companies such as Microsoft and Sun are theoretically superior, there are some overlaps and chaos among them. From this point, we can see that all major companies want to play a role in promoting the development of network service technology.

In March 2003, the executive committee of SE/EE recognized a new Java specification: Java Business Integration (JBI ). In essence, JBI extends the J2EE application package and adds the JBI component function. These JBI components are free objects that use JBI to abstract business process metadata. JBI has a very interesting feature, that is, to describe some things, although these things already exist in many similar descriptions.
JBI overview
Business Process metadata is the key to the entire specification. Some existing integration specifications, such as BPEL4WS and WC3 design team, have tried to define metadata. JBI promises to provide an integrated environment that meets the unified requirements of the business process metadata industry.
JBI components need to be supported in three main aspects: JBI runtime environment, JBI host, and JBI binding. The JBI environment defines a standard internal expression for business protocol messages. These messages can be obtained from other applications, including network service applications.
JBI host is responsible for JBI component hosting and lifecycle management. JBI provides support for special component models. Therefore, JBI allows support for this model in the JBI environment and extends the business integration capability of the JBI environment.
JBI binding is used to communicate with external servers. They are bound to the business protocols of the environment.
Conversion
Although the JBI specification is short, it is indeed convenient and practical. JBI tries to simplify the infrastructure in J2EE, which allows developers to execute business-specific processes and package them as components. These components are used in J2EE container and can send and receive messages or requests.
This normative work draft will not be published until 2004, so there is enough time to promote and develop areas that are not developed in the network business interaction service. Let's wait and see what impact JBI will have on network services.