Author: buildbot
Date: Thu May 26 22:53:45 2016
New Revision: 989239
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 22:53:45 2016
@@ -1 +1 @@
-1745670
+1745671
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 22:53:45 2016
@@ -1 +1 @@
-1745670
+1745671
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 22:53:45 2016
@@ -215,30 +215,22 @@ configured Workbench home directory.</p>
installed workbench plugins, including third-party plugins.
However, it will also load various GUI-supporting functions,
which may consume extra memory.</p>
-<ul>
-<li><strong>Installing service plugins.</strong> </li>
-</ul>
+<h3 id="installing-service-plugins">Installing service plugins.<a
class="headerlink" href="#installing-service-plugins" title="Permanent
link">¶</a></h3>
<p>To install service plugins for the
command-line tool, manually edit the <em>plugins/plugins.xml</em>
in the installation or home directory. The <code><plugin>...
</plugin></code> block
can be copied from the <em>plugins/plugins.xml</em> in the <a
href="http://dev.mygrid.org.uk/wiki/display/tav250/Taverna+home+directory";>home
directory</a>
of a Workbench installation where the plugin is installed.</p>
-<ul>
-<li><strong>Disk space considerations.</strong> </li>
-</ul>
+<h3 id="disk-space-considerations">Disk space considerations.<a
class="headerlink" href="#disk-space-considerations" title="Permanent
link">¶</a></h3>
<p>The standalone installation and download
is smaller than the workbench - but keeping both the standalone and embedded
versions installed will use more disk space than the workbench version alone.
(Note: the command-line tool could use the {repository}} folder
from the workbench using symlinks or modifiying
<em>plugins/plugins.xml</em>.)</p>
-<ul>
-<li><strong>Standalone version has remote capability, GUI not
required.</strong> </li>
-</ul>
+<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
GUI access.</p>
-<ul>
-<li><strong>With embedded version, runs can show up in workbench.</strong>
</li>
-</ul>
+<h2 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></h2>
<p>Running the embedded
version with the database and provenance enabled allows the command-line runs
to show up in the workbench as
@@ -247,9 +239,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>
-<ul>
-<li><strong>Potential conflicts.</strong> </li>
-</ul>
+<h3 id="potential-conflicts">Potential conflicts.<a class="headerlink"
href="#potential-conflicts" title="Permanent link">¶</a></h3>
<p>Although the standalone version would not be in
conflict with the workbench database (as it's in a different home directory),
it could be in conflict with parallel runs of the command-line tool.
