1 / 63

SOA, Web Service In Grid Computing

SOA, Web Service In Grid Computing. Phạm Hùng Tiến 00708210 Đặng Hoài Đức 00708190. Agenda. Service Oriented Architecture Web Service Grid Service Open Grid Service Architecture(OGSA) Web Service Resource Framework. Service - What Is It?.

garth
Download Presentation

SOA, Web Service In Grid Computing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA, Web Service In Grid Computing Phạm Hùng Tiến 00708210 Đặng Hoài Đức 00708190

  2. Agenda • Service Oriented Architecture • Web Service • Grid Service • Open Grid Service Architecture(OGSA) • Web Service Resource Framework

  3. Service - What Is It? • An autonomous (business) system that accepts one or more requests and returns one or more responses via a set of published and well-defined interfaces

  4. Service - An example • Restaurant provides various kinds of food (services) to its customers according to their requests. • Shopping cart • Payment service • Order service • Checkout service

  5. Service - What Is Service Orientation? • A business-driven “modeling strategy” that defines the business functionality in terms of loosely coupled autonomous business systems (or services) that exchange information based on messages.

  6. Service - Tenets(1) • Boundaries Are Explicit • A well-defined and published public interface • Should be easy to consume • Provide fewer public interfaces • Don’t expose implementation details

  7. Service - Tenets (2) • Autonomous • Services are built and deployed independently of other services

  8. Service - Tenets (3) • Share the Schema and Contract, Not the Class • Schema = Data • Contract = Behavior • Services do not pass classes and types; they pass schemas and contracts

  9. Service - Tenets (4) • Service Compatibility Is Based on Policy • Structural compatibility is based on the contract (WSDL and optionally BPEL4WS) and the schema (XSD) • WS-Policy provides for additional, automated analysis of the service-assurance compatibility between services

  10. SOA - What Is It? • Service-Oriented Architecture (SOA) is a mechanism that enables organizations to facilitate communication between the systems running on multiple platforms • SOA is a collection of well-defined services, each individual service can be modified independently of other services to help respond to the ever-evolving market conditions of a business

  11. Service Registry Register Find Bind, Execute Service Consumer Service Provider SOA - Actors • Service Provider • Provides a stateless, location transparent business service • Service Registry • Allows service consumers to locate service providers that meet required criteria • Service Consumer • Uses service providers to complete business processes

  12. SOA - Benefits Business Benefits • Focus on Business Domain solutions • Leverage Existing Infrastructure • Agility Technical Benefits • Loose Coupling • Autonomous Service • Location Transparency • Late Binding

  13. SOA - An Example • Storage Service • Storing and retrieving data • Reserving space, monitoring status of storage service • Querying and defining the policies that govern who is allowed access the service. • Data Transfer Service • Provide operations for requesting the transfer of data from one storage service to another • Managing and monitoring such transfers • Querying and defining policies that govern how difference transfer requests are prioritized. • Troubleshooting Service

  14. SOA vs. Component-Based • The key difference is SOA provides a message-based approach based on open standards • SOA is platform independent

  15. SOA - Advantages of Using Messaging • Cross-platform • Asynchronous communications • Reliable communication • Thread management • Remote communication • Marshaling and Unmarshaling • End-to-end security

  16. Web Service • A web service is a programmable application component accessible via standard web protocols. • A Web service is a software system designed to support interoperable machine-to-machine interaction over a network • Just one kind of implementation of a service

  17. Web Service - Key Aspects • Standard protocol • HTTP, SMTP, FTP. • Service description • Need to describe their interfaces in detail so that a client knows how to “consume” the functionality provided by the service. • WSDL: Web Services Description Language. • Finding services • Users need to know what web services exist and where to find them so the clients can bind to them and use the functionality. • UDDI : Universal Discovery, Description, and Integration repositories

  18. Web Service - Protocol Stack

  19. Web Service SOAP - Simple Object Access Protocol • Lightweight communication protocol based on XML • Used to exchange structured and typed information between systems • Allows to invoke methods on remote machines without knowing specific details of the platform or software running on those machines

  20. Web Service - SOAP Characteristics • Extensible. • Works across a number of standardized underlying network protocols. • Independent of the underlying language or platform or programming model.

  21. Web Service - SOAP Message Structures

  22. SOAP Message -Sample • Method Signature int doubleAnInteger ( int numberToDouble ); • Request <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <ns1:doubleAnInteger xmlns:ns1="urn:MySoapServices"> <param1 xsi:type="xsd:int">123</param1> </ns1:doubleAnInteger> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

  23. SOAP Message -Sample • Response <?xml version="1.0" encoding="UTF-8" ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xsi=http://www.w3.org/1999/XMLSchema-instance xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <ns1:doubleAnIntegerResponse xmlns:ns1="urn:MySoapServices" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <return xsi:type="xsd:int">246</return> </ns1:doubleAnIntegerResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

  24. Web Service Application Web Service - Messaging Using SOAP SOAP SOAP Network protocols (HTTP …) Network protocols (HTTP …)

  25. Web Service WSDL-Web Service Description Language • Describes Service Endpoints • What are Endpoints ? • The entity that a client connects to using a specific protocol and data format when consuming a service

  26. Web Service - WDSL: An Overview

  27. Web Service- WDSL : An Example

  28. Web Service - How It Works?

  29. Agenda • Service Oriented Architecture • Web Service • Grid Service • Open Grid Service Architecture(OGSA) • Web Service Resource Framework

  30. Grid Service - What is Grid ? • Criteria for a Grid: • Coordinates resources that are not subject to centralized control. • Uses standard, open, general-purpose protocols and interfaces. • Delivers nontrivial qualities of service.

  31. Grid Service - What Is It? • Web services that are customized to grid environment: • HTTP, SOAP, XML, (G)WSDL

  32. Grid Service vs. Web Service • Transient in Nature (Lifetime, Migration) • Stateful Service • Service Data Elements (SDE) • Introspection • GWSDL Vs. WSDL • Standard Required Interfaces for all Services • Lifetime Management • Service Data Interaction • Interfaces Predefined for common (core) Services

  33. Agenda • Service Oriented Architecture • Web Service • GridService • Open Grid Service Architecture (OGSA) • Web Service Resource Framework

  34. OGSA – Open Grid Service Architecture • Grid Service • Builds on Web Service • Improves Web Service • How services are created? • How long they live? • How to manage faults? • How to manage long-lived state?

  35. OGSA - Core Elements

  36. OGSA OGSI – Open Grid Service Infrastructure • Grid service descriptions and instances • Service state, metadata, and introspection • Naming and name resolution • Two-level naming • Service life cycle • Fault types

  37. OSGAOGSI – Grid Service Descriptions and Instances • Description: gWSDL • GWSDL: portType extension <gwsdl:portType name="MathPortType“ extends="ogsi:GridService"> </gwsdl:portType> • Service Data • Instance  Transient Service • Create • Destroy

  38. OGSA OGSI – Service Data • Standard WSDL has no formalized concept of service state • OGSI addresses these issues by defining WSDL extensions that allow for the explicit declaration of publicly visible state associated with an interface (called service data), and by defining standard operations for accessing (via both queries and subscriptions) that state • Accessing Service Data • Pull Mode • Push Mode( Subscription)

  39. OGSA OGSI – Service Data

  40. OGSA OGSI – Naming • Dynamic & Stateful  Distinguish one dynamically created service instance from another  Naming • Allows Grid Services to be upgraded during their lifetime (change protocol, add new protocol,…) • Two level Naming • Grid Service Handle (GHS)  Mapped by Handle Resolution Service • No protocol, no protocol binding, no network address • Invariant • Grid Service Reference (GSR) • Use to send requests • Change over service’s lifetime

  41. OGSA OGSI – Service Life Cycle • Negotiating an initial lifetime • Explicit termination • Requesting a lifetime modification • A client requests a lifetime modification by directing keep-alive messages • The client sends periodic keep-alive requests to indicate its continued interest in the service • What happens next?

  42. OGSA OGSI – Service Life Cycle(cont) • One of three things happens: • The transfer completes, and the file transfer service instance terminates. • The client fails, and its failure to send further keepalive messages leads to the destruction of the transfer service instance once its lifetime expires. • The client decides that it is no longer interested in the transfer and, to conserve resources, performs an explicit destroy of the transfer service instance.

  43. OGSA OGSI – Fault Model • Define common approach for conveying fault information from operations. • Comprises a standard XSD type, ogsi:FaultType • Original service • Time stamp

  44. OGSA OGSI – Service Groups • Organizing group of service instances • Why? • Someone want to group service instances together

  45. OGSA - Core Services • Address such fundamental issues • Name resolution and discovery • HandleResolver interface • Service domains • Security • Policy • Messaging, queuing, and logging • Events • For interoperability • Metering and accounting • Collect, deliver, store, and manage information about resource usage

  46. OGSA Data and Information Services • Data naming and access • Replication • Tracking, discovering, and performing replication of data resources. • Metadata and provenance • Describing and tracking how data are created • Regenerate data on demand

  47. OGSAResource and Service Management • Provisioning and resource management • Negotiating between resource consumers and resource providers for dynamic resource allocation • Service orchestration • Transactions • Administration and deployment

  48. OGSA and GT3

  49. Agenda • Service Oriented Architecture • Web Service • GridService • Open Grid Service Architecture (OGSA) • Web Service Resource Framework

  50. WSRF – Web Service Resource Framework

More Related