<!--
  ~ Copyright 2005-2007 WSO2, Inc. (http://wso2.com)
  ~
  ~ Licensed under the Apache License, Version 2.0 (the "License");
  ~ you may not use this file except in compliance with the License.
  ~ You may obtain a copy of the License at
  ~
  ~ http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing, software
  ~ distributed under the License is distributed on an "AS IS" BASIS,
  ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  ~ See the License for the specific language governing permissions and
  ~ limitations under the License.
  -->

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
       "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<body>
<p>[<a
href="http://dist.wso2.org/products/wsas/java/@wso2wsas_version@">Download</a>]
| [<a href="index_docs.html">Documentation Index</a>] | [<a
href="release_notes.html">Release Note</a>]</p>

<h1>User Guide</h1>

<p>This document provides information and instructions on the functionality
of WSO2 WSAS UI console.</p>

<p>Your feedback on WSO2 WSAS is most appreciated. Please send them to our <a
href="mail-lists.html">mailing lists</a>.</p>

<h2>Content</h2>

<div class="toc">
<ul>
  <li><a href="#Introducti">Introduction</a></li>
  <li><a href="#Welcome">Welcome Page</a></li>
  <li><a href="#Signing">Signing In</a></li>
  <li><a href="#Navigation">Navigation Bar</a></li>
  <li><a href="#Home">Home</a></li>
  <li><a href="#Manage">Manage Services</a>
    <ul>
      <li><a href="#Remove">Remove Service Group:</a></li>
      <li><a href="#Deploying">Deploying Services:</a>
        <ul>
          <li><a href="#Upload">Upload a Service Artifact
            (.aar,.jar,.zip,.dbs)</a></li>
          <li><a href="#Upload1">Upload a New POJO Service (.jar)</a></li>
          <li><a href="#Upload2">Upload a New Spring Service (.xml and
            .jar)</a></li>
          <li><a href="#Upload3">Upload a Data Service</a></li>
          <li><a href="#Deploy">Deploy Axis1 Services (.wsdd files)</a>
            <ul>
              <li><a href="#Usage">Usage</a></li>
              <li><a href="#Axis1">Axis1 RPC Services</a></li>
            </ul>
          </li>
          <li><a href="#Service">EJB Service Provider</a></li>
        </ul>
      </li>
      <li><a href="#Feed">RSS Feed:</a></li>
      <li><a href="#Atom">Atom Feed:</a></li>
      <li><a href="#Deleting">Deleting Faulty Services:</a></li>
      <li><a href="#Service1">Service Group Management:</a></li>
      <li><a href="#Service2">Service Management:</a></li>
    </ul>
  </li>
  <li><a href="#DynamicCodegen">Dynamic Codegen</a></li>
  <li><a href="#Manage1">Manage Modules</a>
      <ul>
		<li><a href="#sandesha2">Sandesha2 Information</a></li>
	</ul>
  </li>

  <li><a href="#Manage2">Manage Security</a>
    <ul>
      <li><a href="#Role">Role Management:</a></li>
      <li><a href="#User">User Management:</a></li>
    </ul>
  </li>
  <li><a href="#Manage3">Manage Transports</a></li>
  <li><a href="#Manage4">Manage KeyStores</a></li>
  <li><a href="#Manage5">Manage Logging</a>
    <ul>
      <li><a href="#Configure">Configure Log4J Loggers:</a></li>
      <li><a href="#Configure1">Configure Log4J Appenders:</a></li>
      <li><a href="#Global">Global Log4J Configuration:</a></li>
      <li><a href="#RestoreDefault">Restore Default:</a></li>
      <li><a href="#FilteringLoggers">Filter Loggers:</a></li>
    </ul>
  </li>
  <li><a href="#Restart">Restart Server</a></li>
  <li><a href="#Monitor">Monitor System</a></li>
  <li><a href="#Monitor1">Monitor Statistics</a></li>
  <li><a href="#Monitor2">Monitor Logs</a></li>
  <li><a href="#Monitor3">Monitor Tracer</a></li>
  <li><a href="#Monitor4">Monitor Flows</a></li>
  <li><a href="#Miscellane">Miscellaneous</a>
    <ul>
      <li><a href="#Signing1">Signing Out</a></li>
      <li><a href="#Register">Register</a></li>
    </ul>
  </li>
  <li><a href="#Browser">Web Browser Specific Settings</a>
    <ul>
      <li><a href="#Internet">Internet Explorer 6 :</a></li>
    </ul>
  </li>
  <li><a href="#service_sec">Manage Service Security Configuration</a></li>
  <li><a href="#sts_config">Security Token Service Configuration</a></li>
</ul>
</div>

<h2 id="Introducti">Introduction</h2>

<p>WSO2 WSAS is a lightweight, high performant and integrated Web services
middleware platform. Learn more about <a href="index.html">WSO2 WSAS</a>!</p>

<p>WSO2 WSAS Management Console is your one stop shop to administer the WSO2
Web Services Application Server. You can administer/configure your
modules/services as well as monitor the system through this interface.</p>

<p>WSO2 WSAS Management Console runs on <a
href="http://en.wikipedia.org/wiki/Ajax_(programming)">AJAX</a> (Asynchronous
Javascript and XML) and SOAP, making it a fast administration tool. All the
functionalities are provided by a set of Web services exposed by the WSO2
WSAS.</p>

<p>Before going through the functionality, we recommend that you read the <a
href="#browser_settings">Web Browser Specific Settings</a> section to ensure
that you have access to the full list of features WSO2 WSAS AJAX Management
console offers through your Web browser.</p>

<p>The functionality of the Management Console is described in detail
below.</p>

<h2 id="Welcome">Welcome Page</h2>

<p>Once WSO2 WSAS, v@wso2wsas_version@ has been successfully installed (see
<a href="installation_guide.html">Installation Guide</a> for installation
details), start the WSO2 WSAS server. Then, launch a Web browser instance and
point it to the URL <a
href="https://localhost:9443/">https://localhost:9443/</a> or <a href="http://localhost:9762">
http://localhost:9762</a> (when running in
Stand-alone mode) or <a
href="https://localhost:9443/">https://localhost:9443/wso2wsas/</a> or<a
href="http://localhost:9762/">http://localhost:9762/wso2wsas/</a>  (when
deployed inside a Servlet container) if you are using the default settings.
This will take you to the welcome page page of the WSO2 WSAS Console
as shown below.</p>

<strong>Note</strong>:
<p> WSO2 WSAS has two transport listeners: HTTP and
HTTPS. By default, the HTTP listener opens on port 9762, while the HTTPS
listener opens on port 9443. The administrator functionality is exposed only
via the HTTPS port.</p>

