Skip to end of metadata
Go to start of metadata

Taverna stores user settings and preferences in the Taverna home directory. You do not normally need to edit files in this folder, as it is controlled by the Taverna Workbench user interface.

The location of the home directory depends on the standard folder for preferences for your user account on your operating system.

Workbench home directory

The easiest way to find the Taverna Home directory is from within Taverna:

  1. In Taverna's menu, click Advanced -> Show logs and data folder
  2. A Windows explorer / Finder / Gnome File manager window should appear.

The exact location and name of the home directory depends on your operating system and which Taverna version and edition you are running.

For instance for Taverna Workbench Core 2.5.0:

OS

Path

Windows 8 / 7 / Vista

C:\Users\johndoe\AppData\Roaming\taverna-core-2.5.0

Windows XP

C:\Documents and Settings\johndoe\Application Data\taverna-core-2.5.0

OS X

/Users/johndoe/Library/Application Support/taverna-core-2.5.0

Linux/UNIX

/home/johndoe/.taverna-core-2.5.0

Note that in Windows when browsing to this folder you might be required to enable Show system folders in Windows Explorer as the AppData/Application Data folder is hidden. Alternatively you can click Windows click Start->Run and type %APPDATA% into the text box to open the folder.

Snapshot builds of Taverna will include the timestamp of the build date, e.g. /home/johndoe/.taverna-enterprise-2.5.2-snapshot-20140520/

Content

The content of the home directory varies with which plugins you have used in Taverna, but would typically include:

Folder

Description

conf

Preferences, layout settings, recent workflows, etc

externaltool

Preferences for the Tool activity

lib

JARs to be used as Beanshell /API consumer dependencies

logs

Internal log files written by Taverna (not workflow logs)

moby-cache

Cache of BioMoby 's service ontology

plugins

Installed plugins and plugin sites

registration

Response to Registration dialogue

repository

JARs of downloaded plugins and updates

security

Encrypted password and certificate store for credential manager

t2-database

Database of workflow values and provenance

updates

When Taverna last checked for available updates

var

Temporary files, ie. workflow runs to be deleted from database

Troubleshooting

Taverna support might occasionally advise you to delete or edit some or all of these files if an error has occurred. This would reset your Taverna installation to the factory installation. You will normally need to quit Taverna first to avoid locked files.

  • If a plugin won't install or load properly, try deleting plugins and repository to start again
  • If BioMoby is not finding Moby Objects, try deleting moby-cache
  • If you have forgotten your Credential Manager master password, delete security
  • If Taverna fails to load previous runs or start a new run, try deleting t2-database
  • If Taverna can't make any network connections because of a proxy settings, try deleting conf

Taverna command line tool

The Taverna command line tool, uses a separate home directory to avoid conflicts with the workbench:

OS

Path

Linux/UNIX

/home/johndoe/.taverna-cmd-core-2.5.0

OS X

/Users/johndoe/Library/Application Support/taverna-cmd-core-2.5.0

Windows 7 / Vista

C:\Users\johndoe\AppData\Roaming\taverna-cmd-core-2.5.0

Windows XP

C:\Documents and Settings\johndoe\Application Data\taverna-cmd-core-2.5.0

This means that plugins installed to the workbench won't be installed for the command line tool, and that its workflow runs don't show up in the workbench. If you would prefer that to work, use instead the executeworkflow.sh or executeworkflow.bat that is bundled with the workbench installation.

To install plugins to the separate Command Line tool installation, you would need to manually edit the equivalent of $HOME/.taverna-cmd-core-2.5.0/plugins/plugins.xml to install plugins for the command line. (see the plugin author's documentation or the plugins/plugin.xml of the workbench that has the plugin installed). If you do this, try to ensure that the <dependency> only includes the execution bit of the plugin, for instance my-activity rather than my-activity-ui. If you include the latter, the command line tool will download and initiate parts of the Workbench, which could slow down the command line launch and in some cases fail workflow execution.

 

Labels
  • None