Petals ESB lifecycles

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
{gliffy:name=Component lifecyle|version=5}

Actions associated to states:
* when starting the component, it will be able to process request messages,
* when stopping the component, no more request message is processed,
* when shutting down the component, all resources (as database, pools, ...) used on states {{STARTED}} and {{STOPPED}} are released.

h2. Constraints

* to realize a transition on the service-assembly life-cycle, the component must be in state STARTED or STOPPED.

|| Component state || deploy || start || stop || shutdown || undeplpoy ||
| UNLOADED | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! |!checkErro.png|align=center,width=20px! |
| LOADED/UNINSTALLED | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! | !checkErro.png|align=center,width=20px! |!checkErro.png|align=center,width=20px! |
{gliffy:name=Service-Unit lifecyle|version=2}
The implicit state 'UNDEPLOYED' does not really exist because the service unit is not deployed.

Actions associated to states:
* when starting the service unit, endpoints or equivalents are registered, and consumption of services or equivalent is running,
* when stopping the service unit, consumption of services or equivalent is stopped,
* when shutting down the service unit, endpoints or equivalents are no more registered.