Web Services: A Distributed Component-Based Computing Architecture

1. 웹 서비스 개요

2. 중앙 집중 형 컴퓨팅

3. 분산 컴퓨팅 (2-Tier)

4. 분산 컴퓨팅 (n-Tier)

5. 컴포넌트(Component)

6. 컴포넌트(Component)

7. 컴포넌트(Component)

8. 컴포넌트(Component)

9. 비즈니스 컴포넌트(Business Components)

10. Component based Architecture J2EE Architecture

11. Distributed Components

12. Web Services New services provided by various Web service combinations

13. Protocol A protocol is like an alphabet or dictionary. It allows you to translate things. A protocol is open if the "translator guide" is available to anyone. It means that you can easily build a software that talk and understand this protocol. A closed protocol is a protocol for which the "translator guide" is not available. It means that only the company who developed the protocol can use it and build software using it.

14. Web Service

15. UDDI (Universal Description, Discovery and Integration) UDDI Structure

16. UDDI Messages Flow of UDDI messages between Client and Registry

17. How UDDI Works

18. WSDL (Web Service Description Language) Role of WSDL in Web service use

19. WSDL (Web Service Description Language) Composition of a WSDL document, including Web service URL in implementation component

20. WSDL Document Data structures and data types are defined or referenced The logic encapsulated by the service is divided up and made available through service operations Specific messaging requirements are established Naming conventions are applied to the service interface itself

21. SOAP (Simple Object Access Protocol) SOAP's features allow communication with Web services even if they are protected by firewalls

22. SOAP (Simple Object Access Protocol)

23. XML (eXtensible Markup Language)

24. 웹 서비스? 웹 환경에서의 분산 컴포넌트 기반 컴퓨팅 아키텍처!

25. Case Study This case study develops a web application that accepts place names, and returns a map showing a road route between the two places. Traditional Application Design

26. Case Study This case study develops a web application that accepts place names, and returns a map showing a road route between the two places. Application Design using a Web Service Architecture • The development of this application has resulted in the deployment of a number of reusable services that can initiate the development of other applications • The architecture is scalable: even if all services were initially deployed on a single computer, if the server is swamped by heavy use, services can easily be migrated to different computers • The most suitable participant can provide the back-end services (e.g. the Atlas of Canada can provide the server that provides the base map).

27. Appendix

28. Technologies • XML (eXtensible Markup Language) • markup language that underlies most of the specifications used for Web services.   • SOAP (Simple Object Access Protocol) • A network, transport, and programming language-neutral protocol that allows a client to call a remote service. The message format is XML. • WSDL (Web services description language) • An XML-based interface and implementation description language. The service provider uses a WSDL document in order to specify the operations a Web service provides.  • UDDI (universal description, discovery, and integration) • Both a client-side API and a SOAP-based server implementation that can be used to store and retrieve information on service providers and Web services.

29. How it works • A Web Service is a URL-addressable software resource that performs functions (or a function). • Web Services communicate using standard protocol known as SOAP (Simple Object Access Protocol). • A Web Service is located by its listing in a Universal Discovery, Description and Integration (UDDI) directory.

30. Characteristics • A Web Service is accessible over the Web. • Web Services communicate using platform-independent and language-neutral Web protocols. • A Web Service provides an interface that can be called from another program. • A Web Service is registered and can be located through a Web Service Registry. • Web Services support loosely coupled connections between systems.

31. What are Web Services good for? Integration • In a lot of organizations, the data and logic of one application are basically useless to other applications. When an application and its data are isolated from other applications, we often say that they are in “silos.” • Web Services are better at sharing data and functions. The result is that the “silos” come down, and previously isolated systems can talk to each other.

32. What are they good for? Access • Web Services are especially good at providing access through different interfaces. • A Web Service can have a dedicated client application, but it can also be readily accessed through browsers, wireless devices, voice-activated interfaces, and so on. • Adding new access methods is much simpler than with a traditional application.

33. What are they good for? Flexibility • One of the more important innovations in Web Services is “machine-to-machine communications.” • This means that a Web Service can ask another Web Service to do something, and that Web Service can ask another Web Service to do something, and so on. • In the future, many Web Services will really just be aggregations of other Web Services.

34. What are they good for? Application Assembly • Future applications will be assembled from a diverse group of web services, aggregating functionality. • Reusability is extended to the execution level, versus reusability from just the design and construction level.