GreenVulcano Wiki - User contributions [en]

Template:GVVersion

2012-02-27T16:30:37Z

C.ortenzi:

{| style="border: 1px solid #888888; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse:collapse"
| style="padding: .1em .3em;" | Version:
| style="padding: .1em .3em; border: 3px solid #e30; text-align: center;" | <span style="font-weight: bold; font-size: 180%;">{{{version|X.X}}}</span>
|}<noinclude>

<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows the valid {{GVESB}} version for the paragraph. It appears on the right side of the window in a bordered text field.
==Example==
{{GVVersion|version=≥3.1}}
If the paragraph is valid for {{GVESB}} version 3.1 and later, you should write this.

<nowiki>{{GVVersion|scope=&ge;|version=3.1}}</nowiki>
==Usage==
<syntaxhighlight lang="xml">{{GVVersion[|scope = >|≥|<|≤][|version = version number]}}</syntaxhighlight>
*''scope'': is a symbol showing which scope is to be applied for the version. For instance, a &ge; symbol (≥) states that the paragraph is appliable for {{GVESB}} 3.1 and later. If omitted, the paragraph is valid only for the version.
*''version'': is the version to be shown.
</div>
<noinclude>

Template:GVVersion

2012-02-27T16:30:18Z

C.ortenzi:

{| style="border: 1px solid #888888; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse:collapse"
| style="padding: .1em .3em;" | Version:
| style="padding: .1em .3em; border: 3px solid #e30; text-align: center;" | <span style="font-weight: bold; font-size: 180%;">{{{version|X.X}}}</span>
|}<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows the valid {{GVESB}} version for the paragraph. It appears on the right side of the window in a bordered text field.
==Example==
{{GVVersion|version=≥3.1}}
If the paragraph is valid for {{GVESB}} version 3.1 and later, you should write this.

<nowiki>{{GVVersion|scope=&ge;|version=3.1}}</nowiki>
==Usage==
<syntaxhighlight lang="xml">{{GVVersion[|scope = >|≥|<|≤][|version = version number]}}</syntaxhighlight>
*''scope'': is a symbol showing which scope is to be applied for the version. For instance, a &ge; symbol (≥) states that the paragraph is appliable for {{GVESB}} 3.1 and later. If omitted, the paragraph is valid only for the version.
*''version'': is the version to be shown.
</div>
<noinclude>

Template:GVVersion

2012-02-27T15:57:31Z

C.ortenzi:

Template:GVVersion

2012-02-27T15:46:45Z

C.ortenzi: Created page with "{| style="border: 1px solid #888888; float: right; font-size: 80%; margin: 0 0 .5em .5em; line-height: 1.2; text-align: right; border-collapse:collapse" | style="padding: .1em .3..."

Template:L VULCON

2012-02-27T15:24:38Z

C.ortenzi:

[[VulCon]]<sup>®</sup><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template provides a link to GreenVulcano graphical tool page. You should use it within this wiki everytime you need to insert a link to this product.
==Example==
In order to insert a link to GreenVulcano graphical tool page you should write this:

<nowiki>{{L_VULCON}}</nowiki>

and you will get:

{{L_VULCON}}
==Usage==
This template does not require parameters.
</div>
<noinclude>

Template:VULCON

2012-02-27T15:22:20Z

C.ortenzi:

VulCon<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano graphical tool name with correct font and color formatting. You should use it within this wiki everytime you need to mention the product. If you need to insert a link to the product, you should use [[Template:L_VULCON]] instead.
==Example==
In order to show GreenVulcano graphical tool name, you should write this:

<nowiki>{{VULCON}}</nowiki>

and you will get:

