Author: buildbot
Date: Thu May 26 22:48:16 2016
New Revision: 989237
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:48:16 2016
@@ -1 +1 @@
-1745667
+1745669
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 22:48:16 2016
@@ -1 +1 @@
-1745667
+1745669
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:48:16 2016
@@ -201,46 +201,52 @@ that is bundled with the Taverna Workben
</ul>
<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>
<ul>
-<li>
-<p><strong>Versions use different configuration directories.</strong> The
standalone
+<li><strong>Versions use different configuration directories.</strong> </li>
+</ul>
+<p>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>Manually configure proxy settings.</strong> Any <a
href="http://dev.mygrid.org.uk/wiki/display/tav250/HTTP+proxy+preferences";>proxy
settings</a>
+<ul>
+<li><strong>Manually configure proxy settings.</strong> </li>
+</ul>
+<p>Any <a
href="http://dev.mygrid.org.uk/wiki/display/tav250/HTTP+proxy+preferences";>proxy
settings</a>
must be manually configured.
Copy <em>conf/HttpProxy-B307A902-F292-4D2F-B8E7-00CC983982B6.config</em> from a
configured Workbench home directory.</p>
-</li>
-<li>
-<p><strong>Bundled tool may use more memory.</strong> The bundled tool will
load all
+<ul>
+<li><strong>Bundled tool may use more memory.</strong> </li>
+</ul>
+<p>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>
-</li>
-<li>
-<p><strong>Installing service plugins.</strong> To install service plugins for
the
+<ul>
+<li><strong>Installing service plugins.</strong> </li>
+</ul>
+<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>
-</li>
-<li>
-<p><strong>Disk space considerations.</strong> The standalone installation and
download
+<ul>
+<li><strong>Disk space considerations.</strong> </li>
+</ul>
+<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>
-</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
+<ul>
+<li><strong>Standalone version has remote capability, GUI not
required.</strong> </li>
+</ul>
+<p>The standalone version can easily be installed and used on remote servers
without
GUI access.</p>
-</li>
-<li>
-<p><strong>With embedded version, runs can show up in workbench.</strong>
Running the embedded
+<ul>
+<li><strong>With embedded version, runs can show up in workbench.</strong>
</li>
+</ul>
+<p>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>."
@@ -248,16 +254,15 @@ 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>
-<li>
-<p><strong>Potential conflicts.</strong> Although the standalone version would
not be in
+<ul>
+<li><strong>Potential conflicts.</strong> </li>
+</ul>
+<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.
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>
-</li>
-</ul>
<p><a name="CommandLineTool-ExecuteworkflowScript"></a></p>
<h2 id="executeworkflow-script">Executeworkflow Script<a class="headerlink"
href="#executeworkflow-script" title="Permanent link">¶</a></h2>
<p>To get help and a full set of options for the executeworkflow script,
