GreenVulcano Wiki - User contributions [en]

ServiceCallerTask

2013-07-01T13:57:58Z

N.lariviera: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

==Description==

Use this task for invoking {{GVESB}} services.

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

ServiceCallerTask is the Task for invoking {{GVESB}} services.

The ServiceCallerTask Element is used by: [[GVTaskConfiguration#TaskGroup||TaskGroup]].

The following table shows the ServiceCallerTask element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''task'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.task.GVServiceCallerTask'''.
|-
| name || required || Task name. The attribute's value can't be null.
|-
| auto-start || optional || If 'true' Task is automatically registered on the timer.
The attribute's admitted values are:
* true
* false
|-
| enabled || optional || Task activation status.
The attribute's admitted values are:
* true
* false
|-
| id-service || required || ID_SERVICE be used for the invocation.
The attribute's value cannot be null.
|-
| id-system || optional || ID_SYSTEM be used for the invocation.
If specified, the attribute's value cannot be null.
|-
| operation || required || Operation name to be used for the invocation.
The attribute's value cannot be null.
|-
| transacted || optional || Performs the invocation in transaction.
The attribute's admitted values are:
* false
* true
If specified, the attribute's value cannot be null.
|-
| timeout || optional || Timeout of the transaction.
If specified, the attribute's value cannot be null.
|-
| max-calls-sequence || optional || Maximum number of calls in sequence. Default: 1
If specified, the attribute's value cannot be null.
|}

A ServiceCallerTask element might have the following sub-elements:
* [[Description]]
* [[Triggers]]
* [[JbProperties]]
* [[JNDIHelper]]
* [[ChangeGVBuffer]]
* [[ServiceCallerTask#OutputData|OutputData]]
* [[ServiceCallerTask#NextAction|NextAction]]

===OutputData===

This element allows to define options for saving the output data on file.

The following table shows the OutputData element's attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| output-directory || required || The path of the directory containing the file(s) that will save the GVBuffer output body of the service performed.
|-
| output-policy || required || This attribute defines the way in which you saved the output of the service.
If ''create'' the output of the service will be stored on a single file whose name is that of the task.
The file will be overwritten each time the service is invoked. Es: ''Taskname.xxx''
If ''append'' the output of the service will be stored on a single file whose name is that of the task: each invocation of the
service, the data will be appended to the file.
If ''create-new'' the service saved output separates the files whose name is given by the task name followed by the date/time in format dd-MM-yyyy-hh-mm-ss-SSS. Es: 'Taskname'-01-01-2010-10-45-05-234.xxxx
|-
| output-type || required || This attribute defines the data type of output that will be saved.
If ''body'' the [[GVBuffer]] body contents will be saved, as defined in the parameter ''output-policy'': the file extension is ''.dat''.
If ''dump'' will be made a dump of all [[GVBuffer]], including property, as defined in the parameter ''output-policy'': the file extension is ''.dump''.
If ''both'' will save the body and the [[GVBuffer]] dump.
|}

===NextAction===

Action to be executed after the invocation of {{GVESB}}.

If any condition is checked does the following Action:
* if output is an Exception -> ''rollback-exit''
* if output is a [[GVBuffer]] -> ''commit-continue''

The following table shows the NextAction element's attribute :
{|class="gvtable"
! Attribute !! Type !! Description
|-
| action || required || The action to execute if the condition is verified. The attribute's admitted values are:
* commit-continue
* rollback-exit
* commit-exit
* rollback-continue
|}

Might contain the following sub-elements:
* [[Description]]
* [[GVBufferCondition]] or [[ExceptionCondition]] or [[JavaScriptCondition]] or [[IdentityCondition]]

VulCon

2013-03-25T12:39:37Z

N.lariviera: /* Installation */

==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>
{{VOTE}}

Axis2MessageContextDataProvider

2012-07-16T17:18:50Z

N.lariviera:

The DataProvider Axis2MessageContextDataProvider Axis allows you to set objects to manipulate input / output for webservices.

The objects used in Axis2 are [http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/package-summary.html OMElement].

The context of the DataProvider object is [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html org.apache.axis2.MessageContext]

The class [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/util/XMLUtils.html org.apache.axis2.util.XMLUtils ] has a number of methods for manipulating objects OM.

For example, OGNL you can use the following expression:
<syntaxhighlight lang="java5">
envelope.body.addChild (@org.apache.axis2.util.XMLUtils@toOM (#input.object.getDocumentElement()))
</syntaxhighlight>

to add body, or set Axis2 invocation related options:

<syntaxhighlight lang="java5">
options.setProperty(@org.apache.axis2.Constants$Configuration@ENABLE_REST, @org.apache.axis2.Constants@VALUE_TRUE)
</syntaxhighlight>

to enable REST.

=={{GVESB}} Configuration==

The Axis2MessageContextDataProvider Element is used by: [[GVDataProviderManager#DataProviders|DataProviders]].
The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dataProvider'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.gvdp.impl.Axis2MessageContextDataProvider'''.
|-
| name || required || Name of the Axis2MessageContextDataProvider.
|}

Contains the sub-element [[Field]].

{{VOTE}}

Axis2MessageContextDataProvider

2012-07-10T10:54:41Z

N.lariviera:

The DataProvider Axis2MessageContextDataProvider Axis allows you to set objects to manipulate input / output for webservices.

The objects used in Axis2 are [http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/package-summary.html OMElement].

The context of the DataProvider object is [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html org.apache.axis2.MessageContext]

The class [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/util/XMLUtils.html org.apache.axis2.util.XMLUtils ] has a number of methods for manipulating objects OM.

For example, OGNL you can use the following expression:
<syntaxhighlight lang="java5">
envelope.body.addChild (@org.apache.axis2.util.XMLUtils@toOM (#input.object.getDocumentElement()))
</syntaxhighlight>

to add body, or set Axis2 invocation related options:

<syntaxhighlight lang="java5">
options.setProperty(@org.apache.axis2.Constants.Configuration@ENABLE_REST, @org.apache.axis2.Constants@VALUE_TRUE)
</syntaxhighlight>

to enable REST.

=={{GVESB}} Configuration==

The Axis2MessageContextDataProvider Element is used by: [[GVDataProviderManager#DataProviders|DataProviders]].
The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dataProvider'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.gvdp.impl.Axis2MessageContextDataProvider'''.
|-
| name || required || Name of the Axis2MessageContextDataProvider.
|}

Contains the sub-element [[Field]].

{{VOTE}}

Axis2MessageContextDataProvider

2012-07-10T10:49:03Z

N.lariviera:

The DataProvider Axis2MessageContextDataProvider Axis allows you to set objects to manipulate input / output for webservices.

The objects used in Axis2 are [http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/package-summary.html OMElement].

The context of the DataProvider object is [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html org.apache.axis2.MessageContext]

The class [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/util/XMLUtils.html org.apache.axis2.util.XMLUtils ] has a number of methods for manipulating objects OM.

For example, OGNL you can use the following expression:
<syntaxhighlight lang="java5">
envelope.body.addChild (@org.apache.axis2.util.XMLUtils@toOM (#input.object.getDocumentElement()))
</syntaxhighlight>

to add body.

=={{GVESB}} Configuration==

The Axis2MessageContextDataProvider Element is used by: [[GVDataProviderManager#DataProviders|DataProviders]].
The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dataProvider'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.gvdp.impl.Axis2MessageContextDataProvider'''.
|-
| name || required || Name of the Axis2MessageContextDataProvider.
|}

Contains the sub-element [[Field]].

{{VOTE}}

Axis2MessageContextDataProvider

2012-07-10T10:43:25Z

N.lariviera:

The DataProvider Axis2MessageContextDataProvider Axis allows you to set objects to manipulate input / output for webservices.

The objects used in Axis2 are [http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/package-summary.html OMElement].

The context of the DataProvider object is [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/context/MessageContext.html org.apache.axis2.MessageContext]

The class [http://axis.apache.org/axis2/java/core/api/org/apache/axis2/util/XMLUtils.html org.apache.axis2.utilXMLUtils ] has a number of methods for manipulating objects OM.

For example, OGNL you can use the following expression:
<syntaxhighlight lang="java5">
envelope.body.addChild (@org.apache.axis2.util.XMLUtils@toOM (#input.object.getDocumentElement()))
</syntaxhighlight>

to add body.

=={{GVESB}} Configuration==

The Axis2MessageContextDataProvider Element is used by: [[GVDataProviderManager#DataProviders|DataProviders]].
The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || This attribute must assume the value '''dataProvider'''.
|-
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.gvdp.impl.Axis2MessageContextDataProvider'''.
|-
| name || required || Name of the Axis2MessageContextDataProvider.
|}

Contains the sub-element [[Field]].

{{VOTE}}