GVExample TOUPPER - Revision history

D.franco: /* Testing with {{GVCONSOLE}} */

2014-05-28T15:28:40Z

‎Testing with {{GVCONSOLE}}

Anonymous at 16:16, 21 November 2012

2012-11-21T16:16:38Z

A.capaldo: /* How To */

2012-10-09T14:18:37Z

‎How To

Anonymous: /* Testing with {{GVCONSOLE}} */

2012-02-20T09:25:44Z

‎Testing with {{GVCONSOLE}}

Anonymous: /* Testing with {{GVCONSOLE}} */

2012-02-20T09:21:34Z

‎Testing with {{GVCONSOLE}}

G.dimaio at 11:47, 19 February 2012

2012-02-19T11:47:18Z

Anonymous: /* Testing with {{GVCONSOLE}} */

2012-02-19T09:52:17Z

‎Testing with {{GVCONSOLE}}

Anonymous: /* Description */

2012-02-19T09:51:01Z

‎Description

G.dimaio at 09:26, 19 February 2012

2012-02-19T09:26:37Z

G.iannello: /* How To */

2012-02-17T11:50:44Z

‎How To

@@ Line 118: / Line 118: @@
 # Click RequestReply
-When the service completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
+When the service completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined, so only the main information about the process is present (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
 In case of error or exceptions you can review the logs file present in the folder <nowiki>$GV_HOME</nowiki>/log/.

@@ Line 1: / Line 1: @@
 ==Description==
-This simple example shows a simple [[Paradigms_of_communication|synchronous service]] and its configuration.
+This example shows a simple [[Paradigms_of_communication|synchronous service]] and its configuration.
-The service accept a string as input, then returns it converted to uppercase.
+The service accepts a string as input, then returns it converted to uppercase.
 ==How To==

@@ Line 90: / Line 90: @@
 # Before you proceed press F5 to refresh the file list.
 # Right click the ''conf'' folder. It will open a drop-down list.
-# Export your project as a compressed file.
+# Export your project as a VulCon project file (.zip).
 ===Testing with {{GVCONSOLE}}===

@@ Line 103: / Line 103: @@
 The section [[Deploy_Service|Deploy Services]] will be open. In this section you can select the services you want to deploy.
-# Clicking on service TOUPPER a new view will be showed containing the files GVCore.xml present in local and on server side.
+# Clicking on service TOUPPER a new view will be showed containing the file ''GVCore.xml'' present in local and on server side.
 # Click Deploy. Now you can save the document and write some notes about it.
 # Save the Document. By saving you will return to the [[Deploy Service]] section.

@@ Line 100: / Line 100: @@
 # [[GV_Console#Access|Access to the {{GVCONSOLE}}]].
 # In the Deploy New Service section click Browse and select the file where you saved the {{VULCON}} configuration.
-#`Click Submit.
+# Click Submit.
 The section [[Deploy_Service|Deploy Services]] will be open. In this section you can select the services you want to deploy.

@@ Line 94: / Line 94: @@
 ===Testing with {{GVCONSOLE}}===
-It is finally arrived the time to test your project. To do that execute the following steps:
+It is finally the time to test your project. To do that execute the following steps:
 [[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} project as <nowiki>REPG1.zip</nowiki>. To deploy the new Service follow this steps:
@@ Line 118: / Line 118: @@
 # Click RequestReply
-When the service completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>${{gv.app.home}}</nowiki>/log/TestOutput.txt).
+When the service completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>$GV_HOME</nowiki>/log/TestOutput.txt).
-In case of error or exceptions you can review the logs file present in the folder <nowiki>${{gv.app.home}}</nowiki>/log/.
+In case of error or exceptions you can review the logs file present in the folder <nowiki>$GV_HOME</nowiki>/log/.

@@ Line 1: / Line 1: @@
 ==Description==
-This simple example shows a [[Paradigms_of_communication|synchronous service]] and its configuration.
+This simple example shows a simple [[Paradigms_of_communication|synchronous service]] and its configuration.
-A string is passed and {{GVESB}} returns it uppercase.
+The service accept a string as input ,then returns it converted to uppercase.
 ==How To==
 [[File:NewVulconProject.jpg|thumb| New Vulcon Project]]As this might be our first example, the first step will be the creation of a new {{VULCON}} Project.
