You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@taverna.apache.org by bu...@apache.org on 2016/05/26 23:31:46 UTC
svn commit: r989251 - in /websites/staging/taverna/trunk: cgi-bin/ content/
content/documentation/command-line/index.html
Author: buildbot
Date: Thu May 26 23:31:46 2016
New Revision: 989251
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:31:46 2016
@@ -1 +1 @@
-1745681
+1745682
Propchange: websites/staging/taverna/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 26 23:31:46 2016
@@ -1 +1 @@
-1745681
+1745682
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:31:46 2016
@@ -249,30 +249,40 @@ either a standalone <em>-startdb</em> da
<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>
<p>This section provides additional information on configuring proxy settings,
installing service plugins, disk space considerations and potential conflicts.</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>
+<ul>
+<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>
must be manually configured.
Copy <em>conf/HttpProxy-B307A902-F292-4D2F-B8E7-00CC983982B6.config</em> from a
configured Workbench home directory.</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
+</li>
+<li>
+<p><strong>Installing service plugins.</strong>
+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
+</li>
+<li>
+<p><strong>Disk space considerations.</strong>
+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="potential-conflicts">Potential conflicts.<a class="headerlink" href="#potential-conflicts" title="Permanent link">¶</a></h3>
-<p>Although the standalone version would not be in
+</li>
+<li>
+<p><strong>Potential conflicts.</strong>
+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>
<hr />
<p><a name="CommandLineTool-ExecuteworkflowScript"></a></p>
<h2 id="executeworkflow-script">Executeworkflow Script<a class="headerlink" href="#executeworkflow-script" title="Permanent link">¶</a></h2>