Service - Revision history

Anonymous: /* {{VULCON}} / {{GVESB}} Configuration */

2012-04-10T12:56:34Z

‎{{VULCON}} / {{GVESB}} Configuration

Anonymous: /* {{VULCON}} / {{GVESB}} Configuration */

2012-04-10T12:53:59Z

‎{{VULCON}} / {{GVESB}} Configuration

Anonymous: /* {{VULCON}} / {{GVESB}} Configuration */

2012-04-10T12:52:48Z

‎{{VULCON}} / {{GVESB}} Configuration

Anonymous: /* How to */

2012-03-05T11:51:46Z

‎How to

G.dimaio at 16:54, 27 February 2012

2012-02-27T16:54:33Z

G.iannello: /* {{VULCON}} / {{GVESB}} Configuration */

2012-02-13T15:54:23Z

‎{{VULCON}} / {{GVESB}} Configuration

G.iannello: /* {{VULCON}} / {{GVESB}} Configuration */

2012-02-13T15:53:44Z

‎{{VULCON}} / {{GVESB}} Configuration

G.iannello: /* {{VULCON}} / {{GVESB}} Configuration */

2012-02-13T15:53:17Z

‎{{VULCON}} / {{GVESB}} Configuration

G.iannello: /* {{VULCON}} / {{GVESB}} Configuration */

2012-02-13T15:52:58Z

‎{{VULCON}} / {{GVESB}} Configuration

G.iannello: /* Description */

2012-02-13T15:52:15Z

‎Description

@@ Line 5: / Line 5: @@
 =={{VULCON}} / {{GVESB}} Configuration==
-[[File:VULCONService.jpg|thumb|Service configuration]]A {{GVESB}} service is identified by a unique name (id-service), belongs to a [[group]] and has an activation state.
+[[File:VULCONService.jpg|thumb|Service configuration]]A {{GVESB}} service has the following main characteristics:
 You can configure the conditions applied to the routing of Service's flows ([[Conditions]] section).

@@ Line 5: / Line 5: @@
 =={{VULCON}} / {{GVESB}} Configuration==
-A {{GVESB}}'s service is identified by a unique name (id-service), belongs to a [[group]] and has an activation state.
+[[File:VULCONService.jpg|thumb|Service configuration]]A {{GVESB}} service is identified by a unique name (id-service), belongs to a [[group]] and has an activation state.
 You can configure the conditions applied to the routing of Service's flows ([[Conditions]] section).
@@ Line 11: / Line 11: @@
 The definitions used here are valid for all [[Flow|flows]] associated with service and overwrite any global definitions.
-[[File:VULCONService.jpg|thumb|Service configuration]]The following table shows the Service element's attributes:
 {|class="gvtable"
 ! Attribute !! Type !! Description

@@ Line 11: / Line 11: @@
 The definitions used here are valid for all [[Flow|flows]] associated with service and overwrite any global definitions.
-[[File:VULCONService.jpg|thumb|Service configuration]]The Service element has the attributes:
+[[File:VULCONService.jpg|thumb|Service configuration]]The following table shows the Service element's attributes:
-* ''id-service'': The unique name of the service. Corresponds to the value contained in the 'service' field of the data buffer (GVBuffer).
+{|class="gvtable"
-* ''group-name'': Service group membership. Groups are defined in the [[Group]] section.
+! Attribute !! Type !! Description
-* ''service-activation'': Activation status of service. The status can be: <br/>- on: service is active.<br/>- paused: service is inactive, the asynchronous client's requests are taken in charge by {{GVESB}}. They will be served when the service return on state 'on'. <br/> - off: service is inactive and no request are taken in charge by {{GVESB}}. <br/> The current version doesn't implement the state 'paused'.<br/> The attribute's default value is: on.
+|-
-* ''creation-date'': Service creation date. The information in this field is purely descriptive and has no impact on the functionality of {{GVESB}}.<br/> This information will be used for the production of reports on configuration.
+| id-service || required || The unique name of the service. Corresponds to the value contained in the 'service' field of the data buffer (GVBuffer).
-* ''brief-description'': Service description. This information will be used for the production of reports on configuration.
+|-
-and the subelements:
+Might contain the sub-elements:
-* Description,
+* [[Description]]
-* Operation,
+* [[Operation]]
-* BpelOperation,
+* [[BpelOperation]]
-* AliasList,
+* [[AliasList]]
-* Conditions.
+* [[Conditions]]
 ==How to==

@@ Line 27: / Line 27: @@
 ==How to==
-You can insert a new ''Service'' from the Core view right clicking the [[Services]] element, Insert after (or Insert before), ''Service''.
+You can insert a new ''Service'' from the Core view right clicking the [[GVServices#Services|Services]] element, Insert after (or Insert before), ''Service''.
-It is also possible to create a new Service using the [[Wizard]].
+It is also possible to create a new Service using the Wizard.

@@ Line 1: / Line 1: @@
 ==Description==
-A [http://en.wikipedia.org/wiki/Service_(systems_architecture) Service] is the provisioning of one or more functions ([[Operation|Operations]]) within a [[System]] environment. It refers to a group of software components that perform a specific business logic.
+A [http://en.wikipedia.org/wiki/Service_(systems_architecture) Service] is the container of one or more workflow ([[Operation|Operations]]). It refers to a group of software components that perform a specific business logic.
 =={{VULCON}} / {{GVESB}} Configuration==
-A {{GVESB}}'s service is identified by a unique name (id-service), belongs to a [[group]] and has an activation state and a number of clients enabled at its invocation (section [[Client]]).
+A {{GVESB}}'s service is identified by a unique name (id-service), belongs to a [[group]] and has an activation state.
 You can configure the conditions applied to the routing of Service's flows ([[Conditions]] section).