1. SHIWA Desktop Cardiff University David Rogers, Ian Harvey, Ian Taylor, Andrew Jones

2. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Introduction What is SHIWA Desktop? What is a SHIWA Bundle? SHIWA Desktop Interfaces SHIWA Desktop GUI –Demo

3. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich What is SHIWA Desktop? The Desktop solution for SHIWA Project Connects a user’s desktop workflow environment to the SHIWA Repository Provides lightweight upload and download in common format for engines Tool for serialisation and deserialisation of SHIWA Bundles

4. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich What is SHIWA Desktop? Provides three interfaces: –Command-line interface script-based interaction with a workflow engine –An API workflow engine can use this to interface directly with a SHIWA Bundle –A graphical front-end automatic creation of Bundles from within GUI-based workflow systems e.g. Askalon, Moteur and Triana

5. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich What are SHIWA Bundles? Aggregation of data representing a workflow –Employs the OAI-ORE standard Physical aggregation as a single entity (ZIP file) Can reference anything with a URL (within bundle or elsewhere) Provides a common language/format for workflow engines –Once workflow engines can consume bundles and export them, workflow interoperability can exist within pipelines of workflows (or so- called meta workflows) Resource Map (list of URLs) Resource Map (list of URLs)

6. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Bundle Components Workflow Implementation –Definition File Abstract Workflow –Signature Data Configuration –Variable data Environment Configuration –Constant data

7. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Command Line Interface Support interfacing with workflow systems (especially non-Java ones) through the command line Bundles can be unpacked to provide input and dependency files Provides a simple way to interface using scripts to wrap a workflow engine without modifying its internal behaviour

8. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop Core API Three key parts with the Desktop Data API –SHIWABundle Object - reads in SHIWA bundles, converting the metadata into RDF element objects –RDF Element Objects – objects representing the elements found in the Metadata files, e.g. workflow resources, the aggregated resources and the components of a workflow signature. –WorkflowEngineHandler Interface – simplified interface for integrating a workflow engine, allowing ease of publishing and deployment of workflows.

9. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Workflow Engine Handler An engine-specific component that understands the internal operations of a workflow engine and its object models WorkflowEngineHandler Interface –Simple to implement –Provides a means of pre-populating technical metadata e.g. engine name, version, the workflow language, the serialization of the workflow and the workflow signature object. –A signature includes a name a list of inputs and outputs

10. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Workflow Engine Handler User develops workflow within local workflow system When user wishes to publish, SHIWA Desktop is invoked, with handler passed to it

11. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Workflow Engine Handler Workflow Engine Input + Value Output + Value Dependency+ Value Signature Definition File Dependency+ Value Handler List inputPorts List outputPorts Map dependencies Metadata

12. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop GUI Common user interface for engine GUIs Users have full control over the contents of a Workflow Bundle Typically-required metadata can be added easily Re-use of information on repository is encouraged

13. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich

14. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich

15. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop GUI Signature Panel defines all inputs and outputs Launched from an integrated workflow environment; information is pre filled Missing ports and human readable descriptions can be added

16. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop GUI Dependencies can also be defined Input/Output ports are VARIABLES Dependencies are CONSTANTS

17. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop GUI Configuration Tab allows user to supply input Data Configurations map to the signature Environment Configurations map to the dependencies

18. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich SHIWA Desktop GUI Supporting files may be added to the Workflow Allows Workflow to be enhanced with additional data/metadata, yielding a complete research object

19. David Rogers, Ian Harvey, Ian Taylor, Andrew Jones EGI Community Forum 2012, Munich Summary SHIWA Bundles provide a simple transfer format for Workflows and associated information SHIWA Desktop API defines operations for reading and writing of SHIWA Bundles SHIWA Desktop GUI presents a common Bundling interface