Presentation is loading. Please wait.

Presentation is loading. Please wait.

Presentation 7: SOAP, WSDL & introduction to UDDI.

Similar presentations


Presentation on theme: "Presentation 7: SOAP, WSDL & introduction to UDDI."— Presentation transcript:

1 Presentation 7: SOAP, WSDL & introduction to UDDI

2 Ingeniørhøjskolen i Århus Slide 2 af 51 Outline Overview of Web Services & SOAP Service-Oriented Architecture –Service Description –Service Registration and Discovery –Service Execution Emerging Web Services standards: SOAP, WSDL, UDDI (introduced)

3 Ingeniørhøjskolen i Århus Slide 3 af 51 Web Service Defined W3C definition: –[Definition: 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.]

4 Ingeniørhøjskolen i Århus Slide 4 af 51 Overview SOAP & Web services SOAP – Simple Object Access Protocol - & Web services: –A light-weight & ultra heterogenic alternative to CORBA, DCOM & RMI –Openness in focus – meant for opening legacy applications for others –Not meant in the role of Inter business, large scale, transaction heavy communication (as CORBA & J2EE) –But can prob. be used for it! –Does not have services for transactions, concurrency, persistence, scalability –Does have discovery services (UDDI) giving some degree of location transparency –Does have Interface Definition Language for heterogeneity (WSDL) –Fails on several of the dist. system requirements! –But easy to implement yourself!

5 Ingeniørhøjskolen i Århus Slide 5 af 51 Why SOAP When We Have CORBA? CORBA has been considered too complex by many –May not be true with new development tools using wizards They aim at solving different tasks: –SOAP covers light-weight application integration within the enterprise, exposing legacy business objects across enterprises, and sharing resources (like Google Search Engine, or Sonofon SMS/MMS API) on the net, as well as technology openness –CORBA has a wide range of services for (as we shall see later): Locating, creating & moving objects Object relationship management between hosts Persistency services – activation frameworks etc. Distributed concurrency and transaction management Security –Only some are supported in SOAP tech family – its lightweight –Lesson: define your needs – and find the right technology

6 Ingeniørhøjskolen i Århus Slide 6 af 51 Regarding SOAP SOAP is not by it self revolutionary – its merely: –a framework for exchanging XML-based information in a network (via protocols of the TCP/IP family) – with RPC capabilities –the currently most hyped XML / Web service technology But when combined with other technologies like –WSDL & –UDDI –It solves several of the requirements of a Distributed System And the fact that it is an open standard – supported by all major software vendors and programming languages: –C++ –Java –C# –Delphi –Visual Basic and many more Makes it somewhat revolutionary! A practical solution – like WWW

7 Ingeniørhøjskolen i Århus Slide 7 af 51 Examples of Web Services Google's Web Service - access the Google search engineGoogle's Web Service –http://www.google.com/apis/ Amazon's Web Service - access Amazon's product informationAmazon's Web Service –http://associates.amazon.com/exec/panama/associates/join/develo per/resources.html XMethods - collection of information about existing Web servicesXMethods –http://www.xmethods.com SalCentral - WSDL / SOAP Web services search-engineSalCentral –http://www.salcentral.com/salnet/webserviceswsdl.asp

8 Ingeniørhøjskolen i Århus Slide 8 af 51 Google Web Service

9 Ingeniørhøjskolen i Århus Slide 9 af 51 Service-Oriented Architecture (SOA) Client Server Registry Abstract Architecture - Web service stack Abstract Architecture - Web service stack Legacy code on server Legacy code on server Opening up for doing business (the sharing of objects) on the Internet

10 Ingeniørhøjskolen i Århus Slide 10 af 51 Technologies for Implementing SOA SOAP for communication WSDL for contract & binding UDDI & WSDL for registration & discovery

11 Ingeniørhøjskolen i Århus Slide 11 af 51 SOAP SOAP is used for Client/Server communications

12 Ingeniørhøjskolen i Århus Slide 12 af 51 What is SOAP? Simple Object Access Protocol Wire protocol similar to –IIOP for CORBA –JRMP for RMI XML is used for data encoding –“text” based protocol vs. “binary” protocol Supports XML-based RPC

13 Ingeniørhøjskolen i Århus Slide 13 af 51 What is Not SOAP? Not a component model –So it will not replace objects and components, i.e. EJB, JavaBeans and.NET Not a programming language –So it will not replace Java, C# og C++ Not a solution for all –So it will not replace other distributed computing technologies such as RMI and CORBA

