Difference between revisions of "GVServices"

From GreenVulcano Wiki
Jump to: navigation, search
(→‎Description)
 
(One intermediate revision by the same user not shown)
Line 2: Line 2:
  
 
GVServices is the {{GVESB}} Core configuration root element.
 
GVServices is the {{GVESB}} Core configuration root element.
 +
 +
=={{GVESB}} Configuration==
 +
 +
GVService element is visualized and can be configured from the [[The_views|{{VULCON}} Core view]] or from the [[Parameter|{{GVCONSOLE}} Parameter Area]].
 +
 +
The GVServices Element is used by [[GVCore]]. The following table shows its attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| type || fixed || This attribute must assume the value '''module'''
 +
|-
 +
| name || fixed || Module ID always set to '''SERVICES'''
 +
|}
  
 
Contains three subsections:
 
Contains three subsections:
Line 9: Line 22:
  
 
Might contain also the sub-elements:
 
Might contain also the sub-elements:
−
* Description
+
* [[Description]]
 +
* [[#BpelEngineConfiguration|BpelEngineConfiguration]]
 
* [[#Persistence|Persistence]]
 
* [[#Persistence|Persistence]]
  
−
The GVServices Element is used by [[GVCore]]. Its attributes are:
+
===Management===
−
* ''type'': module.
+
 
−
* ''name'': Module ID always set to 'SERVICES'.
+
The Management Element contains the configuration of management components.
 +
 
 +
It is a GVServices sub-element and has the attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| call-administration-on-init || optional || Defines if monitoring components on cluster operation can contact the administration node on initialization. <br/> The attribute's default value is '''no''' and its admitted values are:
 +
* yes
 +
* no
 +
|}
 +
 
 +
===BpelEngineConfiguration===
 +
 
 +
The BpelEngineConfiguration Element is used by: [[GVServices]].
 +
 
 +
The following table shows the BpelEngineConfiguration element's attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| deployMentUnitProcess || required || Defines parameter configuration for Bpel process.
 +
|-
 +
| startServer || required || Start Engine Bpel.
 +
The attribute's admitted values are:
 +
* true
 +
* false
 +
The attribute's value cannot be null.
 +
|-
 +
| transactionTimeout || required || Timeout Transaction.
 +
|}
 +
 
 +
Its sub-elements are:
 +
* [[Description]]
 +
* [[#EngineProperties|EngineProperties]]
 +
 
 +
====EngineProperties====
 +
 
 +
Bpel Engine properties.
 +
 
 +
The EngineProperties Element is used by: [[#BpelEngineConfiguration|BpelEngineConfiguration]].
 +
 
 +
The following table shows the EngineProperties element's attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| name || required || Property name.
 +
The attribute's value cannot be null.
 +
|-
 +
| value || required || Property value.
 +
|}
 +
 
 +
Might contain the sub-element:
 +
* [[Description]]
  
−
==Management==
+
===Persistence===
  
−
The Management Element contains the configuration of management components. It is a GVServices subelement and has the attributes:
+
The Persistence Element is only used by [[GVServices]]. It has the attributes:
−
* call-administration-on-init: Defines if monitoring components on cluster operation can contact the administration node on initialization. <br/> The attribute's default value is '''no''' and its admitted values are:
+
{|class="gvtable"
−
** yes
+
! Attribute !! Type !! Description
−
** no
+
|-
 +
| jdbc-connection-name || required || The attribute's value cannot be null.
  
−
==Persistence==
+
|-
 +
| enabled || required || Its  admitted values are:
 +
* true
 +
* false
 +
|}
  
−
The Persistence Element is only used by GVServices.It has the attributes:
+
Its sub-elements are:
−
* ''jdbc-connection-name''
+
* Description
−
* ''enabled'': Its  admitted values are:
+
* [[#SequenceSQL|SequenceSQL]]
−
** true
 
−
** false
 
  
−
Its subelements are:
+
====SequenceSQL====
−
* Description,
 
−
* SequenceSQL.
 
  
−
===SequenceSQL===
+
The SequenceSQL Element is only used by Persistence.
  
−
The element value can't be null. The SequenceSQL Element is only used by Persistence.
+
The element value cannot be null.  
  
−
==Groups==
+
===Groups===
  
−
This section defines the {{GVESB}} services groups. The Groups Element is used by GVServices.
+
This section defines the {{GVESB}} services groups.  
  
−
It has the subelement:
+
It has the sub-elements:
−
* Description,
+
* [[Description]]
−
* [[Group]].
+
* [[Group]]
  
−
==Services==
+
===Services===
  
 
This configuration section defines the services provided by {{GVESB}}, systems entitled to rely on these services, which workflows can be invoked and which operations should be taken as a result of invocations from the clients.
 
This configuration section defines the services provided by {{GVESB}}, systems entitled to rely on these services, which workflows can be invoked and which operations should be taken as a result of invocations from the clients.
Line 55: Line 121:
 
You can insert into this section of the configuration also documentary information that have no impacts on {{GVESB}} operations, but that can enrich the reports produced.
 
You can insert into this section of the configuration also documentary information that have no impacts on {{GVESB}} operations, but that can enrich the reports produced.
  
−
The Services Element is used by GVServices.
+
The Services Element is used by [[GVServices]].
  
−
It has the subelements:
+
It has the sub-elements:
−
* Description,
+
* [[Description]]
−
* [[Service]].
+
* [[Service]]

Latest revision as of 12:46, 10 April 2012

Description

GVServices is the GreenVulcano® ESB Core configuration root element.

GreenVulcano® ESB Configuration

GVService element is visualized and can be configured from the VulCon Core view or from the GV Console Parameter Area.

The GVServices Element is used by GVCore. The following table shows its attributes:

Attribute Type Description
type fixed This attribute must assume the value module
name fixed Module ID always set to SERVICES

Contains three subsections:

  • Management
  • Groups: contains the configurations of Services groups.
    A group can handle the activation state of multiple services at once.
  • Services: contains the configuration of GreenVulcano® ESB Services.

Might contain also the sub-elements:

Management

The Management Element contains the configuration of management components.

It is a GVServices sub-element and has the attributes:

Attribute Type Description
call-administration-on-init optional Defines if monitoring components on cluster operation can contact the administration node on initialization.
The attribute's default value is no and its admitted values are:
  • yes
  • no

BpelEngineConfiguration

The BpelEngineConfiguration Element is used by: GVServices.

The following table shows the BpelEngineConfiguration element's attributes:

Attribute Type Description
deployMentUnitProcess required Defines parameter configuration for Bpel process.
startServer required Start Engine Bpel.

The attribute's admitted values are:

  • true
  • false

The attribute's value cannot be null.

transactionTimeout required Timeout Transaction.

Its sub-elements are:

EngineProperties

Bpel Engine properties.

The EngineProperties Element is used by: BpelEngineConfiguration.

The following table shows the EngineProperties element's attributes:

Attribute Type Description
name required Property name.

The attribute's value cannot be null.

value required Property value.

Might contain the sub-element:

Persistence

The Persistence Element is only used by GVServices. It has the attributes:

Attribute Type Description
jdbc-connection-name required The attribute's value cannot be null.
enabled required Its admitted values are:
  • true
  • false

Its sub-elements are:

SequenceSQL

The SequenceSQL Element is only used by Persistence.

The element value cannot be null.

Groups

This section defines the GreenVulcano® ESB services groups.

It has the sub-elements:

Services

This configuration section defines the services provided by GreenVulcano® ESB, systems entitled to rely on these services, which workflows can be invoked and which operations should be taken as a result of invocations from the clients.

For each triple <service, client, operation> is instantiated a flow defined in the Flow section. Here you configure the activation state of statistics, input / output services, checks, and other operational details.

You can insert into this section of the configuration also documentary information that have no impacts on GreenVulcano® ESB operations, but that can enrich the reports produced.

The Services Element is used by GVServices.

It has the sub-elements:

Retrieved from "https://gvwiki.greenvulcano.com/gvwiki/index.php?title=GVServices&oldid=3300"