UDDI Demo at XML 2003 conference: work team results

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

Title: UDDI Demo at XML 2003 conference: work team results

All,

The work team for the preparation of the scenario description (see CC field for a list of members) met last week and created a draft scenario description with an accompanying diagram. Please find our deliverables below so that we can discuss them at today's TC meeting and proceed with the submission to OASIS management.

Thanks,
 Claus

---------------------------

Technical deployment model
The scenario involves at least 3 UDDI registries and at least 2 UDDI client applications so that at least six interactions can be demoed. This demonstrates the need for the UDDI standard and demonstrates that all clients and servers conform to the UDDI specification.

UDDI Version 2 is demonstrated. Eventually, the "Using WSDL in a UDDI registry" TN, Version 2 is demonstrated.

Business scenario
A supply chain scenario is demonstrated (see attached diagram). The UDDI clients are part of purchasing applications (representing different companies from a certain industry, e.g. car manufacturers), the UDDI registries are part of private exchanges (representing communities from different industry verticals, e.g. tire industry, plastics industry, paintings industry). The basic assumption is that the car manufacturers have a business relationship (as a customer) with the private exchanges so that they can use their (UDDI) services.

The car manufacturers use the UDDI inquiry APIs that are provided by the private exchanges to
  a) discover updated information about their known suppliers and the Web services they use and
  b) dynamically discover new suppliers and their Web services.
The second use case is more appropriate in the early steps of the overall supply chain, such as for using Web services to request product catalogs, including terms and conditions for offered products. It can be used, for example, to demonstrate dynamic aggregation of product catalogs (provided that the catalogs are accessible over the same Web service type, a.k.a. tModel). The queries are parametrized by the product type, and/or Web service type in order to find suitable suppliers and Web services. The category systems and Web service types may be specific to the industry vertical of the different UDDI registries and may also indicate additional characteristics, such as whether the Web services are in test or production mode.

The scenario also covers the UDDI publication API in that the automotive suppliers each have a business relationship (as a supplier) with some of the private exchanges so that they can use their (UDDI) services to update information about themselves and the Web services they offer. In particular, updates are demonstrated that make the suppliers' UDDI registrations visible to the manufacturers' inquiries, e.g. by categorizing the businessEntity accordingly.

<<UDDI@XML2003Scenario.PNG>>

UDDI@XML2003Scenario.PNG