Web Services & UDDI

1. Web Services & UDDI

2. Web services are distributed components that communicate • using standard protocols such as Simple Object Access • Protocol (SOAP) and HTTP. • Web services exposes callable API functions, better known • as Web Methods over the Internet. • Web services publish details of their interface using XML • vocabulary called Web Services Description Language(WSDL).

3. WSDL describes the interface for the Web service. • WSDL is an XML-based vocabulary that describes the set • of SOAP messages that a Web service supports. • Every Web service has an associated WSDL file that • documents the Web methods including their arguments • and return types.

4. Generates a proxy class that can be used by the Web • service consumers for communicating with the Web • service. • .NET also provides a default service description screen that • summarizes the WSDL information in a readable format. • Automatic generation of XML based WSDL. • Avoids handling SOAP responses and requests.

5. The proxy class assembles the requests and responses • in the correct format. • Web services are stateless. • Web services are platform and language agnostic.

6. Universal Description, Discovery and Integration (UDDI) • is a specification for building distributed databases that • enable interested parties to “discover” each other’s • Web services. • Provides easy discovery, sharing, and reuse of Web • services and other programmable resources.

7. UDDI sites publish a pair of SOAP-based APIs : • Inquiry API • Publisher API . • UDDI services enables companies to run their own • private UDDI service for use on the corporate • intranet or extranet.

8. UDDI Services helps companies organize and • catalog programmatic resources. • The four core entities that you need to model when • developing UDDI services are: • Provide • Service • Binding • tModel

10. .NET provides high-level tools to query UDDI business • registries and generate wrapper classes that allow • them to place calls to the Web services.