MTAT Enterprise System Integration

Size: px

Start display at page:

Download "MTAT Enterprise System Integration"

Todd Beasley
6 years ago
Views:

1 MTAT Enterprise System Integration Lecture 10: WSDL/SOAP Web services Luciano García-Bañuelos University of Tartu

The picture Enterpriseso2ware Presenta,on Presenta,on Integra,onlayer Applica,onlogic Applica,onlogic Dataaccess Dataaccess Whatiftheexecu,onofan enterpriseso2warespansacross theboundariesofan

2 The picture Enterpriseso2ware Presenta,on Presenta,on Integra,onlayer Applica,onlogic Applica,onlogic Dataaccess Dataaccess Whatiftheexecu,onofan enterpriseso2warespansacross theboundariesofan organiza,on? Goal:Interoperability Challenges:Distribu,on, Heterogeneity,LooseDcoupling, Security,etc. Ourfocuswillbeontwo architecturalstyles: REST:Resourceoriented architecture SOA:Serviceoriented architecture RESTLUCIANOGARCÍADBAÑUELOS 1

3 Web Services Web services is an effort to build a distributed computing platform for the Web Goals Enable universal interoperability Widespread adoption, ubiquity: All major industrial actors are involved Supported also by many academic actors WEBSERVICESLUCIANOGARCÍADBAÑUELOS 2

4 WS: Architectural principles Organiza2on/Querying) UDDI) Service)directory) Discovery Adver,sement Service)descrip2on) WSDL)? Consumer) Binding& Invoca,on Service)provider) Interac2on) SOAP) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 3

Descrip2on ) )Organiza2on/Querying) WSDL UDDI Interac2on) SOAP XMLencoding

5 Web Services stack Adhoc aggrega,on Adver-sement& &&discovery& Binding& && Invoca-on& Orchestra2on) WSDBPEL Composi2on) ) ) ) Choreography) WSDCDL Descrip2on ) )Organiza2on/Querying) WSDL UDDI Interac2on) SOAP XMLencoding Transport) Sync:HTTP,FTP Async:SMTP,JMS WEBSERVICESLUCIANOGARCÍADBAÑUELOS 4

6 RPC: Elements of implementation Call Execu,on Return Client) Service) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 5

7 RPC: Elements of implementation Call Parammsg marshalling Parammsg unmarshalling Block Ac,vate Return Client) Parammsg sending Parammsg recep,on Service) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 6

8 RPC: Elements of implementation Call Block Resume Return Resultmsg unmarshalling Result marshalling Client) Resultmsg recep,on Resultmsg sending Service) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 7

9 WSDL Acronym for Web Service Definition Language XML-based, extensible language for: Describing service interfaces Specifying binding details! In a platform-independent way Emerged as a de facto standard, now endorsed by the W3C WEBSERVICESLUCIANOGARCÍADBAÑUELOS 8

10 WSDL document <definitions> <types> definition of types... </types> <message> definition of messages... </message> Abstract Descrip,on <porttype> <operation>... </operation> <operation>... </operation> </porttype> <binding> definition of bindings... </binding> <service> <port>... </port> <port>... </port> </service> Grounding Descrip,on </definitions> WEBSERVICESLUCIANOGARCÍADBAÑUELOS 9