{{VULCON}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T15:16:49Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB product name with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you should write this:

<nowiki>{{GVESB}}</nowiki>

and you will get:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVCONSOLE

2012-02-27T15:15:21Z

C.ortenzi:

GV Console<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano console product name with correct font and color formatting. You should use it within this wiki everytime you need to mention the product. If you need to insert a link to the product, you should use [[Template:L_GVCONSOLE]] instead.
==Example==
In order to show GreenVulcano console product name, you should write this:

<nowiki>{{GVCONSOLE}}</nowiki>

and you will get:

{{GVCONSOLE}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:L GVCONSOLE

2012-02-27T15:14:27Z

C.ortenzi:

[[GV Console]]<sup>®</sup><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template provides a link to GreenVulcano console page. You should use it within this wiki everytime you need to insert a link to this product.
==Example==
In order to insert a link to GreenVulcano console page you should write this:

<nowiki>{{L_GVCONSOLE}}</nowiki>

and you will get:

{{L_GVCONSOLE}}
==Usage==
This template does not require parameters.
</div>
<noinclude>

Template:GVCONSOLE

2012-02-27T15:11:30Z

C.ortenzi:

GV Console<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano console product name with correct font and color formatting. You should use it within this wiki everytime you need to mention the product. If you need to insert a link to the product, you should use [[Template:L_GVCONSOLE]] instead.
==Example==
In order to show GreenVulcano console product name, you shoukd write this:

<nowiki>{{GVCONSOLE}}</nowiki>

and you will get:

{{GVCONSOLE}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T15:07:43Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB product name with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

and you will get:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T15:04:07Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

and you will get:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T15:02:55Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T15:02:24Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>
a
</noinclude>

Template:GVESB

2012-02-27T15:01:51Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span><noinclude>a</noinclude>

Template:GVESB

2012-02-27T14:57:32Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>

Template:GVESB

2012-02-27T14:56:58Z

C.ortenzi:

<includeonly><span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span></includeonly>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>
==Usage==
This template does not require parameters.
</div>

Template:GVESB

2012-02-27T14:56:35Z

C.ortenzi:

<includeonly><span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span></includeonly>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>

Template:GVESB

2012-02-27T14:56:11Z

C.ortenzi:

<includeonly><span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span></includeonly>

<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>

Template:GVESB

2012-02-27T14:53:42Z

C.ortenzi:

<includeonly><span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span></includeonly>

Template:GVESB

2012-02-27T14:52:42Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>

Template:GVESB

2012-02-27T14:52:16Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
</noinclude>

Template:GVESB

2012-02-27T14:51:52Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
==Template documentation==
==Purpose==
==Example==
==Usage==
</noinclude>

Template:GVESB

2012-02-27T14:51:24Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
===Template documentation===
==Purpose==
==Example==
==Usage==
</noinclude>

Template:GVESB

2012-02-27T14:50:50Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>
==Usage==
This template does not require parameters.
</noinclude>

Template:GVESB

2012-02-27T14:50:08Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T14:49:17Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T14:48:22Z

C.ortenzi:

<includeonly><span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span></includeonly>

<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>

Template:GVESB

2012-02-27T14:44:24Z

C.ortenzi: Undo revision 2729 by C.ortenzi (talk)

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>

Template:GVESB

2012-02-27T14:43:16Z

C.ortenzi: Undo revision 2730 by C.ortenzi (talk)

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T14:42:26Z

C.ortenzi:

<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:GVESB

2012-02-27T14:41:36Z

C.ortenzi:

<span class="gvprodname">GreenVulcano<sup>®</sup> ESB</span>
<noinclude>
<div style="background-color: #ffe; border: 1px solid #888; padding:0.5em">
===Template documentation===
==Purpose==
This template shows GreenVulcano ESB logo with correct font and color formatting. You should use it within this wiki everytime you need to mention the product.
==Example==
In order to show GreenVulcano ESB product name, you shoukd write this:

<nowiki>{{GVESB}}</nowiki>

that generates the following output:

{{GVESB}}
==Usage==
This template does not require parameters.
</div>
</noinclude>

Template:Main Page/Overview

2012-02-16T10:28:29Z

C.ortenzi:

<div class="mainbox">
<h2>Overview</h2>
<div class="mainbox_content">
{{GVESB}} is an Enterprise Service Bus, [http://en.wikipedia.org/wiki/Open_source Open Source], fully developed by one of the most experienced [http://en.wikipedia.org/wiki/Enterprise_application_integration EAI] teams, derived from a deep understanding of the topic on vendor products and from the direct participation in implementations of ESB systems with very challenging design requirements:

* High transactions volume
* Large number of interconnected systems and different protocols supported
* Response in near real time
* Availability of technology adapters (Database, File, {{L_GVWS}}, e-Mail, etc)
* Availability of application adapters
* Powerful and flexible [[Data transformation]] engine

{{GVESB}} is a Java-based software built to support complex [http://en.wikipedia.org/wiki/Service-oriented_architecture SOA] architectures. Its [[multi-layer architecture]] allows an unlimited customization, solving most of enterprise integration issues like exchanging data between existing systems. Many [[plugins]] and [[adapters]] are already available for a huge flexibility.

See also: [[License]]
</div>
</div>

License

2012-02-16T10:19:40Z

C.ortenzi:

==Introduction==
{{GVESB}} is available under three different distributions: ''Community'', ''Enterprise'' and ''Full Enterprise''. The ''Community'' distribution is recommended for test and integrate ESB capabilities, whereas ''Enterprise'' and ''Full Enterprise'' distributions are suitable for production use.
For more information about distributions differentiation, please visit our [http://www.greenvulcano.com/en/download.html offering] page.
==Community license==
{{GVESB}} ''Community'' is released under [http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html LGPL] license. Also, it includes the following third-party software as part of the source code, examples, or as dependencies:

{| class="gvtable"
!Name||License
|-
|Avalon-Frame-Api||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axiom-api||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axiom-Impl||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axis2-adb||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axis2-kernel||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axis2-transport-http||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Axis2-transport-local||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|axis||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-anim||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-awt||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-bridge||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-css||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-dom||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-extension||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-ext||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-gvt||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-parser||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-script||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-svg-dom||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-svggen||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-transcoder||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-util||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Batik-xml||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Bcprov-jdk16||[http://www.bouncycastle.org/licence.html Legion of the Bouncy Castle]
|-
|Common-bean-utils||[http://apache.org/licenses/LICENSE-1.1 Apache 1.1]
|-
|Common-cli||[http://apache.org/licenses/LICENSE-1.1 Apache 1.1]
|-
|Common-codec||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-collection||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-dbcp||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-digester||[http://apache.org/licenses/LICENSE-1.1 Apache 1.1]
|-
|Common-discovery||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-fileupload||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-http-client||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-io||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Common-logging-api||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Commons-logging||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Commons-modeler||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Commons-net||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Commons-pool||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|dom4j||[http://dom4j.sourceforge.net/dom4j-1.6.1/license.html DOM4J]
|-
|fop||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Geronimo-activation||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Geronimo-stax||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|hapi||[http://www.mozilla.org/MPL/MPL-1.1.html Mozilla Pub 1.1]
|-
|hsql||[http://hsqldb.org/web/hsqlLicense.html HSQL]
|-
|Http-core||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|hypersonic||[http://hsqldb.org/web/hsqlLicense.html HSQL]
|-
|ICU4J||[https://jazz.net/downloads/pages/rational-team-concert/3.0/M4/license/early_release_license_files/ICU4J-license.html ICU4j]
|-
|javassist||[http://www.mozilla.org/MPL/MPL-1.1.html Mozilla Pub 1.1]
|-
|Jaxb-api||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|Jaxb-impl||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|jaxen||[https://serviceregister.overheid.nl/soa/systinet/platform/doc/legal/using.jaxen.licence.html jaxen Licence]
|-
|Jaxws-api||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|Jaxws-rt||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|jdom||[https://serviceregister.overheid.nl/soa/systinet/platform/doc/legal/legal.notices.jdom.html Jdom Licence]
|-
|Joda-time||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Jsch||[http://www.gnu.org/copyleft/gpl.html GNU GPL]
|-
|js||[http://www.mozilla.org/MPL/MPL-1.1.html Dual: Mozilla 1.1]
|-
|juddi||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|jxl||[http://www.gnu.org/copyleft/gpl.html GNU GPL]
|-
|mail||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|mex||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|mimepull||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|Mysql-connector-java||[http://www.gnu.org/copyleft/gpl.html GNU GPL]
|-
|neethi||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|ognl||[http://svn.opensymphony.com/svn/opensymphony/trunk/www/license.html OpenSimphony Software 1.1]
|-
|ojdbc||[http://www.oracle.com/technetwork/licenses/standard-license-152015.html OTN]
|-
|opensaml||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|openws||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|quartz||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|rampart||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|resolver||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|rmiio||[http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html GNU LGPL]
|-
|Saaj-api||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|Saaj-impl||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|saxon||[http://www.mozilla.org/MPL/MPL-1.1.html Mozilla Pub 1.1]
|-
|scout||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|sjsxp||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|slf4j||[http://www.slf4j.org/license.html slf4j]
|-
|tax-api||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Stax-ex||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|streambuff||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|Uddi-ws||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|velocity||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Woden-api||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Woden-impl||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|wsdl4j||[http://www.opensource.org/licenses/cddl1.php CDDL Licence]
|-
|wss4j||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Wstx-asl||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|xalan||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|xerceslmpl||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xml-apis-ext||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xml-apis||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xmlgrafics-commons||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xml-resolver||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xml-Schema||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|Xml-sec||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|xmltooling||[http://velocity.apache.org/engine/devel/license.html Apache 2.0]
|-
|xom||[http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html GNU LGPL]
|}

GVBuffer

2012-02-14T16:06:00Z

C.ortenzi: /* Structure */

==Description==
The {{GVBUFFER}} data structure (it.greenvulcano.gvesb.buffer.GVBuffer) represents the container that carries information within the components of {{GVESB}}:

Inbound Adapter <-> Core <-> Plug-in outbound

The business information are inserted in the 'object' field, the {{GVBUFFER}} data structure can contains any data type: JMS messages, SOAP Envelope, Document, strings, byte arrays, etc.
The data structure contains properties specific of {{GVESB}} platform:
*[[Service|service]]: service invoked
*[[System|system]]: the system client identifier that invokes the service
*[[Id|id]]: the identifier of the particular transaction (eg, to identify the response of a specific asynchronous request), the id is unique for the all service execution
*retCode: return code of the service invocation (possibly defined by the client/server contract for a specific service)
The data structure also offers the ability to define and modify some service specific properties within the workflow, to be used by JavaScript and/or OGNL and in evaluating routing conditions.

==Structure==
[[File:GVBuffer.png|thumb|GVBuffer structure]]

All {{GVBUFFER}}s have the same shape, based on three primary components (see the image):
*Platform fields, those fields contain all information to indentify the flow
*Properties, this section contains an object thats maps keys to values. This object cannot contain duplicate keys; each key can map to at most one value.
*Payload, This buffer section contains the service data

A single service can have more {{GVBUFFER}} instances in its [[Execution Context]], each operation (node) in a {{GVESB}} service can declare a {{GVBUFFER}} as input and/or output. A {{GVBUFFER}} in the [[Execution Context]] can be also overwritten by another operation.

Following the {{GVBUFFER}} public fields/methods:
<syntaxhighlight lang="java5">
/**
* Constructs a GVBuffer with all fields.
* @throws GVException if system or service or id are null
*/
public GVBuffer(String system, String service, Id id, int retCode, Object object) throws GVException

/**
* Construct a GVBuffer with system, service, id.
* @throws GVException if system or service or id are null
*/
public GVBuffer(String system, String service, Id id) throws GVException

/**
* Construct a GVBuffer with system and service.
* @throws GVException if system or service are null
*/
public GVBuffer(String system, String service) throws GVException

/**
* Default constructor.
*/
public GVBuffer() throws GVException

/**
* Copy constructor.
*/
public GVBuffer(GVBuffer toCopy)

/**
* @return the system
*/
public String getSystem()

/**
* @return the service
*/
public String getService()

/**
* @return the id
*/
public Id getId()

/**
* @return the retCode
*/
public int getRetCode()

/**
* @return the internal object
*/
public Object getObject()

/**
* @param system
* @throws GVException if system is null
*/
public void setSystem(String system) throws GVException

/**
* @param service
* @throws GVException if service is null
*/
public void setService(String service) throws GVException

/**
* @param id
* @throws GVException if id is null
*/
public void setId(Id id) throws GVException

/**
* @param retCode
*/
public void setRetCode(int retCode)

/**
* @param object
*/
public void setObject(Object object)

/**
* @return properties.
*/
private Map<String, String> getProperties()

/**
* @param name
* @return the property value
*/
public String getProperty(String name)

/**
* @return the property names iterator
*/
public Iterator<String> getPropertyNamesIterator()

/**
* @return the property names set
*/
public Set<String> getPropertyNamesSet()

/**
* @return the property names as array of string
*/
public String[] getPropertyNames()

/**
* @param property
* @param value
* @throws GVException if name or value are null
*/
public void setProperty(String property, String value) throws GVException

/**
* @param property
*/
public void removeProperty(String property)

/**
* @param props
*/
public void removeProperties(Map<String, String> props)

</syntaxhighlight>

====Example====
In the example below is shown a flow composed of four nodes. The first one uses as input {{GVBUFFER}} associated to the identifier 'to_process'; the result of the node processing will be into another {{GVBUFFER}} associated to the 'read_data' identifier. Subsequent nodes will work on the same buffer ('read_data'), which will be the output parameter of the <GVEndNode>: so information in it will be delivered to the client.

<syntaxhighlight lang="XML">
<Flow first-node="extract_data" point-x="19" point-y="137">
<GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
dump-in-out="false" id="extract_data"
id-system="CREDIT" input="to_process"
next-node-id="add_ext" op-type="call"
operation-name="CreditCards" output="read_data"
point-x="149" point-y="140" type="flow-node"/>
<ChangeGVBufferNode class="it.greenvulcano.gvesb.core.flow.ChangeGVBufferNode"
dump-in-out="false" id="add_ext" input="read_data"
next-node-id="send_email"
op-type="change GVBuffer" point-x="309"
point-y="137" type="flow-node">
<ChangeGVBuffer clear-data="false">
<PropertyDef name="FILE_EXT"
value="decode{{ognl{{property['BIRT_REPORT_TYPE']}}::excel::xls::pdf}}"/>
</ChangeGVBuffer>
</ChangeGVBufferNode>
<GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
dump-in-out="false" id="send_email"
id-system="CREDIT" input="read_data"
next-node-id="end" op-type="call"
operation-name="SendEmailSVCResponse"
output="read_data" point-x="473" point-y="137"
type="flow-node"/>
<GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode"
end-business-process="yes" id="end" op-type="end"
output="read_data" point-x="671" point-y="137"
type="flow-node">
<ChangeGVBuffer clear-data="true"/>
</GVEndNode>
</Flow>
</syntaxhighlight>

Example of {{GVBUFFER}} manipulation through JavaScript:
<syntaxhighlight lang="javascript">
// data is a GVBuffer instance

// suppose data.object contains a java.lang.String
var obj = data.getObject();

// set a service specific property
data.setProperty("STR_LENGTH", obj.length());

// set a platform property
data.setRetCode(-1000);

// modify the payload
data.setObject(obj.getBytes());
</syntaxhighlight>

The same example built with OGNL.
The comments aren't allowed in OGNL scripts, so are defined externally:
<nowiki>#</nowiki>input is a GVBuffer instance, suppose <nowiki>#</nowiki>input.object contains a java.lang.String, then set a service specific property, and finally set a platform property
<syntaxhighlight lang="javascript">
#obj = #input.object,
#input.property['STR_LENGTH'] = #obj.length(),
#input.retCode = -1000
</syntaxhighlight>

Main Page

2012-02-10T15:55:06Z

C.ortenzi:

__NOTOC__
<div align="center">
<p style="font-size: 2em">Welcome to {{GVESB}} Wiki</p>
<p>the place where you can find all information about our [http://en.wikipedia.org/wiki/Enterprise_service_bus ESB].</p>
<p>Start exploring {{GVESB}} '''[[Basic concepts]]''' or follow the links below!</p>
{|cellspacing="0"
|valign="top" width="50%"|
{{Main Page/Overview}}
{{Main Page/Installation}}
{{Main Page/Examples}}
|valign="top" align="left" width="50%"|
{{Main Page/VulCon}}
{{Main Page/GVConsole}}
|}
</div>
__NOEDITSECTION__

Main Page

2012-02-10T15:53:20Z

C.ortenzi:

__NOTOC__
<div align="center">
<div style="font-size: 2em">Welcome to {{GVESB}} Wiki</div>
<div>the place where you can find all information about our [http://en.wikipedia.org/wiki/Enterprise_service_bus ESB].<br>
Start exploring {{GVESB}} '''[[Basic concepts]]''' or follow the links below!
</div>
{|cellspacing="0"
|valign="top" width="50%"|
{{Main Page/Overview}}
{{Main Page/Installation}}
{{Main Page/Examples}}
|valign="top" align="left" width="50%"|
{{Main Page/VulCon}}
{{Main Page/GVConsole}}
|}
</div>
__NOEDITSECTION__

Main Page

2012-02-10T15:50:40Z

C.ortenzi:

__NOTOC__
<div align="center">
<div style="font-size: 2em">Welcome to {{GVESB}} Wiki</div>
<div>
the place where you can find all information about our [http://en.wikipedia.org/wiki/Enterprise_service_bus ESB].<br>
Start exploring {{GVESB}} '''[[Basic concepts]]''' or follow the links below!
</div>
{|cellspacing="0"
|valign="top" width="50%"|
{{Main Page/Overview}}
{{Main Page/Installation}}
{{Main Page/Examples}}
|valign="top" align="left" width="50%"|
{{Main Page/VulCon}}
{{Main Page/GVConsole}}
|}
</div>
__NOEDITSECTION__

Main Page

2012-02-10T15:42:57Z

C.ortenzi:

__NOTOC__
<div align="center">
<div style="font-size: 2em">Welcome to {{GVESB}} Wiki</div>
the place where you can find all information about our [http://en.wikipedia.org/wiki/Enterprise_service_bus ESB].<br>
Start exploring {{GVESB}} '''[[Basic concepts]]''' or follow the links below!
<br />
{|cellspacing="0"
|valign="top" width="50%"|
{{Main Page/Overview}}
{{Main Page/Installation}}
{{Main Page/Examples}}
|valign="top" align="left" width="50%"|
{{Main Page/VulCon}}
{{Main Page/GVConsole}}
|}</div>
__NOEDITSECTION__

HL7

2012-02-09T16:51:53Z

C.ortenzi:

==Overview==
[http://www.hl7.org/ HL7] is a standard for the exchange, integration, sharing and retrieval of electronic health information. The standard defines how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world.

* Created to exchange information related to patients
* Standardizes the health system at clinical data exchange level
* Provides interfaces that allow the data flow through various systems
* Makes the health interoperability possible

==Message structure==
A HL7 message is composed by segments placed in a specific order. Each message is made up of a certain number of different segments (some are optional) that, combined, form a determined message type. A specific segment, identified by a code and a sequence number, represents a logic group of data fields and can be used only once within a specific message.

==HL7 Connector==
The {{GVESB}} HL7 connector enables the inbound and outbound connections using the HL7 protocol in its version 2.x.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of HL7 applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the HL7 standard used.

Basically the connector allows the virtualization of the input/output operations to a HL7 application, making available to the service definition process the interfaces able to hide all the technical details related to HL7 standard. It is possible to define the message exchange mode transforming with a mapping operation the HL7 messages in XML messages, using any schema. The composition of the integration flow will comprise a data structure close to the business model that user is adopting or anyway a user defined data structure.

The Inbound HL7 Connector allows the HL7 message creation (in the version 2.x) to be sent to one or more destinations; the Outbound HL7 Connector allows to choose what message type to accept and route. Multiple destinations can be chosen automatically basing on the HL7 filters specifications.

{{GVESB}} [[XML Data mapper | Data transformation]] feature allows fast creation of data transformation and mapping of the HL7 messages. The data mapping is made through simple "Drag and Drop" operations.

==Outbound HL7 connector==

Allows to define a call to a HL7 system defining the connection parameters and using the operation defined in an integration flow on {{GVESB}} through [[VulCon]].

These are the easy steps to follow to define a HL7 [[Channel]]:

Creation of a [[System]] and of a [[Channel]] with the definition of a [[Hl7-call]] [[Operation]]

[[File:1100px-ChannelHl7.png|thumb|center|512px]]

* host: hostname or IP address of the HL7 application waiting for the message
* name: [[Virtual Layer]] [[operation]] name
* port: application HL7 port
* timeout: channel HL7 timeout

Definition of a service for the invocation of the defined HL7 [[channel]]:

[[File:1100px-ServizioHl7.png|thumb|center|512px]]

The service defined in this way can be called in any way allowed by {{GVESB}} i.e. [[Web Services]], http, tcp-ip, etc.
The HL7 connector manages the messages transforming them into XML messages.

For the mapping from a generic message to a HL7 message it is possible to define a transformation map through [[XML Data mapper | VulCon]] tool.
To create the map, go to map configuration after having defined the xsd schema for the input message (incoming from any data source) and the output HL7 format:

[[File:TrasfHl7.png|thumb|center|512px]]

[[File:1100px-Mapping.png|thumb|center|512px]]

==Inbound HL7 Connector==
The inbound HL7 connector allows the definition of a HL7 message listener, associating the message reception to a {{GVESB}} [[service]].
The received HL7 message can be forwarded to one or more systems using any available {{GVESB}} enabled protocol: [[Web Services]], JDBC, email, ftp, etc. After every message received, a response message must be sent as acknowledge of the transaction (or abort). The connector enables the reply message creation with no applicative effort, mapping automatically the flow result with the ACK message to send back to the caller application.

The easy steps to follow to define an HL7 [[channel]] are the following:

Definition of a filter to apply to every received HL7 message:
[[File:1100px-ListnerHl7.png|thumb|center|512px]]

Association to a HL7 message to the [[service]] defined on {{GVESB}}:
[[File:1100px-ListenerServiceHl7.png|thumb|center|512px]]

HL7

2012-02-09T16:44:36Z

C.ortenzi:

==Overview==
[http://www.hl7.org/ HL7] is a standard for the exchange, integration, sharing and retrieval of electronic health information. The standard defines how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world.

* Created to exchange information related to patients
* Standardizes the health system at clinical data exchange level
* Provides interfaces that allow the data flow through various systems
* Makes the health interoperability possible

==Message structure==
A HL7 message is composed by segments placed in a specific order. Each message is made up of a certain number of different segments (some are optional) that, combined, form a determined message type. A specific segment, identified by a code and a sequence number, represents a logic group of data fields and can be used only once within a specific message.

==HL7 Connector==
The {{GVESB}} HL7 connector enables the inbound and outbound connections using the HL7 protocol in its version 2.x.
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of HL7 applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the HL7 standard used.

Basically the connector allows the virtualization of the input/output operations to a HL7 application, making available to the service definition process the interfaces able to hide all the technical details related to HL7 standard. It is possible to define the message exchange mode transforming with a mapping operation the HL7 messages in XML messages, using any schema. The composition of the integration flow will comprise a data structure close to the business model that user is adopting or anyway a user defined data structure.

The Inbound HL7 Connector allows the HL7 message creation (in the version 2.x) to be sent to one or more destinations; the Outbound HL7 Connector allows to choose what message type to accept and route. Multiple destinations can be chosen automatically basing on the HL7 filters specifications.

{{GVESB}} [[XML Data mapper | Data transformation]] feature allows fast creation of data transformation and mapping of the HL7 messages. The data mapping is made through simple "Drag and Drop" operations.

==Outbound HL7 connector==

Allows to define a call to a HL7 system defining the connection parameters and using the operation defined in an integration flow on {{GVESB}} through [[VulCon]].

These are the easy steps to follow to define a HL7 [[Channel]]:

Creation of a [[System]] and of a [[Channel]] with the definition of a [[Hl7-call]] [[Operation]]

[[Image:1100px-ChannelHl7.png]]

* host: hostname or IP address of the HL7 application waiting for the message
* name: [[Virtual Layer]] [[operation]] name
* port: application HL7 port
* timeout: channel HL7 timeout

Definition of a service for the invocation of the defined HL7 [[channel]]:

[[Image:1100px-ServizioHl7.png]]

The service defined in this way can be called in any way allowed by {{GVESB}} i.e. [[Web Services]], http, tcp-ip, etc.
The HL7 connector manages the messages transforming them into XML messages.

For the mapping from a generic message to a HL7 message it is possible to define a transformation map through [[XML Data mapper | VulCon]] tool.
To create the map, go to map configuration after having defined the xsd schema for the input message (incoming from any data source) and the output HL7 format:

[[Image:TrasfHl7.png]]

[[Image:1100px-Mapping.png]]

==Inbound HL7 Connector==
The inbound HL7 connector allows the definition of a HL7 message listener, associating the message reception to a {{GVESB}} [[service]].
The received HL7 message can be forwarded to one or more systems using any available {{GVESB}} enabled protocol: [[Web Services]], JDBC, email, ftp, etc. After every message received, a response message must be sent as acknowledge of the transaction (or abort). The connector enables the reply message creation with no applicative effort, mapping automatically the flow result with the ACK message to send back to the caller application.

The easy steps to follow to define an HL7 [[channel]] are the following:

Definition of a filter to apply to every received HL7 message:
[[Image:1100px-ListnerHl7.png]]

Association to a HL7 message to the [[service]] defined on {{GVESB}}:
[[Image:1100px-ListenerServiceHl7.png]]

Template:Main Page/VulCon

2012-02-09T16:23:35Z

C.ortenzi:

<div class="mainbox">
<h2>{{VULCON}}<sup>®</sup></h2>
<div class="mainbox_content">
{{GVESB}} Enterprise is provided of a powerful graphical designing tool {{VULCON}}<sup>®</sup>.
It can be used to easily build integrations among systems and to model service flows.

See {{L_VULCON}} section for further information and to understand how it is possible to create a [http://en.wikipedia.org/wiki/Service-oriented_modeling service oriented modeling approach], avoiding developers to write new soure code or manually edit any configuration file.

To create and deploy a new service with {{GVESB}} there's no need to write and test new Java code!

With the latest release of {{VULCON}}<sup>®</sup>, the graphical design tool for {{GVESB}}, integration will never be easier, since {{VULCON}}<sup>®</sup> is, by far, the easiest and most accessible way to build integration flows.
</div>
</div>

Template:Main Page/Installation

2012-02-09T16:22:47Z

C.ortenzi:

<div class="mainbox">
<h2>Installation</h2>
<div class="mainbox_content">
{{GVESB}}, entirely made in Java, provides full compatibility with most operating systems that support natively the Java Virtual Machine provided by Sun Microsystems. In order to install, configure and run {{GVESB}}, please follow next items:
* [[Compatible platforms]]
* [[Prerequisites]]
* [[Installation]]
* [[Post Installation]]
* [[Starting]] {{GVESB}}
* [[FAQs]]
</div>
</div>

Template:Main Page/Examples

2012-02-09T16:22:01Z

C.ortenzi:

<div class="mainbox">
<h2>Examples</h2>
<div class="mainbox_content">
The installation of {{GVESB}} is provided with several examples of service configuration. These examples are listed [[First GVESB Projects| here]]. In its sub-sections are described the configuration procedures for this services.

If you are already familiar with {{GVESB}}, you can step directly to the [[Advanced Test Projects]] that shows some examples of application.

If you want to test your own skills using {{GVESB}}, it is also provided the [[Test your self]] section. Here you can find a complete exercise with its answer, step by step.
</div>
</div>

Template:Main Page/GVConsole

2012-02-09T16:21:11Z

C.ortenzi:

<div class="mainbox">
<h2>{{GVCONSOLE}}<sup>®</sup></h2>
<div class="mainbox_content">
{{GVESB}} is provided of a sophisticated ''web application'' for the administration and deploy of the entire platform.

See {{L_GVCONSOLE}} section for detailed information on how to:
* Save a configuration
* View and restore previous configurations
* Profile users
* Create and design workflows
* Configure any component, layer and connector
* Start and stop services (also logical groups of services)
* Test services
* Monitor the state of one or more {{GVESB}} instances
* Hot reload new services and configurations (you never need to stop the server!)
* Create statistical graphics
* Track the log files with advanced filtering
* ... and more ...
</div>
</div>

Template:Main Page/Overview

2012-02-09T16:20:04Z

C.ortenzi:

Main Page

2012-02-09T16:01:39Z

C.ortenzi: /* {{GVCONSOLE}}® */

Welcome to {{GVESB}} Wiki, the place where you can find all information about our [http://en.wikipedia.org/wiki/Enterprise_service_bus ESB]. Start exploring {{GVESB}} '''[[Basic concepts]]''' or follow the links below!

==Overview==
{{GVESB}} is an Enterprise Service Bus, [http://en.wikipedia.org/wiki/Open_source Open Source], fully developed by one of the most experienced [http://en.wikipedia.org/wiki/Enterprise_application_integration EAI] teams, derived from a deep understanding of the topic on vendor products and from the direct participation in implementations of ESB systems with very challenging design requirements:

* High transactions volume
* Large number of interconnected systems and different protocols supported
* Response in near real time
* Availability of technology adapters (Database, File, {{L_GVWS}}, e-Mail, etc)
* Availability of application adapters
* Powerful and flexible [[Data transformation]] engine

{{GVESB}} is a Java-based software built to support complex [http://en.wikipedia.org/wiki/Service-oriented_architecture SOA] architectures. Its [[multi-layer architecture]] allows an unlimited customization, solving most of enterprise integration issues like exchanging data between existing systems. Many [[plugins]] and [[adapters]] are already available for a huge flexibility.

==Installation==
{{GVESB}}, entirely made in Java, provides full compatibility with most operating systems that support natively the Java Virtual Machine provided by Sun Microsystems. In order to install, configure and run {{GVESB}}, please follow next items:
* [[Compatible platforms]]
* [[Prerequisites]]
* [[Installation]]
* [[Post Installation]]
* [[Starting]] {{GVESB}}
* [[FAQs]]

==Examples==

The installation of {{GVESB}} is provided with several examples of service configuration. These examples are listed [[First GVESB Projects| here]]. In its sub-sections are described the configuration procedures for this services.

If you are already familiar with {{GVESB}}, you can step directly to the [[Advanced Test Projects]] that shows some examples of application.

If you want to test your own skills using {{GVESB}}, it is also provided the [[Test your self]] section. Here you can find a complete exercise with its answer, step by step.

=={{VULCON}}<sup>®</sup>==
{{GVESB}} Enterprise is provided of a powerful graphical designing tool {{VULCON}}<sup>®</sup>.
It can be used to easily build integrations among systems and to model service flows.

See {{L_VULCON}} section for further information and to understand how it is possible to create a [http://en.wikipedia.org/wiki/Service-oriented_modeling service oriented modeling approach], avoiding developers to write new soure code or manually edit any configuration file.

To create and deploy a new service with {{GVESB}} there's no need to write and test new Java code!

With the latest release of {{VULCON}}<sup>®</sup>, the graphical design tool for {{GVESB}}, integration will never be easier, since {{VULCON}}<sup>®</sup> is, by far, the easiest and most accessible way to build integration flows.

=={{GVCONSOLE}}<sup>®</sup>==
{{GVESB}} is provided of a sophisticated ''web application'' for the administration and deploy of the entire platform.

See {{L_GVCONSOLE}} section for detailed information on how to:

* Save a configuration
* View and restore previous configurations
* Profile users
* Create and design workflows
* Configure any component, layer and connector
* Start and stop services (also logical groups of services)
* Test services
* Monitor the state of one or more {{GVESB}} instances
* Hot reload new services and configurations (you never need to stop the server!)
* Create statistical graphics
* Track the log files with advanced filtering
* ... and more ...

Template:Main Page/GVConsole

2012-02-09T16:01:26Z

C.ortenzi: Created page with "<div class="mainbox"> <h2>{{GVCONSOLE}}<sup>®</sup></h2> <div style="padding: 0.5em;"> {{GVESB}} is provided of a sophisticated ''web application'' for the administration an..."

<div class="mainbox">

<h2>{{GVCONSOLE}}<sup>®</sup></h2>
<div style="padding: 0.5em;">
{{GVESB}} is provided of a sophisticated ''web application'' for the administration and deploy of the entire platform.

See {{L_GVCONSOLE}} section for detailed information on how to:

* Save a configuration
* View and restore previous configurations
* Profile users
* Create and design workflows
* Configure any component, layer and connector
* Start and stop services (also logical groups of services)
* Test services
* Monitor the state of one or more {{GVESB}} instances
* Hot reload new services and configurations (you never need to stop the server!)
* Create statistical graphics
* Track the log files with advanced filtering
* ... and more ...

</div></div>

Template:Main Page/VulCon

2012-02-09T16:00:22Z

C.ortenzi:

<div class="mainbox">

<h2>{{VULCON}}<sup>®</sup></h2>
<div style="padding: 0.5em;">
{{GVESB}} Enterprise is provided of a powerful graphical designing tool {{VULCON}}<sup>®</sup>.
It can be used to easily build integrations among systems and to model service flows.

See {{L_VULCON}} section for further information and to understand how it is possible to create a [http://en.wikipedia.org/wiki/Service-oriented_modeling service oriented modeling approach], avoiding developers to write new soure code or manually edit any configuration file.

To create and deploy a new service with {{GVESB}} there's no need to write and test new Java code!

With the latest release of {{VULCON}}<sup>®</sup>, the graphical design tool for {{GVESB}}, integration will never be easier, since {{VULCON}}<sup>®</sup> is, by far, the easiest and most accessible way to build integration flows.

</div></div>

Template:Main Page/VulCon

2012-02-09T15:59:53Z

C.ortenzi: Created page with "<div class="mainbox"> <h2>{{VULCON}}<sup>®</h2> <div style="padding: 0.5em;"> {{GVESB}} Enterprise is provided of a powerful graphical designing tool {{VULCON}}<sup>®</s..."

<div class="mainbox">

<h2>{{VULCON}}<sup>®</h2>
<div style="padding: 0.5em;">
{{GVESB}} Enterprise is provided of a powerful graphical designing tool {{VULCON}}<sup>®</sup>.
It can be used to easily build integrations among systems and to model service flows.

See {{L_VULCON}} section for further information and to understand how it is possible to create a [http://en.wikipedia.org/wiki/Service-oriented_modeling service oriented modeling approach], avoiding developers to write new soure code or manually edit any configuration file.

To create and deploy a new service with {{GVESB}} there's no need to write and test new Java code!

With the latest release of {{VULCON}}<sup>®</sup>, the graphical design tool for {{GVESB}}, integration will never be easier, since {{VULCON}}<sup>®</sup> is, by far, the easiest and most accessible way to build integration flows.

</div></div>