-# From the Menu panel of {{VULCON}} click File -> New -> Project. A new windows will be open containing the projects type.
+# From the Menu panel of Eclipse click File -> New -> Project. A new windows will be open containing the projects type.
 # Select Vulcon -> "New Vulcon Project" item. Then click Next
-# Set the project name and Location. We named the project GVEXAMPLE and the Location as <nowiki>${{gv.app.home}}/TEST/TESTFS</nowiki>. Then click finish. The new {{VULCON}} project GVEXAMPLE has been created.
+# Set the project name and Location. We named the project GVEXAMPLE and choose a Location of your choice. Then click finish. The new {{VULCON}} project GVEXAMPLE has been created.
-The best mode for creating a [[Service]] is through the Service Wizard. Before using it you must first define a new [[Group]], [[System]] and [[Channel]], if you do not want to use those already present, and the workflow operations.
+The preferred mode for creating a [[Service]] (at least its skeleton) is through the Service Wizard. Before using it you must first configure the test VCL plugin tho execute the uppercase conversion. So let's define a new [[Group]], [[System]] and [[Channel]], if you do not want to use those already present, and then start the Wizard.
 From the core view:
 # Right click the element Groups -> Insert after (or Insert before) -> Group. A new element Group will be created.
@@ Line 22: / Line 23: @@
 # Click on this new Channel element and set the property ''id_channel''. We named it TEST_CHANNEL
 # Finally, insert the operation you need for the workflow. In this case a ''test-service-call''. Right clicking Channel -> Insert after -> [[test-service-call]]. A new element ''test-service-call'' will be created.
-# Set the [[test-service-call]] attributes. From the properties view set the ''name'' attribute as ''test''.
+# Set the [[test-service-call]] attributes. From the properties view set the ''name'' attribute as ''test'' and the ''service'' attribute as ''toupper''.
 [[File:NewServiceWizard.jpg|thumb|New {{GVESB}} Service Wizard]]Now we are able to use the Wizard.
 # From the Core View of {{VULCON}}. Right click the element Services -> Wizard New Service
 # A new window will be open where you can set the name of the Service you want to create, in this case we name it TOUPPER, and as Group, we use TEST_GROUP. You can also select the communication paradigm, for this example it will be [[Paradigms_of_communication#synchronous-synchronous|synchronous-synchronous]]. Click next.
-# Set System as GVESB_TEST and Channel as TEST_CHANNEL. Then choose the Operation, in this case Test. Then finish.
+# Set System as GVESB_TEST and Channel as TEST_CHANNEL. Then choose the Operation, in this case ''test''. Then finish.
@@ Line 39: / Line 40: @@
 The GVCore.xml configuration file will be changed as follows:
 * Into ''Services'' element will be added the tag
 <syntaxhighlight lang="XML">
@@ Line 91: / Line 96: @@
 It is finally arrived the time to test your project. To do that execute the following steps:
