web services interoperability through standardisation
DESCRIPTION
Web Services Interoperability Through Standardisation. The EMBRACE Technology Recommendation. Why Use Web Services In The First Place?. Interoperability Interoperability Interoperability. Service Oriented Architecture (SOA). Functionality is most commonly expressed as services. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/1.jpg)
Web Services Interoperability Through Standardisation
The EMBRACE Technology Recommendation
![Page 2: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/2.jpg)
Why Use Web Services In The First Place?
Interoperability
Interoperability
Interoperability
![Page 3: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/3.jpg)
Service Oriented Architecture (SOA)
• Functionality is most commonly expressed as services.
• Each service provides one clearly defined basic functionality.
• Higher level functionality is achieved using service composition.
![Page 4: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/4.jpg)
Web Services Interoperability organisation
• Initial Web Service specifications were quite flexible– Many different ways to make Web Services– Hard to make tools that could be used for all types of services
• Web Services Interoperability organisation was founded to establish more restrictive specifications– Similar services– Outdated tools
![Page 5: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/5.jpg)
The Evolution Of Web Services
![Page 6: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/6.jpg)
![Page 7: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/7.jpg)
![Page 8: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/8.jpg)
![Page 9: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/9.jpg)
SOA Is Becoming Boring
Has become part of the software industrySAPOracle IBMMicrosoft
![Page 10: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/10.jpg)
SOA Is A Part Of Society
Applications in Norway:All parts of governmentPoliceMajor hospitalsCompanies
![Page 11: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/11.jpg)
The Technology Recommendation: An EMBRACE of WS-I
• WS-I is ready (ish) to use
• Many tools and supporting technologies available
• Competence is available
![Page 12: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/12.jpg)
A closer look at Web Services
<Warning> XML </Warning>
![Page 13: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/13.jpg)
Client
WSDL
File
Web service
Usage scenario
![Page 14: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/14.jpg)
Client
WSDL
File
Web service
Client reads the WSDL file
![Page 15: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/15.jpg)
Client
WSDL
File
Web service
Client sends request
![Page 16: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/16.jpg)
Client
WSDL
File
Web service
Client receives the response
![Page 17: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/17.jpg)
Extensible Markup Language
• A way of structuring information• Use Elements and attributes
<Element> ... </Element>
<Element attribute="..." ></Element>
![Page 18: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/18.jpg)
XML Schema
Schema
<element name=“Person"> <complexType> <sequence> <element name="firstname"
type="string"/> <element name="lastname" type="string"/> <element name="age" type="int"/>
</sequence> </complexType> </element>
Instance
<person> <firstname>John</firstname> <lastname>Doe</lastname> <age>40</age> </person>
Person
First Name
Last NameAge
Class
Person
JohnDoe40
Object
![Page 19: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/19.jpg)
XML Binding
Representing the information in an XML document as an object in computer memory
<person> <firstname>John</firstname> <lastname>Doe</lastname> <age>40</age> </person>
Person
JohnDoe40
![Page 20: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/20.jpg)
Namespaces
• Avoids naming conflicts• We can use prefixes for shorter notation
<ParentElement xmlns:ns1="http://mysite.com/NS1">
<ns1:Element> ... </ns1:Element>
</ParentElement>
![Page 21: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/21.jpg)
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
![Page 22: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/22.jpg)
SOAP Message
<Envelope><Header> </Header><Body> </Body>
</Envelope>
Or just:
<Envelope><Body> </Body>
</Envelope>
![Page 23: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/23.jpg)
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.
![Page 24: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/24.jpg)
WSDL file
<definitions>
<types> XML Schema definitions of data formats
<message> Definition of messages for input and output of the operations in this service.
<portType> Definition of the operations available at this service.
<binding> The binding of the operations to a set of protocols. SOAP over HTTP is most commonly used
<service> Name and network address of this service
</definitions>
![Page 25: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/25.jpg)
Schema part of a WSDL
.......<xs:element name="getMatrixById"> <xs:complexType> <xs:sequence> <xs:element name="Id" type="xs:string"/> <xs:element ref="Format"/> <xs:element ref="Database"/> </xs:sequence> </xs:complexType></xs:element>.......
![Page 26: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/26.jpg)
Corresponding SOAP message
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:jas="http://bccs.uib.no/Jaspar"><soapenv:Header/> <soapenv:Body> <jas:getMatrixById> <jas:Id>MA0003</jas:Id> <jas:Format>PFM</jas:Format> <jas:Database>CORE</jas:Database> </jas:getMatrixById> </soapenv:Body></soapenv:Envelope>
![Page 27: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/27.jpg)
Sample Perl Client
my $wsdl = XML::LibXML->new->parse_file('http://api.bioinfo.no/wsdl/JasparDB.wsdl');my $proxy = XML::Compile::WSDL11->new($wsdl);
my $getMatrixById = $proxy->compileClient('getMatrixById');my $answer = $getMatrixById->( Id => $get_by_id, Format => $format, Database => $db );my $matrix = $answer->{parameters}{Matrix};
_print_matrix($matrix);
![Page 28: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/28.jpg)
eVita Project
• Norwegian research council eScience program • Has funded a 2.3 me project to build a SOA to support
systems biology research at BCCS.• Built with WS-I Web Services• Partners in UK
– MyGrid – Manchester Interdisciplinary Biocentre
![Page 29: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/29.jpg)
EuTRACC The European Transcriptome, Regulome & Cellular Commitment Consortium
• Aims to identify TFs and interacting partners expressed
in neuronal and haematopoietic cell types.
• European NoE
• Primarily partners with biological competence
• Lenhard group responsible for analysis
![Page 30: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/30.jpg)
EuTRACC tasks
• Integrative analysis of proteomics, gene expression, chip-chip and chip-seq data
• Determine the principal regulatory network components
• Build supporting infrastructure
– Performed by the eVita project
![Page 31: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/31.jpg)
IRCThe International Regulome Consortium
– The discovery of how gene function is regulated in
mammalian cells during development
– Collaborates closely with EuTRACC
– Will use same/simmilar infrastructure
![Page 32: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/32.jpg)
Jaspar Database
• Database of profiles of transcription factor binding sites
• Prediction of over-represented TFBS i sets of genes
• Statistical analysis
![Page 33: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/33.jpg)
Steps forward in EMBRACE
• Define common data types
• Links to ontologies
![Page 34: Web Services Interoperability Through Standardisation](https://reader036.vdocuments.net/reader036/viewer/2022062301/568150f3550346895dbf0e83/html5/thumbnails/34.jpg)
Acknowledgements
Vincent Breton Jean Salzemann CNRS /Clermont-Ferrand
All other members of the Technology Recommendation and Watch WP
Steve Pettifer UMAN
Inge JonassenPål PuntervollRein Aasland BCCS
Toby Gibson EMBL