airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r798085 - /websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html
Date Fri, 04 Nov 2011 20:42:37 GMT
Author: buildbot
Date: Fri Nov  4 20:42:37 2011
New Revision: 798085

Log:
Staging update by buildbot

Modified:
    websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html

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 Nov
 4 20:42:37 2011
@@ -97,18 +97,24 @@ with default setup you have to start the
 <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. Please refer to this <a href="http://axis.apache.org/axis2/java/core/docs/installationguide.html#servlet_container">guide</a>
for installation guide.</p>
-<p>To deploy a Message Broker on Tomcat.
-1. Copy AIRAVATA_HOME/standalone-server/repository/services/messagebroker-0.0.1-SNAPSHOT.aar
to webapps/axis2/WEB-INF/services directory.
-2. 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.

-3. Download and copy a database library (Apache Derby or MySql) to webapps/axis2/WEB-INF/lib
directory.</p>
-<p>To deploy a Message Box on Tomcat.
-1. Copy AIRAVATA_HOME/standalone-server/repository/services/messagebox-0.0.1-SNAPSHOT.aar
to webapps/axis2/WEB-INF/services directory.
-2. 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.

-3. Download and copy a database library (Apache Derby or MySql) to webapps/axis2/WEB-INF/lib
directory.</p>
-<p>To deploy a GFac Axis2 Service on Tomcat.
-1. Copy AIRAVATA_HOME/standalone-server/repository/services/gfac-axis2-interface-0.0.1-SNAPSHOT.aar
to webapps/axis2/WEB-INF/services directory.
-2. Create a configuration file in webapps/axis2/WEB-INF/conf/repository.properties. A sample
configuration can be looked up in AIRAVATA_TRUNK/standalone-server/conf/repository.properties.
 <br />
-</p>
+<p>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>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>
+</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>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>
+</ol>
+<p>To deploy a GFac Axis2 Service on Tomcat.</p>
+<ol>
+<li>Copy AIRAVATA_HOME/standalone-server/repository/services/gfac-axis2-interface-0.0.1-SNAPSHOT.aar
to webapps/axis2/WEB-INF/services directory.</li>
+<li>Create a configuration file in webapps/axis2/WEB-INF/conf/repository.properties.
A sample configuration can be looked up in AIRAVATA_TRUNK/standalone-server/conf/repository.properties.
 <br />
+</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
@@ -117,18 +123,20 @@ In Airavata code go to AIRAVATA_CODE/mod
 AIRAVATA_CODE/moduels/ws-messenger/distribution/target/.</p>
 <h3 id="how_to_deploy_ws-messenger_with_mysql">How to Deploy WS-Messenger with Mysql</h3>
 <p>Currently WS-Messenger supports Derby and Mysql databases. Users have to change
AIRAVATA_HOME/standalone-server/conf/msgBox.properties to change the message Box
-database and AIRAVATA_HOME/standalone-server/conf/msgBroker.properties to change the message
Broker database. 
-1. First create a mysql database in your server with required name (Assume name is:wsmg and
username/password is : airavata/airavata).
-2. Create a tables in the above database using the following scripts.
-AIRAVATA_HOME/standalone-server/bin/database_scripts/mgsBox-mysql.sql and
-AIRAVATA_HOME/standalone-server/bin/database_scripts/msgBroker-mysql.sql</p>
+database and AIRAVATA_HOME/standalone-server/conf/msgBroker.properties to change the message
Broker database. </p>
+<ol>
+<li>First create a mysql database in your server with required name (Assume name is:wsmg
and username/password is : airavata/airavata).</li>
+<li>Create a tables in the above database using the following scripts.</li>
+</ol>
+<p>AIRAVATA_HOME/standalone-server/bin/database_scripts/mgsBox-mysql.sql</p>
+<p>AIRAVATA_HOME/standalone-server/bin/database_scripts/msgBroker-mysql.sql</p>
 <ol>
 <li>Change msgBox.properties and msgBroker.properties files with database driver name
and database urls as below.</li>
 </ol>
-<p>msgBox.jdbc.driver=com.mysql.jdbc.Driver
-   msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
-<p>broker.jdbc.driver=com.mysql.jdbc.Driver
-   broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
+<p>msgBox.jdbc.driver=com.mysql.jdbc.Driver</p>
+<p>msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
+<p>broker.jdbc.driver=com.mysql.jdbc.Driver</p>
+<p>broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
 <ol>
 <li>Change the driver class name based on your driver and copy your driver to AIRAVATA_HOME/standalon-server/lib
directory and start the server.. You are ready to go with 
    Mysql database.</li>
@@ -136,18 +144,17 @@ AIRAVATA_HOME/standalone-server/bin/data
 <h3 id="how_can_i_run_ws-messenger_without_using_any_database">How can I run WS-Messenger
without using any database.</h3>
 <p>Yes, WS-Messenger supports in-memory messaging. If you want to change message broker
or message box to be in memory you simply have to change the appropriate property in
 msgBroker.properties and msgBox.properties as below.</p>
-<p>For Message Box - AIRAVATA_HOME/standalone-server/conf/msgBox.properties - msgBox.usedatabase=true
-For Message Broker - AIRAVATA_HOME/standalone-server/conf/msgBroker.properties - broker.storage.type=memory</p>
+<p>For Message Box - AIRAVATA_HOME/standalone-server/conf/msgBox.properties - msgBox.usedatabase=true</p>
+<p>For Message Broker - AIRAVATA_HOME/standalone-server/conf/msgBroker.properties -
broker.storage.type=memory</p>
 <h3 id="how_to_use_xbaya_arguments">How to use XBaya Arguments</h3>
 <p>XBaya can be started using AIRAVATA_HOME/bin/xbaya-gui.sh in the binary distribution.
 During XBaya startup you can give number of arguments for quick detail you can run xbaya-gui.sh
with -help.</p>
-<p>-help
-   -config - Users can put their configuration in to a properties file and give that file
path as the argument value.
+<p>-help</p>
+<p>-config - Users can put their configuration in to a properties file and give that
file path as the argument value.
              In the properties file users can use following property names.
-             gpel-engine-url,gfac-url,msg-box-url,msg-broker-url,dsc-url.
-   -title - Title that you want to show in the XBaya GUI, if you set title as "My Workflow"
You will see a title at the
-            Top of the window as "Workflow - My Workflow".  <br />
-</p>
+             gpel-engine-url,gfac-url,msg-box-url,msg-broker-url,dsc-url.</p>
+<p>-title - Title that you want to show in the XBaya GUI, if you set title as "My Workflow"
You will see a title at the
+            Top of the window as "Workflow - My Workflow".</p>
 <p>-enableProvenanceSmartRun - This parameter can be used to enable smart rerun feature,
which will keep track of inputs and outputs, if user provide the same inputs to the same service
which was ran previously, Xbaya will not invoke the service again, it will simply use the
output of the previous invocation. 
     [true/false] </p>
 <p>-enableProvenance         - This is a parameter to let XBaya to store inputs and
outputs in to Registry. 



Mime
View raw message