Author: buildbot
Date: Thu May 26 23:03:31 2016
New Revision: 989240
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:03:31 2016
@@ -1 +1 @@
-1745671
+1745673
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 23:03:31 2016
@@ -1 +1 @@
-1745671
+1745673
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:03:31 2016
@@ -199,38 +199,25 @@ 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>
-<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>
-<h3 id="versions-use-different-configuration-directories">Versions use
different configuration directories.<a class="headerlink"
href="#versions-use-different-configuration-directories" title="Permanent
link">¶</a></h3>
+<h2 id="differences-between-versions-and-other-important-information"><img
alt="" src="/img/information.png" />Differences between versions and other
important information<a class="headerlink"
href="#differences-between-versions-and-other-important-information"
title="Permanent link">¶</a></h2>
+<p>This section describes some of the differences between the bundled and
standalone versions of
+<em>executeworkflow</em> and provides additional information on configuring
proxy settings,
+installing service plugins, and disk space considerations.</p>
+<h3
id="what-are-the-differences-between-the-bundled-and-standalone-versions">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></h3>
+<h4 id="versions-use-different-configuration-directories">Versions use
different configuration directories.<a class="headerlink"
href="#versions-use-different-configuration-directories" title="Permanent
link">¶</a></h4>
<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>
-<h3 id="manually-configure-proxy-settings">Manually configure proxy
settings.<a class="headerlink" href="#manually-configure-proxy-settings"
title="Permanent link">¶</a></h3>
-<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>
-<h3 id="bundled-tool-may-use-more-memory">Bundled tool may use more memory.<a
class="headerlink" href="#bundled-tool-may-use-more-memory" title="Permanent
link">¶</a></h3>
+<h4 id="bundled-tool-may-use-more-memory">Bundled tool may use more memory.<a
class="headerlink" href="#bundled-tool-may-use-more-memory" title="Permanent
link">¶</a></h4>
<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>
-<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>
-<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>
-<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>
+<h4 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></h4>
<p>The standalone version can easily be installed and used on remote servers
without
GUI access.</p>
-<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>
+<h4 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></h4>
<p>Running the embedded
version with the database and provenance enabled allows the command-line runs
to show up in the workbench as
@@ -239,7 +226,25 @@ 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>
-<h3 id="potential-conflicts">Potential conflicts.<a class="headerlink"
href="#potential-conflicts" title="Permanent link">¶</a></h3>
+<h3 id="other-important-information">Other important information<a
class="headerlink" href="#other-important-information" title="Permanent
link">¶</a></h3>
+<h4 id="manually-configure-proxy-settings">Manually configure proxy
settings.<a class="headerlink" href="#manually-configure-proxy-settings"
title="Permanent link">¶</a></h4>
+<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>
+<h4 id="installing-service-plugins">Installing service plugins.<a
class="headerlink" href="#installing-service-plugins" title="Permanent
link">¶</a></h4>
+<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>
+<h4 id="disk-space-considerations">Disk space considerations.<a
class="headerlink" href="#disk-space-considerations" title="Permanent
link">¶</a></h4>
+<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>
+<h4 id="potential-conflicts">Potential conflicts.<a class="headerlink"
href="#potential-conflicts" title="Permanent link">¶</a></h4>
<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.
