Plugins have been developed outside the myGrid team. To access these plugins you must enter the plugin site in Taverna’s plugin manager. In Taverna 1.7.1, select Plugin Manager from the Tools menu and then Find Plugins and Add Plugin Site. The third-party plugins include: A Soaplab2 plugin that allows users to include Soaplab2 services in [...]

As with most software, Taverna 2 beta 1 has a some known bugs, especially as it is a beta version. This is the list of the unresolved bugs for Taverna 2 beta 1 that are currently entered in the myGrid team’s JIRA system: [T2-190] Taverna contrib local worker translators depends on all of Taverna 1 [T2-193] First build [...]

Here is a quick introduction to what is new or different in the user interface of Taverna 2 beta 1 from Taverna 1. Activity Palette The scavenger panel is replaced by an activity palette that is user configurable. Drop down boxes allow selection of what is to be browsed at first or second level, and the free [...]

Description Taverna 2 beta 1 is the public beta for Taverna 2. Taverna 2 is scheduled for release in December 2008. Increased Functionality Taverna 2 beta 1 has greatly improved functionality over Taverna 1. It includes: An improved user interface A configurable flexible activity (service) palette A new graphical workflow editor including Drag and drop of activities into the workflow Graphical [...]

Metrics have been run to compare the performance of Taverna 1 and Taverna 2 beta 1. The most noticeable difference is when the workflow makes extensive use of iteration (multiple calls of the same activity). This allows the new enactor to pipeline the output of the calls to the activity. The comparative performance of [...]

In Taverna 1, if a service is called multiple times, then Taverna 1 waits until all calls of the service are finished before it passes any data on to subsequent services. For example, if a service is called 1000 times, then although data from the first call will become available quickly, Taverna 1 waits [...]

In Taverna 1, LocalWorkers are implemented as Java classes built into Taverna. In Taverna 2 beta 1, they have been replaced by a library of standard beanshells. It is possible to configure a LocalWorker in order to create your own beanshell that implements specialised functionality. It is intended that the LocalWorkers will be the first example [...]

In Taverna 1 you can specify a default value on the port of a processor. If the port is not connected, then when you run the workflow, the port will receive the default value. Default values are not available with Taverna 2 beta 1. When a Taverna 1 workflow that uses default values is [...]

In addition to the improved functionality of Taverna, there are two obvious differences between workflows within Taverna 1 and Taverna 2 beta 1: The appearance of Default Values on processor ports The implementation of LocalWorkers

Possible problems Taverna 2 beta 1 will translate and run most Taverna 1 workflows. This document describes some of the rare problems you may experience when loading a Taverna 1 workflow into Taverna 2 beta 1. Many of these migration issues will be resolved in the near future. Please see the roadmap for details. What will not translate Taverna [...]