1. Taverna Server 3 Donal Fellows

2. Taverna Server Workflow Execution Server Runs Taverna Workflows Limits amount of time to run Deletes old workflow runs Multi-user Manages run separation Manages privilege separation Separate management interface JMX or (tightly-secured) web application

3. Server Architecture Tomcat Container + CXF Framework Taverna Server Webapp Common System Model Per User File Manager Web Portal Ruby Client Per-Run Taverna Workflow Engine Processing Service Catalog Services Storage Services Taverna 3 Workbench (forthcoming) Deployment Host Common Management Model User Workflows SOAP REST Atom Jabber Web Selected Notification Endpoints Management Interface (separate auth)

4. Current Status Mostly the same as Taverna Server 2.5 Majority of API will remain identical Architecture not in need of major revision Supports Scufl2 Workflows as well as T2Flow Transparent switch according to what is supplied Depends on T3 Platform internally Scufl2 libraries for workflow parsing (Lightly-adapted) Command Line for execution

5. Future Changes Produce and Consume Run Bundles Almost there already Shared message bus between execution engine and server Enables pre-warming the execution engines for faster apparent startup Producing snapshots of the Run Report Non-trivial: message-bus is security-critical and performance-critical component

6. Future Architecture Message Bus Taverna Server Webapp Per-User File Manager Per-Run Workflow Execution Engine starts SOAP REST