Difference between revisions of "Client"

From GreenVulcano Wiki
Jump to: navigation, search
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.
 
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.
 
The definitions used here are valid for all flows associated with pair <service,client> and override any global definitions in the 'Service' section.

Revision as of 12:14, 1 February 2012

Description

Defines a service's client.

VulCon / GV Console 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 GreenVulcano® ESB.

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 GreenVulcano® ESB 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 <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.

The Client Element is used by Clients. Its attributes are:

  • id-system: Name of the client.
    Before you can specify this parameter, you must configure the client system in the Systems section.
  • statistics: Indicates whether the calculation of statistics for the pair <service,client> is enabled or not.
    • on: enables the calculation of statistics
    • off: disables the calculation of statistics. Default value
  • 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 GreenVulcano® ESB. 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 GreenVulcano® ESB.