### Java Business Integration

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.

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.

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 the NetBeans Integrated Development EnvironmentTM(NetBeans IDE).

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.

From the Admin Console, you can do the following:

- Service Assemblies: View Service Assemblies, manage their lifecycle states, and deploy and undeploy them. For more information, see Service Assemblies.

- JBI components: View Binding Components and Service Engines, manage their lifecycle states, and install and uninstall them. For more information, see JBI Components.

- Shared Libraries: View, install and uninstall Shared Libraries. For more information, see Shared Libraries.

- Manage Lifecycle states: For more information, see Lifecycle States within the JBI Environment.