wishmaster
CJSDN高级会员
发贴: 942
积分: 62
|
于 2002-07-21 03:17
A Web service is an interface that describes a collection of operations that are network accessible through standardized XML messaging. IBM's Web Services Toolkit for dynamic e-business (WSTK) is a collection of preview technologies that allow you to start experimenting with Web services. This tutorial is designed to walk you through the process of designing, deploying, and utilizing services implemented with the Web Services Toolkit. For the benefit of those of you who have not yet had a chance to download and install the WSTK, I've included a section that briefly describes the process of initially setting up the toolkit and preparing the environment for use. Before you can complete this tutorial, you must have the following running or installed on your system: IBM Web Services Toolkit Version 3.1 Windows 2000 (with Service Pack 2 or higher), Windows XP, or Linux JDK 1.3 or higher Internet Explorer 5.0 (or higher) or Netscape 4.5 (or higher) The Web services architecture page 1 of 5 The Web services architecture describes a framework in which e-business services can be described, published, discovered, and invoked dynamically in a distributed computing environment. This architecture defines four primary artifacts (whose names are marked in boldface in the next two paragraphs) and three standard operations that govern how those artifacts interact with one another. At the core of the Web services model is the notion of a service, which is defined as a collection of operations that carry out some type of task, such as ordering a book or translating a letter. Within the context of Web services, a service can be described, discovered, and invoked using standard XML technologies such as SOAP, WSDL, and UDDI. Services are implemented and published by service providers. They are discovered and invoked by service requesters. Information about a service may be kept within a service registry. The following diagram illustrates how these three artifacts interact with one another. Figure 1: Service providers, requesters and brokers From a business perspective, the service provider is the owner of the service. From a technical perspective, it is the platform that provides access to the service. Likewise, the service requester is both the business that requires a particular function to be fulfilled and the tools necessary for discovering and invoking a service. The three fundamental operations, which are shown in the diagram above, can be described in the following ways: Publish: Performed by the service provider to advertise the existence and capabilities of a service. Find: Performed by the service requester to locate a service that meets a particular need or fits technology fingerprint. Bind: Performed by the service requester to invoke the service being provided by the service provider.
|