It is recommended to switch to Taverna 2 Server where possible.
Taverna 1.7.x Server combines the Remote Execution Service with the Remote Execution plugin for Taverna 1.7.x Workbench to let users set up a dedicated server for executing workflows opened in the Workbench remotely. A user can submit a workflow for execution from the Taverna 1.7.x Workbench, detach, and check the workflow execution status later either from the Workbench or from a Web page.
- Download the Taverna Remote Execution Service
- Source code
- Documentation for the Taverna 1.7.x Server
- Documentation for the Taverna 1.7.x Workbench plugin
Running a remote execution service securely
This information was supplied by Jeffrey L Tilson. It refers to the 1.7.1 version but should also be true for 1.7.2.
Let us denote the Remote Execution Engine running on a “server” system as REE.
These directions are loosely based on the blog of Marlon Pierce. There are additions, however, to account for the REE.
- Install the REE into Tomcat 5.5 per the instructions.
- Define an SSL connector ( in my case on port 8443)
- From the “client”, connect to the server:8443 and export the certificate. In Firefox, this process requires: 1) accepting the certificate permanently, 2) installing the Firefox plugin to export certificates, 3) export the certificate to a file.
- From the “client”, import that cert to a keystore of choice. For Taverna 1.7.1+execute-remote plugin to work, you must specify the keystore environment variables, e.g. KEYSTORE_DIR, etc.
- On the “server”, you need to install the same certificate into a “server” keystore so the forked REE-taverna jobs can connect back to port 8443. If you do not, a job launched from the “client” will launch, queue, and initialise, but then hang without apparent error. The job will never finish (“never” being defined as t > my patience threshold).
- On the “server”, specify the KEYSTORE_DIR, etc, variables.