GV Console - Revision history

Anonymous: /* {{GVCONSOLE}} Menu */

2012-02-11T08:49:50Z

‎{{GVCONSOLE}} Menu

G.iannello: /* Description */

2012-02-03T21:08:16Z

‎Description

C.ortenzi: /* Next steps */

2012-02-03T00:34:14Z

‎Next steps

C.ortenzi: /* Next steps */

2012-02-03T00:33:46Z

‎Next steps

Anonymous: /* Next steps */

2012-01-31T13:21:14Z

‎Next steps

G.dimaio at 16:47, 25 January 2012

2012-01-25T16:47:47Z

Anonymous: /* Access */

2012-01-25T09:45:39Z

‎Access

Anonymous: /* Access */

2012-01-25T09:45:08Z

‎Access

Anonymous: /* Next steps */

2012-01-25T09:14:44Z

‎Next steps

Anonymous: /* Next steps */

2012-01-25T09:14:02Z

‎Next steps

@@ Line 26: / Line 26: @@
 * Deploy a new service ([[Deploy New Services]]);
 * Modify the {{GVESB}} XML configuration ([[Parameter]]);
-* Manage WebService deployment ([[Web Service]]);
+* Manage WebService deployment ([[Web Services]]);
 * Use {{GVCONSOLE}} Tools ([[Utility]])
 * Test {{GVESB}} services ([[Testing]]);

@@ Line 1: / Line 1: @@
 ==Description==
-The {{GVCONSOLE}} is a Web Application which provide a centralized point to manage, monitor and administer all the {{GVESB}} instances.
+The {{GVCONSOLE}} is a Web Application providing a centralized tool to manage, monitor and administer all the {{GVESB}} instances.
-The application make easier the deployment of Services on the {{GVESB}} servers, the functional testing, the log listing and system performance visualization.
+This application makes the deployment of Services on the {{GVESB}} servers easier, helps the functional testing, the log listing and system performance visualization.
 ==Access==

← Older revision		Revision as of 00:34, 3 February 2012
Line 37:		Line 37:

	In order to learn more about {{GVCONSOLE}} see [[Examples using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy new services]] and test your [[{{VULCON}} first flow]].		In order to learn more about {{GVCONSOLE}} see [[Examples using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy new services]] and test your [[{{VULCON}} first flow]].
		+	{{VOTE}}

← Older revision		Revision as of 00:33, 3 February 2012
Line 36:		Line 36:
	==Next steps==		==Next steps==

−	In order to learn more about {{GVCONSOLE}} see [[Examples using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy ~~the~~ new services]] and test your [[{{VULCON}} first flow]].	+	In order to learn more about {{GVCONSOLE}} see [[Examples using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy new services]] and test your [[{{VULCON}} first flow]].

← Older revision		Revision as of 13:21, 31 January 2012
Line 36:		Line 36:
	==Next steps==		==Next steps==

−	In order to learn more about {{GVCONSOLE}} see [[~~Example~~ using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy the new services]] and test your [[{{VULCON}} first flow]].	+	In order to learn more about {{GVCONSOLE}} see [[Examples using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services\|deploy the new services]] and test your [[{{VULCON}} first flow]].

@@ Line 1: / Line 1: @@
-==Definition==
+==Description==
-Once a [[service]] has been created, the user must be able to manage all the {{GVESB}} infrastructure and monitoring the system on which it is working. Adding to these services its respective system, channel, operations, together with other elements valid for the {{GVESB}} correct operation, the level of complexity increases. It is therefore necessary to have visibility and control system performance.
+The {{GVCONSOLE}} is a Web Application which provide a centralized point to manage, monitor and administer all the {{GVESB}} instances.
+The application make easier the deployment of Services on the {{GVESB}} servers, the functional testing, the log listing and system performance visualization.
 ==Access==
@@ Line 10: / Line 9: @@
-{{GVESB}} Console is available at:
+{{GVESB}} Console can be accessed at the URL:
@@ Line 16: / Line 15: @@
-where ''ipAddress'' is the server address where the application has been deployed and ''gvconsole'' is the name given to the web console.
+where ''ipAddress'' is the server address where the application has been deployed and ''gvconsole'' is the name given to the web application.
-In order to display the web console, user must login by submitting a valid administrative ''username'' and ''password''.
+In order to display the web console, users must login by submitting a valid administrator account credentials.
 =={{GVCONSOLE}} Menu==
@@ Line 25: / Line 24: @@
 [[File:GVConsoleInitPage.jpg|thumb|400px|GVConsole]]
-* deploy a new service ([[Deploy New Services]]);
+* Deploy a new service ([[Deploy New Services]]);
-* configure a parameter directly into the XML document ([[Parameter]]);
+* Modify the {{GVESB}} XML configuration ([[Parameter]]);
-* configure the web service ([[Web Service]]);
+* Manage WebService deployment ([[Web Service]]);
-* use the {{GVCONSOLE}} Tools ([[Utility]])
+* Use {{GVCONSOLE}} Tools ([[Utility]])
-* test the {{GVESB}} services ([[Testing]]);
+* Test {{GVESB}} services ([[Testing]]);
-* view the log messages ([[Log]])
+* View the log messages ([[Log]])
-* create reports ([[Report]]);
+* Create BIRT reports ([[Report]]);
-* see the save point ([[SavePoint]]);
+* Manage the SavePoint ([[SavePoint]]);
-* Monitor the JVM ([[Monitoring]]).
+* Monitor JVM metrics ([[Monitoring]]).
 ==Next steps==
-In order to learn more about {{GVCONSOLE}} see [[Example using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this web application works, you may want to [[Deploy New Services|deploy the new services]] and test your [[{{VULCON}} first flow]].
+In order to learn more about {{GVCONSOLE}} see [[Example using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this application works, you may want to [[Deploy New Services|deploy the new services]] and test your [[{{VULCON}} first flow]].

← Older revision		Revision as of 09:45, 25 January 2012
Line 17:		Line 17:

	where ''ipAddress'' is the server address where the application has been deployed and ''gvconsole'' is the name given to the web console.		where ''ipAddress'' is the server address where the application has been deployed and ''gvconsole'' is the name given to the web console.
−
	In order to display the web console, user must login by submitting a valid administrative ''username'' and ''password''.		In order to display the web console, user must login by submitting a valid administrative ''username'' and ''password''.

← Older revision		Revision as of 09:14, 25 January 2012
Line 36:		Line 36:
	==Next steps==		==Next steps==

−	In order to learn more about {{GVCONSOLE}} see [[Example using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this web application works, you may want to [[~~deploy new services~~\|deploy the new services]] and test your [[{{VULCON}} first flow]].	+	In order to learn more about {{GVCONSOLE}} see [[Example using the {{GVCONSOLE}}]] section. Otherwise, if you already know how this web application works, you may want to [[Deploy New Services\|deploy the new services]] and test your [[{{VULCON}} first flow]].