Federal CIO Council XML Web Services Working Group

1
Web Services and Registries Pilot Proposal
Joseph M. Chiusano Booz Allen Hamilton
Federal CIO Council XML Web Services Working
Group Washington, DC July 22, 2003
2
Objective and Outcomes
3
The main objective of the Web Services and
Registries pilot is to demonstrate the
capability of UDDI and ebXML registries to
interoperate during Web Servicesbased
collaborations

• Secondary objectives are
• To demonstrate the capabilities of UDDI for Web
  Service description registration, maintenance,
  discovery
• To demonstrate and raise awareness of the
  capabilities of ebXML Registry for Web Service
  description registration, maintenance, discovery
• Planned outcome is
• A pilot report detailing the products utilized,
  use cases executed, and methodologies used
• Report can be circulated among various groups, to
  include
• Federal CIO Council XML Web Services Working
  Group
• OASIS E-Government TC
• OASIS/ebXML Registry TC
• OASIS UDDI TC

4
UDDI and ebXML Registry
5
The UDDI and ebXML registries are the most
prominent e-business registries in existence today

• An e-business registry is a software product that
  acts as an organizing focal point for the wealth
  of information and interactions that conducting
  e-business requires
• E-business registries are central to the
  execution of e-business because they allow for
  the registration, management, and discovery of
  those critical items that are crucial for the
  conduct of e-business
• While UDDI and ebXML registries have different
  primary focuses, they both have a common trait
  the capability to register Web services
  descriptions
• This proposed pilot will focus on this common
  aspect of UDDI and ebXML Registry

6
Over the past several years, there has been much
speculation as to which registry standard would
win out as the primary e-business registry
specification

• Such speculation is unwarranted each registry
  specification has a different primary focus
• Joseph Chiusano explains this concept in his
  April 2003 WebServices.org article titled UDDI
  and ebXML Registry A Co-Existence Paradigm
• In examining the primary focus of each
  registry, we consider that there are two general
  ways in which an e-business registry may be used
  for discovery and for collaboration. Both
  registries allow for the discovery of businesses,
  their Web Services, and the technical interfaces
  they make available. However, UDDI is focused
  exclusively on this discovery aspect, while ebXML
  Registry is focused on both discovery and
  collaboration.

7
The UDDI TC is in the process of producing a
Technical Note detailing how to enable automatic
discovery of ebXML framework components using UDDI

• Title UDDI as the registry for ebXML
  components
• This Technical Note does not address ebXML
  components registered in an ebXML Registry
• Components are addressed by URL
• Proposed pilot would extend the use cases in this
  Technical Note to assume ebXML components are
  registered in an ebXML registry
• Although it is possible to discover a UDDI
  registry from within an ebXML Registry, the
  OASIS/ebXML Registry TC has not yet produced a
  Technical Note on this capability

8
Although the UDDI and ebXML Registry information
models are vastly different, their
representations of Web services are very
architecturally similar

• These similarities will serve to facilitate
  interactions between UDDI and ebXML registry in
  terms of Web Services descriptions

9
The Version 3.0 specifications of UDDI and ebXML
Registry bring the two specifications closer than
ever in terms of features

• Examples
• Cooperating/Distributed Registries
• Event Notification/Publish-Subscribe
• Digital Signature Support
• HTTP Interface
• These similarities will also serve to facilitate
  interactions between UDDI and ebXML registry in
  terms of Web Services descriptions

10
UDDI and ebXML Registry Three Tier Vision
11
The following is a representation of my
Three-Tier Version for interoperability and
interaction between UDDI and ebXML registries
Tier 1 Seamless Federation of Registries
Tier 2 Local Representations/Publish Subscribe
Proposed Pilot

• Each Tier builds upon the previous Tier
• Proposed pilot exists at Tier 3

12
Tier 3s Reachthrough Capability involves
reaching through from one registry type to
another

• Scenario involves at least one trading partner
  with a UDDI registry and at least one with an
  ebXML registry
• Collaboration would involve Web Services
  descriptions from both registries
• The UDDI-enabled trading partner would register
  a pointer to the ebXML registry-enabled trading
  partners Web Services descriptions in their UDDI
  registry, and vice-versa
• Example
• An ebXML Collaboration Protocol Agreement (CPA)
  is created from two Collaboration Protocol
  Profiles (CPPs) that are maintained in an ebXML
  registry, and utilize a WSDL description that is
  maintained in a UDDI registry

13
Tier 3s Reachthrough Capability involves
reaching through from one registry type to
another (contd)
Trading Partner 2
Trading Partner 1
Web Services Descriptions
ebXML Registry
14
Tier 2s Local Representation/Publish
Subscribe allows each registry type to maintain
local representations of Web Services descriptions

• Local representations may be preferred by a
  registry host
• Gives a greater degree of control over the object
• Publish/Subscribe capabilities would be used to
  notify an ebXML registry/user of a change in the
  master version of a Web Services descriptions
  in the UDDI registry, and vice-versa

15
Tier 2s Local Representation/Publish
Subscribe allows each registry type to maintain
local representations of Web Services
descriptions (contd)
Trading Partner 2
Trading Partner 1
Publish/Subscribe Notifications Web Services
Descriptions
ebXML Registry
16
Tier 1 envisions a Seamless Federation of
Registries in which the registry type is
irrelevant for operations

• A federation can include both UDDI and ebXML
  registries

17
Tier 1 envisions a Seamless Federation of
Registries in which the registry type is
irrelevant for operations (contd)

• In addition to Tier 2 and Tier 1 capabilities,the
  following capabilities would exist
• Seamless Query Search for a Web Services
  description in any registry in a federation,
  regardless of registry type
• Seamless Synchronization Synchronization of Web
  Services descriptions between all registries in a
  federation, regardless of registry type
• Seamless Relocation Relocation of Web Services
  descriptions from one registry to another in a
  federation, regardless of registry type

18
Pilot Requirements
19
The following are the minimum requirements for
this proposed pilot

• Software Products
• 1 UDDI Version 3.0-compliant product
• 1 ebXML Registry Version 3.0-compliant product
• May include only the Web Services description
  registration and maintenance features
• Use Cases
• 1-2 Use Case Authors
• 1-2 Use Case Executors
• Documentation
• 1 Pilot Results Documenter
• Coordination
• 1 Pilot Coordinator

20
Questions?
21
Contact Information

• Joseph M. Chiusano
• Booz Allen Hamilton
• McLean, VA
• [phone]
• chiusano_joseph_at_bah.com