Return-Path:
X-Original-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org
Delivered-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id DF78CD2DD
for ;
Fri, 6 Jul 2012 13:39:30 +0000 (UTC)
Received: (qmail 83922 invoked by uid 500); 6 Jul 2012 13:39:30 -0000
Delivered-To: apmail-incubator-airavata-commits-archive@incubator.apache.org
Received: (qmail 83878 invoked by uid 500); 6 Jul 2012 13:39:30 -0000
Mailing-List: contact airavata-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: airavata-dev@incubator.apache.org
Delivered-To: mailing list airavata-commits@incubator.apache.org
Received: (qmail 83868 invoked by uid 99); 6 Jul 2012 13:39:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2012 13:39:30 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2012 13:39:27 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
by eris.apache.org (Postfix) with ESMTP id 34E64238890D
for ;
Fri, 6 Jul 2012 13:39:07 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r824793 - in /websites/staging/airavata/trunk/content: ./
airavata/documentation/howto/howto.html
Date: Fri, 06 Jul 2012 13:39:07 -0000
To: airavata-commits@incubator.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120706133907.34E64238890D@eris.apache.org>
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
How can I run WS-Messenger without using any database.
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
+ 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
How to use XBaya Arguments
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]
+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]
+
How XBaya is going to pick Available GFac URLs
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