airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r824793 - in /websites/staging/airavata/trunk/content: ./ airavata/documentation/howto/howto.html
Date Fri, 06 Jul 2012 13:39:07 GMT
Author: buildbot
Date: Fri Jul  6 13:39:06 2012
New Revision: 824793

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:39:06 2012
@@ -1 +1 @@
-1358199
+1358202

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:39:06 2012
@@ -188,25 +188,27 @@ database and AIRAVATA_HOME/standalone-se
 <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.
-    * 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>
+<em> For Message Box - AIRAVATA_HOME/standalone-server/conf/msgBox.properties - msgBox.usedatabase=true
+</em> 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.
-    * -help
-    * -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".
-    * -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]
-    * -enableProvenance         - This is a parameter to let XBaya to store inputs and outputs
in to Registry. [true/false]</p>
+During XBaya startup you can give number of arguments for quick detail you can run xbaya-gui.sh
with -help.</p>
+<ul>
+<li>-help</li>
+<li>-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.</li>
+<li>-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".</li>
+<li>-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]</li>
+<li>-enableProvenance         - This is a parameter to let XBaya to store inputs and
outputs in to Registry. [true/false]</li>
+</ul>
 <h3 id="how-xbaya-is-going-to-pick-available-gfac-urls">How XBaya is going to pick
Available GFac URLs</h3>
 <p>When you start the Registry at very first and then GFac service, GFac service is
registering its URL with Registry, GFac does that frequently, so if you 
 have n number of GFac nodes running everyone is registering its URL. Since Every GFac node
is registering in a given time interval, if one node goes down



Mime
View raw message