11 WSDL elements porttype opera,on inmessage outmessage SOAP stub Port (e.g.hep://host/svc) Binding SOAP Service CORBA stub Port Binding IIOP WEBSERVICESLUCIANOGARCÍADBAÑUELOS 10

12 WSDL:TypesandMessages WSDL Example <definitions name="sales" targetnamespace=" xmlns=" xmlns:salesx=" <import namespace=" location="salesx.xsd"/> <message name="rfqmsg"> <part name="payload" element="salesx:rfq"/> </message> <message name="quotemsg"> <part name="payload" element="salesx:quote"/> </message> <message name="ordermsg"> <part name="payload" element="salesx:order"/> </message> <message name="cancelordermsg"> <part name="payload" element="salesx:cancelorder"/> </message> <message name="rejectrfqmsg"> <part name="payload" element="salesx:rejectrfq"/> </message> Imported Schema WEBSERVICESLUCIANOGARCÍADBAÑUELOS 11

13 WSDL:PortTypesandOpera,ons WSDL Example <porttype name="providerpt"> <operation name="rfq"> <input message="tns:rfqmsg"/> One-way Operation </operation> <operation name="order"> <input message="tns:ordermsg"/> </operation> <operation name="cancelorder"> <input message="tns:cancelordermsg"/> Two-Way Operation, also with fault </operation> </porttype> <operation name="rfq"> <input message="tns:rfqmsg"/> <porttype name="requesterpt"> <operation name="quote"> <output message="tns:rfqackmsg"/> <input message="tns:quotemsg"/> <fault name="cannotunderstandrfq" message="tns:rfqfaultmsg"/> </operation> <operation name="rejectrfq"> </operation> <input message="tns:rejectrfqmsg"/> </operation> </porttype> WEBSERVICESLUCIANOGARCÍADBAÑUELOS 12

14 WSDL:Bindings WSDL Example <binding name="providerptbinding" type="tns:providerpt"> <soap:binding style="document" transport=" <operation name="rfq"> <soap:operation style="document" soapaction="rfq"/> <input> <soap:header message="tns:replytoheader" part="replyto" use="literal"/> <soap:header message="tns:messageidheader" part="messageid use="literal"/> <soap:body use="literal"/> </input> </operation>... </soap:binding> </binding> WEBSERVICESLUCIANOGARCÍADBAÑUELOS 13

15 WSDL:Services <service name="salesbp"> <port name="providerptport" binding="tns:providerptbinding"> <soap:address location=" </port> URI where the provider is accessible </service> <service name="requesterptservice"> <port name="requesterptport" binding="tns:requesterptbinding"> <soap:address location=" </port> </service>... </definitions> WSDL Example The requester s location is set on the fly in the SOAP header WEBSERVICESLUCIANOGARCÍADBAÑUELOS 14

16 Developing Web Services using WSDL ContractDfirst: WSDL wsimport wsdl.exe Applica,on dependent Marshalling/ Unmarshalling (SOAPmsg) Applica,on dependent Marshalling/ Unmarshalling (SOAPmsg) Client) (Java) Applica,on independent Communica,on middleware Applica,on independent Communica,on middleware Service) (C#) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 15

17 Developing Web Services using WSDL Applica,onDfirst: WSDL wsimport wsgen Applica,on dependent Marshalling/ Unmarshalling (SOAPmsg) Applica,on dependent Marshalling/ Unmarshalling (SOAPmsg) Java applica,on with annota,ons Client) (Java) Applica,on independent Communica,on middleware Applica,on independent Communica,on middleware Service) (Java) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 16

Example: Web Service <@ WebService Language="C#" Class="RentIt.Catalog" >!! using System;! using System.Web;! using System.Web.Services;! using System.Collections.Generic;!! namespace RentIt {!

18 Example: Web Service WebService Language="C#" Class="RentIt.Catalog" >!! using System;! using System.Web;! using System.Web.Services;! using System.Collections.Generic;!! namespace RentIt {!! [WebService (Namespace = " public class Catalog : WebService {! public Catalog () {}!! [WebMethod]! public List<Plant> GetAllPlants() {! Plant bike = new Plant("Bike", "Nice city bike", 10);! Plant truck = new Plant("Truck", "Slightly rusty, but reliable", 100);!! List<Plant> list = new List<Plant>();! list.add(bike); list.add(truck);! return list;! }! }! } WEBSERVICESLUCIANOGARCÍADBAÑUELOS 17

$2f\n", plant.getname(), plant.getdescription(), plant.$

19 Example: Web Service Client public static void main(string args[]) { CatalogSoap proxy = new Catalog().getCatalogSoap(); List<Plant> plants = proxy.getallplants().getplant(); } for (Plant plant : plants) { System.out.printf("-10s, -40s, 10.2f\n", plant.getname(), plant.getdescription(), plant.getprice()); } WEBSERVICESLUCIANOGARCÍADBAÑUELOS 18

20 WS-* in Action (runtime) Phase 1 Serialize (obj > XML) XML SOAP request XML Phase 2 Deserialize (XML > obj) SOAP message SOAP message Requester Provider Proxy object Web XML Web service object Client Web Server XML XML Phase 4 Deserialize (XML > obj) SOAP message SOAP response SOAP message Phase 3 Serialize (obj > XML) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 19

21 SOAP Used to be Simple Object Access Protocol, but no longer an acronym SOAP envelope: <Envelope)xmlns=" )))<Header>...</Header>)) )))<Body>...</Body>)) </Envelope>)) ) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 20

22 Example 1 <env:envelope )xmlns:env=" ) )xmlns:w=" ) )xmlns:n=" )))<env:header>)) ))))))<w:ticket>54b42cf401a</w:ticket>) ))))))<n:token>)) )))))))))<n:value> </n:value>)) )))))))))<n:issuer> ))))))</n:token>)) )))</env:header>) )))<env:body>)) ))))))<w:buy>) ))))))))))<w:product>light)gadget</w:product>) ))))))))))<w:amount>430</w:amount>)) ))))))</w:buy>) )))</env:body>)) </env:envelope>) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 21

23 Envelope Headers Encryption information Access control Routing Auditing Data extensions INITIAL SENDER INTERMEDIARY INTERMEDIARY INTERMEDIARY ULTIMATE RECEIVER WEBSERVICESLUCIANOGARCÍADBAÑUELOS 22

24 Example 1 <env:envelope )xmlns:env=" ) )xmlns:c=" ) )xmlns:c=" ))<env:header>)) ))))<c:encoding)env:role=" ))))))))))))))))env:mustunderstand="true">) )))))))gzip+base64) ))))</c:encoding>) ))))<r:route)env:relay="true") )))))))))))))env:role=" ))))))<r:node> </r:node>) ))))))<r:node> </r:node>)) ))))</r:route>) ))</env:header>)) ))<env:body>)) ))))H4sICACI/0EAA3EA80jNycnXUSjPL8pJUeQCABinVXsOAAAA) ))</env:body>)) </env:envelope>) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 23

25 SOAP data encoding name Zacharias Doe Jane Dow name spouse spouse father name John Doe mother father family name Jack Doe WEBSERVICESLUCIANOGARCÍADBAÑUELOS 24

26 SOAP data encoding (cont.) <family)xmlns:env=" ))))))))xmlns:enc=" ))))))))env:encodingstyle=" ))))))))xmlns=" ))<name>jack)doe</name>) ))<father)enc:id="1">) ))))<name>john)doe</name>) ))))<father>) ))))))<name>zacharias)doe</name>) ))))</father>) ))))<spouse)enc:ref="2"/>) ))</father>) ))<mother)enc:id="2">) ))))<name>jane)dow</name>) ))))<spouse)enc:ref="1"/>) ))</mother>) </family>) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 25

27 WSDL & SOAP BINDINGS RPC Request/Response model Body contains one element named after the operation Document Payload semantics Partners decide upon XSD of the message being exchanged ENCODINGS Encoded Data encoding explicitly specified in the message exchanged Data types explicitly specified Literal Only values are included RPC/Encoded RPC/Literal Document/Encoded Document/Literal WEBSERVICESLUCIANOGARCÍADBAÑUELOS 26

28 Examples <soap:envelope> <soap:body> <mymethod> <x xsi:type="xsd:int">5</x> <y xsi:type="xsd:float">5.0</y> </mymethod> </soap:body> </soap:envelope> Document/literal RPC/encoded <soap:envelope> <soap:body> <xelement>5</xelement> <yelement>5.0</yelement> </soap:body> </soap:envelope> WEBSERVICESLUCIANOGARCÍADBAÑUELOS 27

29 Back to our sample WSDL WSDL:Bindings <binding name="providerptbinding" type="tns:providerpt"> <soap:binding style="document" transport=" <operation name="rfq"> <soap:operation style="document" soapaction="rfq"/> <input> <soap:header message="tns:replytoheader" part="replyto" use="literal"/> <soap:header message="tns:messageidheader" part="messageid use="literal"/> <soap:body use="literal"/> </input> </operation>... </soap:binding> </binding> WEBSERVICESLUCIANOGARCÍADBAÑUELOS 28

30 Protocol Bindings Transmission protocols: HTTP, SMTP, Route from the initial sender to the ultimate receiver may involve different protocols RPC fits naturally into HTTP request/response WEBSERVICESLUCIANOGARCÍADBAÑUELOS 29

31 HTTP Binding in SOAP Message exchange patterns: Request/Response (e.g., RPC) => POST SOAP response => GET HTTP/1.1)200)OK) Content<Type:)application/soap+xml;)charset="utf<8") Content<Length:)273) ) <env:envelope)) )xmlns:env=" )xmlns:rs=" ))<env:body>) ))))<rs:writereciperesponse) )))))))env:encodingstyle=)" ))</env:body>) </env:envelope>)) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 30

32 Additional WS-* Specifications WS-Addressing: Defines SOAP headers for Including sender, return addresses and message IDs Including references to related messages (can be useful to relate a request and a reply) WS-Security: Defines extensions to SOAP for propagation of security tokens which securely identify and authenticate clients, message integrity via XML Signature, message confidentially via XML Encryption. WS-ReliableMessaging Extensions for reliable delivery of messages (exactly-once delivery) WEBSERVICESLUCIANOGARCÍADBAÑUELOS 31

33 Acknowledgements My slides are based on material by Møller & Schwatzbach Sam Guinea (polimi) Text books An introduction to XML and Web Technologies Møller & Schwatzbach, Addison-Wesley 2006 WEBSERVICESLUCIANOGARCÍADBAÑUELOS 32

MTAT Enterprise System Integration. Lecture 3: Web Services SOAP & REST

MTAT Enterprise System Integration. Lecture 3: Web Services SOAP & REST MTAT.03.229 Enterprise System Integration Lecture 3: Web Services SOAP & REST Luciano García Bañuelos luciano.garcia ät ut.ee Web Services Web services is an effort to build a distributed computing platform