Author: buildbot
Date: Thu May 26 23:30:16 2016
New Revision: 989250
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:30:16 2016
@@ -1 +1 @@
-1745680
+1745681
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 23:30:16 2016
@@ -1 +1 @@
-1745680
+1745681
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:30:16 2016
@@ -212,21 +212,29 @@ that is bundled with the Taverna Workben
<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">¶</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>
+<ul>
+<li>
<p><strong>Versions use different configuration directories.</strong>
The standalone command-line tool stores its configuration settings in a
<strong>separate</strong>
<a
href="http://dev.mygrid.org.uk/wiki/display/tav250/Taverna+home+directory";>home
directory</a>,
called <em>taverna-cmdline-2.x.x</em> - while the bundled tool uses the same
directory and settings as the Taverna Workbench.</p>
+</li>
+<li>
<p><strong>Bundled tool may use more memory.</strong>
The bundled tool will load all
installed workbench plugins, including third-party plugins.
However, it will also load various GUI-supporting functions,
which may consume extra memory.</p>
-<h3 id="standalone-version-has-remote-capability-gui-not-required">Standalone
version has remote capability, GUI not required.<a class="headerlink"
href="#standalone-version-has-remote-capability-gui-not-required"
title="Permanent link">¶</a></h3>
-<p>The standalone version can easily be installed and used on remote servers
without
+</li>
+<li>
+<p><strong>Standalone version has remote capability, GUI not required.</strong>
+The standalone version can easily be installed and used on remote servers
without
GUI access.</p>
-<h3 id="with-embedded-version-runs-can-show-up-in-workbench">With embedded
version, runs can show up in workbench.<a class="headerlink"
href="#with-embedded-version-runs-can-show-up-in-workbench" title="Permanent
link">¶</a></h3>
-<p>Running the embedded
+</li>
+<li>
+<p><strong>With embedded version, runs can show up in workbench.</strong>
+Running the embedded
version with the database and provenance enabled allows the command-line runs
to show up in the workbench as
"<a
href="http://dev.mygrid.org.uk/wiki/display/tav250/Result+Perspective";>Workflow
runs</a>."
@@ -234,6 +242,8 @@ 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>
+</li>
+</ul>
<hr />
<p><a name="important"></a></p>
<h2 id="other-important-information"><img alt="" src="/img/information.png"
/>Other important information<a class="headerlink"
href="#other-important-information" title="Permanent link">¶</a></h2>