<p>You can now read all the WSO2 WSAS <strong>documents</strong> by pointing
your Web browser to <a
href="https://localhost:9443/docs">https://localhost:9443/docs</a> or <a
href="http://localhost:9762/docs">http://localhost:9762/docs</a>
(Stand-alone) or <a
href="https://localhost:9443/docs">https://localhost:9443/wso2wsas/docs</a> or <a
href="http://localhost:9762/docs">https://localhost:9762/wso2wsas/docs</a>
(Servlet) if you are using the default settings.</p>

<p>
	<br/><br/>
   		<img alt="Figure: Welcome Page" src="images/welcome.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Welcome Page</strong></p><br/>

<p>As you can see on the welcome page, WSO2 WSAS v@wso2wsas_version@ has integrated six
important tools that can be used in development time. More information will be available later.</p>

<a name="Signing"></a>

<h2>Signing In</h2>

<p>Signing will be available in the upper right hand corner. Sign In page will
be as shown below. When user clicks the "sign in" link, it will automatically redirect
the request to secure protocol https, if user has already in http protocol. Once the
correct credentials has been provided, user will be logged in to the WSAS management mode.
</p>

<p>
	<br/><br/>
		<img alt="Figure:Sign In page" src="images/sign_in.jpg" />
	<br/><br/>
</p><br/>
<p><strong>Figure: Sign In page</strong></p><br/>

<p>The default username and password to sign into WSO2 WSAS Management
Console:</p>

<p><strong>User name :</strong> admin</p>

<p><strong>Password :</strong> admin</p>

<p>To solve any problems with signing in, click <!--<a
href="../sign_in_help.html">-->
 "Sign-in Help"</p>

<p>The Sign In page contains links to the <!--<a href="../faq.html">-->
 "FAQ" and the <!--<a href="../about.html">-->
 "About WSO2 WSAS" page which gives an introduction about WSO2 WSAS and WSO2
Inc.</p>
<a name="nav_bar"></a>

<h2 id="Navigation">Navigation Bar</h2>
The following links are available on the navigation bar
<ul>
  <li><a href="#home">Home</a></li>
  <li>Manage
    <ul>
      <li><a href="#services">Services</a></li>
      <li><a href="#qos">Modules</a></li>
      <li><a href="#mgrusers">Security</a></li>
      <li><a href="#manage_transports">Transports</a></li>
      <li><a href="#manage_keystores">Key Stores</a></li>
      <li><a href="#config">Logging</a></li>
      <li><a href="#restart">Restart</a></li>
    </ul>
  </li>
  <li>Monitor
    <ul>
      <li><a href="#Monitor_system">System</a></li>
      <li><a href="#Monitor_Statistics">Statistics</a></li>
      <li><a href="#logs">Logs</a></li>
      <li><a href="#Monitor_Tracer">Tracer</a></li>
      <li><a href="#Monitor_flows">Flows</a></li>
    </ul>
  </li>
    <li>Tools
    <ul>
      <li><a href="./tools/wsdl2code.html">WSDL2Code</a></li>
      <li><a href="./tools/wsdlview.html">WSDL View</a></li>
      <li><a href="./tools/wsdl_converter.html">WSDL Converter</a></li>
      <li><a href="./tools/tryit.html">Try It</a></li>
      <li><a href="./tools/aar_validator.html">AAR Validator</a></li>
      <li><a href="./tools/mar_validator.html">MAR Validator</a></li>
    </ul>
  </li>
</ul>
<a name="home"></a>

<h2 id="Home">Home</h2>

