You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by de...@apache.org on 2005/06/07 14:35:46 UTC
svn commit: r188759 - in /webservices/axis/trunk/java/xdocs:
images/admin.jpg images/adminloging.jpg images/adminmain.jpg
images/globalchain.jpg images/moduleengage.jpg images/modules.jpg
images/serviceHandlers.jpg images/viewphases.jpg webadminguide.html
Author: deepal
Date: Tue Jun 7 05:35:46 2005
New Revision: 188759
URL: http://svn.apache.org/viewcvs?rev=188759&view=rev
Log:
changed web asdmin module and (added Ruchith's modificatins)
Added:
webservices/axis/trunk/java/xdocs/images/admin.jpg (with props)
Modified:
webservices/axis/trunk/java/xdocs/images/adminloging.jpg
webservices/axis/trunk/java/xdocs/images/adminmain.jpg
webservices/axis/trunk/java/xdocs/images/globalchain.jpg
webservices/axis/trunk/java/xdocs/images/moduleengage.jpg
webservices/axis/trunk/java/xdocs/images/modules.jpg
webservices/axis/trunk/java/xdocs/images/serviceHandlers.jpg
webservices/axis/trunk/java/xdocs/images/viewphases.jpg
webservices/axis/trunk/java/xdocs/webadminguide.html
Added: webservices/axis/trunk/java/xdocs/images/admin.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/admin.jpg?rev=188759&view=auto
==============================================================================
Binary file - no diff available.
Propchange: webservices/axis/trunk/java/xdocs/images/admin.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: webservices/axis/trunk/java/xdocs/images/adminloging.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/adminloging.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/adminmain.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/adminmain.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/globalchain.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/globalchain.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/moduleengage.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/moduleengage.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/modules.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/modules.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/serviceHandlers.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/serviceHandlers.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/images/viewphases.jpg
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/images/viewphases.jpg?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
Binary files - no diff available.
Modified: webservices/axis/trunk/java/xdocs/webadminguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/webadminguide.html?rev=188759&r1=188758&r2=188759&view=diff
==============================================================================
--- webservices/axis/trunk/java/xdocs/webadminguide.html (original)
+++ webservices/axis/trunk/java/xdocs/webadminguide.html Tue Jun 7 05:35:46 2005
@@ -1,3 +1,4 @@
+<!-- saved from url=(0022)http://internet.e-mail -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
@@ -5,78 +6,109 @@
<title>Axis2 administartion guide</title>
</head>
<body>
-<p><h3><a name="_Toc96698076"></a>Introduction </h3>
-<p>Axis2 web administration module provide a way to configure axis2 dynamically
- but those dynamic configuration wont be persistence, i.e. if the servlet
- container restart then all the dynamic configuration changes will be lost. </p>
-
- <p><h4><a name="_Toc96698076"></a>Loging into Administartion </h4>
+<p><h3>Introduction </h3>
+<p>Axis2 web administration module provides a way to configure axis2 dynamically.
+Its important to note that this dynamic configuration will NOT be persistent, i.e. if the servlet
+ container is restarted then all the dynamic configuration changes will be lost.</p>
+
+ <p><h4><a name="_Toc96698076"></a>Loging into administartion site</h4>
<p>From axis2 index page you can go to administration page by following
-Axis2 Administration link, then logging page will be appeared asking user
-name and password , the default username = admin and default password = axis2 .
- You can change those two values by changing following two parameters in
- server.xml as you required.
+Axis2 Administration link, then logging page will appear asking for a user
+name and a password , the default username is 'admin' (without quotes) and default
+password is 'axis2' (without quotes).
+ You can change those two values by changing following two parameters in server.xml as required.
<p align="left"><strong><img src="images/parameters.jpg"></strong></p>
-<p align="left"><strong><img src="images/adminloging.jpg"></strong></p>
+<p align="left"><strong><img src="images/adminloging.jpg" ></strong></p>
</p>
-<p>If the login succeed you will be see a page like below , where you can use
-that to
- view the running system and dynamically configure the system. </p>
- <p align="left"><strong><img src="images/adminmain.jpg"></strong></p>
+<p>If the login succeed you will be see as shown below. This is where you can view the
+configuration and the state of the running system and dynamically configure it. </p>
+ <p align="left"><strong><img src="images/admin.jpg" ></strong></p>
- <p>The list service in axis2 index page and here are almost the same but only
- additional feature provide with admin module list service is, if there is any
- module engaged globally, to the service or to the operation those details
+<h3>Administration Options</h3>
+<ul>
+<b>System components</b>
+<li><a href="#heading1">List available services</a></li>
+<li><a href="#avmodules">List available modules</a></li>
+<li><a href="#globalmodules">List globally engaged modules</a></li>
+<li><a href="#phases">View available phases</a></li>
+<br>
+<b>Execution chains</b>
+<li><a href="#globalchains">Global chanins</a></li>
+<li><a href="#operationchains">Operation specific chains</a></li>
+<br>
+<b>Other</b>
+<li><a href="#engaginmodule">Engage module</a></li>
+</ul>
+
+
+<h3><a name="heading1"></a>List Available services</h3>
+ <p>The functionality of the 'List Available Services' option is almost same
+ as the functionality of the axis to main page where it displayes the list of
+ deployed services. But as an additional feature, if there are any
+ modules engaged globally, to services or to operations those details
will be displayed here. </p>
-
+<p align="left"><strong><img src="images/adminmain.jpg" ></strong></p>
+
+
+<h3><a name="avmodules"></a>List Available modules</h3>
+
<p>To view the available modules in the "repository/modules" you just have
- to click the view modules then it will show you all the available modules
- in the system and only those modules can be dynamically engaged. </p>
-
- <p align="left"><strong><img src="images/modules.jpg"></strong></p>
- <p> </p>
+ to click the 'Available Modules' then it will show you all the available modules
+ in the system and those modules can be engaged dynamically. </p>
+
+ <p align="left"><strong><img src="images/modules.jpg" ></strong></p>
+ <br>
+ <h3><a name="globalmodules"></a>List Globally engaged modules</h3>
<p>From the globally engaged modules you can see the globally engaged
- modules if there is any , if a modules has engaged globally then the
- handlers belong to that module will be executed irrespective of the service.
+ modules if any , if a module was engaged globally then the
+ handlers that belong to that module will be executed irrespective of the service.
+ The 'Globally Engaged Modules' option lists the above list of modules.
</p>
- <p> </p>
- <p>In axis2 there are two levels of phases, system predefined phases
- (not allowed to change) and user defined phases. The main difference
- between those two levels of phases is irrespective of the service all
- the system pre defined phases will be executed, if the dispatcher find
- the corresponding operation then user defined phase list will be executed.
- And for the module developers and service writers are really required to
- have understanding about phases and their orders. </p>
- <p align="left"><strong><img src="images/viewphases.jpg"></strong></p>
- <p> </p>
- <p>The most interesting of axis2 web admin module is it provide a very basic
- way of viewing the global phase list and handler inside the phases considering
- both phase and handler orders. This kind of information is very valuable to
- debug the system, because there is no way to list out the handlers in the
+ <br>
+ <h3><a name="phases"></a>View available phases</h3>
+
+ <p>In axis2 there are two levels of phases:</p>
+ <ul>
+ <li>system predefined phases(not allowed to be changed)</li>
+ <li>user defined phases</li>
+ </ul>
+ <p>The main difference between those two levels of phases is that, in the case of
+ system predefined phases, the phases will be invoked irrespective of the irrespective of the services.
+ When the dispatcher finds the operation then user defined phase list will be invoked.
+ It should be noted that the module developers and service writers are really required to
+ have a good understanding of phases and phase ordering.</p>
+ <img src="images/viewphases.jpg" >
+ <br>
+
+ <h3><a name="globalchains"></a>View Global chanins</h3>
+ <p>The most interesting feature of axis2 web admin module is that it provide a very basic
+ way of viewing the global phase list and handlers inside the phases depending on
+ both phase and handler orders. This kind of information is extreamly useful in debugging
+ the system, because there is no way to list out the handlers in the
global chains except this. And if you engage a new module the new handlers
- will be added to the global chains and those will be displayed in this view
- phase page. </p>
-
- <p align="left"><strong><img src="images/globalchain.jpg"></strong></p>
- <p> </p>
- <p>From the View Service phase and Handlers can view the handlers corresponding
- to a given service in the same order as there in the real execution chain. </p>
+ will be added to the global chains and those will be displayed in this page.</p>
- <p align="left"><strong><img src="images/serviceHandlers.jpg"></strong></p>
- <p> </p>
+ <p align="left"><strong><img src="images/globalchain.jpg" ></strong></p>
+ <br>
+ <h3><a name="operationchains"></a>View operation specific chains</h3>
+ <p>The 'Operation Specific Chains' can be used to view the handlers corresponding
+ to a given service in the same order as there in the real execution chain.</p>
+ <p align="left"><strong><img src="images/serviceHandlers.jpg" ></strong></p>
+ <br>
-<p>Modules can be engage either globally, to a service or to an operation
-depending on the module implementation. If the module has implemented to
-engage globally then handlers in the module can be refers to any phase in
-the system, that is it can be either system predefined or user defined phase.</P>
-<p>In there other hand if the module has implemented in such a way that is going
- to be deployed to a service or to an operation then the module can NOT refers
- to any of system predefined phases. So that it can only refers to user defined phases. </p>
+ <h3><a name="engaginmodule"></a>Engaging modules</h3>
+<p>Modules can be engaged either globally, to a service or to an operation
+depending on the module implementation. If the module was designed to
+engage the handlers globally then handlers in the module can be included in any phase in
+the system. It can be either system predefined or user defined phase.</P>
+<p>In there other hand if the module was implemented in such a way that is going
+ to be deployed to a service or to an operation then the module canNOT be included in
+ any of system predefined phases. So that it can only be included in user defined phases. </p>
<p>Immediately after engaging the module you can see the status of the engagement
-, whether it is engaged properly or not. </p>
+, indicating whether it is engaged properly or not. </p>
-<p align="left"><strong><img src="images/moduleengage.jpg"></strong></p>
+<p align="left"><strong><img src="images/moduleengage.jpg" ></strong></p>
<p> </p>
</body>