Taverna Remote Execution Service
The Taverna Server combines a Remote Execution Service with the Remote Execution plugin for Taverna 1.7 to give a lab the possibility to set up a dedicated server for executing workflows remotely. The user can submit workflows from Taverna 1.7, detach, and check their execution status later either from Taverna or from a web page.
- Download the Taverna Remote Execution service
- Source code
- Documentation for the server
- Documentation for the plugin
Running a remote execution service securely
This information was supplied by Jeffrey L Tilson. The information supplied for 1.7.1 should also be true for 1.7.2
First define REE as the Remote Execution Engine running on a “server” system Second define TV 1.7 as Taverna 1.7.1 running on a “client” system, viz., my laptop.
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 8443)
- From the “client”, connect to the server:8443 and export the certificate. In Firefox, this process requires 1) accepting the cert permanently, 2) installing the firefox plugin to export certs, 3) export the cert to a file.
- From the “client”, import that cert to a keystore of choice. For TV 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 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.