GreenVulcano Wiki - User contributions [en]

Installation

2021-06-21T14:41:00Z

G.dimaio:

This section describes how to install {{GVESB}} using the new GreenVulcano Universal Installer or the manual installation process.

Installation packages can be found [https://sourceforge.net/projects/greenvulcanoesb/files/GreenVulcano%20ESB/3.4 here].

'''Install using GreenVulcano Universal Installer'''
# Unzip the file ''Installer_GvServer-<version>.Final'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Run the GreenVulcano Universal Installer: [[Installer Overview]]

'''Manual installation process'''
# Unzip the file ''GvServer-<version>.Final-Full'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Setup your {{GVESB}} : [[Manual Installation]]

Developer Studio

2021-06-21T14:40:01Z

G.dimaio:

<div class="version_ge3.3">

==Introduction==
[[File:DeveloperStudioSplash.jpg|thumb|{{DEVELOPERSTUDIO}} splah screen]]
{{DEVELOPERSTUDIO}}<sup>®</sup> is an eclipse-based IDE customized to offer a developer the best design interface to create flows into {{GVESB}}.

It is a lightweight application that contains all the features you need to fully master integration workflows. {{DEVELOPERSTUDIO}}<sup>®</sup> not only contains the plugins for {{L_VULCON}}, {{GVESB}} graphical editor, but also many other useful tools for workflow developing,
like:

* <code>BIRT</code> -> report management
* <code>DROOLS</code> -> business rules management
* <code>JBPM</code> -> business processes management
* <code>BPEL</code> -> bpel processes management
* <code>SOAPUI</code> -> web service test

{{DEVELOPERSTUDIO}}<sup>®</sup> is designed for cater to any people that want to use graphic design tools for business uses:

* Solution Architect
* Business Manager
* Analyst
* Technical Developer

==Requirements==
In order to launch {{DEVELOPERSTUDIO}}<sup>®</sup> you must accomplish only a requirement:
*Java JDK SE (v.1.6 or higher) installed on your machine [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]

==Installation==
{{DEVELOPERSTUDIO}}<sup>®</sup> doesn't need installation. Just download the appropriate version for your OS from [https://sourceforge.net/projects/greenvulcanoesb/files/Developer%20Studio/3.6/ here].

After the download is finished, choose a path to unpack it.

==Running==
In order to run {{DEVELOPERSTUDIO}}<sup>®</sup> choose the file to launch inside the product root directory:

* <code>DeveloperStudio</code> (Linux platforms)

* <code>DeveloperStudio.exe</code> (Windows platforms)

==Next Steps==
If you want to see a detailed step-by-step installation see [[Installing Developer Studio]].

In order to learn more about {{GVESB}} graphical design tool, you can see {{L_VULCON}} page, providing more information and examples.

</div>

{{VOTE}}

Installation

2021-06-21T14:30:50Z

G.dimaio:

This section describes how to install {{GVESB}} using the new GreenVulcano Universal Installer or the manual installation process.

Installation packages can be found [https://sourceforge.net/projects/greenvulcanoesb/files/GreenVulcano%20ESB/ here].

'''Install using GreenVulcano Universal Installer'''
# Unzip the file ''Installer_GvServer-<version>.Final'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Run the GreenVulcano Universal Installer: [[Installer Overview]]

'''Manual installation process'''
# Unzip the file ''GvServer-<version>.Final-Full'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Setup your {{GVESB}} : [[Manual Installation]]

VulCon

2017-05-04T15:10:09Z

G.dimaio: /* Version 3.6 */

==Introduction==
[[File:VulconWorkingArea.jpg|thumb|{{VULCON}} working area]]
{{VULCON}} is a graphical console that helps the users to design and configure {{GVESB}} business flows.
It's an [http://www.eclipse.org/Eclipse] plug-in.

The actors involved in {{GVESB}} business flows implementation are:
*Business Analyst: designs the business flow regardless how to interface systems.
*Technical specialist: configures the flow designed by Business Analyst, adding all technical information needed to interface systems.

At the end of design and configuration job, the user is able to generate a zip file containing all necessary {{GVESB}} files, in order to deploy and test the business flows by means of {{L_GVCONSOLE}}.

==Requirements==
In order to install and run {{VULCON}} plug-in, you must accomplish the following requirements:
*Java JDK SE (v.1.6 or higher) [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]
*Eclipse IDE for Java EE Developers (v.3.5 or higher) [http://www.eclipse.org/downloads/ download]

==Installation==
[[File:VulConPlugin.jpg|thumb|{{VULCON}} plug-in installation]]
The installation procedure consists in decompressing the vulcon-(Version Number).zip file and then copying the jar file into [http://www.eclipse.org/ Eclipse] dropins folder. After starting Eclipse, you can check if the plug-in has been installed correctly, following the menu item
<syntaxhighlight lang="XML">
Help --> About Eclipse Platform --> Installation Details.
</syntaxhighlight>

In the plug-in list check if "{{VULCON}} Editor" is present, in this case it has been successfully installed.

<div class="version_ge3.3">
Unlike the previous version, the installation of the {{VULCON}} plugin is changed. To install or update the {{VULCON}} plugin, an Eclipse update site is now available at the following URL:

'''''<nowiki>http://www.greenvulcano.com/download/vulcon/update-site</nowiki>'''''

To install or update the {{VULCON}} plugin, follow the following steps:
# Select Help > Install New Software...
# In the Work with field, type the update site and click Add...
# Enter a name for the update site (e.g. ''{{VULCON}} update site'') and click Ok
# Check the ''GreenVulcano'' checkbox and click Next. Then follow the dialogs to install the provided features.

At installation completion, check if it was successful looking at menu,
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon
</syntaxhighlight>

</div>

In order to see {{VULCON}} license information
<syntaxhighlight lang="XML">
Open Windows --> Preferences --> VulCon License.
</syntaxhighlight>
From this section you can see:
*the product expiration date
*max {{VULCON}} service's operation
*max {{VULCON}} system's operation
*max {{VULCON}} services
*max {{VULCON}} systems

<div class="version_ge3.3">
[[File:licensevulcon.png|thumb|{{VULCON}} License]]
Unlike the previous version, the installation of the {{VULCON}} license can be done using the following form:
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon --> VulCon License --> Install License File.
</syntaxhighlight>
here you can upload the license received by email.
</div>

==Next steps==
In order to learn more about {{VULCON}} user interface see [[Example Creating a new VulCon project]] and [[{{VULCON}} perspective]] section. Otherwise, if you already know the user interface, you may want to design and configure your [[{{VULCON}} first flow]]. Once implemented your business flow you may visit the [[{{VULCON}} deploy]], and to test it you must use {{L_GVCONSOLE}} deploy. If you have an existing {{VULCON}} project you can [[import]] it. To manage the life cycle of your application you can use [[HP Systinet]].
<div class="version_ge3.3">
See the amazing [[Debugger]] available from {{GVESB}} v3.3, the essential tool for your productivity.
Find [[WizardConfiguration|here]] the new {{VULCON}} configuration wizard.
</div>
<div class="version_ge3.6">
==Version 3.6==
Version 3.6 has the following new features:
*It is unlicensed
*A project can be saved using only the save button on the Tabs bar
*There are four Tabs: Services, Systems, Adapter and Core
*The Tabs have a text filter useful to show only some for components
*The Debugger can be configured for different versions of GreenVulcano ESB server
*It's possible to debug Forward operations

==Configuration 3.6==
[[File:configTab.jpeg|thumb|{{VULCON}} working area]]
[[File:configDebug.jpeg|thumb|{{VULCON}} working area]]
go to: Windows --> Preferences --> VulCon

you can configure the objects to see in Adapter and Core Tree Tab and Debug parameters
</div>

{{VOTE}}

VulCon

2017-05-04T14:15:34Z

G.dimaio: /* Version 3.6 */

==Introduction==
[[File:VulconWorkingArea.jpg|thumb|{{VULCON}} working area]]
{{VULCON}} is a graphical console that helps the users to design and configure {{GVESB}} business flows.
It's an [http://www.eclipse.org/Eclipse] plug-in.

The actors involved in {{GVESB}} business flows implementation are:
*Business Analyst: designs the business flow regardless how to interface systems.
*Technical specialist: configures the flow designed by Business Analyst, adding all technical information needed to interface systems.

At the end of design and configuration job, the user is able to generate a zip file containing all necessary {{GVESB}} files, in order to deploy and test the business flows by means of {{L_GVCONSOLE}}.

==Requirements==
In order to install and run {{VULCON}} plug-in, you must accomplish the following requirements:
*Java JDK SE (v.1.6 or higher) [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]
*Eclipse IDE for Java EE Developers (v.3.5 or higher) [http://www.eclipse.org/downloads/ download]

==Installation==
[[File:VulConPlugin.jpg|thumb|{{VULCON}} plug-in installation]]
The installation procedure consists in decompressing the vulcon-(Version Number).zip file and then copying the jar file into [http://www.eclipse.org/ Eclipse] dropins folder. After starting Eclipse, you can check if the plug-in has been installed correctly, following the menu item
<syntaxhighlight lang="XML">
Help --> About Eclipse Platform --> Installation Details.
</syntaxhighlight>

In the plug-in list check if "{{VULCON}} Editor" is present, in this case it has been successfully installed.

<div class="version_ge3.3">
Unlike the previous version, the installation of the {{VULCON}} plugin is changed. To install or update the {{VULCON}} plugin, an Eclipse update site is now available at the following URL:

'''''<nowiki>http://www.greenvulcano.com/download/vulcon/update-site</nowiki>'''''

To install or update the {{VULCON}} plugin, follow the following steps:
# Select Help > Install New Software...
# In the Work with field, type the update site and click Add...
# Enter a name for the update site (e.g. ''{{VULCON}} update site'') and click Ok
# Check the ''GreenVulcano'' checkbox and click Next. Then follow the dialogs to install the provided features.

At installation completion, check if it was successful looking at menu,
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon
</syntaxhighlight>

</div>

In order to see {{VULCON}} license information
<syntaxhighlight lang="XML">
Open Windows --> Preferences --> VulCon License.
</syntaxhighlight>
From this section you can see:
*the product expiration date
*max {{VULCON}} service's operation
*max {{VULCON}} system's operation
*max {{VULCON}} services
*max {{VULCON}} systems

<div class="version_ge3.3">
[[File:licensevulcon.png|thumb|{{VULCON}} License]]
Unlike the previous version, the installation of the {{VULCON}} license can be done using the following form:
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon --> VulCon License --> Install License File.
</syntaxhighlight>
here you can upload the license received by email.
</div>

==Next steps==
In order to learn more about {{VULCON}} user interface see [[Example Creating a new VulCon project]] and [[{{VULCON}} perspective]] section. Otherwise, if you already know the user interface, you may want to design and configure your [[{{VULCON}} first flow]]. Once implemented your business flow you may visit the [[{{VULCON}} deploy]], and to test it you must use {{L_GVCONSOLE}} deploy. If you have an existing {{VULCON}} project you can [[import]] it. To manage the life cycle of your application you can use [[HP Systinet]].
<div class="version_ge3.3">
See the amazing [[Debugger]] available from {{GVESB}} v3.3, the essential tool for your productivity.
Find [[WizardConfiguration|here]] the new {{VULCON}} configuration wizard.
</div>
<div class="version_ge3.6">
==Version 3.6==
Version 3.6 has the following new features:
*It is unlicensed
*There are four Tabs: Services, Systems, Adapter and Core
*The Tabs have a text filter useful to show only some for components
*The Debugger can be configured for different versions of GreenVulcano ESB server
*It's possible to debug Forward operations

==Configuration 3.6==
[[File:configTab.jpeg|thumb|{{VULCON}} working area]]
[[File:configDebug.jpeg|thumb|{{VULCON}} working area]]
go to: Windows --> Preferences --> VulCon

you can configure the objects to see in Adapter and Core Tree Tab and Debug parameters
</div>

{{VOTE}}

VulCon

2017-05-04T14:10:38Z

G.dimaio: /* Version 3.6 */

==Introduction==
[[File:VulconWorkingArea.jpg|thumb|{{VULCON}} working area]]
{{VULCON}} is a graphical console that helps the users to design and configure {{GVESB}} business flows.
It's an [http://www.eclipse.org/Eclipse] plug-in.

The actors involved in {{GVESB}} business flows implementation are:
*Business Analyst: designs the business flow regardless how to interface systems.
*Technical specialist: configures the flow designed by Business Analyst, adding all technical information needed to interface systems.

At the end of design and configuration job, the user is able to generate a zip file containing all necessary {{GVESB}} files, in order to deploy and test the business flows by means of {{L_GVCONSOLE}}.

==Requirements==
In order to install and run {{VULCON}} plug-in, you must accomplish the following requirements:
*Java JDK SE (v.1.6 or higher) [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]
*Eclipse IDE for Java EE Developers (v.3.5 or higher) [http://www.eclipse.org/downloads/ download]

==Installation==
[[File:VulConPlugin.jpg|thumb|{{VULCON}} plug-in installation]]
The installation procedure consists in decompressing the vulcon-(Version Number).zip file and then copying the jar file into [http://www.eclipse.org/ Eclipse] dropins folder. After starting Eclipse, you can check if the plug-in has been installed correctly, following the menu item
<syntaxhighlight lang="XML">
Help --> About Eclipse Platform --> Installation Details.
</syntaxhighlight>

In the plug-in list check if "{{VULCON}} Editor" is present, in this case it has been successfully installed.

<div class="version_ge3.3">
Unlike the previous version, the installation of the {{VULCON}} plugin is changed. To install or update the {{VULCON}} plugin, an Eclipse update site is now available at the following URL:

'''''<nowiki>http://www.greenvulcano.com/download/vulcon/update-site</nowiki>'''''

To install or update the {{VULCON}} plugin, follow the following steps:
# Select Help > Install New Software...
# In the Work with field, type the update site and click Add...
# Enter a name for the update site (e.g. ''{{VULCON}} update site'') and click Ok
# Check the ''GreenVulcano'' checkbox and click Next. Then follow the dialogs to install the provided features.

At installation completion, check if it was successful looking at menu,
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon
</syntaxhighlight>

</div>

In order to see {{VULCON}} license information
<syntaxhighlight lang="XML">
Open Windows --> Preferences --> VulCon License.
</syntaxhighlight>
From this section you can see:
*the product expiration date
*max {{VULCON}} service's operation
*max {{VULCON}} system's operation
*max {{VULCON}} services
*max {{VULCON}} systems

<div class="version_ge3.3">
[[File:licensevulcon.png|thumb|{{VULCON}} License]]
Unlike the previous version, the installation of the {{VULCON}} license can be done using the following form:
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon --> VulCon License --> Install License File.
</syntaxhighlight>
here you can upload the license received by email.
</div>

==Next steps==
In order to learn more about {{VULCON}} user interface see [[Example Creating a new VulCon project]] and [[{{VULCON}} perspective]] section. Otherwise, if you already know the user interface, you may want to design and configure your [[{{VULCON}} first flow]]. Once implemented your business flow you may visit the [[{{VULCON}} deploy]], and to test it you must use {{L_GVCONSOLE}} deploy. If you have an existing {{VULCON}} project you can [[import]] it. To manage the life cycle of your application you can use [[HP Systinet]].
<div class="version_ge3.3">
See the amazing [[Debugger]] available from {{GVESB}} v3.3, the essential tool for your productivity.
Find [[WizardConfiguration|here]] the new {{VULCON}} configuration wizard.
</div>
<div class="version_ge3.6">
==Version 3.6==
Version 3.6 has the following new features:
*It is unlicensed
*There are four Tabs: Services, Systems, Adapter and Core
*The Tabs have a text filter useful to show only some for components
*The Debugger can be configured for different versions of GreenVulcano ESB server

==Configuration 3.6==
[[File:configTab.jpeg|thumb|{{VULCON}} working area]]
[[File:configDebug.jpeg|thumb|{{VULCON}} working area]]
go to: Windows --> Preferences --> VulCon

you can configure the objects to see in Adapter and Core Tree Tab and Debug parameters
</div>

{{VOTE}}

VulCon

2017-05-04T14:09:03Z

G.dimaio: /* Configuration 3.6 */

==Introduction==
[[File:VulconWorkingArea.jpg|thumb|{{VULCON}} working area]]
{{VULCON}} is a graphical console that helps the users to design and configure {{GVESB}} business flows.
It's an [http://www.eclipse.org/Eclipse] plug-in.

The actors involved in {{GVESB}} business flows implementation are:
*Business Analyst: designs the business flow regardless how to interface systems.
*Technical specialist: configures the flow designed by Business Analyst, adding all technical information needed to interface systems.

At the end of design and configuration job, the user is able to generate a zip file containing all necessary {{GVESB}} files, in order to deploy and test the business flows by means of {{L_GVCONSOLE}}.

==Requirements==
In order to install and run {{VULCON}} plug-in, you must accomplish the following requirements:
*Java JDK SE (v.1.6 or higher) [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]
*Eclipse IDE for Java EE Developers (v.3.5 or higher) [http://www.eclipse.org/downloads/ download]

==Installation==
[[File:VulConPlugin.jpg|thumb|{{VULCON}} plug-in installation]]
The installation procedure consists in decompressing the vulcon-(Version Number).zip file and then copying the jar file into [http://www.eclipse.org/ Eclipse] dropins folder. After starting Eclipse, you can check if the plug-in has been installed correctly, following the menu item
<syntaxhighlight lang="XML">
Help --> About Eclipse Platform --> Installation Details.
</syntaxhighlight>

In the plug-in list check if "{{VULCON}} Editor" is present, in this case it has been successfully installed.

<div class="version_ge3.3">
Unlike the previous version, the installation of the {{VULCON}} plugin is changed. To install or update the {{VULCON}} plugin, an Eclipse update site is now available at the following URL:

'''''<nowiki>http://www.greenvulcano.com/download/vulcon/update-site</nowiki>'''''

To install or update the {{VULCON}} plugin, follow the following steps:
# Select Help > Install New Software...
# In the Work with field, type the update site and click Add...
# Enter a name for the update site (e.g. ''{{VULCON}} update site'') and click Ok
# Check the ''GreenVulcano'' checkbox and click Next. Then follow the dialogs to install the provided features.

At installation completion, check if it was successful looking at menu,
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon
</syntaxhighlight>

</div>

In order to see {{VULCON}} license information
<syntaxhighlight lang="XML">
Open Windows --> Preferences --> VulCon License.
</syntaxhighlight>
From this section you can see:
*the product expiration date
*max {{VULCON}} service's operation
*max {{VULCON}} system's operation
*max {{VULCON}} services
*max {{VULCON}} systems

<div class="version_ge3.3">
[[File:licensevulcon.png|thumb|{{VULCON}} License]]
Unlike the previous version, the installation of the {{VULCON}} license can be done using the following form:
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon --> VulCon License --> Install License File.
</syntaxhighlight>
here you can upload the license received by email.
</div>

==Next steps==
In order to learn more about {{VULCON}} user interface see [[Example Creating a new VulCon project]] and [[{{VULCON}} perspective]] section. Otherwise, if you already know the user interface, you may want to design and configure your [[{{VULCON}} first flow]]. Once implemented your business flow you may visit the [[{{VULCON}} deploy]], and to test it you must use {{L_GVCONSOLE}} deploy. If you have an existing {{VULCON}} project you can [[import]] it. To manage the life cycle of your application you can use [[HP Systinet]].
<div class="version_ge3.3">
See the amazing [[Debugger]] available from {{GVESB}} v3.3, the essential tool for your productivity.
Find [[WizardConfiguration|here]] the new {{VULCON}} configuration wizard.
</div>
<div class="version_ge3.6">
==Version 3.6==
Version 3.6 has the following new features:
*It is unlicensed
*There are four tabs: Services, Systems, Adapter and Core
*you can configure the debugger for different versions of GreenVulcano ESB server

==Configuration 3.6==
[[File:configTab.jpeg|thumb|{{VULCON}} working area]]
[[File:configDebug.jpeg|thumb|{{VULCON}} working area]]
go to: Windows --> Preferences --> VulCon

you can configure the objects to see in Adapter and Core Tree Tab and Debug parameters
</div>

{{VOTE}}

VulCon

2017-05-04T14:07:47Z

G.dimaio: /* Version 3.6 */

==Introduction==
[[File:VulconWorkingArea.jpg|thumb|{{VULCON}} working area]]
{{VULCON}} is a graphical console that helps the users to design and configure {{GVESB}} business flows.
It's an [http://www.eclipse.org/Eclipse] plug-in.

The actors involved in {{GVESB}} business flows implementation are:
*Business Analyst: designs the business flow regardless how to interface systems.
*Technical specialist: configures the flow designed by Business Analyst, adding all technical information needed to interface systems.

At the end of design and configuration job, the user is able to generate a zip file containing all necessary {{GVESB}} files, in order to deploy and test the business flows by means of {{L_GVCONSOLE}}.

==Requirements==
In order to install and run {{VULCON}} plug-in, you must accomplish the following requirements:
*Java JDK SE (v.1.6 or higher) [http://www.oracle.com/technetwork/java/javase/downloads/index.html download]
*Eclipse IDE for Java EE Developers (v.3.5 or higher) [http://www.eclipse.org/downloads/ download]

==Installation==
[[File:VulConPlugin.jpg|thumb|{{VULCON}} plug-in installation]]
The installation procedure consists in decompressing the vulcon-(Version Number).zip file and then copying the jar file into [http://www.eclipse.org/ Eclipse] dropins folder. After starting Eclipse, you can check if the plug-in has been installed correctly, following the menu item
<syntaxhighlight lang="XML">
Help --> About Eclipse Platform --> Installation Details.
</syntaxhighlight>

In the plug-in list check if "{{VULCON}} Editor" is present, in this case it has been successfully installed.

<div class="version_ge3.3">
Unlike the previous version, the installation of the {{VULCON}} plugin is changed. To install or update the {{VULCON}} plugin, an Eclipse update site is now available at the following URL:

'''''<nowiki>http://www.greenvulcano.com/download/vulcon/update-site</nowiki>'''''

To install or update the {{VULCON}} plugin, follow the following steps:
# Select Help > Install New Software...
# In the Work with field, type the update site and click Add...
# Enter a name for the update site (e.g. ''{{VULCON}} update site'') and click Ok
# Check the ''GreenVulcano'' checkbox and click Next. Then follow the dialogs to install the provided features.

At installation completion, check if it was successful looking at menu,
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon
</syntaxhighlight>

</div>

In order to see {{VULCON}} license information
<syntaxhighlight lang="XML">
Open Windows --> Preferences --> VulCon License.
</syntaxhighlight>
From this section you can see:
*the product expiration date
*max {{VULCON}} service's operation
*max {{VULCON}} system's operation
*max {{VULCON}} services
*max {{VULCON}} systems

<div class="version_ge3.3">
[[File:licensevulcon.png|thumb|{{VULCON}} License]]
Unlike the previous version, the installation of the {{VULCON}} license can be done using the following form:
<syntaxhighlight lang="XML">
Windows --> Preferences --> VulCon --> VulCon License --> Install License File.
</syntaxhighlight>
here you can upload the license received by email.
</div>

==Next steps==
In order to learn more about {{VULCON}} user interface see [[Example Creating a new VulCon project]] and [[{{VULCON}} perspective]] section. Otherwise, if you already know the user interface, you may want to design and configure your [[{{VULCON}} first flow]]. Once implemented your business flow you may visit the [[{{VULCON}} deploy]], and to test it you must use {{L_GVCONSOLE}} deploy. If you have an existing {{VULCON}} project you can [[import]] it. To manage the life cycle of your application you can use [[HP Systinet]].
<div class="version_ge3.3">
See the amazing [[Debugger]] available from {{GVESB}} v3.3, the essential tool for your productivity.
Find [[WizardConfiguration|here]] the new {{VULCON}} configuration wizard.
</div>
<div class="version_ge3.6">
==Version 3.6==
Version 3.6 has the following new features:
*It is unlicensed
*There are four tabs: Services, Systems, Adapter and Core
*you can configure the debugger for different versions of GreenVulcano ESB server

==Configuration 3.6==
[[File:configTab.jpeg|thumb|{{VULCON}} working area]]
[[File:configDebug.jpeg|thumb|{{VULCON}} working area]]
go to: Windows --> Preferences --> VulCon
configure object in Tree Tab and Debug parameter
</div>

{{VOTE}}

FAQs

2017-04-14T14:53:31Z

G.dimaio:

'''May I use the open source version of JDK, OpenJDK, instead of the one provided by Oracle?'''

{{GVESB}} is 100% compatible with the ''Java Virtual Machine'' provided by Oracle.
We recommend to use the JDK 1.6 version provided by Oracle, although we are aware of {{GVESB}} users that have found no malfunctionings with OpenJDK.
Starting with version 3.4.0.10 {{GVESB}} runs with JDK 8.

'''I'm unable to start {{GVESB}} because there are some ports already in use on the server. What can I do?'''

The startup script contains the parameter "-Djboss.service.binding.set=ports-default" defined in the variable JB_OPTS.<br/>
You can modify "ports-default" choosing another portset with one in the following list:

* ports-01; The ports-01 bindings are obtained by taking the base bindings and adding 100 to each port value
* ports-02; The ports-02 bindings are obtained by taking the base bindings and adding 200 to each port value
* ports-03; The ports-03 bindings are obtained by taking the base bindings and adding 300 to each port value
<br/>
Eg. -Djboss.service.binding.set=ports-01

'''How can I access the {{GVESB}} administration console?'''

The console is available at ''<nowiki>http://SERVER-HOSTNAME:8080/gvconsole</nowiki>'', where "SERVER-HOSTNAME" should be replaced by the address of the server where {{GVESB}} was installed.

'''I can't access the administration console. What can I do?'''

Check, in the log file ''server.log'', the correct ''deployment'' of the {{L_GVCONSOLE}}. Check on the console of Jboss ''<nowiki>http://SERVER-HOSTNAME:8080/web-console/</nowiki>'' in the J2EE Domains if the file ''gvconsole.war'' is present.

'''I don't know the credentials to access the administration console. Where can I find it?'''

The credentials to access the administration console, {{L_GVCONSOLE}}, can be found in the file ''gvesb-users.properties'' present in the directory ''$GV_HOME/xmlconfig''.

'''I have a problem that I can not solve. How can I contact the {{GVESB}} support?'''

It is possible to contact {{GVESB}} support sending an email to [mailto:support@greenvulcano.com ''support@greenvulcano.com''] containing the details of:

* Version of the Java virtual machine used
* Operating System
* Short description of the hardware architecture

Users are encouraged to attach the log files present in the directories ''$GV_HOME/log'' and ''$GV_SERVER/log''. See also the forum available at http://www.greenvulcano.com/forum/ where it is possible to find any information of a technical nature as well as requesting help from the ''community'' creating a ''thread/post'' with the problem description.

Installation

2017-04-14T14:47:50Z

G.dimaio:

This section describes how install {{GVESB}} using the new GreenVulcano Universal Installer or the manual installation process.

'''Install using GreenVulcano Universal Installer'''
# Unzip the file ''Installer_GvServer-<version>.Final'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Run the GreenVulcano Universal Installer: [[Installer Overview]]

'''Manual installation process'''
# Unzip the file ''GvServer-<version>.Final-Full'' archive in any directory on the server where you plan to install the software. To avoid potential problems the installation path MUST NOT contain spaces.
# Setup your {{GVESB}} : [[Manual Installation]]

Compatible platforms

2017-04-14T14:46:43Z

G.dimaio: /* Supported Software Platforms */

==Supported Hardware Platforms==

{{GVESB}} can be installed on the following hardware platforms:

{| class="gvtable"
! Component !! Technology !! Note
|-
| valign="top"|Processor || Intel x86 <br />x86-64 (AMD64 (AMD) or Intel64 (Intel) <br />Intel IA-64 (Itanium, Itanium II) <br /><br />1 CPU with frequency 1.8 Ghz || valign="top"|{{GVESB}} supports all processors based on Intel x86 and x86-64. <br /> Processors using different technologies are compatible to its support by the ''Java Virtual Machine''
|-
| valign="top"|Memory || 1Gb minim <br /> 2Gb recommended||
|-
| Disk space || 500Mb min || Depends on the log retention policies
|}

==Supported Software Platforms==

{{GVESB}} can be installed on different operating systems. The following table shows the list of compatible software platforms:

{| class="gvtable"
! Technology !! Platform
|-
| valign="top"|Operating system || Microsoft: Windows XP SP3, Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008 <br />
.nix: Linux (kernel 2.6.x), Solaris, AIX, HP-UX <br />
|-
| valign="top"|Application servers || provided JBoss 5.1.0-GA, installable on any J2EE compliant application server <br />

|-
| Java || JDK 1.6 (Sun Microsystems)

JDK 8 (Oracle) for version >= 3.4.0.10
|}

Statement

2017-04-06T20:16:57Z

G.dimaio: /* {{GVESB}} Configuration */

==Description==

This element defines the statement to be evaluated.

Can contains [[placeholders]] that will be replaced at runtime.

=={{GVESB}} Configuration==

The element statement can be used by:
* [[CallDescriptor]]
* [[DBOFlatSelect]]
* [[DBOInsert]]
* [[DBOInsertOrUpdate]]
* [[DBOMultiFlatSelect]]
* [[DBOSelect]]
* [[DBOThreadSelect]]
* [[DBOUpdate]]
* [[DBOUpdateOrInsert]]
* [[Excel-call#Sheet|Sheet]]

Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || required || Must be:
* DBOSelect : select
* DBOInsert : insert
* DBOUpdate : update
* DBOInsertOrUpdate : insert|update
* DBOUpdateOrInsert : insert|update
* DBOCallSP : callsp
* Excel Sheet : select
The attribute's admitted values are:
* select
* insert
* update
* callsp
The attribute's value cannot be null.
|-
| id || optional || Statement identifier. Default is 0. It is used as value of row/@id attribute:
* Select: identifies the statement from which have been extracted the marked rows.
* Update: identifies the statement to be used to process the input row parameters.
The attribute's value cannot be null.
|-
| keys || optional || Only useful in DBOSelect.
Specifies the index of select output on which group the results.
The corresponding values are specified as attributes of 'data' element within the 'RowSet' element.
For example, in the select: SELECT id,company_code,name FROM employees
specifying the attribute keys = "2", the result would be:
<syntaxhighlight lang="XML"><RowSet>
<data key_2="GreenVulcano">
<row><col>19</col><col>pippo</col></row>
<row><col>25</col><col>pluto</col></row>
</data>
</RowSet>
</syntaxhighlight>
Can specify multiple keys separated by commas.

'''The select NEEDS to have an ORDER BY rule with THE SAME fields used in the attribute, and in the same order'''

The attribute's value cannot be null.
|}

Does not contain subelements.

Plugins

2016-02-29T07:34:56Z

G.dimaio: /* Mail */

In {{GVESB}}, a plug-in is a software component that extends the capability to access an external system, database or data in general.

For example, plug-ins are commonly used in {{GVESB}} to read Excel files ([[excelreader-call]]), or for reading/writing a file ([[filereader-call]] / [[filewriter-call]]).

The following tables show all the available {{GVESB}} plugins grouped by technology:

==File system==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVFileReader.png |20px]] || [[filereader-call]] || reading a file present in the local file system
|-
| [[File:GVFileWriter.png |20px]] || [[filewriter-call]] || writing a file in the local file system
|-
| [[File:GVFileManager.png |20px]] || [[filemanager-call]] || searching, moving, coping, deleting, compressing and uncompressing files/directories
|-
| [[File:GVFsMonitor2.png |20px]] || [[fsmonitor-call]] || getting a XML report of a directory containing the existing, created, modified and deleted files, from the last scan, on local or remote file system
|-
| [[File:GVRemoteManager.png |20px]] || [[remotemanager-call]] || performing operations on files/directories present in a remote file system via FTP/SFTP/FTPS
|-
| [[File:GVShellID.png |20px]] || [[shell-call]] || executing a local shell command
|-
| [[File:GVRSHFileReader.png |20px]] || [[rsh-filereader-call]] || reading a file in a local or remote file system through the {{GVESB}} RSH RMI server
|-
| [[File:GVRSHFileWriter.png |20px]] || [[rsh-filewriter-call]] || writing a file in a local or remote file system through the {{GVESB}} RSH RMI server
|-
| [[File:GVRSHCall.png |20px]] || [[rsh-call]] || executing a shell command in a local or remote system through the {{GVESB}} RSH RMI server
|}

==WebService==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVWsCall.png | 20px]] || [[ws-call]] || invoking a Web Service using SOAP
|}
<div class="version_ge3.4">
{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVWsCall.png | 20px]] || [[rest-call]] || invoking a Web Service using REST
|}
</div>

==Data Base==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVDBCall.png | 20px]] || [[db-call]] || basic DB interaction
|-
| [[File:GVDHCall.png | 20px]] || [[dh-call]] || defining the parameter for making a call to [[DataHandler]]
|-
| [[File:GVBirtReportCall.png | 20px]] || [[birt-report-call]] || generate a BIRT report
|-
| [[File:GVExcelCall.png | 20px]] || [[excel-call]] || create an Excel report from a DB select
|-
| [[File:GVAdamCall.png | 20px]] || [[adamsearch-call]] || query ADAM document store using various filters
|}

==JMS==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:Enqueue32.png | 20px]] || [[jms-enqueue]] || performing a queuing/publish operation on a JMS Queue/Topic
|-
| [[File:Dequeue32.png | 20px]] || [[jms-dequeue]] || performing a reception operation from a JMS Queue/Topic
|}

==Routing==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVRoutedCall.png | 20px]] || [[routed-call]] || creating a routing mechanism at the level of communication channel<br/> during the execution of flows, the operation is seen as a simple call
|-
| [[File:GVRoutedDequeueCall.png | 20px]] || [[routed-dequeue]] || creating a routing mechanism at the level of communication channel<br/> during the execution of flows, the operation is seen as a simple dequeue
|-
| [[File:GVRoutedEnqueueCall.png | 20px]] || [[routed-enqueue]] || creating a routing mechanism at the level of communication channel<br/> during the execution of flows, the operation is seen as a simple enqueue
|}