<p>The Home Page of the Management Console will contain the following useful
<strong>system and service information on WSO2 WSAS.</strong></p>
<ul>
  <li><strong>System Summary</strong>
    <ul>
      <!--<li>Free Memory- Free memory of JVM</li>-->
      <!--<li>Request Count - The number of requests that have gone through the
            server (this includes requests to the admin service, which will
            explain the small number you see here</li>-->
      <li>Server Name - The name of the server</li>
      <li>Server Version - The version of the above named server</li>
      <li>Server Start Time- The time the server was started/restarted</li>
      <li>System Up Time - The time span for which the server has been
      running</li>
      <li>Memory Allocated - Total JVM memory allocated for the server</li>
      <li>Memory Usage - Total JVM memory used by the server</li>
    </ul>
  </li>
  <li><strong>Service Summary</strong>
    <ul>
      <li>Total Request Count - Lists the number of requests since the server
        started</li>
      <li>Total Response Count - Lists the number of responses since the
        server started</li>
      <li>Total Fault Count - Lists the number of faults that occurred since
        the server started</li>
      <li>Active Services - Lists how many services are deployed and running
        on the server</li>
    </ul>
  </li>
</ul>

<p>
	<br/><br/>
    	<img alt="Figure1:WSO2 WSAS HOME" src="images/home.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: WSO2 WSAS HOME</strong></p>
<a name="system"></a>

<h2>Manage System</h2>

<p>This page shows you the environmental setup of the
server,<strong></strong> such as Axis2 installation location, Java Home, Java
version &amp; other Java information, OS information, Repository location,
Server name &amp; User information</p>

<p>On this page you have the option of <strong>saving the state of the
system</strong> (after making changes to the state) using 'Save System'
button, and <strong>restarting system</strong> from that saved state using
the 'Restart System' button.</p><br/>

<p>
	<br/><br/>
		<img src="images/system.jpg" alt="Figure:System" />
	<br/><br/>	
</p><br/>
    <p><strong>Figure: System</strong></p>
<a name="services"></a>

<h2 id="Manage">Manage Services</h2>

<p>
	<br/><br/>
		<img alt="Figure:Services and Service Group Management"
src="images/available_services-new.jpg" />
	<br/><br/>
</p>

<p><strong>Figure: Services and Service Group Management</strong></p> <br/><br/>

<p>As shown above, this page lists the available services or those deployed
in each service group in the system, along with links to view the WSDL1.1,
Schema, Policy and Certificate (containing the public key if the service has
been signed using a private key) of each service.</p>

<p>This page also carries a link that displays <a href="#rss">RSS</a> and <a
href="#atom">Atom</a> feeds.</p>

<p>
	<br/><br/>
		<img alt="Figure:View WSDL 1.1 of service echo" src="images/wsdl1.1.jpg"/>
	<br/><br/>	
</p>
<a name="remove_group"><strong>Figure: WSDL 1.1 of Service echo</strong></a>

<h3 id="Remove">Remove Service Group:</h3>

<p><strong>A service group can be removed</strong> using the 'Remove' action
icon listed for each service group, in which case all the services in that
particular service archive will be removed from the system.</p>
<a name="deploy_services"></a>

<h3 id="Deploying">Deploying Services:</h3>
<strong>Uploading a New Service (.aar, .jar or .zip)</strong>

<p>The following new services can be uploaded and managed through this
console.</p>
<ul>
  <li>Service Artifact</li>
  <li>POJO Artifact</li>
  <li>Spring Service</li>
  <li>Data Service</li>
  <li>Axis1 Service</li>
  <li>EJB Service</li>
</ul>

<a name="upload_service_artifact"></a>
<h4>Upload a Service Artifact (.aar,.jar,.zip,.dbs)</h4>

<p>If the <strong>service archive of the relevant service is an
.aar</strong>, you can deploy the service by simply selecting the service
archive by clicking 'Browse', and then uploading the service by clicking
'Upload'. For example, Axis2 packages the services as .aar files. Therefore,
you can simply deploy an Axis2 service by uploading the relevant .aar
file.</p>

<p>
	<br/><br/>
		<img alt="Figure: Uploading an .aar file" src="images/service_artifact.jpg" /> 
	<br/><br/>
</p><br/>

<p><strong>Figure: Uploading an .aar file.</strong></p><br/><br/>

<p>Where the <strong>service archive of the relevant service is a .jar or
.zip file</strong>, then the deployment requires a few more steps. In this
case, you must select the service archive by clicking 'Browse', and then
upload the service by clicking 'Upload'. Then, a page containing the classes
of the archive will appear as shown below. On this page, select the relevant
classes of the Web services you wish to deploy by selecting the corresponding
check boxes. Once you have selected all the classes, click 'Generate' to
deploy the relevant services. This process is called <strong>Dynamic Service
Generation.</strong></p>

<p>If the artifact is of type .dbs, i.e. a data service, please refer to
    <a title="Date Service Guide" href="data_service.html">Data Service Guide</a> for
detailed instructions.</p>

<p>
	<br/><br/>
		<img alt="Figure: Dynamic Services Generation-Uploading .jar or .zip File"
src="images/dynamic_services.jpg" />
	<br/><br/>
</p>

<p><strong>Figure: Dynamic Service Generation-Uploading .jar or .zip
File</strong></p>

<a name="pojo_service"></a>
<h4 id="Upload1">Upload a New POJO Service (.jar)</h4>

<p>Likewise, you can also deploy a POJO services by browsing for and
uploading the relevant .jar files. Please note that the classes and methods
in the .jar have to be @webService &amp; @WebMethod annotated, respectively.
You can also browse for and add other .jar resources that are required for
your annotated .jar's proper execution.</p>

<p>
	<br/><br/>
		<img alt="Figure: POJO service" src="images/pojo-service.jpg" />
	<br/><br/>	
</p>

<a name="spring_service"></a>
<h4 id="Upload2">Upload a New Spring Service (.xml and .jar)</h4>

<p>Likewise, you can also deploy Spring services by browsing for and
uploading the relevant .xml and .jar files. Deploying Spring services follows
the <strong>Dynamic Service Generation</strong> procedure as explained
above.</p><br/>

<p>
	<br/><br/>
		<img alt="Figure: Spring service" src="images/spring_service.jpg" />
	<br/><br/>
</p><br/>

<p><strong>Figure: Uploading a Spring service</strong></p> <br/><br/>

<p>After you specify the .xml and .jar files and click
<strong>Upload</strong>, the following page appears. Here you can select the
Spring beans you want to expose and click <strong>Generate</strong>.</p>  <br/>

<p>
	<br/><br/>
		<img alt="Figure: Dynamic Service Generation for Spring Service-Uploading.xml or .jar File"
src="images/dynamic_services_spring.jpg" />
	<br/><br/>
</p><br/>

<p><strong>Figure: Dynamic Service Generation for Spring Service-Uploading
.xml or .jar File</strong></p> <br/><br/>

<p>If the services were successfully deployed, then a message will appear
saying so. The service that you deployed will now be listed on the main page
of <a href="#services">'Manage Services</a>' (as shown in Figure: Services
and Service Group Management).</p>

<h4 id="Upload3"><a name="rss">Upload a Data Service</a></h4>

<p>Please refer to the <a title="Data Services Guide"
href="data_service.html"><strong>Data Services guide</strong></a> for
detailed instructions on how to host data services on WSAS.</p>

<p></p>
<a name="axis1"></a>

<h4 id="Deploy">Deploy Axis1 Services (.wsdd files)</h4>

<p>WSAS has the built-in capability to support your legacy Axis1 services,
and thus ease migrating to the power and flexiblity of Axis2 without the need
to completely change your existing code. This section describes this feature
and how to use it.</p>

<h5 id="Usage">Usage</h5>

<p>In order to use your Axis1 services, you'll first need to make sure that
all the service and data classes referenced by your WSDD file (typically
called server-config.wsdd) are available to the WSAS Axis1 deployer. In order
to do this, you must upload the appropriate jars and classes.</p>

<p>Use the resources box to provide the paths for any resource .jars that
might be needed, and the Descriptor field to provide the .wsdd file path.</p>

<p>You may also manually put the jars containing your classes into
WSO2WSAS_HOME/repository/services/axis1services/lib, and they will then be
accessible to the Axis2 engine.</p>

<p>Now you're ready to upload your WSDD file, which will actually deploy the
Axis1 services. Browse for the .wsdd file and click
<strong>Upload</strong>.</p>

<p>
	<br/><br/>
		<img alt="WSDD file" src="images/upload-wsdd1.jpg" />
	<br/><br/>
</p> <br/>

<p><strong>Figure: Uploading a .wsdd file.</strong></p>

    <br/><br/>
<p>Once your WSDD file is deployed, all the Axis1 services inside it will
automatically be usable as Axis2 services, all in a single ServiceGroup.</p>

<h5 id="Axis1">Axis1 RPC Services</h5>

<p>When you look at your Axis1 services in the admin console, you'll notice
that certain services do not look as you might expect. Axis2 does not
natively support RPC/encoded services, and many Axis1 services are deployed
this way. When you look at an RPC service in the admin console, you'll only
see a single operation called "invokeAxis1Service". Your service will
function perfectly normally, since the "invokeAxis1Service" operation is
actually a proxy "passthrough" operation which hands all incoming messages to
your Axis1 service. However, you won't be able to engage Modules on a
per-operation basis for these types of services - global and service-based
Modules will work fine.</p>

<p></p>

<p></p>

<h4 id="Service">EJB Service Provider</h4>
Please refer to the<a href="ejb_guide.html">EJB Service Provider Guide</a>
for instructions on how to expose an EJB as a web service.

<p></p>

<h3 id="Feed">RSS Feed:</h3>

<p>RSS feed gives the subscriber updates about any status changes in the
services in WSO2 WSAS. These include activation, de-activation, removal, etc.
of the services. The RSS standard used is 2.0.</p><br />

<p>
	<br/><br/>
    	<img alt="Figure:RSS Feed Page" src="images/rss.jpg" />
    <br/><br/>
</p>
<strong>Figure: RSS Feed Page</strong> <a name="atom"></a>

<h3 id="Atom">Atom Feed:</h3>

<p>Atom feed gives the subscriber updates about any status changes in the
services in WSO2 WSAS. These include activation, de-activation, removal, etc.
of the services. The Atom standard used is 2.0.</p><br />

<p>
	<br/><br/>
    	<img alt="Figure:Atom Feed Page" src="images/atom.jpg " />
    <br/><br/>
</p>

<p><strong>Figure:Atom Feed Page</strong></p>
<a name="Deleting_faulty_services"></a>

<h3 id="Deleting">Deleting Faulty Services:</h3>

<p>If a <strong>faulty service</strong> is deployed, it will be displayed on
the Available Services page as <span
style="font-style: italic; font-weight: bold;">[n] faulty
service(s)</span>:</p>

<p>Clicking on the faulty service link will open the page as shown below, on
which the details of the faulty services will be listed. By using the 'Delete
Faulty Service' icon on this page, you will be able to delete the deployed
faulty service.</p><br />

<p>
	<br/><br/>
    	<img alt="Figure: Deleting Faulty Services" src="images/delete_service.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Deleting Faulty Services</strong></p>
<a name="group_mgt"></a>

<h3 id="Service1">Service Group Management:</h3>

<p>Clicking on the Service Group on the main page of
"<a href="#services">Manage Services</a>" (as shown in Figure:Services and
Service Group Management), will open a page on which you can:</p>
<ul>
  <li><strong>Manage Service Group Parameters</strong>: Users can add, update or delete parameters from the admin console. Parameters should be given a name and a value, which consist of ASCII values. In addition to this, value can have a well formatted XML fragment. </li>
  <li><strong>Manage Module Engagements</strong>: Lists the modules engaged
    at the service group level and on a global level. You can also engage or
    disengage modules to the specific service group.</li>
  <li><strong>Create Service Archive</strong>: This feature will provide the user to create an Axis2 archive out of all the configurations available to a given service group. Thus, before shipping the service to a production environment, user can test whether all related functions such as parameters, module engagement, polices etc are available or its validity so on. Though this will give tremendous development time feature, it has its limitations. Currently this feature could archive a created or generated .AAR. WSAS distribution comes with data services, pojo services, and Axis1 services support. All these domains do not have archives. They would simply be a file with XML formatted description. Thus, if such a service is tried to archive, WSAS would not allow it. It should be noted that an archive can be created only for a service group, not to an individual service. Service group is mapped to a physical .AAR. Thus, it's logical to create an archive only to a service group instead. </li>
  <li><strong>MTOM Configuration</strong>: MTOM is allowed to configure in three ways, True, False and Optional. If one these values are changed, this will cause all underline services  and operations to change its way of corresponding to MTOM</li>
