Difference between revisions of "Group"
| Line 10: | Line 10: | ||
** on: group's services are active. | ** on: group's services are active. | ||
** paused: group's services are inactive, the asynchronous client's requests are taken in charghe by {{GVESB}}. They will be served when the group return on state ''on''. | ** paused: group's services are inactive, the asynchronous client's requests are taken in charghe by {{GVESB}}. They will be served when the group return on state ''on''. | ||
| − | ** off: group's services are inactive and no request | + | ** off: group's services are inactive and no request will be elaborated by {{GVESB}}. |
| + | : The current version does not implement the state ''paused''. The attribute's default value is: on. | ||
Might contain the sub-element Description. | Might contain the sub-element Description. | ||
Latest revision as of 09:14, 1 March 2012
Every GreenVulcano® ESB service is associated to a group.
Action on a group are propagated to every group's member. In particular you can specify activation status of services, it is therefore advisable to insert in the same group services that should be activated or suspended together.
The Group Element is used by the super-element Groups (GVServices subelement to define the GreenVulcano® ESB services groups).
The following list shows the Group element's attributes:
- id-group: Group name.
- group-activation: Activation status of group's services. The status can be:
- on: group's services are active.
- paused: group's services are inactive, the asynchronous client's requests are taken in charghe by GreenVulcano® ESB. They will be served when the group return on state on.
- off: group's services are inactive and no request will be elaborated by GreenVulcano® ESB.
- The current version does not implement the state paused. The attribute's default value is: on.
Might contain the sub-element Description.
