Page History

...

JBI components are most typically provided to you with the JBI container and they provide support for some of the most common protocols and engines. In order to make use of these components as an application developer, you must provide a configuration for each component you want to use. Configurations are implementation specific but the packaging is defined by the JBI spec. Each component configuration must be packaged as a service unit (SU) (see What is a JBI SA SU and how do I create one?) and each SU must be wrapped in a service assembly (SA) (see What is a JBI SA and how do I create one?). These are simply ZIP/JAR files that contain a XML descriptor named jbi.xml that is used by the JBI environment. For those folks who are familar familiar with Java EE development, these ZIP files are similar to WARs and EARs.

Should I Create My Own JBI Components?

Upon first encountering JBI, many people wonder should they create some folks assume that they need to begin writing their own JBI components See the previous link for the answer to this question. components. You might, in fact, need to do this, but understanding why you would need to do this is an important first step. To understand why, read the following FAQ entry:

• Should I Create My Own JBI Components?

Additional Reading

The following articles are highly recommended follow-up reading to the information on this page:

...