==Mail==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVSmtpCall.png | 20px]] || [[smtp-call]] || sending an email using SMTP protocol
|-
| [[File:GVPopCall.png | 20px]] || [[pop-call]] || receiving an email using POP3 protocol
|}
<div class="version_ge3.4">
{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVPopCall.png | 20px]] || [[pop-uid-remove-call]] || removing emails UID from UID cache, useful for email reprocess using POP3 protocol
|-
| [[File:GVSmtpCall.png | 20px]] || [[exchange-send-call]] || sending an email using Exchange WS interface
|-
| [[File:GVPopCall.png | 20px]] || [[exchange-receive-call]] || receiving an email using Exchange WS interface
|-
| [[File:GVPopCall.png | 20px]] || [[exchange-manage-call]] || manage an email on server using Exchange WS interface
|}
</div>
<div class="version_ge3.4.0.10">
{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVPopCall.png | 20px]] || [[imap-call]] || receiving an email using IMAP protocol
|-
| [[File:GVPopCall.png | 20px]] || [[imap-manage-call]] || manage an email on server using IMAP protocol
|-
|}
</div>

==J2EE==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVEjbCall.png | 20px]] || [[j2ee-ejb-call]] || invoking an EJB (Enterprise Java Bean)
|-
| [[File:GVJcaCall.png | 20px]] || [[j2ee-jca-call]] || invoking an adapter JCA (Java Connector Architecture) that exposes the interface CCI (Common Client Interface).
|}

==LDAP==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVLDAPSearch.png | 20px]] || [[ldap-search-call]] || searching data on LDAP servers
|-
| [[File:GVLDAPUpdate.png | 20px]] || [[ldap-update-call]] || updating data on LDAP servers
|}

==Communication==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVHttpCall.png | 20px]] || [[http-call]] || calling HTTP methods on remote servers
|-
| [[File:GVHl7Call.png | 20px]] || [[hl7-call]] || invoking synchronous services on systems that use the HL7 v2 protocol with messages either standard or in XML format
|-
| [[File:call.png | 20px]] || [[jbpm-call]] || using the JBPM plugin
|-
| [[File:call.png | 20px]] || [[jbpm-task-call]] || using the JBPM TASK plugin
|-
| [[File:GVopenspcoopCall.png | 20px]] || [[openspcoop-call]] || using the Open SPCoop plugin
|}

==Utility==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVJmxCall.png | 20px]] || [[jmx-call]] || invoking MBean methods or set/get attributes on servers
|-
| [[File:GVextractData.png | 20px]] || [[extract-data-call]] || extract data from the body of the message
|-
| [[File:GVtest.png | 20px]] || [[test-service-call]] || simulate a test service
|-
| [[File:GVExcelReaderCall.png | 20px]] || [[excelreader-call]] || reading from a Excel file
|-
| [[File:GVGenericCall.png | 20px]] || [[generic-call]] || doing a [[Develop Generic VCL Call|user developed generic plug-in]] invocation
|-
| [[File:GVCoreCall.png | 20px]] || [[gvcore-call]] || invoking directly a flow of the {{GVESB}} core. '''REMOVED in v3.2.0'''
|-
| [[File:GVRulesCall.png | 20px]] || [[rules-call]] || invoking a Rule Engine service
|}
<div class="version_ge3.5">
{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:GVPdfReaderCall.png | 20px]] || [[pdfreader-call]] || convert a Pdf file in a XML document
|}
</div>

==Twitter==

{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:Tweet.png | 20px]] || [[twitter-update-status]] || tweet
|-
| [[File:Retweet.png | 20px]] || [[twitter-retweet-status]] || retweet
|-
| [[File:Follow.png | 20px]] || [[twitter-enable-notification]] || follow
|-
| [[File:Unfollow.png | 20px]] || [[twitter-disable-notification]] || unfollow
|-
| [[File:Follower.png | 20px]] || [[twitter-get-followers-ids]] || get followers
|-
| [[File:AddUser.png | 20px]] || [[twitter-get-friends-ids]] || get friends
|-
| [[File:Message.png | 20px]] || [[twitter-send-direct-message]] || send direct tweet
|}
<div class="version_ge3.3.4,3.4">
{|class="gvtable" style="width: 80%"
! style="width: 5%" | !! style="width: 20%" | Plug-in !! style="width: 75%" | Use this for ...
|-
| [[File:Tweet.png | 20px]] || [[twitter-get-user-timeline]] || get user timeline
|-
| [[File:Tweet.png | 20px]] || [[twitter-search]] || search status updates
|}
</div>
{{VOTE}}

Pop-call

2016-02-29T07:31:07Z

G.dimaio:

==Description==
Use this {{GVESB}} plugin if you want to receive an email using POP3(S) protocol.

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

{{GVESB}} allows you to receive emails using the pop-call plugin. Received messages are translated into an XML document that describes the content of the message and its attachments if presents.

The pop-call element is used by [[Channel]] and [[routed-call]] and has the following attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''call'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.pop.POPCallOperation'''.
|-
| name || required || Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations.
|-
| jndi-name || required || JNDI name of the mail Session configured in the application server.
The mail Sessions can be configured using the file ''mail-service.xml'' present into the folder //GV_HOME/application/deploy
|-
| override-protocol-host || optional || Corresponds to the property mail.protocol.host and overwrites the value of property mail.host specified in the configuration of the mail Session.
|-
| override-protocol-user || optional || Corresponds to the property mail.protocol.user and overwrites the value of property mail.user specified in the configuration of the mail Session.
|-
| delete-messages || optional || Mark a processed message as DELETED. Default false.
|-
| expunge || optional || Expunge (permanently remove) messages marked DELETED. Default false.
|-
| email-rx-cleaner || optional || RegExp pattern for email address cleaning. <br/> Default "[A-z][A-z0-9_]*([.][A-z0-9_]+)*[@][A-z0-9_]+([.][A-z0-9_]+)*[.][A-z]{2,4}".
|}
<div class="version_ge3.4">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| export-EML || optional || Also export a message in EML format. Default false.
|}
</div>
<div class="version_ge3.3.5,3.4.10">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| max-read-messages || optional || Maximum number of emails to be read. Default 10, a value of -1 means read all.
|}
</div>

Into pop-call can contains the following subelements
* Description
* [[JNDIHelper]]
* [[mail-properties]]

Pop-call

2016-02-28T17:10:06Z

G.dimaio:

==Description==
Use this {{GVESB}} plugin if you want to receive an email.

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

{{GVESB}} allows you to receive emails using the pop-call plugin. Received messages are translated into an XML document that describes the content of the message and its attachments if presents.

The pop-call element is used by [[Channel]] and [[routed-call]] and has the following attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''call'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.pop.POPCallOperation'''.
|-
| name || required || Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations.
|-
| jndi-name || required || JNDI name of the mail Session configured in the application server.
The mail Sessions can be configured using the file ''mail-service.xml'' present into the folder //GV_HOME/application/deploy
|-
| override-protocol-host || optional || Corresponds to the property mail.protocol.host and overwrites the value of property mail.host specified in the configuration of the mail Session.
|-
| override-protocol-user || optional || Corresponds to the property mail.protocol.user and overwrites the value of property mail.user specified in the configuration of the mail Session.
|-
| delete-messages || optional || Mark a processed message as DELETED. Default false.
|-
| expunge || optional || Expunge (permanently remove) messages marked DELETED. Default false.
|-
| email-rx-cleaner || optional || RegExp pattern for email address cleaning. <br/> Default "[A-z][A-z0-9_]*([.][A-z0-9_]+)*[@][A-z0-9_]+([.][A-z0-9_]+)*[.][A-z]{2,4}".
|}
<div class="version_ge3.4">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| export-EML || optional || Also export a message in EML format. Default false.
|}
</div>
<div class="version_ge3.3.5,3.4.10">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| max-read-messages || optional || Maximum number of emails to be read. Default 10, a value of -1 means read all.
|}
</div>

Into pop-call can be inserted the following subelements
* Description
* [[JNDIHelper]]
* [[mail-properties]]

XMLMerge

2016-02-18T17:16:31Z

G.dimaio:

==Description==
The element provides the configuration parameters to manage XML documenti merging.

Contains a list of [[#MergeInfo|MergeInfo]] elements, the first one defines the target document on which merge the data.

Is used in [[DBOBuilder]] of DataHandler.

==MergeInfo==
Defines the information for retrieving some XML Nodes from a document and past them on a target document.

Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| source || required || Source document name.
|-
| xpath-source || optional || Source document XPath selector.
|-
| xpath-dest || optional || Destination document parent Node's XPath selector.
|}

==Example==
As an example lets have 'document1':
<syntaxhighlight lang="xml">
<doc>
<element>some text</element>
</doc>
</syntaxhighlight>

and 'document2':
<syntaxhighlight lang="xml">
<doc2>
<element>some text 2</element>
<other-element>some other text</other-element>
</doc2>
</syntaxhighlight>

and 'document3':
<syntaxhighlight lang="xml">
<doc3>
<element>some text 3</element>
<other-element>some other text</other-element>
</doc3>
</syntaxhighlight>

with the following configuration:
<syntaxhighlight lang="xml">
<XMLMerge>
<MergeInfo source="document1"/>
<MergeInfo source="document2"
xpath-source="/doc2/element"
xpath-dest="/doc" />
<MergeInfo source="document3"
xpath-source="/doc3/element"
xpath-dest="/doc" />
</XMLMerge>
</syntaxhighlight>

we get as output the following XML document:
<syntaxhighlight lang="xml">
<doc>
<element>some text</element>
<element>some text 2</element>
<element>some text 3</element>
</doc>
</syntaxhighlight>

XMLAggregate

2016-02-18T17:15:28Z

G.dimaio:

==Description==
The element provides the configuration parameters to manage XML document aggregation as a single document.

Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| root || required || Aggregate document root node name.
|-
| namespace || optional || Root node namespace URI.
|}

