In light of Service Oriented Architecture, we always tend to speak about Web Services. In the stakeholder matrix we have Service Providers, folks who provides a particular type of Service and then we have people who consume these services and are tagged as Service Consumers. While the consumer need not have to hard wire any calls to access these services, so we typically define a mechanism wherein the provider keep on building the services and consumer seamlessly consuming these services.
UDDI as the Universal Directory
Producing and Consuming of services are simply based on certain standards which are accepted industry wide. When a Service Provider produces a new service then they need to notify about this at a central place, typically a repository, which the Service Consumer query (based on the type of service they are looking for). Universal Description, Discovery and Integration can be looked as a place where business and its service related information can be parked an access. UDDI is based on industry standard which includes HTTP, XML and SOAP. The business registery consist of information which are classified into three categories viz. UDDI White Pages, UDDI Yellow Pages and UDDI Green Pages.
The generic process of publishing a Service, its related information and process of querying a repository can be viewed as follows:
Web Service Description Language
Popularly known as WSDL, this forms the basis of a Web Service. From the Service Provider perspective, the steps are to develop a service and publish it on a Universal Directory. From the Service Consumer perspective, the steps involved are to query such Universal Repository and collate information about the requisite service and how to access them. Once the access information are collected, the Service Consumer connects with Service Provider and consumes their Web Service. The communications protocol are based around SOAP and XML and the entire process can be viewed as follows:
No comments:
Post a Comment