Lifecycle States within the JBI Environment

Stateful JBI artifacts such as Binding Components, Service Engines, and Service Assemblies, are managed for the whole domain (repository and one or more targets) and can also be managed per target.

Within a cluster environment, JBI components and Service Assemblies can have the following status in a domain:

On a particular target (a cluster or a standalone server instance), JBI components and Service Assemblies can have the following lifecycle states:

The JBI Runtime persists the lifecycle states of JBI components and Service Assemblies. When the application server shuts down and then restarts, JBI components and Service Assemblies revert to their state at the time the application server shut down.


Note - When the Application Server restarts, the JBI runtime attempts to revert to the "desired" state of a JBI component or a Service Assembly. 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 Application Server, the JBI runtime attempts to start the component again.