Method for middleware assisted system integration in a federated environment

• US 7,519,711 B2
• Filed: 06/15/2006
• Issued: 04/14/2009
• Est. Priority Date: 06/15/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mohindra, Ajay, Naik, Vijay K.
• Primary Examiner(s): Vaughn, Jr.; William C
• Assistant Examiner(s): Shingles; Kristie D
• Application Number:
  US11/453,507
• Publication Number:
  US 20070294405A1
• Time in Patent Office: 1,034 Days
• Field of Search: 709/223, 709/226
• US Class Current: 709/226
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A computer implemented method is provided for instantiating a service on a network. A service infrastructure manager determines whether a service is available at a requested quality of service in response to receiving a request for the service that specifies the quality of service. The service infrastructure manager performs an analysis of components associated with the service to identify resources needed to create the service in response to the service being unavailable at the requested quality of service. Based on the analysis, the service infrastructure manager allocates resources to support the service and instantiates the service at the requested quality of service after the resources have been allocated.

Claims

1. A computer implemented method for instantiating a service on a network, the method comprising:

responsive to service infrastructure manager middleware receiving a request for the service at a quality of service via the network, determining whether the service is available at the requested quality of service by the service infrastructure manager middleware, wherein requests for services are routed to the service infrastructure manager middleware prior to the requests being passed to target hosting services to ensure that the target hosting services are ready and capable of providing the services at requested quality of services prior to the requests arriving at the target hosting services, and wherein the service infrastructure manager middleware includes a service state and configuration repository, an analysis and planning engine, a configuration engine, a deployment engine, and a monitoring engine that initiate steps leading to configuration, allocation, deployment, and testing of components that comprise the service when the service is unavailable at the requested quality of service, and wherein the service state and configuration repository includes an object for each deployable and deployed service, and wherein the analysis and planning engine performs dependency analysis of the components that comprise the service and generates a dependency graph to enable the service at a desired state, and wherein the configuration engine examines allocated components and generates a configuration dependency graph that defines an order in which the allocated components are to be deployed and configured, and wherein the deployment engine uses the configuration dependency graph and the allocated components to configure and deploy the service, and wherein the deployment engine retrieves a business process execution language installation workflow from the service state and configuration repository to execute installation steps for dependent components yet to be installed, and wherein the dependency graph and the configuration dependency graph are stored in a corresponding object for the service in the service state and configuration repository, and wherein the monitoring engine updates a status of each object in the service state and configuration repository, and wherein the service is a unit of activity performed by a compute element, and wherein the service is hosted by a plurality of enterprises using a grid infrastructure that is connected to the network;

responsive to the service being unavailable at the requested quality of service, performing an analysis of components associated with the service to identify resources needed to create the service, wherein the analysis of the components includes resource brokering, resource allocation, deployment, installation, configuration, and testing, and wherein resource allocation includes allocating resources based upon a service level agreement and system wide policies; and

wherein the deployment includes identifying the resources for deployment and deploying a software application on the resources, and wherein the installation includes installing a software application on the resources, and wherein the configuration includes setting parameters of a software application such that the service is available, and wherein the testing includes performing unit testing and functional verification testing to ensure that the service is correctly working as prescribed by a service provider, and wherein unit testing scripts are stored in the dependency graph for each of the components that comprise the service, and wherein functional verification testing scripts are stored with the corresponding object for the service in the service state and configuration repository;

based on the analysis, allocating resources to support the service; and

instantiating the service on the network at the requested quality of service after the resources have been allocated, wherein instantiating the service includes employing supporting services from at least one data center, and wherein the supporting services are components on which the service depends to deliver its service, and wherein the at least one data center provides raw resources, operating system stack, common middleware services to run applications, and application specific middleware services.