</ul>
<br />

<p>
	<br/><br/>
    	<img src="images/servicegroup_engagemodule.jpg"
         alt="Figure: Service Group Management-Engage Module " />
    <br/><br/>
</p>

<p><strong>Figure: Service Group Management-Engage Module</strong></p>
<a name="service"></a>

<h3 id="Service2">Service Management:</h3>

<p>Clicking on the service of a specific service group on the main page of
"<a href="#services">Manage Services</a>" (as shown in Figure:Services and
Service Group Management), will open a page that contains certain
<strong>service specific information</strong>, and also allows you to
<strong>manage the services</strong>.</p>

<p>
    <br/><br/>
</p>
<p>
	<br/><br/>
    	<img alt="Figure: Service Management" src="images/service_mgt.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Service Management Page</strong></p>

<p>Service <strong>information</strong> consists of:</p>
<ul>
  <li>Service name and description</li>
  <li>Service status - It will display whether the service is active or
    inactive. You also have the option of changing the service status using
    the 'Activate'/ 'Inactivate' button.</li>
  <li>Request count - The number of times the service has been called</li>
  <li>Response count -The number of SOAP message responses</li>
  <li>Fault count - The number of times a fault has been encountered</li>
  <li>Maximum Response Time</li>
  <li>Minimum Response Time</li>
  <li>Average Response Time</li>
  <li>End Point References - All the EPRs of the service will be listed here.
    The client can use any URL of its choice.</li>
</ul>

