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

[bu...@apache.org]

Author: buildbot
Date: Fri Feb 17 18:13:09 2012
New Revision: 805200

Log:
Staging update by buildbot for airavata

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

Propchange: websites/staging/airavata/trunk/
------------------------------------------------------------------------------
    cms:source-revision = 1245689

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 Feb 17 18:13:09 2012
@@ -101,51 +101,39 @@ In order to deploy Airavata system on To
 We have tested Airavat with Apache Axis2 1.5.1 Release, so you can use the same release and first deploy Axis2 1.5.1 war in to tomcat.
 To deploy a Message Broker on Tomcat.</p>
 <ol>
-<li>Copy AIRAVATA_HOME/standalone-server/repository/services/messagebroker-0.0.1-SNAPSHOT.aar to webapps/axis2/WEB-INF/services directory.</li>
+<li>Copy AIRAVATA_HOME/standalone-server/repository/services/messagebroker-0.0.1-SNAPSHOT.jar to webapps/axis2/WEB-INF/services directory.</li>
 <li>Create a configuration file in webapps/axis2/WEB-INF/conf/msgBroker.properties. A sample configuration can be looked up in AIRAVATA_HOME/standalone-server/conf/msgBroker.properties. </li>
 <li>Download and copy a database library (Apache Derby or MySql) to webapps/axis2/WEB-INF/lib directory.</li>
 <li>Copy directory AIRAVATA_HOME/standalone-server/bin/database_scripts to webapps/axis2/WEB-INF/lib directory.</li>
 </ol>
 <p>To deploy a Message Box on Tomcat.</p>
 <ol>
-<li>Copy AIRAVATA_HOME/standalone-server/repository/services/messagebox-0.0.1-SNAPSHOT.aar to webapps/axis2/WEB-INF/services directory.</li>
+<li>Copy AIRAVATA_HOME/standalone-server/repository/services/messagebox-0.0.1-SNAPSHOT.jar to webapps/axis2/WEB-INF/services directory.</li>
 <li>Create a configuration file in webapps/axis2/WEB-INF/conf/msgBox.properties. A sample configuration can be looked up in AIRAVATA_HOME/standalone-server/conf/msgBox.properties. </li>
 <li>Download and copy a database library (Apache Derby or MySql) to webapps/axis2/WEB-INF/lib directory </li>
 <li>
 <p>Copy directory AIRAVATA_HOME/standalone-server/bin/database_scripts to webapps/axis2/WEB-INF/lib directory.</p>
 </li>
 <li>
-<p>Copy gfac-schema-utils-<version>.jar from AIRAVATA_HOME/standalone-server/lib director to webapps/axis2/WEB-INF/lib directory.</p>
+<p>Copy all the jars from AIRAVATA_HOME/standalone-server/lib director to webapps/axis2/WEB-INF/lib directory.
+   (You have to copy all the jars if you deploy all the services of airavata in to one tomcat otherwise you only need to copy service specific dependent jars. We hope to document that soon) 
+Note: If you have already deployed MessageBroker in the same tomcat you can skip the step 3 and 4.</p>
 </li>
 </ol>
-<p>Note: If you have already deployed MessageBroker in the same tomcat you can skip the step 3 and 4.</p>
 <p>To deploy a GFac Axis2 Service on Tomcat.</p>
 <ol>
 <li>
-<p>Copy AIRAVATA_HOME/standalone-server/repository/services/gfac-axis2-interface-<version>.aar to webapps/axis2/WEB-INF/services directory.</p>
+<p>Copy AIRAVATA_HOME/standalone-server/repository/services/gfac-axis2-interface-<version>.jar to webapps/axis2/WEB-INF/services directory.</p>
 </li>
 <li>
 <p>Create a configuration file in webapps/axis2/WEB-INF/lib/repository.properties. A sample configuration can be looked up in AIRAVATA_HOME/standalone-server/conf/repository.properties. Based on your setup configure the GSI security credentials and certificate paths in the properties file.</p>
 </li>
 </ol>
 <p>Note: keep the same properties file in TOMCAT_HOME/bin directory too.. This issue will be fixed in later release.</p>
-<ol>
-<li>
-<p>Copy the following Jar files to webapps/axis2/WEB-INF/lib folder.</p>
-<p>3.1 All the jackrabbit jars<br>
-3.2 jcr-2.0.jar<br>
-3.3 commons-configuration-1.6.jar<br>
-3.4 commons-lang-2.4.jar<br>
-3.5 commons-collection-3.2.1.jar<br>
-3.6 xpp3-1.1.3_7.jar<br>
-3.7 slf4j-api-1.6.1.jar
-3.8 slf4j-simple-1.6.1.jar</p>
-</li>
-</ol>
 <p>To deploy Interpretor Service on Tomcat</p>
 <ol>
 <li>
-<p>Copy AIRAVATA_HOME/standalone-server/repository/services/xbaya-gui-<version>.aar to webapps/axis2/WEB-INF/services directory.</p>
+<p>Copy AIRAVATA_HOME/standalone-server/repository/services/xbaya-gui-<version>.jar to webapps/axis2/WEB-INF/services directory.</p>
 </li>
 <li>
 <p>Create configuration file in webapps/axis2/WEB-INF/lib/xbaya.properties and fill up the following property names values based on your gsi security credentials.
@@ -154,7 +142,6 @@ To deploy a Message Broker on Tomcat.</p
 (This step will be required from 0.3 release if you are using previous release users do not have to create xbaya.properties file)</p>
 </li>
 </ol>
-<p>(Optional) To customize the logging level, download and copy needed slf4j library to webapps/axis2/WEB-INF/lib. Please refer to this <a href="http://www.slf4j.org/manual.html#binding">instruction</a>.</p>
 <h3 id="how_do_i_use_only_ws-messenger_component">How do I use only WS-Messenger component</h3>
 <p>Currently first release of Airavata doesn't have a separate pack for WS-Messenger. But users can check out the source of Airavata and build only WS-Messenger and build will
 create a pack which contains only WS-Messenger components and it can be used as the WS-Messenger binary distribution.