Technical Progressive Seminar On Web Service Architecture

By Ayesha Faheem 08871A0509 Under the Supervision of K.Narahari Asst. Professor

 . It has an interface described in a machineprocessable format (specifically Web Services Description Language 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.What’s Web Service?  The "Web service“ defines as "a software system designed to support interoperable machine-to-machine interaction over a network".

This is a public working group note produced by the W3C Web Services Architecture Working Group. Web Service Architecture is an interoperability architecture it identifies those global elements of the global Web service network that are required in order to ensure interoperability between Web services. which is part of the W3C Web Services Activity.Web Service Architecture  Web service architecture identifies the functional component and defines the relationships among those components to affect the desired properties of the overall architecture.   .

Web Service Model  Operations in a Web Service Architecture ◦ Publish  Service descriptions need to be published in order for service requestor to find them ◦ Find  Service requestor retrieves a service description directly or queries the service registry for the service required ◦ Bind  Service requestor invokes or initiates an interaction with the service at runtime .

SOAP: Simple Object Access Protocol  What is SOAP? ◦ ◦ ◦ ◦ ◦ ◦ ◦ ◦ ◦ SOAP is a communication protocol SOAP is for communication between applications SOAP is a format for sending messages SOAP is designed to communicate via Internet SOAP is platform independent SOAP is language independent SOAP is based on XML SOAP is simple and extensible SOAP will be developed as a W3C standard .

SOAP Message Structure  Request and Response messages ◦ Request invokes a method on a remote object ◦ Response returns result of running the method Application-specific message vocabulary  SOAP specification defines an “envelop” ◦ “envelop” wraps the message itself ◦ Message is a different vocabulary ◦ Namespace prefix is used to distinguish the two parts SOAP Envelop vocabulary .

Web Services Description Language  What is WSDL? ◦ ◦ ◦ ◦ ◦ WSDL is written in XML WSDL is an XML document WSDL is used to describe Web services WSDL is also used to locate Web services WSDL is not yet a W3C standard  Operational information about the service ◦ Location of the service ◦ Service interface ◦ Implementation details for the service interface .

the operations that can be performed. and the messages that are involved  <message> element ◦ Defines the data elements of an operation ◦ consists of one or more parts. ◦ The parts can be compared to the parameters of a function call in a traditional programming language .WSDL Document Structure  <portType> element ◦ Defines a web service.

WSDL uses XML Schema syntax to define data types  <binding> element ◦ Defines the message format and communication protocols used by the web service .WSDL Document Structure  <types> element ◦ Defines the data type that are used by the web service ◦ For maximum platform neutrality.

HTTP. Discovery and Integration (UDDI)  What is UDDI? ◦ Directory service where businesses can register and search for Web services  Directory for storing information about web services  Directory of web service interfaces described by WSDL ◦ UDDI communicates via SOAP  What is UDDI Based On? ◦ Uses W3C Internet standards such as XML.Universal Description. and DNS protocols ◦ UDDI uses WSDL to describe interfaces to web services .

UDDI Roles and Operations  Service Registry ◦ Provides support for publishing and locating services ◦ Like telephone yellow pages  Service Provider ◦ Provides e-business services ◦ Publishes these services through a registry  Service requestor ◦ Finds required services via the Service Broker ◦ Binds to services via Service Provider .

Conclusion Web Services substitute for existing distributed computing model such as RPC. reliable message transmission) Efficient methods for composing Web Services . the following problems should be covered  ◦ ◦ ◦ ◦ Security Transaction Management QOS (ex..  To apply to real e-business application.

First Edition Morgan Kauffman Publishers.2003.  http://en. by James McGovern and Sameer Tyagi.wikipedia. Web Service for Information Extraction from the web.B Quafafou.References  “Java Web Service Architecture”.  e. .M.


Sign up to vote on this title
UsefulNot useful