Web Services and Registries Pilot Status

1
Web Services and Registries Pilot Status
Joseph M. Chiusano Booz Allen Hamilton
Federal CIO Council Emerging Technology
Subcommittee Emerging Components
Conference Washington, DC October 20, 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
Although often seen as competing, each registry
specification has a different primary focus

• I explained this concept in my 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.

6
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

7
Three-Tier Vision
8
The pilot began with a 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

• Pilot exists at Tier 3
• This vision is described in my August 2003 ebXML
  Forum article titled UDDI and ebXML Registry
  Three-Tier Vision

9
Tier 3s Reachthrough Capability involves
reaching through from one registry type to
another
Trading Partner 2
Trading Partner 1
Web Services Descriptions
ebXML Registry
10
The Pilot
11
A vast array of vendors and implementers are
participating in this pilot

• Participants
• Adobe (E-Forms)
• Amberpoint (Web Services Monitoring and
  Management)
• Blue Oxide (UDDI/ebXML Registry)
• IWay Software (ebXML Registry)
• Software AG (UDDI)
• SourceForge ebxmlrr (ebXML Registry)
• Systinet (UDDI)
• Yellow Dragon Software (ebXML Registry)
• Adobe will demonstrate an interface between an
  E-Form and a registry via Web Services
• Amberpoint will monitor the SOAP traffic between
  the registries

12
We are in the configuration stage

• Each product is being configured for
• Its interface with Amberpoint software
• Its interface with other registry type
• We anticipate an Operational Capability Demo
  (OCD) in the coming weeks
• We anticipate a live demo in early 2004, with
  use cases ranging from very simple to very
  complex

13
Questions?
14
Contact Information

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