Anne, My understanding about registry in our discussion is that it stores info about services (could be COM objects also) not services themselves. Three types of info: properties/location of servicies and regulations of how to use the services.
What you said "information exchange among the diverse set of systems used to manage communications and message flow at runtime" is message managing function that is an entirely different issue. I think that Microsoft and IBM have different solutions regarding reliable messaging. Do not understand you here. I guess that repositories are used to store services Internet addressible referenced by a registry. A registry could refer to services in local and remote repositories. Registry could be used design time as well as run time. So information in registry could be consumed by both human and programs. Jerry --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Jerry, > > That depends on which product you buy. > > I prefer to differentiate registries from > repositories, although many vendors combine the two into a single product. A registry's primary role is > to enable information exchange among the diverse set > of systems used to manage communications and message flow at runtime (e.g., platforms, ESBs, > XML gateways, management agents, mediation systems, > etc). Given that an orgainzation will almost certainly use multiple systems to implement a > services infrastructure, it's essential that these > systems have a standard means to exchange information related to metadata, policies, access points, routing rules, performance, incidents, SLAs, etc. A UDDI-compliant registry with it's standard data model and protocol provides the means to enable this information exchange. > > Note that a registry acts as an index to > information. The only information > maintained in a registry is properties (using a > name/value pair system called a keyedReference), short description fields, and pointers to more > information. More comprehensive information, such as > schemas, WSDLs, BPEL scripts, documentation, code, etc, should be maintained in a separate repository. > > Most registry products implement the UDDI > specification, which defines both > a data model (via XML Schema) and a protocol (via > WSDL and SOAP APIs) for interfacing with the registry. I view full support for the UDDI v3 > specification, including optional features, such as > the subscription and value set APIs, as a required feature for a registry. > > Registries that fully implement UDDI v3 include HP > Systinet, webMethods Infravio, SOA Software Workbench, and Software AG CentraSite. BEA, Oracle, > and Tibco resell/OEM the Systinet registry as BEA > AquaLogic Service Registry, Oracle Registry (included with Oracle AS,Oracle ESB, and Oracle > SOA Suite), and Tibco Matrix (which is a package > containing Systinet Registry and AmberPoint WSM). > > Registries/repositories that do not fully implement > the UDDI v3 spec include IBM's UDDI implementation (included with WAS v6 --it supports the required > features of UDDI v3, but not the optional features), > IBM WebSphere Registry and Repository (WSRR - it does not support UDDI), Sun's registry/repository > (part of JES -- it supports the UDDI v3 inquiry API > only), BEA Repository (formerly Flashline -- it supports the UDDI v3 inquiry API only), > LogicLibrary (it does not support UDDI), Microsoft > Enterprise UDDI Services (included with Windows Server 2003 -- it supports UDDI v2), and Apache jUDDI > (it supports UDDI v2). > > A growing number of registry products also provide > repository features, and some products are stand-alone repositories (not really registries) -- > although the exact set of repository features varies > significantly among the products. Most registry/repository products provide > content management and maybe version control of various XML artifacts (e.g., WSDL, XML Schema, > XSLT, etc). Some repositories also support a number > of governance capabilities. Some provide lifecycle management of these artifacts with > built-in processes to manage transitions between > lifecycle stages. Some > provide automatic discovery and management of > relationships and dependencies > among artifacts. Some provide extensive reporting > facilities that support > impact analysis, metrics management, and more. Some > provide the means to > define policies, group policies, associate policies > with artifacts, and > automatically test artifacts for compliance with > policies (on-demand or > during lifecycle transitions). Some provide the > means to define and manage > contracts between service consumers and service > providers. > > Given the kind of information you might want to > capture in a repository, you > probably don't want to constrain the data model to > the one defined by UDDI. > And open content model makes the repository much > more extensible and > valuable. HP Systinet, IBM WSRR, BEA Repository > (i.e., Flashline), and > LogicLibrary support an extensible, open content > model. All four systems support a variety of content management and governance features, but only HP Systinet also fully supports UDDI. (HP Systinet > maintains two separate but synchronized data stores -- a UDDI v3 compliant registry and a separate > repository with an open content model). > > Infravio, SOA Software, and Software AG provide > combined registry/repository products which extend the UDDI data model to also support content management > and various other capabilities. The Infravio product > offers more governance features than the others. The data models do not offer the kind of > flexibility available with HP, IBM, BEA, and Logic > Library. > > Anne > > On 2/7/07, Jerry Zhu <[EMAIL PROTECTED]> wrote: > > > > Anne, > > > > Thanks for the info. > > > > You said that UDDI is a protocol talking to > registry. You mentioned three things: registry, repository, and protocol talking to registry. > > > > If I implement SOA, do I need to buy all three > things from three vendors? > > > > Thanks > > > > Jerry ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited
