 | Level: Introductory Yih-Shin Tan (ystan@us.ibm.com), Senior Technical Staff Member, IBM
Brad Topol (btopol@us.ibm.com), Senior Software Engineer, IBM
Vivekanand Vellanki (vellanki@us.ibm.com), Advisory Software Engineer, IBM
Jie Xing (jiexing@us.ibm.com), Advisory Software Engineer, IBM
01 Mar 2004 This series provides you with information on building a business service grid solution with a new Service Domain technology available from IBM alphaWorks. The series includes articles on how to implement business service grids, how to customize grid infrastructures, how to deploy a Service Domain, and in-depth discussions about selected topics within the Service Domain concept and toolkit. This page presents each article in the series, with the most recent first, for your convenience.
Business service grid, Part 7: Keeping informed
March 2004
Parts 1 - 6 of this series describe a service domain that represents a collection of comparable or related Web services through a common services entry point. A service domain applies autonomic computing principles for aggregating Web services and grid services. The service domain technology provides a service grid and can create, filter, discover, cluster, organize, select, route, recover, and switch Web services and grid services autonomically. Using service domain objects enables you to implement business solutions easily and quickly. These service domain objects instantiate multiple service instances into a virtual service, multiple virtual services into high-level virtual services, and so on. Operations of the service grid are based on rules, and deployment is through standard Web services. Service instance suppliers and consumers sign up under the Terms and Conditions provided. A service domain will automatically service consumer requests by using the pool of service suppliers registered. We then discuss how to access, invoke, and use service domains. In this article, we discuss how to keep up with the information that is available from the service domain. Why should you and why shouldn't you care about the information? We introduce several ways of using the information and discuss some approaches for optimizing its management.
Business service grid, Part 6: In operation
December 2003
A service domain applies autonomic computing principles for aggregating Web services and grid services. The service domain technology provides a service grid and can create, filter, discover, cluster, organize, select, route, recover, and switch Web services and grid services autonomically. Using service domain objects enables you to implement business solutions easily and quickly. These service domain objects instantiate multiple service instances into a virtual service, multiple virtual services into high-level virtual services, and so on. Operations of the service grid are based on rules, and deployment is through standard Web services. Service instance suppliers and consumers sign up under the Terms and Conditions provided. A service domain will automatically service consumer requests by utilizing the pool of registered service suppliers. In this article, we discuss how to invoke and access a service domain to start the operational phase.
Business service grid, Part 5: Setting up contracts
October 2003
A service domain represents a collection of comparable or related Web services through a common services entry point. It applies autonomic computing principles for aggregating Web services and grid services. The service domain technology provides a service grid and can create, filter, discover, cluster, organize, select, route, recover, and switch Web services and grid services autonomically. Part 1 of this series described how a service domain represents a collection of comparable or related Web services through a common services entry point. It applies autonomic computing principles for aggregating Web services and grid services. Part 2 used a sample business service grid scenario, gave an overview of implementing a service grid, and had a detailed discussion of service domain creation. Part 3 shows how the policy file can be configured for several facets of a service domain, including service level definitions, service selection, security, error recovery, event monitoring, and service mapping. Part 4 shows how to deploy a service domain into several platforms such as the Web Services Toolkit version 1.0, the Web Services Bus framework, and WebSphere Application Server version 5.0. The authors also describe how to publish a service domain to a public registry such as a UDDI registry or an Open Grid Services Architecture (OGSA) compliant registry. Now, in this article, part 5, we discuss how to register services with the service domain and how to offer the aggregates of these services to clients.
Business service grid, Part 4: Service Domain Deployment
July 2003
In this article, Part 4 of the series, the authors show how to deploy a service domain into several platforms such as the Web Services Toolkit version 1.0, the Web Services Bus framework, and WebSphere Application Server version 5.0. They also describe how to publish a Service Domain to a public registry such as a UDDI registry or an Open Grid Services Architecture (OGSA) compliant registry.
Business service grid, Part 3: Setting up rules
March 2003
In this article, Part 3 of the series, the authors show how the policy file can be configured for several facets of a Service Domain, including service level definitions, service selection, security, error recovery, event monitoring, and service mapping.
Business service grid, Part 2: Implementing a business service grid
February 2003
This article, Part 2 of the series, uses a sample business service grid scenario to show how service grids are used. The authors then provide an overview of the steps to implement a Service Domain. A detailed discussion of the first implementation step, Service Domain creation, is also included.
Business service grid, Part 1: Introduction
February 2003
Part 1 of this series gives you an overview of Service Domain architecture. A Service Domain represents a collection of comparable or related Web services through a common services entry point. It applies autonomic computing principles for aggregating Web services and grid services. The Service Domain technology provides a service grid and can create, filter, discover, cluster, organize, select, route, recover, and switch Web services and grid services autonomically.
About the authors | 
| | Yih-Shin Tan is a Senior Technical Staff Member of IBM Software Group. His areas of expertise include Web based system software architecture, analysis, design, and development, and he has been a frontier exploiter of emerging technologies. Currently he is the lead architect for Web services and grid computing integration technologies in the WebSphere Platform System House Advanced Design and Development organization. He has been instrumental in developing the Service Domain toolkit as a technology concept demonstration on IBM alphaWorks. You can contact Yih-Shin at ystan-at-us.ibm.com.
|
| 
| | Brad Topol is a senior software engineer for IBM in Research Triangle Park, NC in the WebSphere Platform System House Advanced Technology group. He received a Ph.D. in Computer Science from the Georgia Institute of Technology in 1998. Currently, he is actively involved in advanced technology projects in the areas of Web services, grid computing, OGSA, and autonomic computing. You can contact Brad at btopol-at-us.ibm.com.
|
| 
| | Vivekanand Vellanki is involved in advanced technology projects in the areas of Web services, grid computing and autonomic computing. He received his Ph.D. in Computer Science from the Georgia Institute of Technology in 2001. His interests are distributed among computing, Web servers, and peer-to-peer computing. Vivek can be reached at vellanki-at-us.ibm.com.
|
| 
| | Jie Xing, an advisory software engineer, has been with IBM in Research Triangle Park, NC for one and half years. Currently he is involved in advanced technology projects in the areas of Web services, grid computing and autonomic computing. He received his Ph.D. in Operations Research in Computer Science from North Carolina State University in 2000, where his research interests were related to multiagent systems, distributed systems, and workflow. You can contact Jie at jiexing-at-us.ibm.com. |
Rate this page
| |
