Examples using the GV Console - Revision history

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

2012-03-05T13:25:39Z

‎{{GVCONSOLE}} Configuration

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

2012-03-05T13:22:44Z

‎{{GVCONSOLE}} Configuration

Admin: /* Description */

2012-02-17T12:25:16Z

‎Description

Anonymous at 14:44, 12 February 2012

2012-02-12T14:44:05Z

Anonymous at 14:41, 12 February 2012

2012-02-12T14:41:55Z

Anonymous at 14:37, 12 February 2012

2012-02-12T14:37:02Z

Anonymous at 14:19, 12 February 2012

2012-02-12T14:19:57Z

Anonymous at 14:19, 12 February 2012

2012-02-12T14:19:19Z

Anonymous at 14:17, 12 February 2012

2012-02-12T14:17:52Z

Anonymous: Created page with "This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_..."

2012-02-12T10:59:20Z

Created page with "This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_..."

New page

This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_GVESB_Projects]].

Suppose you have

@@ Line 94: / Line 94: @@
 # Click RequestReply
-As you see, the Test View was expanded and it is also possible to view the [[Testing_output|Test output]] where there are present some properties, among those the GVFSM_EXISTING_FILES property setted to 3. But let us see what happened in our File System:
+As you see, the Test View was expanded and it is also possible to view the [[Testing#Test_output|Test output]] where there are present some properties, among those the GVFSM_EXISTING_FILES property setted to 3. But let us see what happened in our File System:
 # In <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestXML/input there are no files.
 # In <nowiki>${{gv.app.home}}</nowiki>/TEST/TESTFS/TestXML/validated files XML1.xml and XML3.xml were moved into.

@@ Line 74: / Line 74: @@
 # [[GV_Console#Access|Access to the {{GVCONSOLE}}]].
 # In the Deploy New Service section click Sfoglia... (Browse) and select the file where you have 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 1: / Line 1: @@
 ==Description==
-This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_GVESB_Projects]].
+This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First projects]].
 ValidateXMLFiles and ValidateSingleXMLFile example scopes are:

@@ Line 82: / Line 82: @@
 # Save the Document. Saving you return to the [[Deploy Service]] section.
 # Repeat operations 1, 2 and 3, now with the service ValidateSingleXMLFile
 [[File:GVConsoleUtilityReload1.jpg|thumb|{{GVCONSOLE}} Utility section]]Now pass to the {{GVCONSOLE}} section [[Utility]].
@@ Line 89: / Line 88: @@
 # Select GVCore.xml and then Reload. A new windows will be open to confirm the operation
 # 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:
@@ Line 95: / Line 93: @@
 # Into the System voice select GVESB
 # Click RequestReply
 As you see, the Test View was expanded and it is also possible to view the [[Testing_output|Test output]] where there are present some properties, among those the GVFSM_EXISTING_FILES property setted to 3. But let us see what happened in our File System:
@@ Line 107: / Line 104: @@
   id=read_validate_file, exception=GV_CALL_SERVICE_ERROR [it.greenvulcano.gvesb.virtual.CallException]:
   service=ValidateSingleXMLFile, system=GVESB, id=7F0001014F37C2F400021D84,
-  message=cvc-complex-type.2.4.a: Invalid content was found starting with element 'child4'. One of '{child3}' is expected.
+  message=cvc-complex-type.2.4.a: Invalid content was found starting with element 'child4'.

@@ Line 63: / Line 63: @@
 </xs:schema>
 </syntaxhighlight>
-* Coping valid and invalid files in two separated directories
+* Coping valid and invalid files in two separated directories: We have prepared the directories
 * Saving a file <filename>.result with the <filename> validation error message
 [[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 Services follow this steps:

@@ Line 7: / Line 7: @@
 #`Click Submit.
-The section [[Deploy_Services|Deploy Services]] will be open. In this section you can select the services you want to deploy.
+The section [[Deploy_Service|Deploy Services]] will be open. In this section you can select the services you want to deploy.
 # Clicking on service ValidateXMLFiles a new view will be open containing the files GVCore.xml present in local and in server.
@@ Line 16: / Line 16: @@
 [[File:GVConsoleUtilityReload1.jpg|thumb|{{GVCONSOLE}} Utility section]]Now pass to the {{GVCONSOLE}} section [[Utility]].
-# Click on [[Reload_configuration|Reload configuration]]
+# Click on [[Reload_Configuration|Reload configuration]]
 # Select GVCore.xml and then Reload. A new windows will be open to confirm the operation
 # Click OK.

← Older revision		Revision as of 14:17, 12 February 2012
Line 1:		Line 1:
	This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_GVESB_Projects]].		This section shows how to deploy and test a new service using the {{L_GVCONSOLE}} using the ValidateXMLFiles and ValidateSingleXMLFile services, presented in the section [[First_GVESB_Projects]].

−	Suppose you have	+	[[File:GVCONSOLEDeploy.jpg\|thumb\|Deploy new Service]]Suppose you have saved the {{VULCON}} Configuration file as "${{gv.app.home}}/TEST/REPG1.zip". To deploy the new Services follow this steps:
		+	# [[Starting\|Start {{GVESB}}]]
		+	# [[GV_Console#Access\|Access to the {{GVCONSOLE}}]].
		+	# In the Deploy New Service section click Sfoglia... (Browse) and select the file where you have saved the {{VULCON}} configuration.
		+	#`Click Submit.
		+
		+	The section [[Deploy Services]] will be open. In this section you can select the services you want to deploy.
		+
		+	# Clicking on service ValidateXMLFiles a new view will be open containing the files GVCore.xml present in local and in server.
		+	# Click Deploy. Now you can save the document and write some notes about it.
		+	# Save the Document. Saving you return to the [[Deploy Service]] section.
		+	# Repeat operations 1, 2 and 3, now with the service ValidateSingleXMLFile
		+
		+	[[File:GVConsoleUtilityReload1.jpg\|thumb\|{{GVCONSOLE}} Utility section]]Now pass to the {{GVCONSOLE}} section [[Utility]].
		+
		+	# Click on [[Reload configuration]]
		+	# Select GVCore.xml and then Reload. A new windows will be open to confirm the operation
		+	# 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:
		+	# Into the Service voice select ValidateXMLFiles
		+	# Into the System voice select GVESB
		+	# Click RequestReply
		+
		+	As you see, the Test View was expanded and it is also possible to view the [[Test output]] where there are present some properties, among those the GVFSM_EXISTING_FILES property setted to 3. But let us see what happened in our File System:
		+	# In ${{gv.app.home}}/TEST/TESTFS/TestXML/input there are no files.
		+	# In ${{gv.app.home}}/TEST/TESTFS/TestXML/validated files XML1.xml and XML3.xml were moved into.
		+	# In ${{gv.app.home}}/TEST/TESTFS/TestXML/discarded file XML2.xml were moved into and a report file named XML2.xml.result was created.