<p>The <strong>service management</strong> options that are available are as
follows:</p>
<ul>
  <li><strong>Manage Service Operations</strong> - This opens the page that
    lists the <strong>published operations</strong> of the service, with the
    options of editing operation specific parameters, and viewing engaged
    modules and Axis2 handlers.<br />
    <p>
    	<br/><br/>
        	<img alt="Figure:Published Operations Page" src="images/operation.jpg"/>
		<br/><br/>        
    </p>
    <p><strong>Figure: Published Operations Page</strong></p> <br/><br/>
    <p>Click on a specific operation link to open the page that displays the
    <strong>operations statistics</strong> and <strong>operation
    parameters</strong>.</p>
    <p>
    	<br/><br/>
        	<img alt="Figure:Figure: Operation Statistics and Parameters"
             src="images/operation_infor.jpg" />
		<br/><br/>
    </p>
    <p><strong>Figure: Operation Statistics and Parameters</strong></p><br /><br/>
    <p>Click on the '<strong>Edit operation specific parameter</strong>' icon
    of a relevant service on the 'Published Operations Page". This will open
    a page with the operation's editable (declared) parameters. You can
    add/update/delete the parameters on this page. When the operation does
    not have editable parameters, the message "No editable parameters
    present" will be displayed.</p>
    <p>To add a new parameter, click 'Add'. You will be prompted for a
    parameter name and value. To change a parameter value, change the
    parameter value in the text box and click 'Update'.</p><br />
    <p>
    	<br/><br/>
        	<img alt="Figure: Edit Operation Parameter" src="images/operation_param.jpg" />
		<br/><br/>
    </p>
    <p><strong>Figure: Edit Operation Parameter</strong></p> <br /><br />
  </li>


    <li>
        <p>
            The '<strong>View Engaged Modules</strong>' icon for each operation
            shown in "Figure: Published Operations Page" opens a page with,
        </p>
        <ul>
            <li>a list of engaged modules at operation level with the option of
                disengaging the module at operation level by using the 'Disengage'
                icon.
            </li>
            <li>a list containing modules that can be engaged. Select a module from
                the list and click 'Engage' to engage the module at operation
                level.
            </li>
            <li>a list of modules engaged at service level.</li>
            <li>a list of globally engaged modules.</li>
        </ul>
        <p>
        	<br/><br/>
            	<img alt="Figure:Figure: Figure: Engaged Operation level Modules"
                 src="images/engage_module_operation.jpg"/>
			<br/><br/>                
        </p><br/>
        <p>
            <strong>Figure: Engaged Operation Level Modules</strong><br/>
        </p>
        <br/>

    </li>

  <li><p>The "<strong>View Axis2 Handler</strong>" icon on "Figure: Published
  Operations Page" opens a page that displays the flow of the Apache Axis2
  handlers of this particular operation of the service.</p>  <br />

  <p>
  	<br/><br/>
      <img alt="Figure:Operation level module" src="images/flow.jpg" />
    <br/><br/>
  </p><br />

  <p><strong>Figure: View Axis2 Handler</strong></p> <br /><br/>
    </li>
  <li><strong>Manage Module Engagements</strong>- Here, the modules engaged
    at service level, service group level and global level are listed. You
    have the option of engaging/disengaging the modules on a service level
    from this page. Modules can be selected from a list and engaged at
    service level by clicking 'Engage'. By using the "Disengage" icon of the
    relevant module, you can easily disengage a service level module.

  <p>
  	<br/><br/>
      <img alt="Figure:Manage Service Level Module Engagements"
           src="images/service_engagemodule.jpg" />
    <br/><br/>
  </p>

  <p><strong>Figure: Manage Service Level Module Engagements</strong></p> <br/><br/>
  <a name="transport_mgt"></a>
    </li>
  <li><strong>Manage Transports</strong> - Here you can add or remove
    transport protocols.
  <p>
  	<br/><br/>
      <img alt="Figure:Service Level Transport Configuration"
           src="images/transport_mgt.jpg" />
    <br/><br/>
  </p><br />
      <p><strong>Figure: Service Level Transport Configuration</strong></p><br /><br/>
  </li>

  <li><strong>Edit Service Parameters</strong>- This link opens a page with
    editable (declared) parameters and non-editable parameters. Declared
    parameters can be edited and updated by using the 'Update' button on this
    page.
	<br/><br/>
      <img alt="Figure:Edit Service Parameters" src="images/edit_parameters.jpg"/>
	<br/><br/>


      <p><strong>Figure: Edit Service Parameters</strong></p>  <br /><br/>
  </li>


  <li><strong>Edit Service Policies</strong> - This link opens a page on
    which you can edit the policy of the Web service. You can save the
    changes made to the policy by clicking 'Update'. If there are policies
    available for the Web service, you will see the following page.

  <p>
  	<br/><br/>
      <img alt="Figure:Edit Service Policies" src="images/edit_policy.jpg"/>
    <br/><br/>
  </p><br />

  <p><strong>Figure: Edit Service Policies</strong></p><br /><br/>
    </li>
  <li><strong>Generate Client</strong> - This link opens a page where you can
    generate stubs for the service. Select the relevant values for the
    databinding parameters - Package name, Invocation style, Generate test
    cases, Unpack classes, and Databinding method. Then click 'Generate'.

  <p>
  	<br/><br/>
      <img alt="Figure:Generate Service Client" src="images/stub.jpg" />
    <br/><br/>
  </p><br />

  <p><strong>Figure: Generate Service Client</strong></p><br /><br/>
    </li>
  <li><p><strong>Try it!</strong> - This feature allows you to generate a SOAP
    1.2 XDHTML client, which has the ability to invoke the actual service.
    This will cover most of the popular spaces. It still has room for
    improvements.</p><br/>
      <p>
      	<br/><br/>
          <img alt="Figure:Try it!" src="images/tryit-main1.jpg"/>
		<br/><br/>
      </p><br/>

  <p><strong>Figure: Try Service - Operations Available</strong></p><br/><br/>
    </li>
  <li>Once the XHTML client has been generated, the user can work on a page
    as follows. It has two sections, the upper section handles the requests
    and the lower section displays the response. Once the user clicks "Try",
    the script executes. The "Table Reset" button resets the request table. <!--<p><strong>Note</strong>: If you are using Mozilla Firefox 1.5.0 or above
        Web browser, and you are using a loop back address (127.0.0.1or
        localhost), while you are connected to a network, in other words, have
        your own machine IP, then you have to point you browser to your machine
        IP (for example, https://192.168.1.250:9443) and resign-in to WSAS
        management console before trying out the above "Try its". This is because
        of Firefox security restrictions on machines connected to a network. If
        you only have a machine IP none of these restrictions are applied and you
        can "Try it" without having to resign-in.</p>-->

    <p>
    	<br/><br/>
        	<img alt="Figure:Try Service Operations" src="images/tryit-new1.jpg"/>
        <br/><br/>
    </p><br />
    <p><strong>Figure: Try Service Operations</strong></p><br /><br/>
  </li>
  <li><p><strong>Application GUI</strong> If a Web service invokes a Web based
    Application GUI, then this link will point your browser to run the Web
    based client application.</p><br/><br/>
	<br/><br/>
      <img src="images/chad_gui_link.jpg" alt="Figure:Chad GUI link"/>
	<br/><br/>
      <strong>Figure: Chad GUI link</strong>
      <br/>
      <br/>
      <p>
      	<br/><br/>
          <img alt="Figure:Application GUI" src="images/gui_app.jpg"/>
        <br/><br/>
      </p><br/>
      <strong>Figure: Application GUI</strong><br/>
  </li>
</ul>


<a name="dyn_codegen"></a>
<h2 id="DynamicCodegen">Dynamic Code Generation </h2>
<p>Dynamic code generation allows users to generate stubs for the given service if and only if the give service contains a WSDL 1.1
or WSDL 2.0. Dynamic codegen allows to generate Java based stubs using ADB, XMLBeans and OMElements. Each methods has
its own pros and cons and different configurations. ADB has chosen as the default invocation style. Thus, user has
the ability to select unwrapping option. If other invocation styles have selected, unwrapping will not be available.
In addition to this, generated code will be supplied with the source. User can choose either WSDL 1.1 or WSDL 2.0 to generate code from.  </p>

<p>
	<br/><br/>
    	<img alt="Figure:Application GUI" src="images/codegen.jpg" />
   	<br/><br/>
</p>
<p><strong>Figure: Code Generation</strong></p><br />

<a name="qos"></a>
<h2 id="Manage1">Manage Modules</h2>

<p>On this page, you can view all the modules available for engagement in the
system. It will give the name, version and description of the modules. Each
module can be removed using the "Remove module" icon and can be globally
engaged/disengaged through the "Globally engage/disengage" icon.</p>

<p>Once a module is globally engaged, it will be listed under the "Globally
Engaged Modules" list.</p>

<p>When you remove a module, that particular module will be completely
removed from the system. That is, the module handlers will be removed from
the handler chain and the module .mar file will be deleted. However, if you
disable a module, then the module will still be in the system while the
handlers from that module will be removed from the handler chain.</p>

<p>To upload a new module, use the 'Browse' button to browse for the .mar
file (module archive), and then click 'Upload'.. The uploaded module will be
added to the topmost list of the available modules with the options "Engage
globally" or 'Remove module'.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Globally Engage Modules" src="images/qos.jpg" />
	<br/><br/>
</p><br />

<p><strong>Figure: Globally Engage Modules</strong></p><br />

<p>When you click on the module name, it takes you to a page where
<strong>module configuration</strong> is possible. Module configuration is
done through <a href="#module_param_config">parameter configuration</a> and
<a href="#module_policy_config">policy configuration</a>. The page also lists
<strong>module information</strong> such as the module ID, version,
description and whether the module is globally engaged.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Module Information and Configuration"
         src="images/qos_module_info.jpg" />
	<br/><br/>         
</p><br />

<p><strong>Figure: Module Information and Configuration</strong></p><br />
<a name="module_param_config"></a>

<p>When the <strong>Configure Parameters</strong> link is clicked, the page
that opens contains editable parameters. You can add or update the parameters
using the 'Add' or 'Update' buttons.</p>

<p>
	<br/><br/>
    	<img alt="Figure: Module Parameter Configuration"
         src="images/module_configure.jpg" />
	<br/><br/>         
</p><br />
      

<p><strong>Figure: Module Parameter Configuration</strong></p><br />

<p>In case there are no editable parameters, a message will appear on the
page informing you that there are no editable parameters found. You will have
the option of adding a new parameter using the 'Add' button.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Module Parameter Configuration- No Parameters Found"
         src="images/module_configure_noparam.jpg" />
	<br/><br/>
</p>

<p><strong>Figure: Module Parameter Configuration- No Parameters
Found</strong></p><br />
<a name="module_policy_config"></a>

<p>Similarly, when the '<strong>Configure Policies</strong>' link in "Figure:
Module Information and Configuration" is clicked, the page containing the
policies will be opened (as displayed below). You can edit in the text area
itself and update any changes by clicking 'Update'. If there are no policies
for the module, then the page will read as "No module policies found."</p>

<p>
	<br/><br/>
    	<img alt="Figure:Module Policy Configuration" src="images/sandesha_policy.jpg" />
    <br/><br/>
</p><br />

<p><strong>Figure: Module Policy Configuration</strong></p><br />

<a name="sandesha2" ></a>
<h3>Sandesha2 Information</h3>
<p>If you select the Sandesha2 module and click on "Show Sandesha2 Information", you will be taken to this page.</p>
<p>
	<br/><br/>
    	<img alt="Figure:Sandesha2 Module Information" src="images/sandesha2_info.jpg" />
    <br/><br/>
</p><br />
   <p><strong>Figure: Sandesha2 Module Information</strong></p><br />
<p>If there are any incoming or outgoing sequences available for Sandesha2, details of such will be displayed here.
Details such as Sequence,internal Sequence ID,Secure,Status will be shown here if available. i.e. Sandesha2 should have been
engaged at some level (operation, service, or globally) for sequences to be visible. Otherwise, the page above will be shown.</p>

<a name="mgrusers"></a>

<h2 id="Manage2">Manage Security</h2>

<p>This page lists areas of security management. Currently it contains User
and Role management.</p>
<ol>
  <li><a href="#roles">Role Management</a> - Creates new roles and edits
    existing roles.</li>
  <li><a href="#users">User Management</a> - Creates new users, assigns roles
    to users and edits existing users.</li>
  <!--<li><a href="admin">Administrator Management</a> - Create new administrators,
    edit existing administrators who administer the WSO2 WSAS Management
    Console.</li>-->
</ol>

<p>
	<br/><br/>
    	<img alt="Figure:Security Management Main Page" src="images/users.jpg"/>
    <br/><br/>
</p><br />

<p><strong>Figure: Security Management Main Page</strong></p><br />
<a name="roles"></a>

<h3 id="Role">Role Management:</h3>

<p>Clicking on the Role Management link will open a page that consists of a
list of existing role names, with the option of adding new role names. This
is done by entering a new role name and clicking 'Add' . If a role was added
successfully, a message (alert) will appear.</p>

<p>You can also delete a role by using the "Delete Role" icon.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Role Management" src="images/role_mgt.jpg" />
    <br/><br/>
</p><br />

<p><strong>Figure: Role Management</strong></p><br />
<a name="users"></a>

<h3 id="User">User Management:</h3>

<p>The User Management link opens a page with a <a href="#present_users">list
of present users</a> with the option of adding new users to this list. In
order to add a new user, the Username, Password and Confirm password (same as
password) fields need to be filled. Select a user role from the list, and
then click 'Add' . If the user was added successfully, a message (alert) will
appear informing you that the user has been added successfully.</p>

<p>Note that the User Role list contains all the role names listed on the <a
href="#roles">Role Management page</a> from which new roles can be added as
well.</p>

<p>
	<br/><br/>
    	<img alt="Figure:User Management" src="images/user_mgt.jpg" />
   	<br/><br/>
</p> <br />

<p><strong>Figure: User Management</strong></p><br />
<a name="present_users"></a>

<p>The <strong>present users list</strong> comes with the "User Name", "User
Description, "User Actions", "User Role" and "User Role Actions" columns.
User Actions contain "Edit" and "Delete User" icons.</p>

<p>Clicking the "Edit" icon opens a page on which you can edit the
corresponding user details - change the role name of the user and reset the
password. Once a new user role is selected from the list, click 'Update Role'
to update the changes. If the role has been successfully changed, a message
will appear confirming the change. To reset the password, the new password
and the confirmation of the new password (same as the new password) should be
correctly entered. Then click 'Reset Password'. If the password was reset
successfully, a message will appear.</p>

<p>
	<br/><br/>
    	<img alt="Figure:User Management-Edit User" src="images/edit_user.jpg"/><br />
    <br/><br/>
</p>

<p><strong>Figure: User Management- Edit User</strong></p><br />
<!--<p>Note : Users with the role "admin" is the same as Administrator users of
the system</p>

<h4>Administrator Management</h4>

<p>Administrator Management link will take you to page with a <a
href="#admin">list of administrator (admin) users</a> with the option of
adding in new administrator users to this list. In order to add new user,
user name, password &amp; confirm password (same as password) need to be be
typed, then clicked on 'Add' button. If administrator was added successfully
an alter message will pop up saying so, and administrator will be added to
the Administrators list above list.</p>

<p>Administrator users list will have an Edit link for each user from which
administrator's password can be reset. Click on Edit and it will take you to
page where new password and confirm password (same as new password) has to be
typed in and clicked on 'Reset Password' button to reset password. If
password is reset successfully, then an alert message will pop up saying
so.</p>-->
Click the "Delete user" icon to delete the corresponding user. The "Delete
Role" icon in the "User Role Actions" column can be used to delete the user
role. <a name="manage_transports"></a>

<h2 id="Manage3">Manage Transports</h2>

<p>This page lists the available HTTPS and HTTP transports, their names and
values.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Transport Management" src="images/manage_transports.jpg"/>
    <br/><br/>
</p>

<p><strong>Figure: Transport Management</strong></p><br />
<a name="manage_keystores"></a>

<h2 id="Manage4">Manage KeyStores</h2>

<p>This page allows Keystore management. It lists the available keystores',
name, type and the actions "<a href="#import_certificate">Importing
Certificates</a>" and "Delete Keystore", which removes the keystore.</p>

<p>The page also contains instructions to add a keystore. This is a three
step process:</p>
<ol>
  <li>Upload the keystore file.</li>
  <li>Enter the password for the Private Key 'client'</li>
  <li>Keystore upload complete. Exit Keystore wizard.</li>
</ol>

<p>
	<br/><br/>
    	<img alt="Figure:KeyStore Management" src="images/keystores.jpg" />
    <br/><br/>
</p>
    <p><strong>Figure:Keystore Management</strong></p><br /><br/>

    <p>User can also observe the keystore by clicking on the name of the keystore.</p>
    <p>
    	<br/><br/>
    		<img alt="Figure:Observe keystore" src="images/keystore_view.jpg"/>
    	<br/><br/>
    </p>
    <p><strong>Figure:Keystore Viewer</strong></p><br />

<a name="import_certificate"></a>

<p>Click the "<strong>Import Certificate</strong>" icon to open the page
displayed below. Here you have the option of importing a certificate by using
"Browse" and "Upload". The previously imported certificates will also be
listed here.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Import Certificate for Key Store"
         src="images/import_certificate.jpg" />
    <br/><br/>
</p>

<p><strong>Figure:Import Certificate for Keystore</strong></p><br />
<a name="config"></a>

<h2 id="Manage5">Manage Logging</h2>

<p>This page contains server settings for logging. Logging settings include
<a href="http://logging.apache.org/log4j/docs/index.html">Log4J</a> <a
href="#loggers">Loggers</a> and <a
href="http://logging.apache.org/log4j/docs/index.html">Log4J</a> <a
href="#appenders">Appenders</a>. Loggers filter the log messages to
Appenders, while Appenders filter the messages for the second time before
writing them to the log files.</p>
<a name="loggers"></a>

<h3 id="Configure">Configure Log4J Loggers:</h3>

<p>Log4J Loggers contain the value's Name, Log Level and Additivity.
The<strong>Log level</strong> list contains TRACE, INFO, DEBUG, WARN, ERROR,
FATAL and OFF from which any one can be selected. Once you select a Log
Level, only the messages at that level and below will be logged. For example,
if you select Log Level ERROR, then all ERROR and FATAL messages will be
logged or rather passed on to the Appender. Switching on
<strong>Additivity</strong> allows to inherit all the Appenders of the parent
Logger.</p>
<a name="appenders"></a>

<h3 id="Configure1">Configure Log4J Appenders:</h3>

<p>Log4J Appenders include values for the Appender Name, Log level, known as
Threshold in this case, Log Pattern and Log File.</p>

<p>The <strong>Threshold</strong> list is the same as the Log Level in
Loggers, in name and action. The <strong>Log Pattern</strong> allows you to
edit the format or the layout in which the logs are created. You can have a
look at the <a
href="http://logging.apache.org/log4j/docs/api/org/apache/log4j/PatternLayout.html">log4j
PatternLayout</a> page to learn the meanings of the values that are used in
the log pattern. Finally you can change the location of the log file with the
<strong>Log File</strong> option.</p>
<a name="global"></a>

<h3>Persist Configuration Changes:</h3>

<p>Check this if you want any changes you make to the logging configuration to persist
even after a server restart. If not checked, logging will be configured with the default settings.</p>

<h3>Global Log4J Configuration:</h3>

<p>Note that by using the Global Log4J Configuration options, you can set the
Log Level and Log Pattern of Log4J Appenders and Loggers to the same value at
the same time.</p>

<p>Values for the above three settings can be edited/changed and updated by
using the Update button.</p>
    <p>
    	<br/><br/>
    		<img alt="Figure:Logging Management" src="images/configuration.jpg" />
    	<br/><br/>
</p>

<p><strong>Figure: Logging Management</strong></p><br />

<h3 id="RestoreDefault">Restore Default</h3>

<p>If user wants to restore to the default log4j properties, user can achive this using "Restore Defaults" option. To make this effective, once restore defaults has been done, user has to restart the system.</p>

    <h3 id="FilteringLoggers">Filter Loggers</h3>
    <p>Log4j configuration will show all available loggers. User can filter loggers based on "Start with" and "Contains."</p>
    <p>
    	<br/><br/>
        	<img src="images/log_config.jpg" alt="Figure:Filter Loggers"/>
        <br/><br/>
    </p>
    <p><strong>Figure:Filter Loggers</strong></p><br/>


<a name="restart"></a>

<h2 id="Restart">Restart Server</h2>

<p>
	<br/><br/>
    	<img alt="Figure:Restart Server" src="images/restart.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Restart Server</strong></p><br/>
<a name="Monitor_system"></a>

<h2 id="Monitor">Monitor System</h2>

<p>
	<br/><br/>
    	<img alt="Figure: Monitor System" src="images/monitor_system.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Monitor System</strong></p><br/>

<p><a name="Monitor_Statistics"></a></p>

<h2 id="Monitor1">Monitor Statistics</h2>
This page shows some statistics related to the WSO2 WSAS instance. These
include Free memory, Request count, Server name, Server start time, System up
time, Active services, Total memory, Average response time, Minimum response
time and the Maximum response time.

<p>
	<br/><br/>
    	<img alt="Figure: Monitor Statistics" src="images/monitor_statistics.jpg"/>
    <br/><br/>
</p>

<p><strong>Figure: Monitor Statistics</strong></p><br/>
<a name="logs"></a>

<h2 id="Monitor2">Monitor Logs</h2>

<p>The system log can be viewed on this page. Log entries will be categorized
into information messages, warning messages, error messages, fatal error
messages and debug messages.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Monitor Logs" src="images/log.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Monitor Logs</strong></p> <br/>
<a name="Monitor_Tracer"></a>

<h2 id="Monitor3">Monitor Tracer</h2>

<p>This tracer shows the SOAP messages, their respective SOAP message
requests and responses when the services are deployed on the server, and the
invoked operations. Make sure that the messages are monitored by turning the
SOAP Tracer on. By default, it is switched off. You can switch it on by
selecting ON in the list.</p>

<p><strong>Warning</strong>:Turning this on will have a performance hit,
since all SOAP messages will be always completely built (i.e., deferred
building will not be done) and stored in the database by WSO2 WSAS. Hence
this option should be used with caution.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Turn ON SOAP Tracer" src="images/tracer_off.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Turn ON SOAP Tracer</strong></p> <br/>

<p>The tracer will only show the messages of the operations that were invoked
after switching on the SOAP tracing.</p>

<p>By using this SOAP tracer, it is possible to see the SOAP messages with
their time-stamps, service name, operation invoked and the number of requests
to the server. The most recent SOAP messages are listed on the top. When a
particular SOAP message is selected, its Request and the Response can be
viewed in collapsible/expandable text boxes.</p>

<p>Note: This tracer does not apply to operations invoked in the admin
services, as they are filtered out.</p>

<p>
	<br/><br/>
    	<img alt="Soap Tracer- Request/Response Messages" src="images/soap_tracer.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: SOAP Tracer- Request/Response Messages</strong></p> <br/>
<a name="Monitor_flows"></a>

<h2 id="Monitor4">Monitor Flows</h2>

<p>
	<br/><br/>
    	<img alt="Monitor Flows- Graphical View" src="images/monitor_flow.jpg"/>
    <br/><br/>
</p>

<p><strong>Figure: Monitor Flows- Graphical View</strong></p>  <br/>

<p>Click the "Text View" link on the top right hand corner of the page to
view the textual representation of the In flow, Out flow, In-Out flow, and
Out-Fault flow SOAP messages. By using the "Graphical View" link, you can go
back to the "Monitor Flows- Graphical View".</p>

<p>
	<br/><br/>
    	<img alt="Monitor Flows- Textual View" src="images/monitor_flow_text.jpg"/>
    <br/><br/>
</p>

<p><strong>Figure: Monitor Flows- Textual View</strong></p> <br/>
<a name="misc"></a>

<h2 id="Miscellane">Miscellaneous</h2>
<a name="signout"></a>

<h3 id="Signing1">Signing Out</h3>

<p>Once signed in, to sign out from the system, click on the Sign Out link at
the upper right-hand of any page.</p>
<a name="register"></a>

<h3 id="Register">Register</h3>

<p>You can register your WSO2 WSAS instance by clicking on this link. By
registering, you will be providing the developers with valuable information
to make WSO2 WSAS a better product. Only information that is shown to you on
the Register Product page will be submitted to the server, and you can change
the information that is extracted from your WSO2 WSAS instance before you
submit them to the server if you wish to do so.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Registration Page" src="images/register.jpg" />
    <br/><br/>
</p>

<p><strong>Figure: Registration Page</strong></p> <br/>
<a name="browser_settings"></a>

<h2 id="Browser">Web Browser Specific Settings</h2>

<p>This section will give you configuration information that is specific to
the Web browser you use to point to the WSO2 WSAS AJAX Management Console.</p>

<h3 id="Internet">Internet Explorer 6 :</h3>

<p>AJAX engines make use of an XMLHttpRequst object to exchange data
asynchronously with remote servers. In Internet Explorer 6, this object is
implemented with ActiveX rather than native JavaScript, which requires that
ActiveX be enabled to run the WSO2 WSAS Management Console.</p>

<p>Once you have configured your Web browser as above, see the <a
href="#signing">Signing In</a> section on how to access the Management
Console.</p>

<h3 id="service_sec">Manage Service Security Configuration</h3>

<p>A service can be secured using any of 12 available security scenarios.
These configurations are available from in the "Manage Security Configuration"
option in "Service Management".
</p>

<p>
	<br/><br/>
    	<img alt="Figure:Service Security Configuration" src="images/security_scenarios.png" />
    <br/><br/>
</p>

There are three main categories of security scenarios available
<ul>
<li>Basic message level security : WS-Security
	<i>Scenario 1 to 8</i>
    </li>
<li>Secure Session : WS-SecureConversation
	<i>Scenario 9 and 10</i></li>
<li>Security based on a token issued by a SecurityTokenService : WS-Trust
	<i>Scenario 11 and 12</i></li>
</ul>

<p>Timestamp properties (time to live and maximum time skew values) of Apache
Rampart policy can be adjusted using the service policy editor after configuring
 the service.</p>

<p>
	<br/><br/>
    	<img alt="Figure:Service Security Configuration" src="images/edit_service_policy.png" />
    <br/><br/>
</p>
    <p><strong>Figure:Service Security Configuration</strong></p><br />


<h3 id="sts_config">Security Token Service Configuration</h3>
<p>
A WS-Trust Security Token Service (wso2wsas-sts) is included in the standard set
of services of WSO2 WSAS. If a service is secured with either Scenario 11 or
Scenario 12 mentioned in the "<a href="#service_sec">Service Security
Configuration</a>" the client can obtain a token from wso2wsas-sts and use that
token in the request to the secured service.
</p>
<p>
Service Management page of wso2wsas-sts has an additional option to configure
the STS.
</p>

<p>
	<br/><br/>
    	<img alt="Figure:Service Security Configuration" src="images/sts_conf.png" />
    <br/><br/>
</p>
    <p><strong>Figure:Service Security Configuration</strong></p> <br/>
This basically allows the admin to add trusted service endpoint addresses to the
STS. The STS will only issue tokens to those trusted services. One must specify
the alias of the cert of the trusted service along with the service endpoint
address. The service certificate must be available in the wsas main keystore
(wso2wsas.jks) and the aliases of the available certificates are provided for
selection.

<br/>
<h3></h3>
</body>
</html>
