Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 8 - Web Services Web Services Architecture

Intelligent Business Integration Reference Guide

The UDDI invocation model is as follows:

1 You use the UDDI business registry (either via a Web interface or using the

inquiry API) to locate the business entity information for the business partner

advertising the web service.

2 You drill down to find the advertised web services and obtain the binding

templates (WSDL documents).

3 You prepare the program based on the WSDL specifications. Create a type tree

based on the WSDL document using the WSDL Importer in the Type Designer.

Then use the Map Designer to create a map that incorporates this type tree.

4 At runtime, the program invokes the web service as planned, using the binding

obtained from the WSDL document.

Web Services Architecture

There are three collaborators in the architecture of a web service: the provider,

consumer, and broker. These collaborators interact using the following three basic

operations:

♦ Publish: The provider publishes a web service (described by a WSDL

document) to the broker, which is typically a UDDI registry.

♦ Request: The consumer requests information from the broker about the web

service.

♦ Bind: The consumer binds its application to the web service. Now the

application can interact with the web service, invoking its methods via SOAP

requests.

By providing support for the importing of WSDL (WSDL Importer) and sending and

receiving of SOAP messages (SOAP and HTTP adapters), Mercator products fit into

this architecture as both a consumer and provider of web services.