14 Ingeniørhøjskolen i Århus Slide 14 af 51 Where is SOAP? W3C XML Protocol working group –SOAP 1.2 current version: Microsoft, SUN, Oracle, HP, IBM all support the W3C recommendation –but there are still differences to be overcome –security issues, transactions etc.

15 Ingeniørhøjskolen i Århus Slide 15 af 51 What does SOAP define? Message Envelope Encoding Rules RPC Convention Binding with underlying protocols –HTTP (which we will use in this course) –SMTP –FTP and others

16 Ingeniørhøjskolen i Århus Slide 16 af 51 SOAP Message Format Possible to Attach binaries (images, cryptographic material) to attachments

17 Ingeniørhøjskolen i Århus Slide 17 af 51 SOAP Message Envelope Encoding information Header –Optional –Could contain context knowledge Security Transaction Body –RPC methods and parameters –Contains application data

18 Ingeniørhøjskolen i Århus Slide 18 af 51 Two types of communication

19 Ingeniørhøjskolen i Århus Slide 19 af 51 SOAP RPC Request Example SUNW

20 Ingeniørhøjskolen i Århus Slide 20 af 51 SOAP RPC Response Example 30.5

21 Ingeniørhøjskolen i Århus Slide 21 af 51 SOAP RPC composition I Information needed for a method call: 1.The URI of the target object (marked with red) SUNW

22 Ingeniørhøjskolen i Århus Slide 22 af 51 SOAP RPC composition II Information needed for a method call: 1.The URI of the target object 2.The Method Name SUNW

23 Ingeniørhøjskolen i Århus Slide 23 af 51 SOAP RPC composition III Information needed for a method call: 1.The URI of the target object 2.The Method Name 3.Parameters 4.Binding protocol (next slide) SUNW Name is not important

24 Ingeniørhøjskolen i Århus Slide 24 af 51 SOAP RPC composition IV: complete SOAP RPC Request POST /StockQuote HTTP/1.1 Host: Content-Type: text/xml; charset="utf-8" Content-Length: nnnn SOAPAction: "Some-URI" SUNW HTTP Encoding Name- space STEP 4: BINDING TO PROTOCOL

25 Ingeniørhøjskolen i Århus Slide 25 af 51 Request to HelloWorld.jws Input parameters type string HTTP Post Call HTTP Host Target Method name

26 Ingeniørhøjskolen i Århus Slide 26 af 51 … and the HTTP Response from Server HTTP Response Method Response Parameter value Parameter name Apache Tomcat Server Responding

27 Ingeniørhøjskolen i Århus Slide 27 af 51 In addition There is: –Response handling –Fault handling

28 Ingeniørhøjskolen i Århus Slide 28 af 51 Lucky us Luckly we dont have to understand SOAP –So it does not really matter that it is somewhat complex –Unless we want to develop clients that do not have a SOAP API –... But then we need an XML parser … and more … –BUT IT IS POSSIBLE and might be feasible

29 Ingeniørhøjskolen i Århus Slide 29 af 51 How to make a Web service with SOAP You need an application or API capable of supporting: –Communication over the Internet (HTTP) –Security (SSL) –XML Parsing capabilities –… Two examples of Application Servers with support: –Apache Tomcat Application Server with AXIS –Microsoft Internet Information Server JAX-RPC (JSR-101) –Java™ API for XML-based RPC –Need to implement features manually

30 Ingeniørhøjskolen i Århus Slide 30 af 51 Issues with SOAP –Lack of business semantics –Insufficient functionality for business operations –Security –Reliability –Under development Low performance

31 Ingeniørhøjskolen i Århus Slide 31 af 51 WSDL WSDL is used for describing WebServices

32 Ingeniørhøjskolen i Århus Slide 32 af 51 What is WSDL? XML language for describing web services Web service is described as – A set of communication endpoints (ports) Endpoint is made of –Abstract definitions of operations and messages –Concrete binding to networking protocol and message format

33 Ingeniørhøjskolen i Århus Slide 33 af 51 Why WSDL? Enables automation of communication details between communicating partners –Machines can read WSDL –Machines can invoke a service defined in WSDL Note that WSDL defines only low-level aspects of Web services, however other technologies might follow … –Security –Transactions –Persistency

34 Ingeniørhøjskolen i Århus Slide 34 af 51 WSDL Document Example Simple service providing stock quotes A single operation called GetLastTradePrice Deployed using SOAP 1.1 over HTTP Request takes a ticker symbol of type string Response returns price as a float

35 Ingeniørhøjskolen i Århus Slide 35 af 51 WSDL Elements Types –Data type definitions –Used to describe exchanged messages –Uses W3C XML Schema as canonical type system

36 Ingeniørhøjskolen i Århus Slide 36 af 51 WSDL Example: Types

37 Ingeniørhøjskolen i Århus Slide 37 af 51 WSDL Elements Messages –Abstract, typed definitions of data being exchanged Operations –Abstract description of an action –Refers to input and output messages Port type –Collection of operations –Resembles a Class in OOPL

38 Ingeniørhøjskolen i Århus Slide 38 af 51 Example: Messages, Operation, Port type

39 Ingeniørhøjskolen i Århus Slide 39 af 51 WSDL Elements Binding –Concrete protocol and data format for a particular Port type –Example: SOAP 1.1, HTTP, MIME Port –Defines a single communication endpoint –Address for binding –URL for HTTP, address for SMTP Service –Aggregate set of related ports

40 Ingeniørhøjskolen i Århus Slide 40 af 51 WSDL Elements

41 Ingeniørhøjskolen i Århus Slide 41 af 51 HelloWorld.jws?wsdl

42 Ingeniørhøjskolen i Århus Slide 42 af 51 Tools Generate WSDL document from –existing Java classes or EJB components –AXIS: Java2WSDL Generate SOAP messages from –WSDL document (via client stub and server skeleton) JAX-RPC, Forte for Java, JBuilder, JDeveloper

43 Ingeniørhøjskolen i Århus Slide 43 af 51 UDDI UDDI for publishing & discovery – the SOA

44 Ingeniørhøjskolen i Århus Slide 44 af 51 UDDI Universel Descrition, Discovery & Integration UDDI defines a scheme to publish and discover information about Webservices Programmatic registration and discovery business entities and their Webservices Based on SOAP, HTTP, XML Registry data –Business registrations –Service type definitions

45 Ingeniørhøjskolen i Århus Slide 45 af 51 Registration “ White pages” – Address, contact, and known identifiers “ Yellow pages” –industrial categorizations –Industry: NAICS (Industry codes - US Govt.) –Product/Services: UN/SPSC (ECMA) –Location: Geographical taxonomy “ Green pages” –technical information about services

46 Ingeniørhøjskolen i Århus Slide 46 af 51 What uses UDDI? Tool building client (Service Consumer) –Browse or search registry –Create a service proxy Tool publishing the service –Generates WSDL –Construct UDDI entries Application that needs dynamic binding –Directly access UDDI –Query can be pre-generated

47 SOAP & Web Services in relation to Distributed Objects

48 Ingeniørhøjskolen i Århus Slide 48 af 51 SOAP and Distributed Objects SOAP in it self has nothing to do with objects There probably is SOAP API’s for C and COBOL The trick is the supporting API’s converting objects to WSDL and SOAP for serialization across the network Using the Proxy Pattern for decoupling – perhaps with the Façade Pattern for larger granularity –Emmerich: Accessing distributed objects is expensive –Use larger granularity More on Architecture later in the course

49 Ingeniørhøjskolen i Århus Slide 49 af 51 Proxy Pattern (GoF version) Watch Client RealWatch ProxyWatchTestWatch setTime() Objects of RealWatch class are locateed on a different machine than the Client object. This is an example of Remote Proxy – which is an Architectural Pattern. from GoF abstract GoF: Gang Of Four (Design Pattern bog af Gamma m.fl.)

50 Ingeniørhøjskolen i Århus Slide 50 af 51 Proxy Pattern (B. Douglas version) Client Object SOAP Proxy Server object BD.s212 Client component Server component Proxy Pattern Client Server Proxy Proxy (= en stedfortræder) By encapsulating The SOAP communication in a Proxy, we have decoupled the Client Object from needing to know that it calls over The Internet. Thus making it easy to implement different Middleware and use the Server object locally We could do the same for The Server object

51 Ingeniørhøjskolen i Århus Slide 51 af 51 Façade Pattern (also GoF) Used for encapsulation and decoupling The entire Client Subsystem is decoupled from the server and a Client Proxy hides the SOAP implementation (also Server Proxy) This is known as Client Stubs & Server Skeletons The entire Client Subsystem is decoupled from the server and a Client Proxy hides the SOAP implementation (also Server Proxy) This is known as Client Stubs & Server Skeletons


Download ppt "Presentation 7: SOAP, WSDL & introduction to UDDI."

Similar presentations


Ads by Google