TestFileAttachment - Revision history

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-20T11:54:02Z

‎{{GVCONSOLE}} Configuration

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-20T11:53:18Z

‎{{GVCONSOLE}} Configuration

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-20T10:44:43Z

‎{{GVCONSOLE}} Configuration

Anonymous: /* Flow implementation */

2012-02-20T10:38:55Z

‎Flow implementation

Anonymous: /* {{VULCON}} Configuration */

2012-02-20T10:35:08Z

‎{{VULCON}} Configuration

Anonymous: /* Flow implementation */

2012-02-20T10:20:31Z

‎Flow implementation

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-20T10:07:19Z

‎{{GVCONSOLE}} Configuration

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-20T10:04:19Z

‎{{GVCONSOLE}} Configuration

Anonymous: /* {{GVCONSOLE}} Configuration */

2012-02-17T11:00:54Z

‎{{GVCONSOLE}} Configuration

G.iannello: /* Flow implementation */

2012-02-16T09:52:34Z

‎Flow implementation

@@ Line 123: / Line 123: @@
 # Click OK.
-[[File:GVExamples_TestFileAttachmentOutput.jpg|thumb|Testing TestFileAttachment]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new services:
+[[File:GVExamplesTestFileAttachmentOutput.jpg|thumb|Testing TestFileAttachment]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new services:
 # Into the Service voice select TestFileAttachment
 # Into the System voice select GVESB

@@ Line 123: / Line 123: @@
 # Click OK.
-[[File:GVConsoleTesting.jpg|thumb|{{GVCONSOLE}} Testing section]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new services:
+[[File:GVExamples_TestFileAttachmentOutput.jpg|thumb|Testing TestFileAttachment]]Go to the {{GVCONSOLE}} section [[Testing]]. In this section you can finally test your new services:
 # Into the Service voice select TestFileAttachment
 # Into the System voice select GVESB

@@ Line 111: / Line 111: @@
 # [[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 59: / Line 59: @@
 ===Flow implementation===
-[[File:NewServiceWizard.jpg|thumb|New {{GVESB}} Service Wizard]]Now we are able to use the Wizard.
+[[File:GVExamples_TestFileAttachmentWizard.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. Set id-service as TestFileAttachment, and Group as TEST_GROUP. The scenario will be [[Paradigms_of_communication#synchronous-synchronous|synchronous-synchronous]]. Click next.

@@ Line 12: / Line 12: @@
 =={{VULCON}} Configuration==
-To configure TestFileAttachment service follow these steps:
+The preferred mode for creating a Service (at least its skeleton) is through the Service Wizard. Before using it you must first configure the VCL plugins neeeded. 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.
 ===Defining System, Channel and Operations===
@@ Line 64: / Line 61: @@
 [[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.
+# A new window will be open where you can set the name of the Service you want to create. Set id-service as TestFileAttachment, and Group as TEST_GROUP. The scenario 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 and Channel as TEST_CHANNEL_FILE. Then choose the first Operation to be executed, in this case ''ScanAttachments''. 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 opened automatically, showing the nodes involved in our [[Flow]].
+[[File:GVExamplesTestFileAttachmentFlow.jpg|thumb|TestFileAttachment flow]] As you can see from the core view, inside the Services element, a new Service named TestFileAttachment has been created. The editor will be opened automatically, showing the nodes involved in our [[Flow]]. To implement the TestFileAttachment service [[Flow]] design it as shown in the picture:
 The following table shows the nodes and attributes to be defined:

← Older revision		Revision as of 10:20, 20 February 2012
Line 62:		Line 62:
	===Flow implementation===		===Flow implementation===

		+	[[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.
		+
		+
		+	[[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.
		+	* A [[Main_nodes\|Check node]] named ''check_status'' is also inserted for controlling the success of the preceding node.
		+	* If ''success'' flow passes to the [[Main_nodes\|End node]] ''return_status''
		+	* In case of Error, flow goes to the [[Main_nodes\|End node]] ''return_error''. The difference with ''return_status'' is signed by the [[Palette\|Connection]] with ''check_status'' Check node. In this case an [[Palette\|Error Connection]] (the Red arrow) have been used.
		+	* Save clicking the ''Save'' icon from the Core View
	[[File:GVExamplesTestFileAttachmentFlow.jpg\|thumb\|TestFileAttachment flow]]To implement the TestFileAttachment service [[Flow]] design it as shown in the picture:		[[File:GVExamplesTestFileAttachmentFlow.jpg\|thumb\|TestFileAttachment flow]]To implement the TestFileAttachment service [[Flow]] design it as shown in the picture:

@@ Line 131: / Line 131: @@
 The Testing View will be expanded and it is also possible to view the GVBuffer Output panel where there are present some properties, among these the GVFM_FOUND_FILES_NUM property set to 3, representing the number of files found.
-The file TestOutput.txt will be generated in the directory $GV_HOME/log as previously set (see [[Testing]], [[data input]] area) containing information about the files found and the email already sent.
+The file TestOutput.txt will be generated in the directory $GV_HOME/log as previously set (see [[Testing]], [[Testing#Data_input|Data input]] area) containing information about the files found and the email already sent.
 <syntaxhighlight lang="XML">
 <pre>

@@ Line 108: / Line 108: @@
 It is time to deploy and test your new Service. To do that execute the following steps:
-[[File:GVCONSOLEDeploy.jpg|thumb|Deploy new Service]]Suppose you have saved the {{VULCON}} Configuration file 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}} Configuration file as <nowiki>"$GV_HOME/TEST/REPG1.zip"</nowiki>. To deploy the new Service follow this steps:
 # [[Starting|Start {{GVESB}}]]
 # [[GV_Console#Access|Access to the {{GVCONSOLE}}]].
@@ Line 131: / Line 131: @@
 The Testing View will be expanded and it is also possible to view the GVBuffer Output panel where there are present some properties, among these the GVFM_FOUND_FILES_NUM property set to 3, representing the number of files found.
-The file TestOutput.txt will be generated in the directory <nowiki>${{gv.app.home}}</nowiki>/log as previously set (see [[Testing]], [[data input]] area) containing information about the files found and the email already sent.
+The file TestOutput.txt will be generated in the directory $GV_HOME/log as previously set (see [[Testing]], [[data input]] area) containing information about the files found and the email already sent.
 <syntaxhighlight lang="XML">
 <pre>
@@ Line 144: / Line 144: @@
 Properties:
 	messageID = <9388830.11329325352084.JavaMail.gv1@gv.com>
-	GVFM_FOUND_FILES_LIST = <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/001.txt;
+	GVFM_FOUND_FILES_LIST = $GV_HOME/TEST/TESTFS/TestAttach/input/001.txt;
-                                 <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/002.txt;
+                                 $GV_HOME/TEST/TESTFS/TestAttach/input/002.txt;
-                                 <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/003.txt
+                                 $GV_HOME/TEST/TESTFS/TestAttach/input/003.txt
 	GVFM_FOUND_FILES_NUM = 3
-	GV_SMTP_ATTACHMENTS = <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/001.txt;
+	GV_SMTP_ATTACHMENTS = $GV_HOME/TEST/TESTFS/TestAttach/input/001.txt;
-                               <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/002.txt;
+                               $GV_HOME/TEST/TESTFS/TestAttach/input/002.txt;
-                               <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/input/003.txt
+                               $GV_HOME/TEST/TESTFS/TestAttach/input/003.txt
 </pre>
 </syntaxhighlight>
@@ Line 164: / Line 164: @@
-You can also check that the files were moved into the directory <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestAttach/sent.
+You can also check that the files were moved into the directory $GV_HOME/TEST/TESTFS/TestAttach/sent.

← Older revision		Revision as of 09:52, 16 February 2012
Line 65:		Line 65:


−	The service ~~searchs~~ the ~~files present~~ in a directory, sends it as attachment and moves it into another directory.	+	The service looks for the file presence in a directory, sends it as attachment and moves it into another directory.