Is used in [[ResultProcessor]] of [[Parallel Flow]].

==Example==
As an example lets have 'document1':
<syntaxhighlight lang="xml">
<doc>
<element>some text</element>
</doc>
</syntaxhighlight>

and 'document2':
<syntaxhighlight lang="xml">
<doc2>
<element>some text 2</element>
<other-element>some other text</other-element>
</doc2>
</syntaxhighlight>

and 'document3':
<syntaxhighlight lang="xml">
<doc3>
<element>some text 3</element>
<other-element>some other text</other-element>
</doc3>
</syntaxhighlight>

with the following configuration:
<syntaxhighlight lang="xml">
<XMLAggregate root="aggregated"
namespace="http://some.url"/>
</syntaxhighlight>

we get as output the following XML document:
<syntaxhighlight lang="xml">
<ns:aggregated xmlns:ns="http://some.url">
<doc>
<element>some text</element>
</doc>
<doc2>
<element>some text 2</element>
<other-element>some other text</other-element>
</doc2>
<doc3>
<element>some text 3</element>
<other-element>some other text</other-element>
</doc3>
</ns:aggregated>
</syntaxhighlight>

Parallel Flow

2016-02-18T17:14:00Z

G.dimaio: /* {{VULCON}} Configuration */

The Parallel nodes are:
[[File:ParallelNode.png|thumb|{{GVESB}} Paraleel Nodes]]
*Spawn SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flow as spawned process.
*Parallel SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as parallel process.
*Split SubFlow : Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as splitted parallel process.

=={{VULCON}} Configuration==

You might insert into your workflow one of the Nodes described above by drag and drop it into the {{VULCON}} Editor View.

When one of these nodes is inserted into the editor, a new element will appear into the element [[Flow]] (or [[SubFlow]]) of your Service [[Operation]]. This element will contain a sub-element which variates depending on the Iteration Node you selected. The following table shows this:

{|class="gvtable"
! Parallel node !! GVCore element !! Notes
|-
| GVSubFlowParallelNode || [[GVSubFlowParallelNode]] || Parallel Flow
|-
| GVSubFlowSpawnNode|| [[GVSubFlowSpawnNode]] || Parallel Flow
|-
| GVSubFlowSplittedNode|| [[GVSubFlowSplittedNode]] || Parallel Flow.
|}

=={{VULCON}} Editor SubFlow==

[[File:EditorSubFlow.png|thumb|{{GVESB}} Editor parallel SubFlow]]
For GVSubFlowParallelNode and GVSubFlowSpawnNode you can edited parallel subflow with specific editor.

{{VOTE}}

DataRetriever

2016-01-27T15:59:38Z

G.dimaio:

==Description==

The element ''DataRetriever'' allows to define a helper function.

=={{GVESB}} configuration==

The DataRetriever elements define helper functions used in data transformations for enriching XML products. Might contain [[placeholders]].

It is defined by the following parameters:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| cacheable || optional || If true the calculated function value, for the given parameters set, is cached for future access during the service processing.<br/> The cache is cancelled at service end. <br/> Default false.
|-
| method || required || Helper function name.
|-
| signature || optional || Comma-separated list of parameters name to be substituted in the function.
|}

===Examples of GenericRetriever functions===

Configuration examples.
<syntaxhighlight lang="xml">
<RetrieverConfig>
<GenericRetriever class="it.greenvulcano.gvesb.datahandling.utils.GenericRetriever"
type="retriever">

<DataRetriever cacheable="true" method="getCityID" signature="NAME">
select ID from CITY
where NAME='@{{NAME}}'
</DataRetriever>

<DataRetriever cacheable="true" method="getCityName" signature="ID">
select NAME from CITY
where ID=@{{ID}}
</DataRetriever>

<DataRetriever method="getPersonID" signature="NAME,CITY">
select ID from PERSON
where NAME='@{{NAME}}'
and ID_CITY=(select ID from CITY where NAME='@{{CITY}}')
</DataRetriever>

<DataRetriever cacheable="true" method="getCardID" signature="NUMBER,ID_OWNER">
select ID from CREDIT_CARD
where CNUMBER='@{{NUMBER}}'
and ID_OWNER=@{{ID_OWNER}}
</DataRetriever>

<DataRetriever method="getSeqVal">
select SEQ_PERSON_ID.nextval from dual
</DataRetriever>
</GenericRetriever>
</RetrieverConfig>
</syntaxhighlight>

Function description.
{|class="gvtable"
! Function !! Parameters !! Cacheable !! Description
|-
| getCityID || NAME || true || Returns the ID field of the first record of table CITY with field NAME equals to the passed parameter.<br/>The parameter is cacheable so, for the given parameter value, the subsequent call returns the same value.
|-
| getCityName || ID || true || Returns the NAME field of the first record of table CITY with field ID equals to the passed parameter.<br/>The parameter is cacheable so, for the given parameter value, the subsequent call returns the same value.
|-
| getPersonID || NAME,CITY || false || Returns the ID field of a record of table PERSON with field NAME equals to the first passed parameter and with an external reference to a record of table CITY with field NAME equals to the second passed parameter.
|-
| getCardID || NUMBER,ID_OWNER || true || Returns the ID field of the first record of table CREDIT_CARD with field CNUMBER equals to the first passed parameter and the field ID_OWNER equals to the second passed parameter.<br/>The parameter is cacheable so, for the given parameters value, the subsequent call returns the same value.
|-
| getSeqVal || || false || Returns the next sequence value.
|}

Usage examples in XSL transformation. The examples use the calling procedure of Java classes of [http://xml.apache.org/xalan-j/extensions.html#ex-java-namespace Xalan-J XSLT Engine].
<syntaxhighlight lang="xml">

<xsl:variable name="name" select="/PersonsData/PersonData/Name"/>
<xsl:variable name="city" select="/PersonsData/PersonData/City"/>
<xsl:element name="col">
<xsl:value-of
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getPersonID',concat($name,',',$city))"/>
</xsl:element>


<xsl:template match="PersonData">
<xsl:variable name="PersonId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getPersonID', concat(Name, ',', City))"/>
<xsl:variable name="CityId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getCityID', City)"/>
.....
<xsl:variable name="PersonId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getSeqVal', '')"/>
.....
<xsl:template match="CardData">
<xsl:param name="OwnerId"/>
<xsl:variable name="CardId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getCardID', concat(Number, ',', $OwnerId))"/>
</syntaxhighlight>

<div class="version_ge3.4.0.9">
From 3.4.0.9 version the getData method can accept 3 parameters, in order to specify the DataRetriever's actual parameters value separator, useful if some parameter value contains a comma.
<syntaxhighlight lang="xml">

<xsl:variable name="name" select="/PersonsData/PersonData/Name"/>
<xsl:variable name="city" select="/PersonsData/PersonData/City"/>
<xsl:element name="col">
<xsl:value-of
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getPersonID',concat($name,'$',$city), '$')"/>
</xsl:element>


<xsl:template match="PersonData">
<xsl:variable name="PersonId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getPersonID', concat(Name, '#', City), '#')"/>
.....
<xsl:template match="CardData">
<xsl:param name="OwnerId"/>
<xsl:variable name="CardId"
select="java:it.greenvulcano.gvesb.datahandling.utils.GenericRetriever.getData
('getCardID', concat(Number, '-', $OwnerId), '-')"/>
</syntaxhighlight>
</div>

DBOCallSP

2016-01-12T08:10:43Z

G.dimaio:

==Description==

The DBOCallSP element represents the DBO optimized for operations on store procedures.

=={{GVESB}} configuration==
[[File:DBOCallSP.jpg|thumb|DBOCallSP with VulCon]]
DBOCallSP might contain the following sub-elements:
* [[Description]]
* [[DHVariables]]
* [[CallDescriptor]]

Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dbo'''
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOCallSP'''
|-
| name || required || DBOCallSP name
|-
| transformation || optional || Transformation to be applied on the input data to obtain the internal XML commands.
|-
| force-mode || required || Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> call - call procedure mode.
The attribute's admitted values are:
* caller
* xml2db
|-
| execute-query || required || This parameter specifies is the callable statements must be executed with API CallableStatement#executeQuery(). <br/> Default is false.
The attribute's admitted values are:
* true
* false
|-
| jdbc-connection-name || required || DataSource JNDI name. <br/> Override connection defined in [[DBOBuilder]].
|-
| ignore-input || required || Tell the engine do not use the input data.
The attribute's admitted values are:
* true
* false
|-
| input-data || required || The default is the value of @name-Input. <br/> Can be set as the @output-data of a preceding DBO to use its output as input.
|-
| output-data || required || The default is the value of @name-Output.
|}

As an example, see the following stored procedure:
<syntaxhighlight lang="sql">
PROCEDURE LOAD_XML_FILE (v_file_name IN VARCHAR2, v_file IN CLOB, v_file_id OUT NUMBER) AS
....
</syntaxhighlight>
<syntaxhighlight lang="xml">
<dh-call class="it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation"
name="TestInsertXML" type="call">
<DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"
isXA="true" jdbc-connection-name="ds.gv_test"
name="TestInsertXML" transacted="true"
type="dbobuilder">
<DBOCallSP class="it.greenvulcano.gvesb.datahandling.dbo.DBOCallSP"
name="InsertXML" transformation="InsertXML"
type="dbo">
<CallDescriptor>
<statement id="0" type="callsp">begin load_xml_file(?, ?, ?); end;</statement>
<SPOutputParameters>
<SPOutputParameter db-type="number"
java-type="string" position="3"
prop-name="RESULT"
return-in-prop="false"/>
</SPOutputParameters>
</CallDescriptor>
</DBOCallSP>
</DBOBuilder>
</dh-call>
</syntaxhighlight>
The service receive as input an XML document (and a '''FILE_NAME''' property) and load it into a table, returning a number representing the key of the file in the table.
The '''InsertXML''' transformation create the following XML in order to provide the parameters for the procedure:
<syntaxhighlight lang="xml">
<RowSet>
<data>
<row id="0">
<col>Test.txt</col>
<col type="long-string"><PersonsData>
<PersonData>
<Name>ANTONIO ROSSI</Name>
<BirthDate>05/02/1980</BirthDate>
<City>MILANO</City>
</PersonData>
</PersonsData></col>
</row>
</data>
</RowSet>
</syntaxhighlight>
The '''DBOCallSP''' output is:
<syntaxhighlight lang="xml">
<RowSet>
<data id="0">
<row id="sp_result">
<col id="RESULT" type="string">11</col>
</row>
</data>
</RowSet>
</syntaxhighlight>

In order to invoke a stored function, as the following:
<syntaxhighlight lang="sql">
FUNCTION LOAD_XML_FILE (v_file_name IN VARCHAR2, v_file IN CLOB) RETURN NUMBER AS
....
</syntaxhighlight>
<syntaxhighlight lang="xml">
<dh-call class="it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation"
name="TestInsertXML" type="call">
<DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"
isXA="true" jdbc-connection-name="ds.gv_test"
name="TestInsertXML" transacted="true"
type="dbobuilder">
<DBOCallSP class="it.greenvulcano.gvesb.datahandling.dbo.DBOCallSP"
name="InsertXML" transformation="InsertXML"
type="dbo">
<CallDescriptor>
<statement id="0" type="callsp">begin ? := load_xml_file(?, ?); end;</statement>
<SPOutputParameters>
<SPOutputParameter db-type="number"
java-type="string" position="1"
prop-name="RESULT"
return-in-prop="false"/>
</SPOutputParameters>
</CallDescriptor>
</DBOCallSP>
</DBOBuilder>
</dh-call>
</syntaxhighlight>
The service receive as input an XML document (and a '''FILE_NAME''' property) and load it into a table, returning a number representing the key of the file in the table.
The '''InsertXML''' transformation create the following XML in order to provide the parameters for the procedure:
<syntaxhighlight lang="xml">
<RowSet>
<data>
<row id="0">
<col out-only="true"/>
<col>Test.txt</col>
<col type="long-string"><PersonsData>
<PersonData>
<Name>ANTONIO ROSSI</Name>
<BirthDate>05/02/1980</BirthDate>
<City>MILANO</City>
</PersonData>
</PersonsData></col>
</row>
</data>
</RowSet>
</syntaxhighlight>
Please note the first '''col''' element, containing the '''out-only''' attribute: it's required as a placeholder to tell the DataHandler the correct order of the input parameters to populate.
The '''DBOCallSP''' output is:
<syntaxhighlight lang="xml">
<RowSet>
<data id="0">
<row id="sp_result">
<col id="RESULT" type="string">11</col>
</row>
</data>
</RowSet>
</syntaxhighlight>

DBOCallSP

2016-01-12T07:58:04Z

G.dimaio:

Remotemanager-call

2015-11-20T18:57:43Z

G.dimaio:

==Description==

This {{GVESB}} plug-in allows you to perform a sequence of file operations in a remote file system accessible via various protocols.

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

The operations allowed are:
* Download a file/directory from a remote directory to a local directory
* Upload a file/directory from a local directory to a remote directory
* Control of one or more files (whose name corresponds to a date regular expressions) in a remote directory
* Deleting a file/directory from a remote directory
* Rename/move a file/directory in a remote directory

The remotemanager-call Element is used by [[Channel]] and [[routed-call]]. It has the attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''call'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.RemoteManagerCall'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|}

and the subelements:

* Description
* [[FTPManager]] | [[FTPSManager]] | [[SFTPManager]]
<div class="version_ge3.4.0.10">
| [[HDFSRemoteManager]]
</div>
* RemoteCommands

===RemoteCommands===

The RemoteCommands element contains the sequence of FTP operations to be carried out. These operations will be performed in the order they were configured. An error in one of the operation marked as critical will terminate the execution of the entire
sequence.