-[[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} project as <nowiki>"${{gv.app.home}}/TEST/REPG1.zip"</nowiki>. To deploy the new Service follow this steps:
+[[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} project as <nowiki>REPG1.zip</nowiki>. To deploy the new Service follow this steps:
 # [[Starting|Start {{GVESB}}]]
 # [[GV_Console#Access|Access to the {{GVCONSOLE}}]].
@@ Line 108: / Line 113: @@
 [[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new service:
-# Into the Service voice select TOUPPER
+# Into the Service field select TOUPPER
-# Into the System voice select GVESB_TEST
+# Into the System field select GVESB_TEST (Optional)
 # Click RequestReply
-When test finishes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (we setted it as <nowiki>${{gv.app.home}}</nowiki>/log/TestOutput.txt).
+When teh service completes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). To view the service payload output click on ''Show as Text'' button. Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (the default location is <nowiki>${{gv.app.home}}</nowiki>/log/TestOutput.txt).
 In case of error or exceptions you can review the logs file present in the folder <nowiki>${{gv.app.home}}</nowiki>/log/.

@@ Line 6: / Line 6: @@
 ==How To==
-[[File:NewVulconProject.jpg|thumb| New Vulcon Project]]As this is our first example, the first step will be the creation of a new {{VULCON}} Project.
+[[File:NewVulconProject.jpg|thumb| New Vulcon Project]]As this might be our first example, the first step will be the creation of a new {{VULCON}} Project.
 # From the Menu panel of {{VULCON}} click File -> New -> Project. A new windows will be open containing the projects type.
 # Select Vulcon -> "New Vulcon Project" item. Then click Next
@@ Line 12: / Line 12: @@
-The best mode for creating a [[Service]] is through the Wizard. But for use it you must first define a new [[Group]], [[System]] and [[Channel]], if you do not want to use those already presents, and the workflow operations.
+The best mode for creating a [[Service]] is through the Service Wizard. Before using it you must first define a new [[Group]], [[System]] and [[Channel]], if you do not want to use those already present, and the workflow operations.
 From the core view:
 # Right click the element Groups -> Insert after (or Insert before) -> Group. A new element Group will be created.
@@ Line 26: / Line 26: @@
 [[File:NewServiceWizard.jpg|thumb|New {{GVESB}} Service Wizard]]Now we are able to use the Wizard.
 # From the Core View of {{VULCON}}. Right click the element Services -> Wizard New Service
-# A new windows will be open where you can set the name of the Service you want to create, in this case we named TOUPPER, and your Group, we used TEST_GROUP. You can also select the paradigm, for this example will be [[Paradigms_of_communication#synchronous-synchronous|synchronous-synchronous]]. Click next.
+# A new window will be open where you can set the name of the Service you want to create, in this case we name it TOUPPER, and as Group, we use TEST_GROUP. You can also select the communication paradigm, for this example it will be [[Paradigms_of_communication#synchronous-synchronous|synchronous-synchronous]]. Click next.
-# Set System as GVESB_TEST and Channel as TEST_CHANNEL. Then chose the Operation, in this case Test. Then finish.
+# Set System as GVESB_TEST and Channel as TEST_CHANNEL. Then choose the Operation, in this case Test. Then finish.
-[[File:TOUPPEREditor.jpg |thumb |TOUPPER flow]]As you can see from the core view, inside the Services element, a new Service named TOUPPER has been created. The editor will be open automatically, showing the nodes involved in our [[Flow]].
+[[File:TOUPPEREditor.jpg |thumb |TOUPPER flow]]As you can see from the core view, inside the Services element, a new Service named TOUPPER has been created. The editor will be opened automatically, showing the nodes involved in our [[Flow]].
 * The [[Main_nodes|Start node]] sets the flow first node. In this case ''request''
 * The [[Operations |Operation node]] ''request'' calls the ''test-service-call'' operation '''test''' and executes it.
@@ Line 38: / Line 38: @@
 * Save clicking the ''Save'' icon from the Core View
-The GVCore.xml configuration file will be changed as follow:
+The GVCore.xml configuration file will be changed as follows:
 * Into ''Services'' element will be added the tag
 <syntaxhighlight lang="XML">
@@ Line 79: / Line 79: @@
 </syntaxhighlight>
-Now you are able to test your first {{VULCON}} service from the {{L_GVCONSOLE}}. But first you need to export the configuration.
+Now you are able to test your first {{VULCON}} Service from the {{L_GVCONSOLE}}. But first you need to export the configuration.
 [[File:GVExamplesTOUPPER5.jpg|thumb|Exporting configuration]]Once the flow is correctly configured, the user can export the configuration and pass it to the {{GVESB}} import tool, in order to add into the {{GVESB}} the service just created.
@@ Line 114: / Line 114: @@
 When test finishes, the Testing view will be expanded for containing the GVBUFFER OUTPUT. In this case no properties have been defined so there are only be presents the main informations about the process (System, Service, Id, etc.). Standard fields and the detailed GVBuffer are described in the [[Testing#Data_input|Output File Name]] (we setted it as <nowiki>${{gv.app.home}}</nowiki>/log/TestOutput.txt).
-In case of error or exceptions you can review the logs file presents in the folder <nowiki>${{gv.app.home}}</nowiki>/log/.
+In case of error or exceptions you can review the logs file present in the folder <nowiki>${{gv.app.home}}</nowiki>/log/.