1. Web Services interoperability and standards

2. Infrastructure Challenge ● Applied bioinformatics need various computer resources ● The amount and size of databases and tools are growing rapidly ● Systems Biology is predicted to become more important

3. How Web Services Can Help ● Replace local resources with remote resources ● Web Services can provide a standardized access method. ● Web Services is being adopted in bioinformatics

4. Definition Of Web Services A Web service is a software system designed to support interoperable machine-to- machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards. W3C Web Services Architecture Working Group

5. Source: Gartner (August 2005)

6. Value Of Web Services Based on standards – Lots of tools available – Massive development of new tools and supporting technologies. – Easy to find information and support

7. Value Of Web Services Provides interoperability ● Text over the Internet => Nothing new ● Remote access => Nothing new ● Interoperability =>New! Widely accepted standards = Interoperability

8. Web Service Standards

9. ● SOAP Version 1.2 – W3C Recommendation since 24 June 2003 – Stable ● Web Services Description Language (WSDL) 1.1 – Not a W3C Recommendation – Version 2.0 is a “Candidate Recommendation” at W3C

10. SOAP The Protocol formerly known as “Simple Object Access Protocol” – The SOAP Envelope for messages – Processing model for how to deal with the messages – Protocol binding framework

11. SOAP Message......

12. SOAP Engines ● Translates from software constructs to SOAP messages (XML). This is known as Serialization. ● Interprets SOAP messages and performs translation into software constructs (de- serialization)

13. Consumer Serialize into a SOAP message Provider Serialize into a SOAP message De-serialize into native data types Serialize into a SOAP message Message Backend SOAP Engine Transport SOAP Engine Backend

14. Web Service Description Language Provides an abstract definition of a Web Service and a binding which ties it to a concrete endpoint. Is completely independent of the Web Service it describes.

15. Architecture Of a Web Service WSDL File Backend Client Server Stub SOAP Engine

16. Web Services Interoperability

17. WS-I ● An open industry effort chartered to promote Web Services interoperability across platforms, applications and programming languages ● Has defined Basic Profile 1.0 which resolves many interoperability issues.

18. Document/Literal wrapped pattern ● WSDL allows a high degree of freedom in the interface design. ● Different SOAP engines might interpret the WSDL in different ways. ● The most interoperable way of designing a WSDL file is the Document/Literal wrapped pattern. Understood by all major SOAP engines.

19. Web Service Resource Framework

20. Challenge ● Some jobs take a long time to complete – CPU intensive tasks – Jobs in queue ● Vanilla Web Services use HTTP calls and expect fast results. ● Possible to extend timeout, but there is still a problem of keeping an open socket for a long time.

21. Asynchronous calls ● Client send request ● Server replies with a reference to the running job ● Client polls for status ● Client retrieves results when the status is completed

22. Client Factory Service Resource Instance Service Resource Submit Web Service Resource Framework

23. Client Factory Service Resource Instance Service Resource Submit Create Resource

24. Client Factory Service Resource Instance Service Resource EPR

25. Client Factory Service Resource Instance Service Resource EPR Get status/results

26. Composition of Web Services

27. Composition Types ● Orchestration – Centralized coordinator – Individual services are not aware of other services ● Choreography – No centralized coordinator – Each service is aware of its role

28. Orchestration standards ● SCUFL – The language used by Taverna – Made especially for eScience/bioinformatics – Proprietary ● BPEL – Standard. Specification soon ready. – Widely accepted – Lots of tools already available, more will come

29. Svenn Helge Grindhaug System Engineer Eric Hajjar PhD Student Anders Lanzén Programmer Ketil Malde Scientist Pål Puntervoll Senior Scientist Nathalie Reuter Group Leader, Service Scientist Gisle Sælensminde PhD Student Thanks to the CBU Service Group: