Skip to end of metadata
Go to start of metadata

SoapLab services are command line applications, wrapped as SOAP services, and served from a Soaplab server. Soaplab is especially well suited for applications with well described input and output parameters.

Importing a SoapLab service

To import a SoapLab service:

1. Click the Import new services button in the Service Panel.
2. Select Soaplab service...

3. Enter the Soaplab server URL (e.g. (Soaplab2 Vital-IT Web Services))  in the pop up window and click Add. The new Soaplab service will be added to existing list of services available in the service panel

EMBOSS application have been wrapped as Soaplab services and available by default in Taverna via the service panel

Configuring a Soaplab service

SoapLab has the capability to invoke long running tasks in polling mode. In this mode the task is launched then periodically revisited to determine status. By using this mechanism Taverna enactment engine can avoid problems with timeouts in the target service or in any intervening web proxies or firewalls. If you see errors such as 'Bad gateway' or 'Timeout' when running SoapLab services, this is the first thing to try.

To configure a SoapLab service:

1. Click on the SoapLab service in the workflow diagram and then select the Details tab in the Workflow Explorer.
2. At the bottom of the details table, click Configure Soaplab.
3. Edit the pop up window.

The Polling? checkbox determines whether Taverna enactor should use polling mode when interacting with the service. By default this is unchecked. When this box is selected the Interval, Maximum Interval and Backoff options become available and have the following meanings:

  • Interval: This is the delay in milliseconds in between attempts to fetch the status of the task, the lower this is the higher the load on your network (as more requests will be made per second) but the better the latency (how quickly Taverna notices the job's finished).
  • Maximum Interval: The polling interval increases over time (subject to the backoff factor), this allows you to define an absolute ceiling on the interval between polling attempts. By default this is one minute (60000 milliseconds)
  • Backoff: The polling interval is multiplied by this factor each time Taverna polls the service and finds no data ready. This happens until either the maximum interval is reached or the job finishes.
  • None