Java Business Integration (JBI) is an implementation of the JSR 208 specification for Java Business Integration, a standard developed under the Java Community Process (JCP) as an approach to implementing a service-oriented architecture (SOA).
JBI defines an environment for plug-in components that interact using a services model based directly on Web Services Description Language (WSDL) 2.0. The plug-in components function as service providers, service consumers, or both.
For detailed information on managing the key components of the JBI runtime environment and their lifecycle states, see the Admin Console Online Help. For information about using the JBI commands, see Sun GlassFish Enterprise Server 2.1.1 Reference Manual.
The key components of the JBI environment are covered in the following sections.
Service Engines are components that provide local services (that is, services within the JBI environment) and consume local or remote services.
Binding Components are proxies for consumers or providers that are outside the JBI environment. Binding components typically are based on a standard communications protocol, such as FTP, JMS, or SMTP, or a call to an external service, such as SAP or WebSphere MQ.
JBI components have the following lifecyle states:
The JBI Runtime persists the life cycle states of JBI Components. When the server shuts down and then restarts, JBI Components revert to their state at the time the Enterprise Server shut down.
The JBI runtime attempts to revert to the "desired" state of a JBI component. For example, suppose you tried to start a JBI component but it did not start due to an error in the component. If you restart the Enterprise Server, the JBI runtime attempts to start the component again.
You can do the following operations on the JBI components. For detailed steps, log on to the Admin Console, navigate to the JBI node, click Components and then click Online Help.
View JBI components by their specific lifestyle states.
Install JBI components.
Uninstall JBI components.
Manage the lifecycle states of the JBI Components.
View the general properties of a JBI Component.
View the configuration information for a JBI Component.
View the descriptor for a JBI Component.
Manage JBI Component Loggers.
Using the Admin Console, you can manage the log levels for JBI Components. Some JBI Components provide several loggers while other components might not provide any. However, there will always be a logger level displayed for the entire component. But the logger level setting will only have an effect if a component implements its loggers based on the default name. The provider of a JBI Component might provide additional documentation on specifying logging levels.
The logging levels for JBI Components are often inherited from a parent logger such as the JBI logger. To view and set parent logging levels, in the Admin Console, select Common Tasks and then Application Server. Then, in the Enterprise Server panel, select Logging and then Log Levels. Look for the drop-down list for the JBI module to view and set the parent JBI logging level.
A Service Assembly is a collection of Service Units that provision target components that together provide or consume specific services for an application. Service Assemblies are typically created in a development tools environment, such as that provided by NetBeans Enterprise Pack.
A Service Assembly has the following lifecyle states:
The JBI Runtime persists the lifecycle states of Service Assemblies. When the Enterprise Server shuts down and then restarts, Service Assemblies revert to their state at the time the Enterprise Server shut down.
The JBI runtime attempts to revert to the "desired" state of a Service Assembly. For example, suppose you tried to start a Service Assembly but it did not start due to an error in the Service Assembly. If you restart the Application Server, the JBI runtime attempts to start the Service Assembly again.
You can do the following operations on Service Assemblies. For detailed steps, log on to the Admin Console, navigate to the JBI node, click Service Assemblies and then click Online Help.
View all the Service Assemblies, with support for sorting and for filtering by lifecycle state.
Deploy a Service Assembly.
Undeploy a Service Assembly.
Manage the lifecyle of a Service Assembly.
View the general properties of a Service Assembly.
View the descriptor for a Service Assembly.
A Shared Library provides Java classes that are not private to a single component and is typically shared by more than one JBI Component. For example, the Java EE Service Engine requires the WSDL Shared Library.
You can do the following operations on Shared Libraries. For detailed steps, log on to the Admin Console, navigate to the JBI node, click Shared Libraries and then click Online Help.
View all Shared Libraries.
Install Shared Libraries.
View General Properties of a Shared Library.
View the descriptor for a Shared Library.
Uninstall a Shared Library.
The descriptor file (jbi.xml) for Service Assemblies, JBI Components, and Shared Libraries provides the following information:
Service Assemblies: Lists the Service Units contained in the Service Assembly and the target for each Service Unit. Some Service Units may also show information on connection endpoints.
JBI Components: Lists the type of the JBI Component (Binding Component or Service Engine), a description of the component, information about relevant classpaths for the component, and the name of any Shared Library upon which it depends.
Shared Libraries: Lists the name of the shared library, and the names of the archive files (.jar files) or class file subdirectories it contains.