B2B Integration : A Practical Guide to Collaborative E-commerce

Web Services 335
According to the technical specifications made available by IBM and
Microsoft, UDDI-based Web services can be created using WSDL by
the following steps:
1. Create the WSDL service interface definition. Typically, industry
groups will define a set of service types and describe them with one
or more service interface definition WSDL documents. The service
interface definition will include service interfaces and protocol
bindings and will be made publicly available. The WSDL service
interface definitions are then registered as UDDI tModels; the
overviewDoc field in each new tModel will point to the corresponding
WSDL document.
2. Build services that conform to the industry standard service definitions.
To do so, retrieve the tModel description of the industry standard
definition and (following the overviewDoc link) obtain the
corresponding WSDL definition document.
3. Deploy and register the new service in the UDDI repository. To do
so, create a UDDI businessService data structure and then register it.
11.6. Web Services Flow Language (WSFL)
The Web Services Flow Language (WSFL) is an XML language for the
description of Web services compositions. It provides the ability to
compose Web services together, describe business processes, create
workflows and describe overall interactions between varying Web
services with no specified sequence. It provides a specification for
implementing business process models, using Web services architecture,
and is used for creating XML-based representation of business models.
WSFL is layered on top of the WSDL. WSDL describes Web
services endpoints where individual business operations can be accessed,
whereas WSFL uses WSDL for the description of service interfaces and
their protocol bindings.
11.7. Putting Everything Together
After having discussed all the components of Web services, let's try to
redefine them. A Web service is a modular application that can be: