Identification of Critical Web Services and their Dynamic Optimal Relocation

• US 20130013774A1
• Filed: 09/15/2012
• Published: 01/10/2013
• Est. Priority Date: 11/12/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ebrahim, Nasser, Iyer, Sreekanth Ramakrishna, Punathil, Gireesh, Reghunath, Riju
• Granted Patent: US 8,990,388 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A web service executing on a web server is monitored by detecting metadata generated for various performance characteristics of the web service. A relocation policy is consulted in response to detecting the performance characteristics exceeding a first predetermined threshold. The relocation policy specifies a target web server as a new location for the web, and instructions for relocating the web service to the target web server if the performance characteristics exceeding a second predetermined threshold. The web service is relocated to the target web server based on the relocation policy and without human intervention.

Claims

1. A method of relocating a web service, comprising:

monitoring parameters of the web service executing on a first server;

detecting a status change based on a change in the parameters;

consulting a relocation policy for instructions on moving the web service in response to the status change;

relocating the web service to a second server; and

rerouting requests for the web service to the second server.

2. The method of claim 1, wherein the web service is relocated to the second server without human intervention, the method further comprising:

defining and storing said relocation policy to include said instructions and said parameters, wherein said instructions specify the second server as a new location for the web service.

3. The method of claim 1, wherein said parameters are based on quality of service (Q0S) parameters and service level agreements (SLA).

4. The method of claim 1, wherein the detecting of said status change further comprises:

receiving metadata associated with the parameters.

5. The method of claim 1, wherein said relocation policy indicates files to be copied to the second server as part of relocating the web service to the second server, the method further comprising:

identifying whether the web service is relocatable using a service analyzer component; and

determining resources to be relocated to the second server.

6. The method of claim 1, wherein the status change is a first status change from a normal status level to a first status level, the method further comprising:

detecting a second status change from a first status level to a second status level based on a change in the parameters; and

initiating activities for the relocating of the web service to said second server in response to the second status change to said second status level;

wherein the consulting of the relocation policy in performed in response to the first status change to said first status level.

7. The method of claim 6, wherein the detecting of the first status change is based on said parameters exceeding a first threshold, the method further comprising:

detecting of the second status change based on said parameters exceeding a second threshold.

8. The method of claim 1, further comprising:

monitoring the web service executing on the second server; and

reverting to execution of the web service on the first server in response to detecting a failure of the web service executing on the second server.

9. The method of claim 1, wherein the relocating of the web service to said second server is performed by an optimized composer and relocator unit, and wherein said relocation policy is included as part of said optimized composer and relocator, the method further comprising:

using the optimized composer to identify optimized relocation methods and a set of required resources including required classes associated with the web service; and

creating an optimized relocatable bundle that packages the required classes with said optimized relocation methods to run said web service upon being relocated to the second server.