Petals Documentation > Petals ESB > Petals ESB 5.4.0 > Page Comparison - Petals ESB lifecycles (v.17 vs v.18)

Petals ESB lifecycles

Version 17 by Christophe DENEUX
on Sep 23, 2014 09:51.
<< Changes from 16 to 17
compared with
Version 18 by Christophe DENEUX
on Sep 23, 2014 10:23.
Changes from 18 to 19 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History
...
{gliffy:name=Shared-Library lifecyle|version=3}
It contains only one state: INSTALLED. The implicit state 'UNINSTALLED' does not really exist because the shared-library is not instantiated or loaded.
The transition from state 'UNINSTALLED' to 'INSTALLED' is realized installing the shared library, and the return to the state 'UNINSTALLED' is realized uninstalling the shared-library. A shared library can be (un)installed using [Petals CLI|petalsesb:Command Line Interface], [the Petals Autoloader|Petals ESB "Autoloader"], Petals Ant Tasks or the JMX API.

{anchor:sharedlibrary-lifecycle-constraints}
...
| STARTED | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! |


{anchor:component-lifecycle}
h1. The component life-cycle
...
The component life-cycle is linked to:
* [the shared life-cycle|#sharedlibrary-lifecycle-constraints],
* the service-unit lifecycle:

* [the service-unit lifecycle|#serviceunit-lifecycle-constraints].
* and have following constraint against the service-unit life-cyle:
|| Service unit state || loadNewInstaller || install || start || stop || shutdown || uninstall || unloadInstaller ||
| UNDEPLOYED | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! |
...
| STOPPED | !checkErro.png|align=center,width=20px!| !checkErro.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! |
| STARTED | !checkErro.png|align=center,width=20px!| !checkErro.png|align=center,width=20px!| !checkOk.png|align=center,width=20px! | !checkOk.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! |
** component required by a service unit must be installed and running (ie. in state STOPPED or STARTED) before to deploy the service unit,
** if service units are deployed on, a component can only be started or stopped. All service units must be undeployed before to try any other transitions.

{anchor:service-assembly-lifecycle}
...
{anchor:service-unit-lifecycle}
h1. The service-unit life-cyle

h2. The life-cycle

The service unit life-cycle is simple:
{gliffy:name=Service-Unit lifecyle}
The implicit state 'UNDEPLOYED' does not really exist because the service unit is not deployed.
The transitions from state 'UNDEPLOYED' to 'SHUTDOWN' is realized deploying the service unit, and the return to the state 'UNDEPLOYED' is realized undeploying the service unit. A service unit can be (un)deployed/started/stopped/shutdown using [Petals CLI|petalsesb:Command Line Interface], [the Petals Autoloader|Petals ESB "Autoloader"], Petals Ant Tasks or the JMX API.

{anchor:serviceunit-lifecycle-constraints}
h2. Constraints