Client - Revision history

G.iannello: /* Description */

2012-03-01T15:51:29Z

‎Description

G.dimaio at 16:57, 27 February 2012

2012-02-27T16:57:56Z

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

2012-02-27T12:33:01Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

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

2012-02-27T12:32:33Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

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

2012-02-27T12:31:51Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

C.romano: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-01T13:40:31Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

C.romano at 13:39, 1 February 2012

2012-02-01T13:39:59Z

C.romano at 12:14, 1 February 2012

2012-02-01T12:14:01Z

Anonymous at 10:22, 1 February 2012

2012-02-01T10:22:58Z

Anonymous: Created page with "==Description== Defines a service's client. =={{VULCON}} / {{GVCONSOLE}} Configuration== Before you can designate a system as a client of a service, you must configure the [[s..."

2012-01-31T22:26:37Z

Created page with "==Description== Defines a service's client. =={{VULCON}} / {{GVCONSOLE}} Configuration== Before you can designate a system as a client of a service, you must configure the [[s..."

New page

==Description==

Defines a service's client.

=={{VULCON}} / {{GVCONSOLE}} Configuration==

Before you can designate a system as a client of a service, you must configure the [[system]] in the [[Systems]] section.

Note that client means the system used by field 'system' of GVBuffer (the data buffer for {{GVESB}}.

This field contains the name of the client system that began transaction. Even in the delivery of responses by server systems (Call-Back), this field will contain the name of the client that had made the request.

In sub-sections will define all {{GVESB}} operations enabled for the couple <[[service]],[[client]]>. Basically you define workflows for each triple <[[service]],[[client]],[[operation]]>.

You can configure routing conditions applied to flows for the pair <service,client> (Conditions]] section).

The definitions used here are valid for all flows associated with pair <service,client> and override any global definitions in the 'Service' section.

The Client Element is used by: Clients. Its attributes are:
* ''id-system'': Name of the client.

@@ Line 1: / Line 1: @@
 ==Description==
-Defines a service's client. Before you can designate a system as a client of a service, you must configure the [[system]] in the Systems section.
+Defines a service client. Before you can designate a system as a "client of a service", you must configure the [[system]] in the Systems section.
-Note that client means the system used by field 'system' of [[GVBuffer]] (the data buffer for {{GVESB}}, and this value can be used in flow's routing conditions.
+Note that client means "the system used by field 'system' of [[GVBuffer]]" (the data buffer for {{GVESB}}), and this value can be used in flows routing conditions.
-This field contains the name of the client system that began transaction. Even in the delivery of responses by server systems (Call-Back), this field will contain the name of the client that had made the request.
+This field contains the name of the client system that began the transaction. Even in the delivery of responses by server systems (Call-Back), this field will contain the name of the client that made the request.

@@ Line 18: / Line 18: @@
 The Client Element is used by Clients. Its attributes are:
-* ''id-system'': Name of the client. <br/> Before you can specify this parameter, you must configure the client system in the [[GVSystems | Systems]] section.
+* ''id-system'': Name of the client. <br/> Before you can specify this parameter, you must configure the client system in the [[System | Systems]] section.
 * ''statistics'': Indicates whether the calculation of statistics for the service is enabled or not.

@@ Line 13: / Line 13: @@
 In sub-sections will define all {{GVESB}} operations enabled for the <[[service]]>. Basically you define workflows for each couple <[[service]],[[operation]]>.
-You can configure routing conditions applied to flows for the <service> (Conditions]] section).
+You can configure routing conditions applied to flows for the <service> ([[Conditions]] section).
 The definitions used here are valid for all flows associated with service and override any global definitions in the 'Service' section.
@@ Line 25: / Line 25: @@
 * ''system-activation'': Activation status of service's client. The status can be:
 ** on: service's client is active. Default value.
-** paused: service's client is inactive, the asynchronous client's requests are tacken in charge by {{GVESB}}. They will be served when the service's client return on state 'on'. The current version does not implement it.
+** paused: service's client is inactive, the asynchronous client's requests are taken in charge by {{GVESB}}. They will be served when the service's client return on state 'on'. The current version does not implement it.
 ** off: service's client is inactive and no request are taken in charge by {{GVESB}}.

@@ Line 5: / Line 5: @@
 =={{VULCON}} / {{GVCONSOLE}} Configuration==
-Before you can designate a system as a client of a service, you must configure the [[system]] in the [[GVSystems|Systems]] section.
+Before you can designate a system as a client of a service, you must configure the [[system]] in the Systems section.
-Note that client means the system used by field 'system' of GVBuffer (the data buffer for {{GVESB}}.
+Note that client means the system used by field 'system' of [[GVBuffer]] (the data buffer for {{GVESB}}.
 This field contains the name of the client system that began transaction. Even in the delivery of responses by server systems (Call-Back), this field will contain the name of the client that had made the request.

@@ Line 20: / Line 20: @@
 * ''id-system'': Name of the client. <br/> Before you can specify this parameter, you must configure the client system in the [[GVSystems | Systems]] section.
-* ''statistics'': Indicates whether the calculation of statistics for the pair <[[service]],client> is enabled or not.
+* ''statistics'': Indicates whether the calculation of statistics for the service is enabled or not.
 ** on: enables the calculation of statistics
 ** off: disables the calculation of statistics. Default value

@@ Line 11: / Line 11: @@
 This field contains the name of the client system that began transaction. Even in the delivery of responses by server systems (Call-Back), this field will contain the name of the client that had made the request.
-In sub-sections will define all {{GVESB}} operations enabled for the couple <[[service]],[[client]]>. Basically you define workflows for each triple <[[service]],[[client]],[[operation]]>.
+In sub-sections will define all {{GVESB}} operations enabled for the couple <[[service]],[[client]]>. Basically you define workflows for each couple <[[service]],[[operation]]>.
-You can configure routing conditions applied to flows for the pair <service,client> (Conditions]] section).
+You can configure routing conditions applied to flows for the <service> (Conditions]] section).
 The definitions used here are valid for all flows associated with pair <service,client> and override any global definitions in the 'Service' section.