Author: buildbot
Date: Thu May 26 23:11:10 2016
New Revision: 989245

Log:
Staging update by buildbot for taverna

Modified:
    websites/staging/taverna/trunk/cgi-bin/   (props changed)
    websites/staging/taverna/trunk/content/   (props changed)
    websites/staging/taverna/trunk/content/documentation/command-line/index.html

Propchange: websites/staging/taverna/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 23:11:10 2016
@@ -1 +1 @@
-1745675
+1745676

Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 23:11:10 2016
@@ -1 +1 @@
-1745675
+1745676

Modified: 
websites/staging/taverna/trunk/content/documentation/command-line/index.html
==============================================================================
--- 
websites/staging/taverna/trunk/content/documentation/command-line/index.html 
(original)
+++ 
websites/staging/taverna/trunk/content/documentation/command-line/index.html 
Thu May 26 23:11:10 2016
@@ -199,6 +199,7 @@ that is bundled with the Taverna Workben
 <ul>
 <li><a 
href="http://dev.mygrid.org.uk/wiki/display/tav250/Extended+version";>Extended 
version</a></li>
 </ul>
+<hr />
 <h2 
id="what-are-the-differences-between-the-bundled-and-standalone-versions"><img 
alt="" src="/img/information.png" />What are the differences between the 
bundled and standalone versions?<a class="headerlink" 
href="#what-are-the-differences-between-the-bundled-and-standalone-versions" 
title="Permanent link">&para;</a></h2>
 <p>This section describes some of the differences between the bundled and 
standalone versions of 
 *executeworkflow * Other important information is provided in the following 
section. </p>
@@ -224,6 +225,7 @@ to show up in the workbench as
 already running, the command-line tool  must use the <em>-clientserver</em> 
option.
 Alternatively, if the workbench is shut down, the command-line tool must use
 either a standalone <em>-startdb</em> database server process or the 
<em>-embedded</em> option.</p>
+<hr />
 <h2 id="other-important-information"><img alt="" src="/img/information.png" 
/>Other important information<a class="headerlink" 
href="#other-important-information" title="Permanent link">&para;</a></h2>
 <p>This section provides additional information on configuring proxy settings, 
 installing service plugins, disk space considerations and potential 
conflicts.</p>
@@ -251,6 +253,7 @@ it could be in conflict with parallel ru
 In this case, a separate <em>-startdb</em> process should be started with the
 other calls using the <em>-clientserver</em> option. See
 <a href="#CommandLineTool-Runningthescriptwithdatabase">#Running the script 
with a database</a></p>
+<hr />
 <p><a name="CommandLineTool-ExecuteworkflowScript"></a></p>
 <h2 id="executeworkflow-script">Executeworkflow Script<a class="headerlink" 
href="#executeworkflow-script" title="Permanent link">&para;</a></h2>
 <p>To get help and a full set of options for the executeworkflow script,
@@ -396,6 +399,7 @@ from a Baclava file. However, if you pro
 what is required, it will automatically be wrapped in one or more
 list levels up to the required depth.
 Providing an input of greater depth than that required will result in an 
error.</p>
+<hr />
 <p><a name="CommandLineTool-Runningthescriptwithdatabase"></a></p>
 <h2 id="running-the-script-with-a-database">Running the script with a 
database<a class="headerlink" href="#running-the-script-with-a-database" 
title="Permanent link">&para;</a></h2>
 <p>Storing data in memory is the default option. If a workflow has a high 
memory
@@ -472,6 +476,7 @@ port for MySQL server, which is 3306.</p
 <p><img alt="" src="/img/warning.png" /> When using <em>-dbproperties</em> 
together with other
 options, the other options take precedence.</p>
 </blockquote>
+<hr />
 <p><a name=CommandLineTool-Examples"></a></p>
 <h2 id="examples">Examples<a class="headerlink" href="#examples" 
title="Permanent link">&para;</a></h2>
 <p>Workflows names are listed at the end of the command, after any options.


Reply via email to