Registry Use Model

printer-friendly version of this section  Print  e-mail this section  E-Mail  add a public, group or private note  Add Note  add a bookmark about this section  Add Bookmark    

Java APIs for XML Kick Start
By Aoyon Chowdhury, Parag Choudhary

Table of Contents
Chapter 9.  Registry Fundamentals


A registry has two types of users: sellers and buyers. A seller is an organization that creates a Web service and publishes it in the registry. A buyer is an organization that queries the registry to find and engage the seller in a business collaboration.

Figure 9.1 shows how seller and buyer organizations use a registry to engage in B2B collaborations.

Figure 9.1. Registry use model.

graphics/09fig01.gif

First, a vertical standards organization such as RosettaNet defines a specification for a particular business process. These specifications include information such as the XML structure that is to be followed by the organizations that use the specification. This ensures that organizations involved in the business engagement have a common understanding of the documents that are exchanged in the B2B communication. These specifications are then submitted to the registry.

A seller company queries the registry for a specification applicable to its business domain. Upon finding the necessary information, the seller company downloads it. The seller company also downloads the core components that define the XML elements used in business documents, such as address, contact, and so on.

Using the downloaded specifications and the core components, the seller company then develops the necessary Web service(s). After the Web services have been developed at the seller's site, the seller registers the information about itself and the services it provides into the registry. To ensure that buyers can easily discover the services and products offered by the seller, the seller organization can also choose to classify the products and services it offers under different classifications and concepts.

Next, the buyer company connects to the registry and browses to find the required services. After it finds the required services, it downloads the specifications and core components, and similar to the seller company, builds an application that uses these standards and components. This is important, because the buyer and seller can only do business when they understand each other's language, which is facilitated by following the same standards and core components.

After the buyer company has created its local system, it negotiates with the seller company on the chosen collaborative process and begins exchanging the business documents in the form of XML documents.


printer-friendly version of this section  Print  e-mail this section  E-Mail  add a public, group or private note  Add Note  add a bookmark about this section  Add Bookmark    
Top

[0672324342/ch09lev1sec3]

 
 


JavaT APIs for XML Kick Start
JAX: Java APIs for XML Kick Start
ISBN: 0672324342
EAN: 2147483647
Year: 2002
Pages: 133

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net