Web Services - SPLessons

Web Services Architecture

Home > Lesson > Chapter 4
SPLessons 5 Steps, 3 Clicks
5 Steps - 3 Clicks

Web Services Architecture

Webservices Architecture

shape Description

A web service is an interface that depicts an accumulation of operations that are system open through institutionalized XML informing. A Web service is portrayed utilizing a standard, formal XML data, known as service description. It covers the subtle elements important to associate with the service, including message designs, transport conventions, and area. The interface shrouds the execution subtle elements of the service, permitting it to be utilized freely of the equipment or programming stage on which it is actualized furthermore autonomously of the programming dialect in which it is composed. This permits and supports Web Services-based applications to be inexactly coupled, part arranged, cross-innovation executions. The following is the architecture of the web services.

shape Web Services Architecture

The following diagram shows the architecture of the web services.

Modules In Webservices Architecture

shape Description

The following are the various modules in web services architecture.

Service provider

The service provider is the head of the service from a business strategy, this is the base that hosts access to the service from the architectural perspective.

Service requestor

From a business point of view, this is the business that needs Service requestor. certain capacities to be fulfilled. From an architectural point of view, this is the application that is searching for and conjuring or starting a connection with any service. The service requestor part can be played by a program driven by a program without a UI.

Service registry

Service registry is a searchable registry of service depictions where benefit Service registry. suppliers distribute their administration(service) depictions. Service requestors discover benefits(services) and get restricting data for administrations amid advancement for static authoritative, dynamic binding.

Operations Of Web Service Architecture

shape Description

The following are the operations of web services architecture.

Publish

To get availability, a service description should be distributed so that the service requestor can discover it. Where it is distributed can shift contingent on the prerequisites of the application

Find

The service requestor recovers a service description straightforwardly Find. on the other hand querying the service registry for the sort of service needed. The find operation may be gathered in two diverse lifecycle stages for the service requestor at configuration time to recover the service interface portrayal for program improvement.

Bind

A service should be summoned. In the case of bind operation the service requestor conjures or starts an association with the service at dynamic utilizing the coupling(binding) points of interest in the service portrayal to find, contact, summon the service.

WSDL And UDDI

shape Description

The UDDI is a distributed registry of web services, it is an open framework and platform independent, UDDI uses RMI and SOAP to communicate, UDDI also uses WSDL. UDDI also a XML based standard. The UDDI stands for Universal Description Discovery and Integration. It will interact with the SOAP, UDDI will use WSDL to provide the interfaces for the web services. The WSDL is called as wiz-dull, where SOAP and UDDI uses WSDL protocol, the definitions of WSDL are used to describe web services and it is also a XML based registry. The functionality of WSDL is how to authenticate a web service and to know the operations performed by the web services and WSDL used by SOAP to provide data over the network with the help of HTTP.

Summary

shape Key Points

  • Service and Service descriptor are the artifacts of the web services.
  • WSDL is also pronounced as wiz-dull.
  • SOAP and UDDI will use WSDL protocol to exchange the information.