svn commit: r824799 - in /websites/staging/airavata/trunk/content: ./ airavata/documentation/howto/howto.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jul  6 13:46:36 2012
New Revision: 824799

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul  6 13:46:36 2012
@@ -1 +1 @@
-1358208
+1358210

Modified: websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html Fri Jul  6 13:46:36 2012
@@ -109,11 +109,23 @@
     <h3 id="how-to-start-airavata-system-and-what-is-the-order-to-start-each-component">How to start Airavata System and what is the order to start each component.</h3>
 <p>To start Airavata system users have to use the scripts provided in AIRAVATA_HOME/bin/ and if you are running all the components 
 with default setup you have to start the components in the following order.</p>
-<p>jackrabbit-server.sh - This is the Jackrabbit server startup script, before starting any other component, you have to start the registry instance first
-                       because all the components are communicating with Registry.</p>
-<p>airavata-server.sh - This starts the WS-Messenger components and GFac service in Apache Axis2 Container. This is pointing to the Registry started in previous step
-             and use the Registry URL is localhost:8081, if you are starting in a different URL, you have to change AIRAVATA_HOME/standalone-server/conf/repository.properties file.</p>
-<p>xbaya-gui.sh       - Now you have available GFac Service running with a Registry, so its time for you to start XBaya and run your Applications. But if you want XBaya to run with normal Web services, not with GFac Service you do not have to start Airvata Service, you can simply use Xbaya alone, if you require provenance, you have to start Registry. </p>
+<ol>
+<li>
+<p>jackrabbit-server.sh - This is the Jackrabbit server startup script, before starting any other component, you have to start the
+                          registry instance first because all the components are communicating with Registry.</p>
+</li>
+<li>
+<p>airavata-server.sh   - This starts the WS-Messenger components and GFac service in Apache Axis2 Container. This is pointing to the
+                          Registry started in previous step and use the Registry URL is localhost:8081, if you are starting in a
+                          different URL, you have to change AIRAVATA_HOME/standalone-server/conf/repository.properties file.</p>
+</li>
+<li>
+<p>xbaya-gui.sh         - Now you have available GFac Service running with a Registry, so its time for you to start XBaya and run
+                          your Applications. But if you want XBaya to run with normal Web services, not with GFac Service you do not
+                          have to start Airvata Service, you can simply use Xbaya alone, if you require provenance, you have to start
+                          Registry.</p>
+</li>
+</ol>
 <h3 id="how-to-deploy-airavata-on-tomcat">How to Deploy Airavata on Tomcat</h3>
 <p>Airavata services depends on Apache Axis2 as a Web Service engine. Each service component in Airavata can be packed as Axis2 Archive (.aar).
 In order to deploy Airavata system on Tomcat, you need to install Apache Axis2 on Tomcat first. This will be handled by the setup script.