The RemoteCommands Element is used by [[remotemanager-call]] and, internally, it is possible to configure the following operations:
{|class="gvtable"
! Remote Command !! Use this for...
|-
| [[Remotemanager-call#RemoteSearchCommand | RemoteSearchCommand]] || Controlling one or more files (whose name corresponds to a regular expressions) in a remote directory
|-
| [[Remotemanager-call#RemoteMoveCommand |RemoteMoveCommand]] || Renaming/moving a file/directory in a remote directory
|-
| [[Remotemanager-call#RemoteDeleteCommand |RemoteDeleteCommand]] || Deleting a file/directory from a remote directory
|-
| [[Remotemanager-call#RemoteDownloadCommand |RemoteDownloadCommand]] || Downloading a file/directory from a remote directory to a local directory
|-
| [[Remotemanager-call#RemoteUploadCommand|RemoteUploadCommand]] || Uploading a file/directory from a local directory to a remote directory
|}

The remote commands can have the following subelements:
* Description
<div class="version_ge3.4.0.10">
* [[PropertyDef]]
</div>

====RemoteSearchCommand====

The {{GVESB}} operation '''RemoteSearchCommand''' checks if one or more files, whose name conforms to a given regular expression, exists within the specified directory.

On completion and in the absence of errors the following properties of output GVBuffer are setted:
# GVRM_FIND_FILES_NUM Number of files found (>= 0)
# GVRM_FIND_FILES_LIST List of names of found files, separated by ','. Set only if the value of field 'GVRM_FIND_FILES_NUM' is greater than 0. <br/> Both the pattern of the file and that the directory can be static or contain [[placeholders]] that are replaced at runtime.

The following table shows its attributes:

{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''remote-command'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVSearch'''.
|-
| sourcePath || required || Absolute path of the directory to search in.
|-
| filePattern || required || File name to search for. Can be a regular expression.
|-
| isCritical || optional || If true an internal error interrupt the command sequence. Default true.
|}

====RemoteMoveCommand====

The {{GVESB}} operation '''RemoteMoveCommand''' moves/renames a file/directory.

The file name, the source and destination directory names can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, all files of the source directory, whose name is in accordance with the corresponding pattern, will be moved to the destination directory. If the destination directory already contains files with the same name, they will be overwritten.

The following table shows its attributes:

{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''remote-command'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVMove'''.
|-
| targetPath || required || Absolute path of the file/directory where is the file to move.
|-
| oldName || required || Name of the file to be moved.
|-
| newName || required || Name of the file moved.
|-
| isCritical || optional || If true an internal error interrupt the command sequence. Default true.
|}

<div class="version_ge3.4.0.10">
The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:
{|class="gvtable"
! Property !! Possible Values
|-
| dfs.file.overwrite || true/false; default=false
|}
This parameter can be used to owerwrite the target destination with the source one when a move operation is used on the HDFS file system.

====RemoteDeleteCommand====

The {{GVESB}} operation '''RemoteDeleteCommand''' deletes a file or directory.

Both the file name and the directory can be static or contain [[placeholders]] that are replaced at runtime. After the replacement of the [[placeholders|placeholder]], the value of the ''filename'' may contain a regular expression, in which case, will erase all files in the specified directory whose name is consistent with the corresponding pattern.

The following table shows its attributes:

{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''remote-command'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDelete'''
|-
| targetPath || required || Absolute path of the file/directory to remove.
|-
| filePattern || optional || File name to remove. Might contain a regular expression. It is used only if ''targetPath'' is a directory, and if empty the filter is ignored.
|-
| isCritical || optional || If true an internal error interrupt the command sequence. Default true.
|}

====RemoteDownloadCommand====

The {{GVESB}} operation '''RemoteDownloadCommand''' downloads a file or directory from a remote directory and saved in the local directory you specified (or in GVBuffer).

File names and directories can be static or contain [[placeholders]] that are replaced at runtime.

The following table shows its attributes:

{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''remote-command'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVDownload'''.
|-
| remotePath || required || Pathname of remote directory containing the file to download. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.
|-
| remoteFilePattern || required || The name of the file to download.
|-
| toGVBufferExpression || optional || GVBuffer OGNL expression used to specify how to handle the current downloaded file. In the expression, the downloaded file will be referenced by the variable #input, and will be a byte [].
|-
| targetPath || optional || Pathname of the local directory to save the downloaded file. Must be an absolute pathname.
|-
| isCritical || optional || If true an internal error interrupt the command sequence. Default true.
|}

<div class="version_ge3.4.0.10">
The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:
{|class="gvtable"
! Property !! Possible Values
|-
| dfs.file.delete-source || fixed=false
|-
| dfs.file.raw-local-filesystem || fixed=true
|-
| dfs.stream-buffer-size || default: 4096
|}
These parameters can be used to specify the related action when a download operation is used on the HDFS file system.

====RemoteUploadCommand====

The {{GVESB}} operation '''RemoteUploadCommand''' uploads a file from a local directory (or [[GVBuffer]]) to the remote directory specified.

File and/or directory names can be static or contain [[placeholders]] that are replaced at runtime.

The following table shows its attributes:

{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''remote-command'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.file.remote.command.GVUpload'''.
|-
| sourcePath || optional || Pathname of the local directory where the file is transferred. Must be an absolute pathname.
|-
| sourceFilePattern || optional || The name of the file to transfer.
|-
| fromGVBufferExpression || optional || OGNL Expression applied to the current [[GVBuffer]] that specifies how to build the file content. In the expression, the [[GVBuffer]] is associated with #object, and must return a byte[].
|-
| remotePath || required || Pathname of remote directory where upload the file. It can be an absolute pathname or relative, in the second case it is relative to home directory of ftp user.
|-
| isCritical || optional || If true an internal error interrupt the command sequence. Default true.
|}

<div class="version_ge3.4.0.10">
The following table shows the PropertyDef possible elements that can be set when the command is executed on the [[HDFSRemoteManager|HDFS]] file system:
{|class="gvtable"
! Property !! Possible Values
|-
| dfs.file.delete-source || true/false; default=false
|-
| dfs.file.overwrite || true/false; default=false
|-
| dfs.permissions.path || Unix-like permission Example: 777; default 700
|-
| dfs.stream-buffer-size || default: 8192
|-
| dfs.replication || default: 1
|-
| dfs.blocksize || default: 4194304
|-
| dfs.permissions.user || hdfs user owner
|-
| dfs.permissions.group || hdfs user group
|}
These parameters can be used to owerwrite the target destination with the source one, set the replication, permissions and the other properties on destination target when an upload operation is used on the HDFS file system.

GVAdapterHttpConfiguration

2015-11-04T14:36:27Z

G.dimaio:

==Description==
The HTTP inbound adapter works identifying an Action and then defining a mapping between the Action and a Formatter.

The Action is defined by the value of the request parameter '''GV_ACTION''' '''(REMOVED in v3.4)'''.

The formatter defines how to parse the request parameters and how to build the response in case of successful or failed ESB's invocation.

The client can send HTTP requests at two url:
* <pre>http://<host>:<port>/gvhttp/inbound/<action></pre>
* <pre>http://<host>:<port>/gvhttp/secure/inbound/<action> (requires authentication)</pre>

=={{GVESB}} Configuration==
The GVAdapterHttpConfiguration Element is used by: GVAdapters.

The following table shows the '''GVAdapterHttpConfiguration''' attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''module'''.
|-
| name || fixed || Module Id always set to '''HTTP_ADAPTER'''.
|}

Contains the sub-elements [[#InboundConfiguration|InboundConfiguration]] [[#Formatters|Formatters]].

==InboundConfiguration==

Contains the sub-elements:
* [[#ActionMappings|ActionMappings]]
* [[#InboundTransactions|InboundTransactions]]

===ActionMappings===

This element can contain more sub-elements:
* [[#ActionMapping|ActionMapping]] '''(REMOVED in v3.3.4 and v3.4)'''
<div class="version_ge3.4/3.3.4">
* [[#GVCoreActionMapping|GVCoreActionMapping]]
* [[#ForwardActionMapping|ForwardActionMapping]]
</div>
<div class="version_ge3.4.0.3/3.3.4.1">
* [[#RESTActionMapping|RESTActionMapping]]
</div>

====ActionMapping====

An '''ActionMapping''' defines a mapping between a request Action and a configured Formatter.

The following table shows the '''ActionMapping''' attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| Action || required || Defines the action name, referenced by the request parameter '''GV_ACTION'''. The attribute's value cannot be null.
|-
| FormatterID || required || References a [[#Formatters|Formatter]] to be used to marshall/unmarshall the data. The attribute's value cannot be null.
|-
| RespContentType || optional || ContentType to be declared while handling HTTP responses to the external system. Default to text/html and is used only if not defined by the formatter.
The possible values are:
* text/html
* text/xml
* text/json
* text/javascript
* application/xml
* application/json
* application/x-www-form-urlencoded
|-
| enabled || required || This parameter defines if an action must be processed.
|}

Each '''ActionMapping''' can contain the following sub-elements:
* [[Description]]
* [[#RetCodeConversionIn|RetCodeConversionIn]]
* [[#RetCodeConversionOut|RetCodeConversionOut]]

====GVCoreActionMapping====

An '''GVCoreActionMapping''' defines a mapping between a request Action and a configured Formatter in order to invoke a {{GVESB}} service.

The following table shows the '''GVCoreActionMapping''' attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''action-mapping'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.adapter.http.mapping.GVCoreHttpServletMapping'''
|-
| Action || required || Defines the action name, must match or be a prefix in <action> part of request URL. The attribute's value cannot be null.
|-
| FormatterID || required || References a [[#Formatters|Formatter]] to be used to marshall/unmarshall the data. The attribute's value cannot be null.
|-
| RespContentType || optional || ContentType to be declared while handling HTTP responses to the external system. Default to text/html and is used only if not defined by the formatter.
The possible values are:
* text/html
* text/xml
* text/json
* text/javascript
* application/xml
* application/json
* application/x-www-form-urlencoded
|-
| enabled || required || This parameter defines if an action must be processed.
|-
| dump-in-out || optional || If true enable the dump of the input/output HTTP data. Default false.
|}

Sets the following properties in input to {{GVESB}} workflow:
{|class="gvtable"
! Property !! Description
|-
| HTTP_METHOD || Requested method
|-
| HTTP_ACTION || Request action
|-
| HTTP_REMOTE_ADDR || Client remote address
|}
<div class="version_ge3.4.0.2/3.3.4.1">
{|class="gvtable"
! Property !! Description
|-
| HTTP_PATH || Request URI path component
|}
</div>
<div class="version_ge3.4.0.4/3.3.4.2">
{|class="gvtable"
! Property !! Description
|-
| HTTP_QUERY || Request URI query component
|}
</div>

Each '''GVCoreActionMapping''' can contain the following sub-elements:
* [[Description]]
* [[#RetCodeConversionIn|RetCodeConversionIn]]
* [[#RetCodeConversionOut|RetCodeConversionOut]]

====ForwardActionMapping====

An '''ForwardActionMapping''' defines a mapping to a request Action in order to forward the request to a remote HTTP server.

The following table shows the '''ForwardActionMapping''' attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''action-mapping'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.adapter.http.mapping.ForwardHttpServletMapping'''
|-
| Action || required || Defines the action name, must match or be a prefix in <action> part of request URL. The attribute's value cannot be null.
|-
| enabled || required || This parameter defines if an action must be processed.
|-
| dump-in-out || optional || If true enable the dump of the input/output HTTP data. Default false.
|}

Each '''ForwardActionMapping''' can contain the following sub-elements:
* [[Description]]
* [[Http-call#endpoint|endpoint]]

====RESTActionMapping====

An '''RESTActionMapping''' defines a mapping between a request Action and a configured URI/Method Mapping in order to invoke a {{GVESB}} service.

The following table shows the '''RESTActionMapping''' attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''action-mapping'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.adapter.http.mapping.RESTHttpServletMapping'''
|-
| Action || required || Defines the action name, must match or be a prefix in <action> part of request URL. The attribute's value cannot be null.
|-
| RespContentType || optional || ContentType to be declared while handling HTTP responses to the external system. Default to application/xml and is used only if not defined by the {{GVESB}} service.
The possible values are:
* text/html
* text/xml
* text/json
* text/javascript
* application/xml
* application/json
* application/x-www-form-urlencoded
|-
| RespCharacterEncoding || optional || Character encoding to be used while handling HTTP responses to the external system. Default to UTF-8 and is used only if not defined by the {{GVESB}} service.
The possible values are:
* US-ASCII
* ISO-8859-1
* ISO-LATIN-1
* UTF-8
* UTF-16BE
* UTF-16LE
* UTF-16
|-
| enabled || required || This parameter defines if an action must be processed.
|-
| dump-in-out || optional || If true enable the dump of the input/output HTTP data. Default false.
|}

Sets the following properties in input to {{GVESB}} workflow:
{|class="gvtable"
! Property !! Description
|-
| HTTP_METHOD || Requested method
|-
| HTTP_ACTION || Request action
|-
| HTTP_PATH || Request URI path component
|-
| HTTP_REMOTE_ADDR || Client remote address
|-
| HTTP_REQ_CONTENT_TYPE || Request content type
|-
| HTTP_REQ_ACCEPT || Request Accept header value
|-
| HTTP_REQ_HEADERS || Contains, if configured in Mapping, the request HTTP headers as xml document, with the following structure
<Hdr>
<h n="hdr name" v="hdr value"/>
<h n="hdr name" v="hdr value"/>
</Hdr>
|-
|}
<div class="version_ge3.4.0.2/3.3.4.2">
{|class="gvtable"
! Property !! Description
|-
| HTTP_QUERY || Request URI query component
|}
</div>

The query string parameters (or x-www-form-urlencoded parameters in POST/PUT) are set as GVBuffer properties.
For POST/PUT requests, if the request content type is application/xml or application/json or text/* the request GVBuffer object will contain a String, for other request content types the request GVBuffer object will contain a byte[].

Set the following properties in output GVBuffer in order to control response parameters:
{|class="gvtable"
! Property !! Description
|-
| HTTP_RESP_STATUS_CODE || Optional, define the HTTP status response code
|-
| HTTP_RESP_STATUS_MSG || Optional, if defined the couple HTTP_RESP_STATUS_CODE and HTTP_RESP_STATUS_MSG defines the error response code
|-
| HTTP_RESP_CHAR_ENCODING || Optional, defines the response character encoding
|-
| HTTP_RESP_CONTENT_TYPE || Optional, defines the rsponse content type:
*if the response content type is application/xml or application/json or text/* the response GVBuffer object must contains a byte[], a String or a Document to be serialized
*for other response content types the response GVBuffer object must contains a byte[]
|-
|}

<div class="version_ge3.4.0.8">
{|class="gvtable"
! Property !! Description
|-
| HTTP_RESP_FILE_NAME || Optional, to define the name of the file to be downloaded through an HTTP request.
|}
</div>

Each '''RESTActionMapping''' can contain the following sub-elements:
* [[Description]]
* [[#Mapping|Mapping]]

====Mapping====
This element contains the mappings from request URI/Method and GV ESB service.
The following table shows the Mapping element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| method || required || Defines the HTTP Method to match.
The possible values are:
* GET
* PUT
* POST
* DELETE
|-
| pattern || required || Defines the rules to be matched in order to identify the request URI.
The URI pattern refers to the Path component only:
http://localhost:8080/gvhttp/inbound/AddressBook/entry/123
Path -> /AddressBook/entry/123
Sample mapping: /APPLICATION=AddressBook/E_COLLECTION=entry/E_UUID=\d+
The URL is splitted on / and must start with the string 'AddressBook', then must contain the string 'entry',
then the last tocken must match the regular expression '\d+' (must be a number of at least 1 digit).
On match, the input GVBuffer will contain the following properties:
APPLICATION = AddressBook
E_COLLECTION = entry
E_UUID = 123
|-
| service || required || The {{GVESB}} service to invoke
|-
| operation || required || The service operation to invoke
|-
| system || optional || The {{GVESB}} system to impersonate
|-
| extract-headers || optional || Defines if the request headers must be extracted. Default to false.
|}

====RetCodeConversionIn====

The following table shows the RetCodeConversionIn element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| RetCodeConversion || optional || The attribute's admitted values are:
* ignore
* 0to1
* 1to0
|}

====RetCodeConversionOut====

The following table shows the RetCodeConversionOut element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| RetCodeConversion || optional || The attribute's admitted values are:
* ignore
* 0to1
* 1to0
|}

===InboundTransactions===

This element contains the transaction definitions for the managed services.

Can contain the sub-element [[#Transaction|Transaction]].

====Transaction====

This element contains the transaction definitions for a given service.

All service managed by the '''GVAdapterHttpConfiguration''' should have a '''Transaction''' element that defines the transaction requirements.

The following table shows the '''Transaction'''attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| service || required || The service name. The attribute's value can't be null.
|-
| system || optional || Default is ALL.
|-
| transacted || required || This parameter defines if a service must be executed in transaction.
The attribute's admitted values are:
* true
* false
|-
| timeout || optional || This parameter defines the transaction timeout in seconds. Default is 30s.
|-
| close-on-response || optional || This parameter defines when transaction must be committed: before or after sending the response to the client. The default is before.
The attribute's admitted values are:
* after
* before
|}

Can contain the sub-element [[Description]].

==Formatters==
The Formatters are responsible for decoding the client request's parameters in order to create the input for a {{GVESB}} service and to convert the service's output into a HTTP response.

Can contain the sub-elements:
*[[ExtendedInboundParamHandlerFormatter]]

Esb 3 5 0 Trunk

2015-10-29T20:59:31Z

G.dimaio:

=={{GVESB}} source 3.5 Trunk==

*Commons
#Added capability to define a delayed initialization on JMXEntryPoint initializers, in order to avoid JMSListener/TimerTask dead-lock on startup recovery after a server crash
#Improved shutdown event management at EAR unloading
#Improved mixed (Unix/Win) path separator handling in file reading/writing on TextUtils and BinaryUtils classes
#Improved conversion of ISO8601 date-time in DateUtils
#Improved encrypt/decrypt of configuration parameters
#Improved reload configuration locking in order to avoid dead-lock
#Removed XPath engine re-initialization during startup.
#Removed recursive invocation of JMXEntrypoint.init() during Initializers execution.
#Improved (N)CLOB fields management in sqlX metadata.
#Corrected EML element definition in PopMessages.xsd
#Corrected JSON<->XML numeric values conversion
#Corrected jms-dequeue/@decorate-gvbuffer definition in GVCore.dtd

*[[GVScriptConfig|Scripting]]
#Added integration framework for JSR-223 "Scripting for the Java Platform", in order to replace current OGNL/JavaScript only processors
#Added JSR-223 engine provider for GV specific OGNL library
#The framework details:
#*usable script engine must at least have MULTITHREADED capability
#*if the script engine implements Compilable interface and the script DESN'T USE placeholders, the script itself is precompiled and reused for better performances
#*XML configuration of scrip handler (language, script or script-file... to be added support for implicit #include of utility scripts)
#*in-line script (as current script processor)
#*external script file
#*improved explicit #include directive to dinamically merge utility scripts
#*all external script file are cached, and the configured paths must be relative to $gv.app.home/scripts folder
#Completed integration of JSR-223 script engines (not in OGNL expression evaluator in ODP)
#Added support to base execution context configuration
#Added script engine configuration deploy to GVConsole
#Removed dependency from Rhino javascript engine
#Various modification to metadata framework and in its client classes
#Added examples that demonstrate various use cases using the following languages (also provided into release package):
#*JavaScript
#*OGNL
#*Groovy
#*JRuby

*Core
#Improved transaction error management in workflow engine
#Moved to INFO level the end trace message of workflow nodes, added execution time in ms
#Added a [[GVOperationNode#json-validation-service|JSON schema validation plug-in]] to be used as Inpu/Ouput Service
#Corrected @loggerLevel handling in GVCoreCallNode, GVIteratorOperationNode/CoreCall and parallel nodes
#Added to [[GVCoreCallNode]] and [[GVIteratorOperationNode#CoreCall | GVIteratorOperationNode/CoreCall]] a new attibute change-log-master-service. If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file. Used only if @change-log-context is true.
#Corrected GVCore pool element clean-up after configuration reload

*DTE ([[XML2JSONTransformation|XML2JSON]] [[JSON2XMLTransformation|JSON2XML]])
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
#*enable the JSON2XML transformer to specify a list of JSON property names to be set as element attributes in output XML
#*enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
#Enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as String values in output JSON, ignoring automatic type conversion
#Improved namespaces exclusion in JSON <-> XML simple conversion policy and added a BadgerFish conversion policy
#Moved to a GV specific version of org.json json library: now the properties creation order is keep in dump and properties listing, in order of better handle conversion to/from XML documents
#Improved management of multi-root JSON document in JSON <-> XML simple conversion policy
#Improved empty array management in XML to JSON conversion
#Changed cardinality of ToPreload DTE element

*Adapters
#Enabled missing [[FTPSManager|FTPS]] remote manager in dtds
#Added [[GVAdamAdapterManager|ADAM]] (Agile Digital Archive Manager) adapter which provides a [[adamsearch-call|search]] operation in order to retrieve hosted documets
#Added an Hadoop HDFS Adapter which provides a [[HDFSRemoteManager|RemoteManager]] implementation that extends the capability of [[remotemanager-call]] and [[fsmonitor-call]]
#Added [[GVPushNotificationManager|Push Notification Adapter]], with Android and iOS notification engine implementation

*DataHandler
#Improved SQL exception message propagation in DBOxxxSelect
#Corrected connection release fake error message when using dynamic connection name definition in DBOBuilder
#In DBOCallSP the "Cursor closed" error is intercepted and don't prevent a successful call completation, returning the other procedure output parameters
#Added to DataHandler's [[DBOInsert]]/[[DBOUpdate]] the capability to handle auto-generated keys at runtime (es. auto-increment primary key field)
#Corrected NullPointerException in DH DBOInsert/DBOUpdate without an input XML
#Improved handling of NCHAR,NVARCHAR,NCLOB fields in DataHandler
#Improved dynamic connection naming in DH external retriever helper
#Added support in DataHandler's [[DBOInsert]]/[[DBOUpdate]] to statements with named parameters, in addition to question mark parameters
#Resolved a column name misreading error in DataHandler's extended RowSet builder
#Added capability to DBOxxxFlatSelect to write extracted records directly into a local file, in order to better handle massive data extractions.
#Provided a new getData method on DH retrievers in order to specify the parameter's actual values separator; useful if the default separator (comma) is present into the parameter's actual values

*Task Scheduler
#Improved transaction's timeout management in Service caller timer task
#Improved TaskManager reload configuration locking in order to avoid dead-lock.
#Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order to append to Scheduler's Threads name also the executing TaskGroup.TaskName in order to simplify troubleshooting
#Improved init/run logging of ServiceCallerTask.NextAction status

*JMS Listener
#Improved debug logging in JMSForwardListener
#Improved concurrent access to HL7ConnectionValidator
#Improved Dump of JMS's MapMessage
#Added an utility class (to be used in ODP) to convert a JMS's message to XML document
#Improved listeners instantiation algorithm in JMS listener pool

*RSH Handler
#Corrected RMI hostname definition in RSH start script

*Adapter/VCL Axis2
#Corrected mixed SOAP 1.1/1.2 request/response handling in Axis2MessageContextDataProvider
#Added new property [[GVWebServices#VulCon_.2F_GV_Console_Configuration | WS_REQ_SOAP_VERSION]] to input GVBuffer
#Improved Axis2 HTTP connection pool management in ws-call

*Adapter [[GVAdapterHttpConfiguration|HTTP]]
#Improved request body handling for POST and PUT HTTP methods in HTTP Inbound Adapter
#Added new GVCore Http servlet mapping's input property: HTTP_PATH containing request's path info
#Added a RESTfull Mapper to HTTP Adapter Inbound, in order to improve publishing of RESTfull services
#Added input http headers management in REST servlet mapping. Improved HTTP Inbound dtd documentation
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer
#Improved customization of status messages in response header for HTTP Adapter Inbound
#Added management of output GVBuffer property HTTP_RESP_FILE_NAME to [[GVAdapterHttpConfiguration#RESTActionMapping|RESTActionMapping]] in order to define the name of the file to be downloaded through an HTTP request

*GVConsole
#Corrected deployment of WSDL files contained in sub-folders
#Improved automatic deployment of service's ACL configuration
#Wrong url generation fixed, in Parameter section, "GreenVulcanoESB - Core Services configuration" menu, Search operation
#Corrected GVConsole's services deployment section when used in HTTPS
#Added automatic deploy of JSON Schemas in GVConsole
#Improved DTD referencing and deploy of aliased DTE Transformations

*VCL OpenSPCoop
#Improved GV request/response marshalling

*VCL Mail
#Improved Session initialization using local properties in smtp-call
#Corrected default value for @email-rx-cleaner regular expression in receive email VCL Operations

*VCL File
#Corrected zip file closing on unzip operation
#Added to RemoteManager methods the capability to provide at the real implementations a Map containing implementation-specific properties
#Updated the [[Remotemanager-call#RemoteCommands|remote commands]] to reads a list of properties from configuration

*VCL [[pdfreader-call]]
#Added a VCL plug-in in order to convert a PDF file to an XML document containing its metadata and stripped page's text
#Added to pdfreader-call the capability to embed into the output XML the PDF document ad base64 encoded element

*VCL HTTP
#Corrected RegisterHttpClientProtocolManager initialization, in order to avoid double JMX registration.
#Added new output property to http-call VCL plug-in: GVHTTP_RESPONSE_MESSAGE containing the response status text

*VCL J2EE
#Added to JMS Enqueue/Dequeue VCL operations the capability to exclude:
#*GVBuffer -> Message properties enrichment during enqueue
#*Message -> GVBuffer properties enrichment during dequeue

*VCL Excel
#Improved Excel Report generator in order to generate report based on XML data

Excel-call

2015-10-29T20:51:04Z

G.dimaio:

==Description==

The {{GVESB}} plugin excell-call allows you to define the information needed to generate Excel reports from a select on the DB.

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

The excel-call Element is used by [[Channel]] and [[routed-call]]. It has the following attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''call'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.excel.GVExcelCallOperation'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|-
| group || optional || Reports group name.
|-
| report || optional || Report name.
|}

and the subelements:
* Description
* GVExcelReport

===GVExcelReport===

Defines the configuration elements of an Excel report. It is used by '''excel-call''' and [[excelreader-call]] and has the following attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required ||Report name
|-
| group || optional || Report group. Default Generic.
|-
| jdbc-connection || required || JNDI name of a DataSource.
|-
| format || optional || Name of the style of the report. Default ''default''.
|}

<div class="version_ge3.4.0.10">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| mode || optional || Defines the source of the data to be converted in Excel file:
*sql: the data are extracted from a DB though an SQL statement
*xml: the data are extracted from an XML document contained into GVBuffer.object field
Default to sql.
|}
</div>

Its subelements are:
* Description
* Sheet(s)

====Sheet====

This element defines the configuration of each sheet of the Report.

The Sheet Element is used by '''GVExcelReport'''. Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| id || required || Sheet id.
|-
| name || required || Sheet name.
|-
| title || optional || Sheet title.
|-
| jdbc-connection || optional || JNDI name of a DataSource. Default to Report connection.
|}

<div class="version_ge3.4.0.10">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| fields || optional || Useful only for XML mode, defines the list of (row) element's attributes (and their order) to be shown in the Excel sheet.
|}
</div>

and its sub-elements:
* [[Description]]
* [[#prep-statement|prep-statement]]
* [[statement]]

=====prep-statement=====

Preparation statement for Excel report generation. Are executed after the report statement. Can contains [[placeholders]].

Its attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || required ||
Must be '''Excel Sheet: insert|update|callsp'''. The attribute's admitted values are:
* select
* insert
* update
* callsp
|-
| id || optional || prep-statement Id.
|}

==Examples==
The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[excel-call]] operation in SQL mode:

<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
<GVSystems name="SYSTEMS" type="module">
<Systems>
<System id-system="system-name" system-activation="on">
<Channel id-channel="CHANNEL_NAME">
<excel-call class="it.greenvulcano.gvesb.virtual.excel.GVExcelCallOperation"
name="listPerson" type="call">
<GVExcelReport format="default" group="CREDIT"
jdbc-connection="ds.gv_test" name="listPerson">
<Sheet id="1" name="Person List"
title="Person List - timestamp{{dd/MM/yyyy HH:mm:ss}}">
<statement type="select"><![CDATA[select p.NAME as "Name", p.BIRTHDATE as "Birth Date", c.NAME as "City"
from PERSON p, CITY c
where p.ID_CITY = c.ID
decode{{@{{NAME}}::NULL::::and p.NAME='@{{NAME}}'}}
order by c.NAME, p.NAME]]></statement>
</Sheet>
<Sheet id="2" name="Credit Card List"
title="Credit Card List - timestamp{{dd/MM/yyyy HH:mm:ss}}">
<statement type="select"><![CDATA[select p.NAME as "Name", cc.CNUMBER as "Card Number", cc.CREDIT as "Credit", decode(cc.ENABLED, 'Y', 'Yes', 'No') as "Active"
from PERSON p, CREDIT_CARD cc
where p.ID = cc.ID_OWNER
decode{{@{{NAME}}::NULL::::and p.NAME='@{{NAME}}'}}
order by p.NAME]]></statement>
</Sheet>
</GVExcelReport>
</excel-call>
</Channel>
</System>
</Systems>
</GVSystems>
</syntaxhighlight>

The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[excel-call]] operation in XML mode:

<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
<GVSystems name="SYSTEMS" type="module">
<Systems>
<System id-system="system-name" system-activation="on">
<Channel id-channel="CHANNEL_NAME">
<excel-call class="it.greenvulcano.gvesb.virtual.excel.GVExcelCallOperation"
name="TestXmlExcel" type="call">
<GVExcelReport format="default" group="AAA_GRP" mode="xml"
jdbc-connection="something" name="TestXmlExcel">
<Sheet id="1" name="Name Sheet 1 of TestXmlExcel" title="Title Sheet 1 of TestXmlExcel"
fields="Name,Surname,BirthDate,City">
<statement id="1" type="select"><![CDATA[/RowSet/data[@id="0"]/row]]></statement>
</Sheet>
<Sheet id="2" name="Name Sheet 2 of TestXmlExcel" title="Title Sheet 2 of TestXmlExcel"
fields="Name,Surname,CardNumber">
<statement id="2" type="select"><![CDATA[/RowSet/data[@id="1"]/row]]></statement>
</Sheet>
</GVExcelReport>
</excel-call>
</Channel>
</System>
</Systems>
</GVSystems>
</syntaxhighlight>
And the following is a sample input XML:
<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
<RowSet>
<data id="0">
<row BirthDate="05/02/1980" City="MILANO" Name="ANTONIO" Surname="ROSSI" blablabla="ccmocmso"/>
<row BirthDate="15/08/1970" City="MILANO" Name="MARIO" Surname="BIANCHI" blablabla="ccmocmso"/>
<row BirthDate="02/10/1979" City="ROMA" Name="ANCO" Surname="MARZIO" blablabla="ccmocmso"/>
<row BirthDate="10/07/1984" City="NAPOLI" Name="CIRO" Surname="ESPOSITO" blablabla="ccmocmso"/>
</data>
<data id="1">
<row CardNumber="1111222233338888" Name="ANTONIO" Surname="ROSSI" blablabla="ccmocmso"/>
<row CardNumber="1234123415555666" Name="MARIO" Surname="BIANCHI" blablabla="ccmocmso"/>
<row CardNumber="1111222233335555" Name="ANCO" Surname="MARZIO" blablabla="ccmocmso"/>
<row CardNumber="1111222233336666" Name="CIRO" Surname="ESPOSITO" blablabla="ccmocmso"/>
</data>
</RowSet>
</syntaxhighlight>

Excel-call

2015-10-29T20:43:19Z

G.dimaio: /* GVExcelReport */

Esb 3 5 0 Trunk

2015-10-29T20:35:07Z

G.dimaio:

=={{GVESB}} source 3.5 Trunk==

*Commons
#Added capability to define a delayed initialization on JMXEntryPoint initializers, in order to avoid JMSListener/TimerTask dead-lock on startup recovery after a server crash
#Improved shutdown event management at EAR unloading
#Improved mixed (Unix/Win) path separator handling in file reading/writing on TextUtils and BinaryUtils classes
#Improved conversion of ISO8601 date-time in DateUtils
#Improved encrypt/decrypt of configuration parameters
#Improved reload configuration locking in order to avoid dead-lock
#Removed XPath engine re-initialization during startup.
#Removed recursive invocation of JMXEntrypoint.init() during Initializers execution.
#Improved (N)CLOB fields management in sqlX metadata.
#Corrected EML element definition in PopMessages.xsd
#Corrected JSON<->XML numeric values conversion
#Corrected jms-dequeue/@decorate-gvbuffer definition in GVCore.dtd

*[[GVScriptConfig|Scripting]]
#Added integration framework for JSR-223 "Scripting for the Java Platform", in order to replace current OGNL/JavaScript only processors
#Added JSR-223 engine provider for GV specific OGNL library
#The framework details:
#*usable script engine must at least have MULTITHREADED capability
#*if the script engine implements Compilable interface and the script DESN'T USE placeholders, the script itself is precompiled and reused for better performances
#*XML configuration of scrip handler (language, script or script-file... to be added support for implicit #include of utility scripts)
#*in-line script (as current script processor)
#*external script file
#*improved explicit #include directive to dinamically merge utility scripts
#*all external script file are cached, and the configured paths must be relative to $gv.app.home/scripts folder
#Completed integration of JSR-223 script engines (not in OGNL expression evaluator in ODP)
#Added support to base execution context configuration
#Added script engine configuration deploy to GVConsole
#Removed dependency from Rhino javascript engine
#Various modification to metadata framework and in its client classes
#Added examples that demonstrate various use cases using the following languages (also provided into release package):
#*JavaScript
#*OGNL
#*Groovy
#*JRuby

*Core
#Improved transaction error management in workflow engine
#Moved to INFO level the end trace message of workflow nodes, added execution time in ms
#Added a [[GVOperationNode#json-validation-service|JSON schema validation plug-in]] to be used as Inpu/Ouput Service
#Corrected @loggerLevel handling in GVCoreCallNode, GVIteratorOperationNode/CoreCall and parallel nodes
#Added to [[GVCoreCallNode]] and [[GVIteratorOperationNode#CoreCall | GVIteratorOperationNode/CoreCall]] a new attibute change-log-master-service. If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file. Used only if @change-log-context is true.
#Corrected GVCore pool element clean-up after configuration reload

*DTE ([[XML2JSONTransformation|XML2JSON]] [[JSON2XMLTransformation|JSON2XML]])
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
#*enable the JSON2XML transformer to specify a list of JSON property names to be set as element attributes in output XML
#*enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
#Enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as String values in output JSON, ignoring automatic type conversion
#Improved namespaces exclusion in JSON <-> XML simple conversion policy and added a BadgerFish conversion policy
#Moved to a GV specific version of org.json json library: now the properties creation order is keep in dump and properties listing, in order of better handle conversion to/from XML documents
#Improved management of multi-root JSON document in JSON <-> XML simple conversion policy
#Improved empty array management in XML to JSON conversion
#Changed cardinality of ToPreload DTE element

*Adapters
#Enabled missing [[FTPSManager|FTPS]] remote manager in dtds
#Added [[GVAdamAdapterManager|ADAM]] (Agile Digital Archive Manager) adapter which provides a [[adamsearch-call|search]] operation in order to retrieve hosted documets
#Added an Hadoop HDFS Adapter which provides a [[HDFSRemoteManager|RemoteManager]] implementation that extends the capability of [[remotemanager-call]] and [[fsmonitor-call]]
#Added [[GVPushNotificationManager|Push Notification Adapter]], with Android and iOS notification engine implementation

*DataHandler
#Improved SQL exception message propagation in DBOxxxSelect
#Corrected connection release fake error message when using dynamic connection name definition in DBOBuilder
#In DBOCallSP the "Cursor closed" error is intercepted and don't prevent a successful call completation, returning the other procedure output parameters
#Added to DataHandler's [[DBOInsert]]/[[DBOUpdate]] the capability to handle auto-generated keys at runtime (es. auto-increment primary key field)
#Corrected NullPointerException in DH DBOInsert/DBOUpdate without an input XML
#Improved handling of NCHAR,NVARCHAR,NCLOB fields in DataHandler
#Improved dynamic connection naming in DH external retriever helper
#Added support in DataHandler's [[DBOInsert]]/[[DBOUpdate]] to statements with named parameters, in addition to question mark parameters
#Resolved a column name misreading error in DataHandler's extended RowSet builder
#Provided a new getData method on DH retrievers in order to specify the parameter's actual values separator; useful if the default separator (comma) is present into the parameter's actual values

*Task Scheduler
#Improved transaction's timeout management in Service caller timer task
#Improved TaskManager reload configuration locking in order to avoid dead-lock.
#Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order to append to Scheduler's Threads name also the executing TaskGroup.TaskName in order to simplify troubleshooting
#Improved init/run logging of ServiceCallerTask.NextAction status

*JMS Listener
#Improved debug logging in JMSForwardListener
#Improved concurrent access to HL7ConnectionValidator
#Improved Dump of JMS's MapMessage
#Added an utility class (to be used in ODP) to convert a JMS's message to XML document
#Improved listeners instantiation algorithm in JMS listener pool

*RSH Handler
#Corrected RMI hostname definition in RSH start script

*Adapter/VCL Axis2
#Corrected mixed SOAP 1.1/1.2 request/response handling in Axis2MessageContextDataProvider
#Added new property [[GVWebServices#VulCon_.2F_GV_Console_Configuration | WS_REQ_SOAP_VERSION]] to input GVBuffer
#Improved Axis2 HTTP connection pool management in ws-call

*Adapter [[GVAdapterHttpConfiguration|HTTP]]
#Improved request body handling for POST and PUT HTTP methods in HTTP Inbound Adapter
#Added new GVCore Http servlet mapping's input property: HTTP_PATH containing request's path info
#Added a RESTfull Mapper to HTTP Adapter Inbound, in order to improve publishing of RESTfull services
#Added input http headers management in REST servlet mapping. Improved HTTP Inbound dtd documentation
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer
#Improved customization of status messages in response header for HTTP Adapter Inbound
#Added management of output GVBuffer property HTTP_RESP_FILE_NAME to [[GVAdapterHttpConfiguration#RESTActionMapping|RESTActionMapping]] in order to define the name of the file to be downloaded through an HTTP request

*GVConsole
#Corrected deployment of WSDL files contained in sub-folders
#Improved automatic deployment of service's ACL configuration
#Wrong url generation fixed, in Parameter section, "GreenVulcanoESB - Core Services configuration" menu, Search operation
#Corrected GVConsole's services deployment section when used in HTTPS
#Added automatic deploy of JSON Schemas in GVConsole
#Improved DTD referencing and deploy of aliased DTE Transformations

*VCL OpenSPCoop
#Improved GV request/response marshalling

*VCL Mail
#Improved Session initialization using local properties in smtp-call
#Corrected default value for @email-rx-cleaner regular expression in receive email VCL Operations

*VCL File
#Corrected zip file closing on unzip operation
#Added to RemoteManager methods the capability to provide at the real implementations a Map containing implementation-specific properties
#Updated the [[Remotemanager-call#RemoteCommands|remote commands]] to reads a list of properties from configuration

*VCL [[pdfreader-call]]
#Added a VCL plug-in in order to convert a PDF file to an XML document containing its metadata and stripped page's text
#Added to pdfreader-call the capability to embed into the output XML the PDF document ad base64 encoded element

*VCL HTTP
#Corrected RegisterHttpClientProtocolManager initialization, in order to avoid double JMX registration.
#Added new output property to http-call VCL plug-in: GVHTTP_RESPONSE_MESSAGE containing the response status text

*VCL J2EE
#Added to JMS Enqueue/Dequeue VCL operations the capability to exclude:
#*GVBuffer -> Message properties enrichment during enqueue
#*Message -> GVBuffer properties enrichment during dequeue

*VCL Excel
#Improved Excel Report generator in order to generate report based on XML data

Esb 3 5 0 Trunk

2015-10-29T20:27:19Z

G.dimaio:

=={{GVESB}} source 3.5 Trunk==

*Commons
#Added capability to define a delayed initialization on JMXEntryPoint initializers, in order to avoid JMSListener/TimerTask dead-lock on startup recovery after a server crash
#Improved shutdown event management at EAR unloading
#Improved mixed (Unix/Win) path separator handling in file reading/writing on TextUtils and BinaryUtils classes
#Improved conversion of ISO8601 date-time in DateUtils
#Improved encrypt/decrypt of configuration parameters
#Improved reload configuration locking in order to avoid dead-lock
#Removed XPath engine re-initialization during startup.
#Removed recursive invocation of JMXEntrypoint.init() during Initializers execution.
#Improved (N)CLOB fields management in sqlX metadata.
#Corrected EML element definition in PopMessages.xsd
#Corrected JSON<->XML numeric values conversion
#Corrected jms-dequeue/@decorate-gvbuffer definition in GVCore.dtd

*[[GVScriptConfig|Scripting]]
#Added integration framework for JSR-223 "Scripting for the Java Platform", in order to replace current OGNL/JavaScript only processors
#Added JSR-223 engine provider for GV specific OGNL library
#The framework details:
#*usable script engine must at least have MULTITHREADED capability
#*if the script engine implements Compilable interface and the script DESN'T USE placeholders, the script itself is precompiled and reused for better performances
#*XML configuration of scrip handler (language, script or script-file... to be added support for implicit #include of utility scripts)
#*in-line script (as current script processor)
#*external script file
#*improved explicit #include directive to dinamically merge utility scripts
#*all external script file are cached, and the configured paths must be relative to $gv.app.home/scripts folder
#Completed integration of JSR-223 script engines (not in OGNL expression evaluator in ODP)
#Added support to base execution context configuration
#Added script engine configuration deploy to GVConsole
#Removed dependency from Rhino javascript engine
#Various modification to metadata framework and in its client classes
#Added examples that demonstrate various use cases using the following languages (also provided into release package):
#*JavaScript
#*OGNL
#*Groovy
#*JRuby

*Core
#Improved transaction error management in workflow engine
#Moved to INFO level the end trace message of workflow nodes, added execution time in ms
#Added a [[GVOperationNode#json-validation-service|JSON schema validation plug-in]] to be used as Inpu/Ouput Service
#Corrected @loggerLevel handling in GVCoreCallNode, GVIteratorOperationNode/CoreCall and parallel nodes
#Added to [[GVCoreCallNode]] and [[GVIteratorOperationNode#CoreCall | GVIteratorOperationNode/CoreCall]] a new attibute change-log-master-service. If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file. Used only if @change-log-context is true.
#Corrected GVCore pool element clean-up after configuration reload

*DTE ([[XML2JSONTransformation|XML2JSON]] [[JSON2XMLTransformation|JSON2XML]])
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
#*enable the JSON2XML transformer to specify a list of JSON property names to be set as element attributes in output XML
#*enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
#Enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as String values in output JSON, ignoring automatic type conversion
#Improved namespaces exclusion in JSON <-> XML simple conversion policy and added a BadgerFish conversion policy
#Moved to a GV specific version of org.json json library: now the properties creation order is keep in dump and properties listing, in order of better handle conversion to/from XML documents
#Improved management of multi-root JSON document in JSON <-> XML simple conversion policy
#Improved empty array management in XML to JSON conversion
#Changed cardinality of ToPreload DTE element

*Adapters
#Enabled missing [[FTPSManager|FTPS]] remote manager in dtds
#Added [[GVAdamAdapterManager|ADAM]] (Agile Digital Archive Manager) adapter which provides a [[adamsearch-call|search]] operation in order to retrieve hosted documets
#Added an Hadoop HDFS Adapter which provides a [[HDFSRemoteManager|RemoteManager]] implementation that extends the capability of [[remotemanager-call]] and [[fsmonitor-call]]
#Added [[GVPushNotificationManager|Push Notification Adapter]], with Android and iOS notification engine implementation

*DataHandler
#Improved SQL exception message propagation in DBOxxxSelect
#Corrected connection release fake error message when using dynamic connection name definition in DBOBuilder
#In DBOCallSP the "Cursor closed" error is intercepted and don't prevent a successful call completation, returning the other procedure output parameters
#Added to DataHandler's [[DBOInsert]]/[[DBOUpdate]] the capability to handle auto-generated keys at runtime (es. auto-increment primary key field)
#Corrected NullPointerException in DH DBOInsert/DBOUpdate without an input XML
#Improved handling of NCHAR,NVARCHAR,NCLOB fields in DataHandler
#Improved dynamic connection naming in DH external retriever helper
#Added support in DataHandler's [[DBOInsert]]/[[DBOUpdate]] to statements with named parameters, in addition to question mark parameters
#Resolved a column name misreading error in DataHandler's extended RowSet builder
#Provided a new getData method on DH retrievers in order to specify the parameter's actual values separator; useful if the default separator (comma) is present into the parameter's actual values

*Task Scheduler
#Improved transaction's timeout management in Service caller timer task
#Improved TaskManager reload configuration locking in order to avoid dead-lock.
#Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order to append to Scheduler's Threads name also the executing TaskGroup.TaskName in order to simplify troubleshooting
#Improved init/run logging of ServiceCallerTask.NextAction status

*JMS Listener
#Improved debug logging in JMSForwardListener
#Improved concurrent access to HL7ConnectionValidator
#Improved Dump of JMS's MapMessage
#Added an utility class (to be used in ODP) to convert a JMS's message to XML document
#Improved listeners instantiation algorithm in JMS listener pool

*RSH Handler
#Corrected RMI hostname definition in RSH start script

*Adapter/VCL Axis2
#Corrected mixed SOAP 1.1/1.2 request/response handling in Axis2MessageContextDataProvider
#Added new property [[GVWebServices#VulCon_.2F_GV_Console_Configuration | WS_REQ_SOAP_VERSION]] to input GVBuffer
#Improved Axis2 HTTP connection pool management in ws-call

*Adapter [[GVAdapterHttpConfiguration|HTTP]]
#Improved request body handling for POST and PUT HTTP methods in HTTP Inbound Adapter
#Added new GVCore Http servlet mapping's input property: HTTP_PATH containing request's path info
#Added a RESTfull Mapper to HTTP Adapter Inbound, in order to improve publishing of RESTfull services
#Added input http headers management in REST servlet mapping. Improved HTTP Inbound dtd documentation
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer
#Improved customization of status messages in response header for HTTP Adapter Inbound
#Added management of output GVBuffer property HTTP_RESP_FILE_NAME to [[GVAdapterHttpConfiguration#RESTActionMapping|RESTActionMapping]] in order to define the name of the file to be downloaded through an HTTP request

*GVConsole
#Corrected deployment of WSDL files contained in sub-folders
#Improved automatic deployment of service's ACL configuration
#Wrong url generation fixed, in Parameter section, "GreenVulcanoESB - Core Services configuration" menu, Search operation
#Corrected GVConsole's services deployment section when used in HTTPS
#Added automatic deploy of JSON Schemas in GVConsole
#Improved DTD referencing and deploy of aliased DTE Transformations

*VCL OpenSPCoop
#Improved GV request/response marshalling

*VCL Mail
#Improved Session initialization using local properties in smtp-call
#Corrected default value for @email-rx-cleaner regular expression in receive email VCL Operations

*VCL File
#Corrected zip file closing on unzip operation
#Added to RemoteManager methods the capability to provide at the real implementations a Map containing implementation-specific properties
#Updated the [[Remotemanager-call#RemoteCommands|remote commands]] to reads a list of properties from configuration

*VCL [[pdfreader-call]]
#Added a VCL plug-in in order to convert a PDF file to an XML document containing its metadata and stripped page's text
#Added to pdfreader-call the capability to embed into the output XML the PDF document ad base64 encoded element

*VCL HTTP
#Corrected RegisterHttpClientProtocolManager initialization, in order to avoid double JMX registration.
#Added new output property to http-call VCL plug-in: GVHTTP_RESPONSE_MESSAGE containing the response status text

*VCL J2EE
#Added to JMS Enqueue/Dequeue VCL operations the capability to exclude:
#*GVBuffer -> Message properties enrichment during enqueue
#*Message -> GVBuffer properties enrichment during dequeue

Esb 3 5 0 Trunk

2015-10-28T20:24:50Z

G.dimaio:

=={{GVESB}} source 3.5 Trunk==

*Commons
#Added capability to define a delayed initialization on JMXEntryPoint initializers, in order to avoid JMSListener/TimerTask dead-lock on startup recovery after a server crash
#Improved shutdown event management at EAR unloading
#Improved mixed (Unix/Win) path separator handling in file reading/writing on TextUtils and BinaryUtils classes
#Improved conversion of ISO8601 date-time in DateUtils
#Improved encrypt/decrypt of configuration parameters
#Improved reload configuration locking in order to avoid dead-lock
#Removed XPath engine re-initialization during startup.
#Removed recursive invocation of JMXEntrypoint.init() during Initializers execution.
#Improved (N)CLOB fields management in sqlX metadata.
#Corrected EML element definition in PopMessages.xsd
#Corrected JSON<->XML numeric values conversion
#Corrected jms-dequeue/@decorate-gvbuffer definition in GVCore.dtd

*[[GVScriptConfig|Scripting]]
#Added integration framework for JSR-223 "Scripting for the Java Platform", in order to replace current OGNL/JavaScript only processors
#Added JSR-223 engine provider for GV specific OGNL library
#The framework details:
#*usable script engine must at least have MULTITHREADED capability
#*if the script engine implements Compilable interface and the script DESN'T USE placeholders, the script itself is precompiled and reused for better performances
#*XML configuration of scrip handler (language, script or script-file... to be added support for implicit #include of utility scripts)
#*in-line script (as current script processor)
#*external script file
#*improved explicit #include directive to dinamically merge utility scripts
#*all external script file are cached, and the configured paths must be relative to $gv.app.home/scripts folder
#Completed integration of JSR-223 script engines (not in OGNL expression evaluator in ODP)
#Added support to base execution context configuration
#Added script engine configuration deploy to GVConsole
#Removed dependency from Rhino javascript engine
#Various modification to metadata framework and in its client classes
#Added examples that demonstrate various use cases using the following languages (also provided into release package):
#*JavaScript
#*OGNL
#*Groovy
#*JRuby

*Core
#Improved transaction error management in workflow engine
#Moved to INFO level the end trace message of workflow nodes, added execution time in ms
#Added a [[GVOperationNode#json-validation-service|JSON schema validation plug-in]] to be used as Inpu/Ouput Service
#Corrected @loggerLevel handling in GVCoreCallNode, GVIteratorOperationNode/CoreCall and parallel nodes
#Added to [[GVCoreCallNode]] and [[GVIteratorOperationNode#CoreCall | GVIteratorOperationNode/CoreCall]] a new attibute change-log-master-service. If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file. Used only if @change-log-context is true.
#Corrected GVCore pool element clean-up after configuration reload

*DTE ([[XML2JSONTransformation|XML2JSON]] [[JSON2XMLTransformation|JSON2XML]])
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
#*enable the JSON2XML transformer to specify a list of JSON property names to be set as element attributes in output XML
#*enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
#Enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as String values in output JSON, ignoring automatic type conversion
#Improved namespaces exclusion in JSON <-> XML simple conversion policy and added a BadgerFish conversion policy
#Moved to a GV specific version of org.json json library: now the properties creation order is keep in dump and properties listing, in order of better handle conversion to/from XML documents
#Improved management of multi-root JSON document in JSON <-> XML simple conversion policy
#Improved empty array management in XML to JSON conversion
#Changed cardinality of ToPreload DTE element

*Adapters
#Enabled missing [[FTPSManager|FTPS]] remote manager in dtds
#Added [[GVAdamAdapterManager|ADAM]] (Agile Digital Archive Manager) adapter which provides a [[adamsearch-call|search]] operation in order to retrieve hosted documets
#Added an Hadoop HDFS Adapter which provides a [[HDFSRemoteManager|RemoteManager]] implementation that extends the capability of [[remotemanager-call]] and [[fsmonitor-call]]
#Added [[GVPushNotificationManager|Push Notification Adapter]], with Android and iOS notification engine implementation

*DataHandler
#Improved SQL exception message propagation in DBOxxxSelect
#Corrected connection release fake error message when using dynamic connection name definition in DBOBuilder
#In DBOCallSP the "Cursor closed" error is intercepted and don't prevent a successful call completation, returning the other procedure output parameters
#Added to DataHandler's [[DBOInsert]]/[[DBOUpdate]] the capability to handle auto-generated keys at runtime (es. auto-increment primary key field)
#Corrected NullPointerException in DH DBOInsert/DBOUpdate without an input XML
#Improved handling of NCHAR,NVARCHAR,NCLOB fields in DataHandler
#Improved dynamic connection naming in DH external retriever helper
#Added support in DataHandler's [[DBOInsert]]/[[DBOUpdate]] to statements with named parameters, in addition to question mark parameters
#Resolved a column name misreading error in DataHandler's extended RowSet builder
#Provided a new getData method on DH retrievers in order to specify the parameter's actual values separator; useful if the default separator (comma) is present into the parameter's actual values

*Task Scheduler
#Improved transaction's timeout management in Service caller timer task
#Improved TaskManager reload configuration locking in order to avoid dead-lock.
#Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order to append to Scheduler's Threads name also the executing TaskGroup.TaskName in order to simplify troubleshooting
#Improved init/run logging of ServiceCallerTask.NextAction status

*JMS Listener
#Improved debug logging in JMSForwardListener
#Improved concurrent access to HL7ConnectionValidator
#Improved Dump of JMS's MapMessage
#Added an utility class (to be used in ODP) to convert a JMS's message to XML document
#Improved listeners instantiation algorithm in JMS listener pool

*RSH Handler
#Corrected RMI hostname definition in RSH start script

*Adapter/VCL Axis2
#Corrected mixed SOAP 1.1/1.2 request/response handling in Axis2MessageContextDataProvider
#Added new property [[GVWebServices#VulCon_.2F_GV_Console_Configuration | WS_REQ_SOAP_VERSION]] to input GVBuffer
#Improved Axis2 HTTP connection pool management in ws-call

*Adapter [[GVAdapterHttpConfiguration|HTTP]]
#Improved request body handling for POST and PUT HTTP methods in HTTP Inbound Adapter
#Added new GVCore Http servlet mapping's input property: HTTP_PATH containing request's path info
#Added a RESTfull Mapper to HTTP Adapter Inbound, in order to improve publishing of RESTfull services
#Added input http headers management in REST servlet mapping. Improved HTTP Inbound dtd documentation
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer
#Improved customization of status messages in response header for HTTP Adapter Inbound
#Added management of output GVBuffer property HTTP_RESP_FILE_NAME to [[GVAdapterHttpConfiguration#RESTActionMapping|RESTActionMapping]] in order to define the name of the file to be downloaded through an HTTP request

*GVConsole
#Corrected deployment of WSDL files contained in sub-folders
#Improved automatic deployment of service's ACL configuration
#Wrong url generation fixed, in Parameter section, "GreenVulcanoESB - Core Services configuration" menu, Search operation
#Corrected GVConsole's services deployment section when used in HTTPS
#Added automatic deploy of JSON Schemas in GVConsole
#Improved DTD referencing and deploy of aliased DTE Transformations

*VCL OpenSPCoop
#Improved GV request/response marshalling

*VCL Mail
#Improved Session initialization using local properties in smtp-call
#Corrected default value for @email-rx-cleaner regular expression in receive email VCL Operations

*VCL File
#Corrected zip file closing on unzip operation
#Added to RemoteManager methods the capability to provide at the real implementations a Map containing implementation-specific properties
#Updated the [[Remotemanager-call#RemoteCommands|remote commands]] to reads a list of properties from configuration

*VCL [[pdfreader-call]]
#Added a VCL plug-in in order to convert a PDF file to an XML document containing its metadata and stripped page's text
#Added to pdfreader-call the capability to embed into the output XML the PDF document ad base64 encoded element

*VCL HTTP
#Corrected RegisterHttpClientProtocolManager initialization, in order to avoid double JMX registration.

*VCL J2EE
#Added to JMS Enqueue/Dequeue VCL operations the capability to exclude:
#*GVBuffer -> Message properties enrichment during enqueue
#*Message -> GVBuffer properties enrichment during dequeue

GVIteratorOperationNode

2015-10-28T20:03:36Z

G.dimaio: /* CoreCall */

==Description==

Node that can perform a sequence of invocations to the operations of the VCL or other workflows.

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

The GVIteratorOperationNode is a [[Flow]] element that extends [[FlowNode]].

The iterations are made on the elements of a collection built by a [[CollectionDataProvider]] configured through the attribute 'collection-DP'. Collection elements are inserted in the [[GVBuffer]] object to pass to the plug-in with which loop through invocations.

You can configure a condition of premature exit from the loop.

By default, even if a particular iteration throws an exception all the iterations will be executed anyway.

The following table shows the GVIteratorOperationNode element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVIteratorOperationNode'''.
|-
| op-type || required || Indicates the type of operation that {{GVESB}} must execute:
* call: perform an VCL invocation.
* enqueue: perform a send a message.
* corecall: execute an service call.
* subcall: execute an subflow call.
|-
| collection-dp || optional || Name of [[Data_provider|Data Provider]] to use. Must return a collection of objects.
The attribute's value can't be null.
|-
| accumulate-output || optional || If true, output of each iteration is to an array containing the previous iteration's output.
Default is true.
|}

Might have the following subelements:
* [[#CoreCall|CoreCall]]
* [[#proxy-call|proxy-call]] or [[#proxy-enqueue|proxy-enqueue]]
* [[#SubFlowCall|SubFlowCall]]
* [[#exit-loop-condition|exit-loop-condition]]
* [[GVOperationNode#InputServices|InputServices]]
* [[GVOperationNode#OutputServices|OutputServices]]

===CoreCall===

Defines the parameters to invoke a {{GVESB}} service.
Dynamic fields can contains [[placeholders]].

The following table shows the CoreCall element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| dynamic || optional || If 'true' then id-system, id-service and operation attributes can contains metadata to be resolved at runtime.
Default ''false''.
|-
| id-service || required || Name of [[Service]] to call.
|-
| id-system || optional || Name of service's client.
|-
| operation || required || Operation to invoke on the service.
Corresponds to a {{GVESB}} communication operation or to a forward.
|-
| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use for modifying the [[GVBuffer]] content at each iteration.
|-
| change-log-context || optional || If true change the log context fields according to the new [[System]]/[[Service]]/[[Operation]] values.
Default ''true''.
|}
<div class="version_ge3.4.0.9">
{|class="gvtable"
! Attribute !! Tyte !! Description
|-
| change-log-master-service || optional || If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file.
Used only if @change-log-context is true.
Default false.
|}
</div>

===proxy-call===

Operation useful as a proxy to other Call operation.

The following table shows the proxy-call element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| type || fixed || This attribute must assume the value '''call'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.internal.ProxyCallOperation'''.
|-
| name || required || Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations.
|-
| id-system || required || System providing the Call operation to call.
|-
| id-channel || required || System's channel.
|-
| operation || required || Channel's Call operation.
|}

Its subelements are:
* Description
* [[ServiceAlias]]

===proxy-enqueue===

Operation useful as a proxy to other Enqueue operation.

The following table shows the proxy-enqueue element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| type || fixed || This attribute must assume the value '''enqueue'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.internal.ProxyEnqueueOperation'''.
|-
| name || required || Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations.
|-
| id-system || required || System providing the Call operation to call.
|-
| id-channel || required || System's channel.
|-
| operation || required || Channel's Enqueue operation.
|}

Its sub-elements are:
* Description
* [[ServiceAlias]]

===SubFlowCall===

This element defines the parameters to invoke a {{GVESB}} Operation's [[SubFlow]].

Dynamic fields can contains the [[placeholders]] that will be replaced at runtime.

The following table shows the SubFlowCall element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| dynamic || optional || If ''true'' then [[SubFlow]] attribute might contain [[placeholders]] to be resolved at runtime.
The default is 'false'.
|-
| subflow || required || Name of [[SubFlow]] to call.
|-
| ref-dp || optional || Name of [[Data provider]] to use for modifying the [[GVBuffer]] content at each iteration.
|-
| change-log-context || optional || If true change the log context fields according to the new Operation([[SubFlow]]) value.
Default true.
|}

===exit-loop-condition===

Defines a condition that occur during an iteration, causing the interruption of the loop calls.

Might contain the following sub-elements:
* Description
* [[#exception-event|exception-event]]

====exception-event====

Defines the type of exception that, if launched at an iteration, causes the interruption of the loop calls.

The following table shows the exception-event element's attributes:
{|class="gvtable"
! Attribute !! Type || Description
|-
| value || optional || The type of exception.
If the execution of a call sequence throws an exception of this type (or its subtype), the loop stops.

The attribute's default value is: java.lang.Exception.
|-
| rethrow || optional || Through this attribute you can specify whether the exception that it stopped the loop iterations must be
propagated (causing the total failure of the call to [[GVIteratorOperationNode]] plug-in) or be retained.

The default value is 'true'.
|}

GVCoreCallNode

2015-10-28T20:03:13Z

G.dimaio:

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

GVCoreCallNode element allows direct invocation of a {{GVESB}} core workflow, is a [[Flow]] element that extends [[FlowNode]].

Dynamic fields can contains [[placeholders]].

The following table shows the GVCoreCallNode element's attributes:
{|class="gvtable"
! Attribute !! Tyte !! Description
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVCoreCallNode'''.
|-
| op-type || fixed || This attribute must assume the value '''corecall'''.
|-
| dynamic || optional || If 'true' id-system, id-service and operation attributes can contains [[placeholders|metadata]] to be resolved at runtime.
|-
| id-service || required || Name of service to invoke.
|-
| id-system || optional || Name of service's client.
|-
| operation || required || Name of service's operation to invoke
|-
| overwrite-sys-svc || optional || If 'true' SYSTEM and SERVICE fields of [[GVBuffer]] will be overwritten.
The default is 'false'.
|-
| change-log-context || optional || If 'true' log context is updated.
The default is 'true'.
|-
| input-ref-dp || optional || Name of [[Data_provider|Data Provider]] to use for input manipulation.
This Data Provider will receive in input a [[GVBuffer]] and must return the object to be inserted in GVBuffer.object.
|-
| output-ref-dp || optional || Name of [[Data_provider|Data Provider]] to use for output manipulation.
This Data Provider will receive in input a [[GVBuffer]] and must return the object to be inserted in GVBuffer.object.
|}

<div class="version_ge3.4.0.9">
{|class="gvtable"
! Attribute !! Tyte !! Description
|-
| change-log-master-service || optional || If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file.
Used only if @change-log-context is true.
Default false.
|}
</div>

and the subelements:
<div class="version_ge3.4">
* [[GVOperationNode#InputServices|InputServices]]
* [[GVOperationNode#OutputServices|OutputServices]]
</div>

GVWebServices

2015-10-28T20:00:06Z

G.dimaio:

==Description==

The element GVWebServices allows to define the [[Web Services]] implemented by {{GVESB}}.

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

The GVWebServices Element is present in the {{VULCON}} Adapter view, as a GVAdapters subelement.

The following table shows GVWebServices element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| version || fixed || This attribute must assume the value '''1.0'''.
|-
| type || fixed || This attribute must assume the value '''module'''.
|-
| name || fixed || This attribute must assume the value '''WEB_SERVICES'''.
|}

Its subelements are:
* [[Description]]
* [[GVWebServices#GreenVulcanoWebServices|GreenVulcanoWebServices]]
* [[GVWebServices#BusinessWebServices|BusinessWebServices]]
* [[GVWebServices#UDDI|UDDI]]
* [[GVWebServices#AxisExtra|AxisExtra]]

The {{GVESB}} service input GVBuffer contains the following properties:
* WS_SERVICE : name of the invoked webservice
* WS_OPERATION : name of the invoked webservice's operation
* WS_REMOTE_ADDR : remote address of the invoking client
* WS_CONTENT_TYPE : request content type
<div class="version_ge3.4.0.9">
* WS_REQ_SOAP_VERSION : request SOAP version URI
</div>

<div class="version_ge3.3">
===GreenVulcanoWebServices===
You can expose a {{GVESB}} core through the configuration of a generic Web Service.
This element represents the {{GVESB}} {{GVWS}} definition.
You can retrieve the WSDL at the address:<pre>http://<host>:<port>/gvaxis2/services/GreenVulcanoWebservice?wsdl</pre>

{|class="gvtable"
! Attribute !! Type !! Description
|-
| gv-service || required || Service name with which to perform the invocation of GreenVulcano ESB..
|-
| gv-operation || required || GreenVulcano ESB operation to invoke.
|-
| transacted || optional || Indicates whether the invocation to be performed in GreenVulcano is transactional or not.
Default: false

A transaction is rolled back if:
* the service ends with exception
* the output SOAP response is a Fault
* the output GVBuffer contains the property WS_FORCE_TX_ROLLBACK=Y
|-
| tx-timeout || optional || Transaction timeout in seconds.
Default: 30s
|-
| force-https || optional || Indicates whether the protocol is https or not.
Default: false
|-
| intput-dp || optional || DataProvider be used to process input data.
|-
| output-dp || optional || DataProvider be used to process response data.
|}
</div>

===BusinessWebServices===

Business web services definition on Axis2.

The following table shows the BusinessWebServices element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| wsdl-directory || required || Directory containing the generated WSDL for the services exposed through Axis2.
|-
| services-directory || required || Directory containing the services generated from a WSDL using Axis2.
|-
| authenticated-http-soap-address || optional || This is the default URL that is used to build the soap:
address for [[Web Services]] that require authentication exposed with http protocol.
This URL can be overridden on different services.
If not specified will be required to define it on the services.
The final URL will be formed by concatenating the name of the service: default-soap-address/service
|-
| authenticated-https-soap-address || optional || This is the default URL that is used in the build the soap:address for web services that require authentication exposed with https protocol.
This URL can be overridden on different services.
If not specified will be required to define it on the services.
The final URL will be formed by concatenating the name of the service: default-soap-address/service
|-
| http-soap-address || optional || This is the default URL that is used in the build the soap:address for web services that not require authentication exposed with http protocol.
This URL can be overridden on different services.
If not specified will be required to define it on the services.
The final URL will be formed by concatenating the name of the service: default-soap-address/service
|-
| https-soap-address || optional || This is the default URL that is used in the build the soap:address for web services that not require authentication exposed with https protocol.
This URL can be overridden on different services.
If not specified will be required to define it on the services.
The final URL will be formed by concatenating the name of the service: default-soap-address/service
|}

Its subelements are:
* [[Description]]
* [[#WebService|WebService]]

====WebService====

This element allows to define a business web services.

The following table shows the WebService element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| web-service || required || The attribute's value can't be null.
|-
| force-https || optional || The attribute's admitted values are:
* true
* false
|-
| soap-address || optional || Il soap:address will be exactly the here specified url.
As a difference with the default-soap-address, it won't be made any composition with the service name.
If default-soap-address is not specified, this is mandatory.
The attribute's value can't be null.
|-
| input-xsd || optional || The path of the XSD that defines the types of input that will be declared in the generated WSDL.
May contain an absolute path or a relative path, in which case, is relative to <nowiki>${{gv.app.home}}/xmlconfig/xsds.</nowiki>
May contain [[placeholders]]. May also include the types of output, in this case does not specify the parameter 'output-xsd'.
The attribute's value can't be null.
|-
| output-xsd || optional || The path of the XSD that defines the types of output that will be declared in the generated WSDL.
May contain an absolute path or a relative path, in which case, is relative to <nowiki>${{gv.app.home}}/xsds.</nowiki>
If not specified only the parameter 'input-xsd' will be used.
The attribute's value can't be null.
|-
| targetNS-from-xsd || optional || Defines if the target namespace of the types in the WSDL shall be that specified in the XSD input. If "false", the target namespace is: <nowiki>http://www.greenvulcano.it/greenvulcano</nowiki>
The attribute's admitted values are:
* true
* false
|-
| useOriginalwsdl || optional || The attribute's admitted values are:
* true
* false
|}

Its subelements are:
* [[Description]]
* [[GVWebServices#WSOperation|WSOperation]]
* [[GVWebServices#Transport|Transport]]
* [[GVWebServices#EngageModule|EngageModule]]

=====WSOperation=====

This element defines the Web Service Operation.

The following table shows the WSOperation element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| operation-qname || required || Qualified Name (QName) of the operation exposed by the web service.
If the namespace is present, it must be specified in braces:
{namespace}localname
|-
| soap-action || optional || MIME Header SOAPAction of the HTTP request.
If not specified is set to SERVICE/OPERATION
|-
| ref-dp || optional || DataProvider to be used for sending the reply to the caller.
The DataProvider will return a MessageContext to be sent as a reply.
If not used, the webservice adapter expects a org.apache.axiom.soap.SOAPEnvelope into object field of GVBuffer.
|}

It has the subelements:
* [[Description]]
* [[GVWebServices#Binding|Binding]]
* [[GVWebServices#PolicyData|PolicyData]]

=====Binding=====

Defined the {{GVESB}} workflow to invoke.

The following table shows the Binding element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| gv-service || required || {{GVESB}} service id
|-
| gv-system || optional || {{GVESB}} system id
|-
| gv-operation || required || service's operation to invoke.
|-
| inputType || optional || Defines how to set the object field of input GVBuffer:
* context : the MessageContext
* envelope : the envelope as XML serialized as string
* body : the body as XML serialized as string
* body-element : the first child of body as XML serialized as string
* header : the header as XML serialized as string
* envelope-om : the envelope as OMElement
* body-om : the body as OMElement
* body-element-om : the first child of body as OMElement
* header-om : the header as OMElement
Default: context
|-
| transaction || optional || Indicates whether the invocation to be performed in {{GVESB}} is transactional or not.
Default: false

A transaction is rolled back if:
** the service ends with exception
** the output SOAP response is a Fault
** the output GVBuffer contains the property WS_FORCE_TX_ROLLBACK=Y
|-
| tx-timeout || optional || Transaction timeout in seconds.
Default to 30s.
|}

=====PolicyData=====

This element is an XML that describes the policies for a specific. Currently it is used only for the WS-Security implemented by the module 'rampart'.

Follows an example of policy to be included on the module 'rampart':
<syntaxhighlight lang="XML">
<wsp:Policy wsu:Id="UTOverTransport" xmlns:wsu="http://docs.oasis-open.org/
wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite> <wsp:Policy> <sp:Basic256/> </wsp:Policy> </sp:AlgorithmSuite>
<sp:Layout> <wsp:Policy> <sp:Lax/> </wsp:Policy> </sp:Layout>
<sp:IncludeTimestamp/>
</wsp:Policy>
</sp:TransportBinding>
<sp:SignedSupportingTokens xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:UsernameTokensp:
IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"/>
</wsp:Policy>
</sp:SignedSupportingTokens>
<ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
<ramp:user>alice</ramp:user>
<ramp:passwordCallbackClass>org.apache.rampart.samples.policy.sample01.PWCBHandler
</ramp:passwordCallbackClass>
</ramp:RampartConfig>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</syntaxhighlight>

The PolicyData Element is used by:
* [[#EngageModule|EngageModule]]
* [[#WSOperation|WSOperation]]

The following table shows the PolicyData element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| policy_key || required || Defines the key to set the policy for the service invocation.
The attribute's admitted values are:
* rampartPolicy
|}

=====Transport=====

Transport configured for webservices.

Its subelements are:
* [[Description]]
* soap
* soap12
* rest : with the attributes
{|class="gvtable"
! Attribute !! Type !! Description
|-
| verb || optional || The attribute's admitted values are:
* GET
* POST
* PUT
* DELETE
|}
* jms : with the attributes
{|class="gvtable"
! Attribute !! Type !! Description
|-
| connectionFactory || optional ||
|-
| initialContextFactory || optional ||
|-
| jndiURL || optional ||
|-
| destination || optional ||
|-
| replyDestination || optional ||
|-
| destinationType || optional || The attribute's admitted values are:
* queue
* topic
|-
| contentType || optional ||
|-
| bytesMessage || optional ||
|-
| textMessage || optional ||
|}

=====EngageModule=====

The EngageModule Element is used by: [[Ws-call#AxisWebServiceInvoker|AxisWebServiceInvoker]] and WebService.

The following table shows the EngageModule element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || Defines the name of a module to hire to handle WS-*.
If set, takes precedence over the attribute 'specifications'.
The attribute's admitted values are:
* rampart
* sandesha2
|-
| type || optional || Defines the class that implements the hander for the module to engage.
The attribute's default value is '''it.greenvulcano.gvesb.virtual.ws.module.DefaultModuleHandler'''.
The attribute's admitted values are:
* it.greenvulcano.gvesb.virtual.ws.module.rampart.RampartModuleHandler
* it.greenvulcano.gvesb.virtual.ws.module.sandesha2.Sandesha2ModuleHandler
The attribute's value can't be null.
|-
| specification || optional || The specification to implement, mandatory and other than 'NO-SPEC' if the name attribute is not declared.
The attribute's default value is: NO-SPEC.
The attribute's admitted values are:
* NO-SPEC
* WS-Security
* WS-ReliableMessaging
|}

Its subelements are:
* Description
* [[GVWebServices#PolicyData|PolicyData]]
* [[GVWebServices#ModuleProperty|ModuleProperty]]

=====ModuleProperty=====

This element set specific properties for the module to engage.

For example, the property 'org.apache.axis2.addressing.AddressingConstants.DISABLE_OUTBOUND_ADDRESSING_VALIDATION' setted to 'true' prevents a fault if SOAPAction is not set.

The following table shows the ModuleProperty element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || The attribute's value can't be null.
|-
| value || required || The attribute's value can't be null.
|-
| type || optional || The attribute's default value is: String.
The attribute's admitted values are:
* String
* Boolean
* Byte
* Short
* Int
* Long
* Float
* Double
|}

===UDDI===

The UDDI Element is used by: GVWebServices.

Might contain the following sub-elements:
* [[Description]]
* [[#JAXMLRegistry|JAXMLRegistry]]
* [[#Proxy|Proxy]]

====JAXMLRegistry====

{{GVESB}} implementation for the UDDI Server JUDDI.

The following table shows the JAXMLRegistry element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.j2ee.xmlRegistry.impl.RegistryImpl'''.
|-
| type || fixed || This attribute must assume the value '''xmlregistry'''.
|-
| id-registry || required || Unique identifier of XMLRegistry
|-
| query-url || required || URL definition to perform the query
|-
| publish-url || required || Definition of the URL to make the publication
|-
| user-name || optional || Defining the user name for authentication on the Registry
|-
| password || optional || Defining the password for authentication on the Registry. #Encrypted
|-
| organization-name || optional || Defining the desired organization's name on the Registry
|}

Its sub-elements are:
* [[Description]]
* [[#Properties|Properties]]

=====Properties=====

List of the properties needed to access the UDDI server.

Its sub-elements are:
* [[Description]]
* [[#connectionFactory|connectionFactory]]
* [[#connectionProperty|connectionProperty]]

=====connectionFactory=====

{{GVESB}} Connection Factory.

The following table show the connectionFactory element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| value || required || Full qualified name of the connection factory.
|}

=====connectionProperty=====

Defines a property to access the UDDI server.

The following table shows the connectionProperty element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || required || Property type.
|-
| name || required || Fully qualified interface name.
|-
| value || required || Fully qualified name of te implementation.
|}

=====Proxy=====

This element defines the Proxy configuration.

It is used by: [[Http-call#endpoint|endpoint]], '''UDDI''' and [[ws-call]].

The following table shows the Proxy element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| host || required || Proxy server IP or name.
|-
| port || optional || Proxy server port. Default: 80
|-
| user || optional || User name.
|-
| password || optional || User password. #Encrypted
|}

===AxisExtra===

The AxisExtra Element is used by: GVWebServices and it is visible from {{L_VULCON}} in the Adapter View.

Its sub-elements are:
* [[Description]]
* [[GVWebServices#PasswordCallback|PasswordCallback]]

====PasswordCallback====

Contains the PwCbBasicHandler items whose attributes are:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''pwcb'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.ws.rampart.policy.pwcb.PwCbBasicHandler'''.
|}

The PwCbBasicHandler Element contains the sub-elements:
* [[Description]]
* [[GVWebServices#UserDef|UserDef]]

=====UserDef=====

Each UserDef Element allows to define an User.

The following table shows the UserDef element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| name || required || The attribute's value can't be null.
|-
| password || required || #Encrypted
|}

Esb 3 4 0 9 Final

2015-10-28T19:58:57Z

G.dimaio: Created page with "=={{GVESB}} package 3.4.0.9 Final== *Commons #Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order ..."

=={{GVESB}} package 3.4.0.9 Final==

*Commons
#Added to TaskManager the capability to interrupt running Tasks execution on configuration reloading. Modified TaskManager in order to append to Scheduler's Threads name also the executing TaskGroup.TaskName in order to simplify troubleshooting.
#Corrected jms-dequeue/@decorate-gvbuffer definition in GVCore.dtd.

*Core
#Corrected @loggerLevel handling in GVCoreCallNode, GVIteratorOperationNode/CoreCall and parallel nodes
#Added to [[GVCoreCallNode]] and [[GVIteratorOperationNode#CoreCall | GVIteratorOperationNode/CoreCall]] a new attibute change-log-master-service. If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file. Used only if @change-log-context is true.
#Improved init/run logging of ServiceCallerTask.NextAction status

*DataHandler
#Provided a new getData method on DH retrievers in order to specify the parameter's actual values separator; useful if the default separator (comma) is present into the parameter's actual values

*Adapter/VCL Axis2
#Corrected mixed SOAP 1.1/1.2 request/response handling in Axis2MessageContextDataProvider.
#Added new property [[GVWebServices#VulCon_.2F_GV_Console_Configuration | WS_REQ_SOAP_VERSION]] to input GVBuffer.

*VCL Mail
#Corrected default value for @email-rx-cleaner regular expression in receive email VCL Operations

GreenVulcanoVersions

2015-10-28T19:47:08Z

G.dimaio:

==GreenVulcano ESB versions==
Following {{GVESB}} versions list organized by maturity level. Click on the version's number to see the change-log.

===Development versions===
{|class="gvtable" | Version | Released
|-
| [[esb_3_5_0_Trunk]] || to be released
|}

===Current stable versions===
{|class="gvtable" | Version | Released
|-
| [[esb_3_4_0_9_Final]] || 2015-10-28
|-
| [[patch_3_4_0_8_Final]] || 2015-06-10
|-
| [[esb_3_4_0_7_Final]] || 2015-02-13
|-
| [[esb_3_4_0_6_Final]] || 2014-11-27
|-
| [[patch_3_4_0_5_Final]] || 2014-09-21
|-
| [[patch_3_4_0_4_Final]] || 2014-09-12
|-
| [[patch_3_4_0_3_Final]] || 2014-07-31
|-
| [[esb_3_4_0_2_Final]] || 2014-07-16
|-
| [[esb_3_4_0_Final]] || 2014-05-23
|}

===Maintenance versions===
{|class="gvtable" | Version | Released
|-
| [[patch_3_3_4_2_Final]] || 2014-09-21
|-
| [[patch_3_3_4_1_Final]] || 2014-07-31
|-
| [[esb_3_3_4_Final]] || 2014-07-16
|-
| [[esb_3_3_3_Final]] || 2013-11-06
|-
| [[esb_3_3_2_Final]] || 2013-07-24
|-
| [[esb_3_3_1_Final]] || 2013-05-27
|-
| [[esb_3_3_0_Final]] || 2013-03-04
|}

Esb 3 5 0 Trunk

2015-10-28T19:44:48Z

G.dimaio:

Patch 3 3 4 2 Final

2015-10-28T19:43:19Z

G.dimaio:

=={{GVESB}} patch 3.3.4.2 Final==

*Commons
#Improved Dump of JMS's MapMessage
#Added an utility class (to be used in ODP) to convert a JMS's message to XML document
#Corrected default delete filter in LogCleanerTask
#Improved conversion of ISO8601 date-time in DateUtils

*DataHandler
#In DBOCallSP the "Cursor closed" error is intercepted and don't prevent a successful call completation, returning the other procedure output parameters

*DTE ([[XML2JSONTransformation|XML2JSON]] [[JSON2XMLTransformation|JSON2XML]])
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
##enable the JSON2XML transformer to specify a list of JSON property names to be set as element attributes in output XML
##enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
##enable the XML2JSON transformer to specify a list of XML element names to be forcefully set as String values in output JSON, ignoring automatic type conversion

*Adapter HTTP Inbound
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer ([[GVAdapterHttpConfiguration|see]])
#Improved customization of status messages in response header for HTTP Adapter Inbound

*Adapter HL7
#Corrected HAPI base library in 3.3.4 branch

JSONUtils

2015-10-28T19:42:18Z

G.dimaio:

Class FQN: '''it.greenvulcano.util.json.JSONUtils'''

==Following the JSONUtils public static methods==
* Parsing & Conversion
<syntaxhighlight lang="java5">
/**
* Convert the input XML to a JSONObject.
* JSON does not distinguish between elements and attributes.
* Sequences of similar elements are represented as JSONArrays.
* If an element have attributes, content text/cdata may be placed in a "contentText" member.
* Comments and namespaces are ignored.
* If the root element is 'DEFAULT_ROOT' then isn't included into JSON output.
*
* @param xml
* the document to convert
* @return a JSONObject representing the JSON document
* @throws JSONUtilsException when error occurs
*/
public static JSONObject xmlToJson(Object xml) throws JSONUtilsException

/**
* Convert the input XML to a JSONObject.
* JSON does not distinguish between elements and attributes.
* Sequences of similar elements (or elements which local-name are in forceElementsArray)
* are represented as JSONArrays.
* If an element have attributes, content text/cdata may be placed in a "contentText" member.
* Comments and namespaces are ignored.
* If the root element is 'DEFAULT_ROOT' then isn't included into JSON output.
*
* @param xml
* the document to convert
* @param forceElementsArray
* a set containing element's local-name to be forced as JSONArray also if in single instance
* @param forceStringValue
* a set containing element's local-name to be forced as String values, ignoring type conversions
* @return a JSONObject representing the XML document
* @throws JSONUtilsException
*/
public static JSONObject xmlToJson(Object xml, Set<String> forceElementsArray, Set<String> forceStringValue) throws JSONUtilsException

/**
* Convert a JSONObject into an XML structure.
* If the JSON to be converted doesn't have a single root element
* then is automatically created a 'DEFAULT_ROOT' root element.
*
* @param json
* a JSONObject
* @return a Node representing the JSON document
* @throws JSONException
*/
public static Node jsonToXml(Object json) throws JSONUtilsException

/**
* Convert a JSONObject into an XML structure.
* If the JSON to be converted doesn't have a single root element
* then is automatically created a 'DEFAULT_ROOT' root element.
*
* @param json
* a JSONObject
* @param forceAttribute
* a set containing keys name to be set as XML attributes
* @return a Node representing the JSON document
* @throws JSONException
*/
public static Node jsonToXml(Object json, Set<String> forceAttributes) throws JSONUtilsException

/**
* Convert a JSONObject into Node structure.
* If not specified a rootName and the JSON to be converted doesn't have
* a single root element then is automatically created a 'DEFAULT_ROOT' root element.
*
* @param json
* a JSONObject
* @param rootName
* the optional name of the root element
* @return a Node representing the JSON document
* @throws JSONUtilsException
*/
public static Node jsonToXml(Object json, String rootName) throws JSONUtilsException

/**
* Convert a JSONObject into Node structure.
* If not specified a rootName and the JSON to be converted doesn't have
* a single root element then is automatically created a 'DEFAULT_ROOT' root element.
*
* @param json
* a JSONObject
* @param rootName
* the optional name of the root element
* @param forceAttributes
* a set containing keys name to be set as XML attributes
* @return a Node representing the JSON document
* @throws JSONUtilsException
*/
public static Node jsonToXml(Object json, String rootName, Set<String> forceAttributes) throws JSONUtilsException

/**
* Convert the input XML to a JSONObject using BadgerFish convention.
* See <a href="http://badgerfish.ning.com">http://badgerfish.ning.com</a>
*
* @param xml
* the document to convert
* @return a JSONObject representing the XML document
* @throws JSONUtilsException
*/
public static JSONObject xmlToJson_BadgerFish(Object xml) throws JSONUtilsException

/**
* Convert a JSONObject in BadgerFish notation into Node structure.
* See <a href="http://badgerfish.ning.com">http://badgerfish.ning.com</a>
*
* @param json
* a JSONObject
* @return a Node representing the JSON document
* @throws JSONUtilsException
*/
public static Node jsonToXml_BadgerFish(Object json) throws JSONUtilsException
</syntaxhighlight>

The JSONObject javadoc are [http://www.json.org/javadoc/index.html?org/json/JSONObject.html here].

Patch 3 4 0 4 Final

2015-10-28T19:37:11Z

G.dimaio:

=={{GVESB}} patch 3.4.0.4 Final==

*Commons/DTE
#Added [[JSONUtils]] utility class in order to manage JSON<->XML conversions
#The new converter perform better than that implemented in JSON library and:
##enable the [[JSON2XMLTransformation|JSON2XML]] transformer to specify a list of JSON property names to be set as element attributes in output XML
##enable the ([[XML2JSONTransformation|XML2JSON]] transformer to specify a list of XML element names to be forcefully set as JSONArray in output JSON
#Improved conversion of ISO8601 date-time in DateUtils
#Improved encrypt/decrypt of configuration parameters

*Adapter HTTP Inbound
#Improved request text payload recognition in Adapter HTTP Inbound
#Added HTTP_QUERY property to request GVBuffer ([[GVAdapterHttpConfiguration|see]])
#Improved customization of status messages in response header for HTTP Adapter Inbound (added a property in gvstart script)

*JMS Listener
#Improved Dump of JMS's MapMessage
#Added an utility class (JMSMessageToXML, to be used in ODP) to convert a JMS's message to XML document

JSONUtils

2015-10-28T19:36:28Z

G.dimaio: Created page with "Class FQN: '''it.greenvulcano.util.json.JSONUtils''' ==Following the JSONUtils public static methods== * Parsing & Conversion <syntaxhighlight lang="java5"> /** * Convert the i..."

UtilityClasses

2015-10-28T19:23:52Z

G.dimaio:

{{GVESB}} provides some utility classes that can simplify the configurator/developer work:
* [[BinaryUtils]] : Binary data manipulation
* [[CryptoHelper]] : Cryptography helper
* [[DateUtils]] : Date&Time manipulation
* [[JSONUtils]] : JSON manipulation
* [[PropertiesHandler]] : Metadata helper
* [[TextUtils]] : Text manipulation
* [[ThreadMap]] : Passing data between iterated Flow/SubFlow
* [[XMLConfig]] : XML configuration helper
* [[XMLUtils]] : XML manipulation
* [[XSLTUtils]] : XSLT helper

Manual Installation

2015-09-15T20:57:16Z

G.dimaio:

This section describes the {{GVESB}} installation steps on systems unsupported by the GreenVulcanoUniversalInstaller or when you are unable to run it.

'''Copy the file'''
# Unzip the file ''GvServer-3.3.0.Final-Full'' in any directory on the server where you plan to install the software. To avoid potential problems the installation path and the JAVA_HOME MUST NOT contain spaces.
{| class="note"
|-
| align="left" | [[File:linux.png]] || In case of *nix operating systems, you can choose to create an installation directory for {{GVESB}} into the user's home directory (ex. /home/gvuser), or paths established by the System Administrators (ex. /opt). Navigate to the directory chosen for installation and decompress the file with the command:
extract GvServer-3.3.0.Final-Full.tar.gz<br/>
or<br/>
tar -xvf GvServer-3.3.0.Final-Full.tar.gz
|}
{| class="note"
|-
| align="left" | [[File:windows.png]] || In case of Windows operating systems, you should unpack the ZIP file to a directory editable by the user, used to run {{GVESB}}. It is recommended NOT to use spaces in the directory name. Navigate to the directory chosen for installation and decompress the file using a program compatible with the GNU zip compression format.
|}

'''Environment configuration'''

Before using {{GVESB}} is necessary to set some environment variables.
# Configure the JBOSS_HOME environment variable with the absolute path installation of JBoss;
# Configure the GV_HOME environment variable with the absolute path where {{GVESB}} has been installed;
# Configure the GV_SERVER environment variable with the absolute path where is the JBoss server of {{GVESB}};
# Configure the JAVA_HOME environment variable with the absolute path where JDK is installed.

Follow the examples below to configure properly the environment variables.
{| class="note"
|-
| [[File:linux.png]]
| In case of *nix operating systems, edit the file ''env_scripts.sh'' under GvEnterprise3.3.0/GvServer/GreenV/bin and set the variables values as follows:

export JBOSS_HOME = /home/gvuser/GvEnterprise3.3.0/GvServer/jboss-5.1.0.GA<br/>
export GV_SERVER = $JBOSS_HOME/server/GreenV<br/>
export GV_HOME = /home/gvuser/GvEnterprise3.3.0/GvServer/GreenV<br/>
export CLASSPATH = $GV_HOME/xmlconfig<br/>
export JAVA_HOME = /usr/lib/jvm/java-6-sun
|}

{| class="note"
|-
| [[File:windows.png]]
| In case of Microsoft Windows operating systems, edit the file ''env_scripts.cmd'' under GvEnterprise3.3.0/GvServer/GreenV/bin and set the variables values as follows:

set JBOSS_HOME = C:\GvEnterprise3.3.0\GvServer\jboss-5.1.0.GA<br/>
set GV_SERVER = %JBOSS_HOME\server\GreenV<br/>
set GV_HOME = C:\GvEnterprise3.3.0\GvServer\GreenV<br/>
set CLASSPATH = %GV_HOME%\xmlconfig<br/>
set JAVA_HOME = C:\SDK\jdk<br/>
|}

'''Boot Parameters'''

In addition to the above variables, the file ''gvstart.sh'' (or ''gvstart.cmd'' in Microsoft Windows environments) contains other values for configuring the {{GVESB}} start. A list of these variables is present bellow:
{| class="gvtable"
! Parameter
! Description
|-
| JB_OPTS
| JBoss server options. <br/>-Djboss.partition.name=GreenVPartition <br/>-Djboss.service.binding.set=ports-default <br/>-Djboss.bind.address=0.0.0.0 <br/>-Dbind.address=localhost <br/>-Djava.net.preferIPv4Stack=true <br/>-Djava.rmi.server.hostname=localhost
|-
| GV_OPTS
| {{GVESB}} options. <br/>-Dgv.app.home=$GV_HOME -Dit.greenvulcano.util.xpath.search.XPathAPIFactory.cfgFileXPath=GVCore.xml<nowiki>|</nowiki>/GVCore/GVXPath/XPath <br/>-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl <br/>-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl <br/>-Djxl.nogc=true <br/>-Dit.greenvulcano.log.db.JDBCAppender.logState=false <br/>-Dgv.pop.uidcache.manager=it.greenvulcano.gvesb.virtual.pop.uidcache.MemoryUIDCacheManager <br/>-Dit.greenvulcano.util.thread.BaseThread.dumpInstCount=true <br/>-Dit.greenvulcano.util.thread.BaseThread.dumpCreateStack=false <br/>-Dit.greenvulcano.gvesb.identity.IdentityInfo.debug=true
|-
| JAVA_OPTS
| Java Virtual Machine options: <br/>-Xms512M -Xmx1024M -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
|-
|}

{| class="note"
|-
| [[File:linux.png]]
| In case of *nix systems, the user with which {{GVESB}} will be executed must have exec permission for the following scripts:
: $GV_HOME/bin/env_scripts.sh<br/>
: $GV_HOME/bin/gvstart.sh<br/>
: $GV_HOME/bin/gvstop.sh<br/>
: $GV_HOME/hsqldb/bin/start_DB.sh<br/>
: $GV_HOME/hsqldb/stop_DB.sh<br/>
: $JBOSS_HOME/bin/run.sh<br/>
: $JBOSS_HOME/bin/shutdown.sh
|}

Manual Installation

2015-09-15T20:56:18Z

G.dimaio:

This section describes the {{GVESB}} installation steps on systems unsupported by the GreenVulcanoUniversalInstaller or when you are unable to run it.

'''Copy the file'''
# Unzip the file ''GvServer-3.3.0.Final-Full'' in any directory on the server where you plan to install the software. To avoid potential problems the installation path and the JAVA_HOME MUST NOT contain spaces.
{| class="note"
|-
| align="left" | [[File:linux.png]] || In case of *nix operating systems, you can choose to create an installation directory for {{GVESB}} into the user's home directory (ex. /home/gvuser), or paths established by the System Administrators (ex. /opt). Navigate to the directory chosen for installation and decompress the file with the command:
extract GvServer-3.3.0.Final-Full.tar.gz
or
tar -xvf GvServer-3.3.0.Final-Full.tar.gz
|}
{| class="note"
|-
| align="left" | [[File:windows.png]] || In case of Windows operating systems, you should unpack the ZIP file to a directory editable by the user, used to run {{GVESB}}. It is recommended NOT to use spaces in the directory name. Navigate to the directory chosen for installation and decompress the file using a program compatible with the GNU zip compression format.
|}

'''Environment configuration'''

Before using {{GVESB}} is necessary to set some environment variables.
# Configure the JBOSS_HOME environment variable with the absolute path installation of JBoss;
# Configure the GV_HOME environment variable with the absolute path where {{GVESB}} has been installed;
# Configure the GV_SERVER environment variable with the absolute path where is the JBoss server of {{GVESB}};
# Configure the JAVA_HOME environment variable with the absolute path where JDK is installed.

Follow the examples below to configure properly the environment variables.
{| class="note"
|-
| [[File:linux.png]]
| In case of *nix operating systems, edit the file ''env_scripts.sh'' under GvEnterprise3.3.0/GvServer/GreenV/bin and set the variables values as follows:

export JBOSS_HOME = /home/gvuser/GvEnterprise3.3.0/GvServer/jboss-5.1.0.GA<br/>
export GV_SERVER = $JBOSS_HOME/server/GreenV<br/>
export GV_HOME = /home/gvuser/GvEnterprise3.3.0/GvServer/GreenV<br/>
export CLASSPATH = $GV_HOME/xmlconfig<br/>
export JAVA_HOME = /usr/lib/jvm/java-6-sun
|}

{| class="note"
|-
| [[File:windows.png]]
| In case of Microsoft Windows operating systems, edit the file ''env_scripts.cmd'' under GvEnterprise3.3.0/GvServer/GreenV/bin and set the variables values as follows:

set JBOSS_HOME = C:\GvEnterprise3.3.0\GvServer\jboss-5.1.0.GA<br/>
set GV_SERVER = %JBOSS_HOME\server\GreenV<br/>
set GV_HOME = C:\GvEnterprise3.3.0\GvServer\GreenV<br/>
set CLASSPATH = %GV_HOME%\xmlconfig<br/>
set JAVA_HOME = C:\SDK\jdk<br/>
|}

'''Boot Parameters'''

In addition to the above variables, the file ''gvstart.sh'' (or ''gvstart.cmd'' in Microsoft Windows environments) contains other values for configuring the {{GVESB}} start. A list of these variables is present bellow:
{| class="gvtable"
! Parameter
! Description
|-
| JB_OPTS
| JBoss server options. <br/>-Djboss.partition.name=GreenVPartition <br/>-Djboss.service.binding.set=ports-default <br/>-Djboss.bind.address=0.0.0.0 <br/>-Dbind.address=localhost <br/>-Djava.net.preferIPv4Stack=true <br/>-Djava.rmi.server.hostname=localhost
|-
| GV_OPTS
| {{GVESB}} options. <br/>-Dgv.app.home=$GV_HOME -Dit.greenvulcano.util.xpath.search.XPathAPIFactory.cfgFileXPath=GVCore.xml<nowiki>|</nowiki>/GVCore/GVXPath/XPath <br/>-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl <br/>-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl <br/>-Djxl.nogc=true <br/>-Dit.greenvulcano.log.db.JDBCAppender.logState=false <br/>-Dgv.pop.uidcache.manager=it.greenvulcano.gvesb.virtual.pop.uidcache.MemoryUIDCacheManager <br/>-Dit.greenvulcano.util.thread.BaseThread.dumpInstCount=true <br/>-Dit.greenvulcano.util.thread.BaseThread.dumpCreateStack=false <br/>-Dit.greenvulcano.gvesb.identity.IdentityInfo.debug=true
|-
| JAVA_OPTS
| Java Virtual Machine options: <br/>-Xms512M -Xmx1024M -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
|-
|}

{| class="note"
|-
| [[File:linux.png]]
| In case of *nix systems, the user with which {{GVESB}} will be executed must have exec permission for the following scripts:
: $GV_HOME/bin/env_scripts.sh<br/>
: $GV_HOME/bin/gvstart.sh<br/>
: $GV_HOME/bin/gvstop.sh<br/>
: $GV_HOME/hsqldb/bin/start_DB.sh<br/>
: $GV_HOME/hsqldb/stop_DB.sh<br/>
: $JBOSS_HOME/bin/run.sh<br/>
: $JBOSS_HOME/bin/shutdown.sh
|}

Patch 3 4 0 8 Final

2015-06-10T15:53:30Z

G.dimaio: Created page with "=={{GVESB}} patch 3.4.0.8 Final== *Commons #Corrected JSON<->XML numeric values conversion. *DTE #Changed cardinality of ToPreload DTE element. *Adapter #Added [[GVPushNotific..."

=={{GVESB}} patch 3.4.0.8 Final==

*Commons
#Corrected JSON<->XML numeric values conversion.

*DTE
#Changed cardinality of ToPreload DTE element.

*Adapter
#Added [[GVPushNotificationManager|Push Notification Adapter]], with Android and iOS notification engine implementation.

*Core
#Corrected GVCore pool element clean-up after configuration reload.

*Adapter HTTP Inbound
#Added management of output GVBuffer property HTTP_RESP_FILE_NAME to [[GVAdapterHttpConfiguration#RESTActionMapping|RESTActionMapping]] in order to define the name of the file to be downloaded through an HTTP request.

*RSH Handler
#Corrected RMI hostname definition in RSH start script.

Jms-enqueue

2015-06-10T15:46:44Z

G.dimaio:

The ''jms-enqueue'' element allows you to perform a enqueue on a JMS destination. It is used by [[Channel]] and [[routed-dequeue]].

GVBuffer fields will be made available through the JMS message properties:

{|class="gvtable"
! Field !! JMS
|-
|system || SYSTEM
|-
|service || SERVICE
|-
|id || ID
|-
|retCode || RET_CODE
|-
|properties || p$<property name> (only GVBuffer properties with names that are valid Java identifier are managed)
|}

It has the attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''enqueue'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|-
| connection-factory || required || JMS connection factory JNDI name.
|-
| destination-name || required || Destination JNDI name. Set appropriately the ''destination-type'' parameter.
|-
| destination-type|| optional || Destination type. Default: queue. <br/> The attribute's admitted values are:
* queue
* topic
|-
| transacted || optional || Specifies whether the enqueue has to open his own transaction or fall in a global transaction.
* ''true'' open his own transaction and do not fall in the global transaction.
* ''false'' fall in the active global transaction. Must be used a XA connection factory.
: This parameter is not relevant if the connection factory is not XA. Default: false.
|-
| acknowledge-type || optional || In transactional enqueue acknowledgment is managed by the application server. <br/> This parameter is meaningful only for non-transactional enqueue and can take the following values:
* auto-acknowledge: the acknowledgment from application server is automatically given upon delivery of the message.
* client-acknowledge: the client must explicitly acknowledgment the message.
* dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgment messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
|-
| delivery-mode || optional || Specifies whether the JMS server must file on a persistent store the message before returning to the caller. <br/> Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
* persistent : guarantees delivery. Default value
* non-persistent: don't guarantees delivery
|-
| priority || optional || Message priority. The messages with higher priority will be received before messages with lower priority. The priorities set for JMS ranging from 0 (lowest priority) to 9 (highest priority). The default priority of JMS messages is 4.
|-
| time-to-live || optional || Lifetime of sent messages, in milliseconds. <br/> Upon expiration of the time-to-live the JMS server is allowed to discard the message without delivering it. If not specified it is assumed a time-to-live of one year.
|-
| use-vcl-pool || optional || Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities. Default: true
|-
| invalidate-conn-on-pool-insertion || optional || Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false
|-
| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use. This Data Provider will return the JMS Message to send.
|-
| dump-message || optional || If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false
|}
<div class="version_ge3.4.0.7">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| decorate-message || optional || If true the message to be enqueued is enriched with input GVBuffer properties value. Default true. The attribute's admitted values are:
* true
* false
|}
</div>

Its subelements are:

* Description
* [[JNDIHelper]]
* [[ServiceAlias]]
* [[XAHelper]]

{{VOTE}}

Jms-dequeue

2015-06-10T15:46:32Z

G.dimaio:

==Description==

The ''jms-dequeue'' element allows you to perform a dequeue from a JMS destination.

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

It is used by [[Channel]] and [[routed-dequeue]].

JMS message properties are mapped to [[GVBuffer]] fields:

{|class="gvtable"
! Field !! JMS
|-
|system || SYSTEM
|-
|service || SERVICE
|-
|id || ID
|-
|retCode || RET_CODE
|-
|properties || p$<property name> (only [[GVBuffer]] properties with names that are valid Java identifier are managed)
|}

If it is not defined a Data Provider, the [[GVBuffer]] object field contains the received message.
Can be defined a JMS message selector to filter messages.

It has the attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dequeue'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.j2ee.JMSDequeueOperation'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|-
| connection-factory || required || JMS connection factory JNDI name.
|-
| destination-name || required || Destination JNDI name. Set appropriately the ''destination-type'' parameter.
|-
| destination-type || optional || Destination type. Default: queue. <br/> The attribute's admitted values are:
* queue
* topic
|-
| transacted || optional || Specifies whether the dequeue has to open his own transaction or fall in a global transaction.
* 'true' open his own transaction and do not fall in the global transaction.
* 'false' fall in the active global transaction. Must be used a XA connection factory.
: This parameter is not relevant if the connection factory is not XA. Default: false.
|-
| acknowledge-type || optional || In transactional dequeue acknowledgement is managed by the application server. <br/> This parameter is meaningful only for non-transactional dequeue and can take the following values:
* auto-acknowledge: the acknowledgement from application server is automatically given upon delivery of the message.
* client-acknowledge: the client must explicitly acknowledgement the message.
* dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgement messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
|-
| receive-type || required || Allows you to specify whether the receipt should be made in blocking mode, non-blocking mode, or with timeout.
* non-blocking: is performed a non-blocking receive. If a message is already queued then it's immediately read. <br> If there are no messages available then {{GVESB}} throws a time-out exception.
* timeout: is performed a timeout receive. {{GVESB}} wait for the specified time. If a message is queued then it's immediately read. <br/> If there are no messages available then {{GVESB}} throws a time-out exception.
* blocking: the current thread blocks indefinitely until a message arrives. Use with caution.
|-
| receive-timeout || optional || Time-out duration in ms. This parameter is meaningful only if ''receive-type'' is set to ''time out''. <br/> If 'receive-type' is set to 'time out' and 'receive-timeout' is not defined, then is assumed a timeout of 1000 ms.
|-
| receive-timeout-overridable || optional || Specifies whether the value set to 'receive-timeout' can be overwritten at runtime. Reserved for future use. The attribute's default value is: false. The attribute's admitted values are:
* false
* true
|-
| durable-subscriber || optional || Specifies the name of the durable subscriber. Durable subscriptions provide the receipt of all messages sent to the topic, even if the subscribers are not running when the messages are sent.
|-
| no-local || optional || Avoid receiving local messages. Reserved for future use. The attribute's admitted values are:
* true
* false
|-
| use-vcl-pool || optional || Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities.
Default: true
|-
| invalidate-conn-on-pool-insertion || optional || Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false. The attribute's admitted values are:
* false
* true
|-
| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use. This Data Provider will receive in input a JMS Message and must return the object to be inserted in [[GVBuffer]].
|-
| dump-message || optional || If true the dequeued message is dumped on log file, at DEBUG severity level. Default false. The attribute's admitted values are:
* true
* false
|}
<div class="version_ge3.4/3.3.4">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| keep-input-extra-properties || optional || Specifies if the dequeue must keep input GVBuffer properties, not present in the JMS message, in the output GVBuffer. Default false. The attribute's admitted values are:
* true
* false
|}
</div>
<div class="version_ge3.4.0.7">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| decorate-gvbuffer || optional || If true the output GVBuffer is enriched with the received message properties value. Default true. The attribute's admitted values are:
* true
* false
|}
</div>

Its subelements are:

* Description
* [[JNDIHelper]]
* [[message-selector]]
* [[ServiceAlias]]
* [[XAHelper]]

Jms-dequeue

2015-06-10T15:45:57Z

G.dimaio:

==Description==

The ''jms-dequeue'' element allows you to perform a dequeue from a JMS destination.

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

It is used by [[Channel]] and [[routed-dequeue]].

JMS message properties are mapped to [[GVBuffer]] fields:

{|class="gvtable"
! Field !! JMS
|-
|system || SYSTEM
|-
|service || SERVICE
|-
|id || ID
|-
|retCode || RET_CODE
|-
|properties || p$<property name> (only [[GVBuffer]] properties with names that are valid Java identifier are managed)
|}

If it is not defined a Data Provider, the [[GVBuffer]] object field contains the received message.
Can be defined a JMS message selector to filter messages.

It has the attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dequeue'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.j2ee.JMSDequeueOperation'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|-
| connection-factory || required || JMS connection factory JNDI name.
|-
| destination-name || required || Destination JNDI name. Set appropriately the ''destination-type'' parameter.
|-
| destination-type || optional || Destination type. Default: queue. <br/> The attribute's admitted values are:
* queue
* topic
|-
| transacted || optional || Specifies whether the dequeue has to open his own transaction or fall in a global transaction.
* 'true' open his own transaction and do not fall in the global transaction.
* 'false' fall in the active global transaction. Must be used a XA connection factory.
: This parameter is not relevant if the connection factory is not XA. Default: false.
|-
| acknowledge-type || optional || In transactional dequeue acknowledgement is managed by the application server. <br/> This parameter is meaningful only for non-transactional dequeue and can take the following values:
* auto-acknowledge: the acknowledgement from application server is automatically given upon delivery of the message.
* client-acknowledge: the client must explicitly acknowledgement the message.
* dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgement messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
|-
| receive-type || required || Allows you to specify whether the receipt should be made in blocking mode, non-blocking mode, or with timeout.
* non-blocking: is performed a non-blocking receive. If a message is already queued then it's immediately read. <br> If there are no messages available then {{GVESB}} throws a time-out exception.
* timeout: is performed a timeout receive. {{GVESB}} wait for the specified time. If a message is queued then it's immediately read. <br/> If there are no messages available then {{GVESB}} throws a time-out exception.
* blocking: the current thread blocks indefinitely until a message arrives. Use with caution.
|-
| receive-timeout || optional || Time-out duration in ms. This parameter is meaningful only if ''receive-type'' is set to ''time out''. <br/> If 'receive-type' is set to 'time out' and 'receive-timeout' is not defined, then is assumed a timeout of 1000 ms.
|-
| receive-timeout-overridable || optional || Specifies whether the value set to 'receive-timeout' can be overwritten at runtime. Reserved for future use. The attribute's default value is: false. The attribute's admitted values are:
* false
* true
|-
| durable-subscriber || optional || Specifies the name of the durable subscriber. Durable subscriptions provide the receipt of all messages sent to the topic, even if the subscribers are not running when the messages are sent.
|-
| no-local || optional || Avoid receiving local messages. Reserved for future use. The attribute's admitted values are:
* true
* false
|-
| use-vcl-pool || optional || Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities.
Default: true
|-
| invalidate-conn-on-pool-insertion || optional || Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false. The attribute's admitted values are:
* false
* true
|-
| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use. This Data Provider will receive in input a JMS Message and must return the object to be inserted in [[GVBuffer]].
|-
| dump-message || optional || If true the dequeued message is dumped on log file, at DEBUG severity level. Default false. The attribute's admitted values are:
* true
* false
|}
<div class="version_ge3.4/3.3.4">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| keep-input-extra-properties || optional || Specifies if the dequeue must keep input GVBuffer properties, not present in the JMS message, in the output GVBuffer. Default false. The attribute's admitted values are:
* true
* false
|}
</div>
<div class="version_ge3.4.0.7">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| decorate-gvbuffer || optional || If true the output GVBuffer is enriched with the received message properties value. Default true
|}
</div>

Its subelements are:

* Description
* [[JNDIHelper]]
* [[message-selector]]
* [[ServiceAlias]]
* [[XAHelper]]

Jms-enqueue

2015-06-10T15:44:28Z

G.dimaio:

The ''jms-enqueue'' element allows you to perform a enqueue on a JMS destination. It is used by [[Channel]] and [[routed-dequeue]].

GVBuffer fields will be made available through the JMS message properties:

{|class="gvtable"
! Field !! JMS
|-
|system || SYSTEM
|-
|service || SERVICE
|-
|id || ID
|-
|retCode || RET_CODE
|-
|properties || p$<property name> (only GVBuffer properties with names that are valid Java identifier are managed)
|}

It has the attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''enqueue'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation'''.
|-
| name || required || Operation name. Used in the [[Flow]] section to associate workflow nodes to VCL operations.
|-
| connection-factory || required || JMS connection factory JNDI name.
|-
| destination-name || required || Destination JNDI name. Set appropriately the ''destination-type'' parameter.
|-
| destination-type|| optional || Destination type. Default: queue. <br/> The attribute's admitted values are:
* queue
* topic
|-
| transacted || optional || Specifies whether the enqueue has to open his own transaction or fall in a global transaction.
* ''true'' open his own transaction and do not fall in the global transaction.
* ''false'' fall in the active global transaction. Must be used a XA connection factory.
: This parameter is not relevant if the connection factory is not XA. Default: false.
|-
| acknowledge-type || optional || In transactional enqueue acknowledgment is managed by the application server. <br/> This parameter is meaningful only for non-transactional enqueue and can take the following values:
* auto-acknowledge: the acknowledgment from application server is automatically given upon delivery of the message.
* client-acknowledge: the client must explicitly acknowledgment the message.
* dups-ok-acknowledge: allows the JMS server to perform optimizations on the logic of acknowledgment messages, but can cause the redelivery of messages. Should only be used with systems that are tolerant to duplicated message. Default: auto-acknowledge
|-
| delivery-mode || optional || Specifies whether the JMS server must file on a persistent store the message before returning to the caller. <br/> Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
* persistent : guarantees delivery. Default value
* non-persistent: don't guarantees delivery
|-
| priority || optional || Message priority. The messages with higher priority will be received before messages with lower priority. The priorities set for JMS ranging from 0 (lowest priority) to 9 (highest priority). The default priority of JMS messages is 4.
|-
| time-to-live || optional || Lifetime of sent messages, in milliseconds. <br/> Upon expiration of the time-to-live the JMS server is allowed to discard the message without delivering it. If not specified it is assumed a time-to-live of one year.
|-
| use-vcl-pool || optional || Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities. Default: true
|-
| invalidate-conn-on-pool-insertion || optional || Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false
|-
| ref-dp || optional || Name of [[Data_provider|Data Provider]] to use. This Data Provider will return the JMS Message to send.
|-
| dump-message || optional || If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false
|}
<div class="version_ge3.4.0.7">
{|class="gvtable"
! Attribute !! Type !! Description
|-
| decorate-message || optional || If true the message to be enqueued is enriched with input GVBuffer properties value. Default true
|}
</div>

Its subelements are:

* Description
* [[JNDIHelper]]
* [[ServiceAlias]]
* [[XAHelper]]

{{VOTE}}

Esb 3 4 0 7 Final

2015-06-10T15:36:02Z

G.dimaio: Created page with "=={{GVESB}} package 3.4.0.7 Final== *Commons #Removed XPath engine re-initialization during startup. #Removed recursive invocation of JMXEntrypoint.init() during Initializers ex..."

=={{GVESB}} package 3.4.0.7 Final==

*Commons
#Removed XPath engine re-initialization during startup.
#Removed recursive invocation of JMXEntrypoint.init() during Initializers execution.
#Improved (N)CLOB fields management in sqlX metadata.
#Improved reload configuration locking in order to avoid dead-lock.
#Corrected EML element definition in PopMessages.xsd

*Task Scheduler
#Improved TaskManager reload configuration locking in order to avoid dead-lock.

*JMS Listener
#Improved listeners instantiation algorithm in JMS listener pool.

*DataHandler
#Resolved a column name misreading error in DataHandler's extended RowSet builder.

*GVConsole
#Improved DTD referencing and deploy of aliased DTE Transformations

*VCL HTTP
#Corrected RegisterHttpClientProtocolManager initialization, in order to avoid double JMX registration.

*VCL J2EE
#Added to JMS [[jms-enqueue|Enqueue]]/[[jms-dequeue|Dequeue]] VCL operations the capability to exclude:
##GVBuffer -> Message properties enrichment during enqueue
##Message -> GVBuffer properties enrichment during dequeue

GreenVulcanoVersions

2015-06-10T15:25:16Z

G.dimaio:

==GreenVulcano ESB versions==
Following {{GVESB}} versions list organized by maturity level. Click on the version's number to see the change-log.

===Development versions===
{|class="gvtable" | Version | Released
|-
| [[esb_3_5_0_Trunk]] || to be released
|}

===Current stable versions===
{|class="gvtable" | Version | Released
|-
| [[patch_3_4_0_8_Final]] || 2015-06-10
|-
| [[esb_3_4_0_7_Final]] || 2015-02-13
|-
| [[esb_3_4_0_6_Final]] || 2014-11-27
|-
| [[patch_3_4_0_5_Final]] || 2014-09-21
|-
| [[patch_3_4_0_4_Final]] || 2014-09-12
|-
| [[patch_3_4_0_3_Final]] || 2014-07-31
|-
| [[esb_3_4_0_2_Final]] || 2014-07-16
|-
| [[esb_3_4_0_Final]] || 2014-05-23
|}

===Maintenance versions===
{|class="gvtable" | Version | Released
|-
| [[patch_3_3_4_2_Final]] || 2014-09-21
|-
| [[patch_3_3_4_1_Final]] || 2014-07-31
|-
| [[esb_3_3_4_Final]] || 2014-07-16
|-
| [[esb_3_3_3_Final]] || 2013-11-06
|-
| [[esb_3_3_2_Final]] || 2013-07-24
|-
| [[esb_3_3_1_Final]] || 2013-05-27
|-
| [[esb_3_3_0_Final]] || 2013-03-04
|}

ThreadMap

2015-02-19T08:47:10Z

G.dimaio: Created page with "Class FQN: '''it.greenvulcano.util.thread.ThreadMap''' This class contains static utility methods to attach/detach objects to current Thread context. ==ThreadMap public static m..."

Class FQN: '''it.greenvulcano.util.thread.ThreadMap'''
This class contains static utility methods to attach/detach objects to current Thread context.

==ThreadMap public static methods==
<syntaxhighlight lang="java5">
/**
* Retrieve the object associated to 'key' in the current Thread map
*
* @param key
* the key to search for
* @return the found object, or null
*/
public static Object get(Object key)

/**
* Retrieve the objects associated to 'key' in all Thread maps
*
* @param key
* the key to search for
* @return the found objects, or an empty array
*/
public static Object[] allThreadGet(Object key)

/**
* Insert the object 'value' associated to 'key' in the current Thread map
*
* @param key
* the key to use for mapping
* @param value
* the value to insert
*/
public static void put(Object key, Object value)

/**
* Insert the object 'value' associated to 'key' in all Thread maps
*
* @param key
* the key to use for mapping
* @param value
* the value to insert
*/
public static void allThreadPut(Object key, Object value)

/**
* Remove the object associated to 'key' in the current Thread map
*
* @param key
* the key to search for
* @return the found object, or null
*/
public static Object remove(Object key)

/**
* Remove the objects associated to 'key' in all Thread maps
*
* @param key
* the key to search for
*/
public static void allThreadRemove(Object key)
</syntaxhighlight>

==ThreadMap RESERVED public static methods==
<p style="color: red">The following methods MUST be used only in Core development.<br/>
Using them with caution.</p>

<syntaxhighlight lang="java5">
/**
* Clean the current Thread map
*/
public static void clean()

/**
* Clean all Thread maps
*/
public static void cleanAll()
</syntaxhighlight>