Author: gnaylor
Date: Thu May 26 22:48:09 2016
New Revision: 1745669
URL: http://svn.apache.org/viewvc?rev=1745669&view=rev
Log:
Add whitespace in What are differences section
Modified:
incubator/taverna/site/trunk/content/documentation/command-line/index.md
Modified:
incubator/taverna/site/trunk/content/documentation/command-line/index.md
URL:
http://svn.apache.org/viewvc/incubator/taverna/site/trunk/content/documentation/command-line/index.md?rev=1745669&r1=1745668&r2=1745669&view=diff
==============================================================================
--- incubator/taverna/site/trunk/content/documentation/command-line/index.md
(original)
+++ incubator/taverna/site/trunk/content/documentation/command-line/index.md
Thu May 26 22:48:09 2016
@@ -16,7 +16,6 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-
The Apache Taverna Command-line Tool is a script that runs Taverna workflows
from a terminal. The command-line script is called *executeworkflow*
(*executeworkflow.bat* on Windows and *executeworkflow.sh* on Linux/UNIX).
@@ -29,40 +28,52 @@ that is bundled with the Taverna Workben
##What are the differences between the bundled and
standalone versions?
- - **Versions use different configuration directories.** The standalone
+ - **Versions use different configuration directories.**
+
+ The standalone
command-line tool stores its configuration settings in a **separate**
[home
directory](http://dev.mygrid.org.uk/wiki/display/tav250/Taverna+home+directory),
called *taverna-cmdline-2.x.x* - while the bundled tool uses the same
directory and settings as the Taverna Workbench.
+ - **Manually configure proxy settings.**
- - **Manually configure proxy settings.** Any [proxy
settings](http://dev.mygrid.org.uk/wiki/display/tav250/HTTP+proxy+preferences)
+ Any [proxy
settings](http://dev.mygrid.org.uk/wiki/display/tav250/HTTP+proxy+preferences)
must be manually configured.
Copy *conf/HttpProxy-B307A902-F292-4D2F-B8E7-00CC983982B6.config* from a
configured Workbench home directory.
- - **Bundled tool may use more memory.** The bundled tool will load all
+ - **Bundled tool may use more memory.**
+
+ 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.
- - **Installing service plugins.** To install service plugins for the
+ - **Installing service plugins.**
+
+ To install service plugins for the
command-line tool, manually edit the *plugins/plugins.xml*
in the installation or home directory. The ``<plugin>... </plugin>`` block
can be copied from the *plugins/plugins.xml* in the [home
directory](http://dev.mygrid.org.uk/wiki/display/tav250/Taverna+home+directory)
of a Workbench installation where the plugin is installed.
- - **Disk space considerations.** The standalone installation and download
+ - **Disk space considerations.**
+
+ 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 *plugins/plugins.xml*.)
- - **Standalone version has remote capability, GUI not required.** The
-standalone version can easily be installed and used on remote servers without
+ - **Standalone version has remote capability, GUI not required.**
+
+ The standalone version can easily be installed and used on remote servers
without
GUI access.
- - **With embedded version, runs can show up in workbench.** Running the
embedded
+ - **With embedded version, runs can show up in workbench.**
+
+ Running the embedded
version with the database and provenance enabled allows the command-line runs
to show up in the workbench as
"[Workflow
runs](http://dev.mygrid.org.uk/wiki/display/tav250/Result+Perspective)."
@@ -71,7 +82,9 @@ already running, the command-line tool
Alternatively, if the workbench is shut down, the command-line tool must use
either a standalone *-startdb* database server process or the *-embedded*
option.
- - **Potential conflicts.** Although the standalone version would not be in
+ - **Potential conflicts.**
+
+ 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 *-startdb* process should be started with the
