Difference between revisions of "System"

From GreenVulcano Wiki
Jump to: navigation, search
m ({{VULCON}} / {{GVESB}} Configuration)
({{VULCON}} / {{GVESB}} Configuration)
 
(12 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
=={{VULCON}} / {{GVESB}} Configuration==
 
=={{VULCON}} / {{GVESB}} Configuration==
  
A ''System'' is identified by an univocal name, has an activation state, and a number of communication interfaces grouped in [[channel|channels]].
 
Moreover, in order to simplify operational management, for each system you can define a list of contacts (see below).
 
  
Its attributes are:
+
A '''System''' is composed of one or more '''Channels''' and is identified by a unique name. The '''System''' entity groupes the operations made ​​toward an external application. The '''System''' can be activated or deactivated switching the field '''system-activation'''. Activating a '''System''' means that all its '''Operations''' are activated. When a '''Service''' invokes an operation at runtime it receives an Exception in case the '''Operation''' is deactivated.
 +
Moreover, in order to simplify operational management, for each '''System''' you can define a list of contacts (see below).
 +
 
 +
'''System''' attributes:
 
{|class="gvtable"
 
{|class="gvtable"
 
! Attribute !! Type !! Description
 
! Attribute !! Type !! Description
Line 20: Line 21:
 
|}
 
|}
  
and its subelements:
+
'''System''' subelements:
 
* Description
 
* Description
 
* [[Channel]]
 
* [[Channel]]
* Contact (see bellow)
+
* [[#Contact|Contact]]
  
 
The configurations of all systems interfaced to {{GVESB}} are contained in the element '''Systems'''.
 
The configurations of all systems interfaced to {{GVESB}} are contained in the element '''Systems'''.
Line 36: Line 37:
  
 
It has the following attributes:
 
It has the following attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| first-name || required || Contact first name
 +
|-
 +
| last-name || required || Contact last name
 +
|-
 +
| role || optional || Contact role
 +
|-
 +
| mobile || optional || Contact mobile
 +
|-
 +
| telephone || optional || Contact telephone
 +
|-
 +
| e-mail || optional || Contact email
 +
|}
  
* ''first-name''
+
{{VOTE}}
* ''last-name''
 
* ''role''
 
* ''mobile''
 
* ''telephone''
 
* ''e-mail''
 

Latest revision as of 17:11, 26 February 2013

Description

The System element is any system or application interconnected with GreenVulcano® ESB.

VulCon / GreenVulcano® ESB Configuration

A System is composed of one or more Channels and is identified by a unique name. The System entity groupes the operations made ​​toward an external application. The System can be activated or deactivated switching the field system-activation. Activating a System means that all its Operations are activated. When a Service invokes an operation at runtime it receives an Exception in case the Operation is deactivated. Moreover, in order to simplify operational management, for each System you can define a list of contacts (see below).

System attributes:

Attribute Type Description
id-system required System unique identifier.
system-activation optional Activation status of system. The status can be:
  • on: system services are active.
  • paused: system services are inactive, the asynchronous client requests are taken in charge by GreenVulcano® ESB.
    They will be served when the system returns on state 'on'.
  • off: system services are inactive and no request is taken in charge by GreenVulcano® ESB.
    The current version does not implement the state 'paused'. The attribute's default value is: on.

System subelements:

The configurations of all systems interfaced to GreenVulcano® ESB are contained in the element Systems.

Contact

This element identifies a contact for an external system. The information contained in this element are optional and have no impact on the GreenVulcano® ESB functioning.

Such information may be used to produce reports.

The Contact Element is used only by System.

It has the following attributes:

Attribute Type Description
first-name required Contact first name
last-name required Contact last name
role optional Contact role
mobile optional Contact mobile
telephone optional Contact telephone
e-mail optional Contact email

{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>