ZwiftBooks uses a Web services repository to list its offerings
Book delivery service, It must
Decide on the service it wants to provide
Pick a registry (or registries) for uploading its information
Decide how to list its service at the registry
Define explicitly how users can connect to its service
Deciding on a Service
The first step is to decide what aspects of the business ZwiftBooks wants to expose to potential clients.
Picking a Registry
There are currently several registries implemented by various software vendors.
ZwiftBooks selects SuperReg, a registry run by a major Web services company that is known to get lots of traffic.
Deciding How to List
An important issue for ZwiftBooks is how is get discovered on the registry.
Table outlines the options for storing information in a UDDI repository.
Web services registries support white, yellow, and green pages.
Of course, ZwiftBooks will be in the white pages under "Z,".
What ZwiftBooks needs is to list itself by category, just like in the conventional yellow pages. A logical place would probably be "Books." But is that enough?
Individuals and software agents will search repositories.
Remember, Web services is intended for computer-to-computer interactions.
There may be a human on the other end of the computer trying to find a book service,
ZwiftBooks needs to think about how to make itself attractive to computer-based agents trolling the Web for business partners.
Is ZwiftBooks prepared to deliver book information based on industry standards? If so, then maybe ZwiftBooks is worth a further look; if not, it's time for the robot to move on.
Web services yellow pages will list companies according to conformant standards.
What will be important in attracting software agents
Thus, instead of listing itself just under "Books" in the yellow pages, ZwiftBooks may also want to list itself as conformant to the International Book Exchange Consortium or whatever standards it is prepared to abide by.
Potential customers and partners can at least know in advance that it is possible to do business with ZwiftBooks according to their own processes and procedures.
Defining How to Connect
The final step for ZwiftBooks is to place an entry into the green pages that describes how to connect to and query the ZwiftBooks server.
To do this ZwiftBooks prepares a WSDL document using WSDL's XML syntax.
Operation
Publish: How the provider of Web services registers itself
Directory
White pages: Name, address, telephone number, and other contact information of a given business
Information
Business information: A businessEntity object contains information about services, categories, contacts, URLs, and other things necessary to interact with a given business
Operation
Find: How an application finds a particular Web service
Directory
Yellow pages: Categories of businesses based on existing (nonelectronic) standards
Information
Service information: Describes a group of Web services. These are contained in a businessService object.
Operation
Bind: How an application connects to and interacts with Web services after it's been found
Directory
Green pages: Technical information about the Web services provided by a given business
Information
Binding information: The technical details necessary to invoke Web services. This includes URLs, information about method names, argument types, and so on. The bindingTemplate object represents this data.
Service specification detail: This is metadata about the various specifications implemented by a given Web service. These are called tModels in the UDDI specification
No comments:
Post a Comment