Web services-based computing resource lifecycle management

• US 8,255,485 B2
• Filed: 12/07/2010
• Issued: 08/28/2012
• Est. Priority Date: 11/21/2001
• Status: Expired due to Fees

• Current Assignee: Akana, Inc. (Perforce Software Incorporated)
• Original Assignee: Blue Titan Software, Inc. (Perforce Software Incorporated)
• Inventors: Martinez, Frank, Toth, Paul Kevin, Darugar, Parand Tony
• Primary Examiner(s): Burgess, Barbara
• Application Number:
  US12/962,496
• Publication Number:
  US 20110196940A1
• Time in Patent Office: 630 Days
• Field of Search: 709/203, 709/223, 709/217, 709/238, 709/227
• US Class Current: 709/217
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods, apparatuses and systems facilitating life-cycle management and utilization of network resources. In one embodiment, instancing, virtualization and dynamic provisioning functionality facilitating management and utilization of web services is provided. The instancing functionality supports a web services network platform allowing for registration and use of multiple instances or versions of a given web service or other network-accessible computing resource. In one embodiment, the present invention combines the virtualization and dynamic provisioning functionality to facilitate the development of client application code in routed web services network architectures. In one embodiment, a set of management functions that may be applied to management of computing resources in any IP-based network.

Claims

1. A method for dynamic provisioning of web services, comprising

receiving, at a computing device, an interface description document associated with a web service;

identifying one or more operations supported by the web service;

creating by the computing device, for one or more identified operations, routing entity information for routing service operation requests associated with the web service;

configuring one or more routing nodes of a web services network infrastructure with the routing entity information created for the one or more identified operations;

modifying the interface description document to replace, for one or more identified operations, endpoint location information corresponding to the one or more identified operations in the interface description document with location information of a first routing node of the one or more routing nodes of the web services network infrastructure; and

transmitting the modified interface description document in response to a request for the interface description document.

2. The method of claim 1 further comprising

identifying mutable elements in the interface description document;

and

replacing at least one mutable element in the interface description document with information reflecting a current state of the one or more routing nodes of the web services network infrastructure.

3. The method of claim 1 wherein the routing entity information for the one or more identified operations includes unique operation identifiers corresponding to respective identified operations supported by the web service, and wherein the unique operation identifiers map to binding information associated with the web service.

4. The method of claim 1 wherein the interface description document includes a first binding defining the endpoint location and protocols for accessing the web service;

wherein the web services network infrastructure supports a second binding type; and

wherein the method further comprises;

replacing the first binding in the interface description document with a second binding defining the endpoint location of a routing node within the web services network infrastructure and the protocols for accessing the routing functionality of the routing node.

5. The method of claim 4 wherein the first binding is a SOAP binding.

6. The method of claim 5 wherein the second binding is a SOAP binding identifying a routing node associated with the web services network infrastructure and a web service operation.

7. The method of claim 1 wherein the interface description document is a Web Services Definition Language (WSDL) document.

8. The method of claim 1 wherein the location information of the first routing node comprises an IP address of the routing node in an encoded URL that further includes an operation identifier that maps to an identified operation of the web service.

9. A method comprising:

receiving, at a computing device, an interface description document associated with a web service, wherein the interface description document describes an operation and an endpoint location;

modifying the interface description document by replacing the endpoint location with location information of a web services network routing node;

associating a web service operation identifier with the operation in the interface description document;

adding a routing entry to a web services network directory including the web service operation identifier and the endpoint location associated with the web service; and

transmitting the modified interface description document in response to a request for the interface description document.

10. The method of claim 9 wherein the interface description document is a WSDL document.

11. The method of claim 9 wherein the location information of the web services network routing node comprises an IP address of the web services network routing node in an encoded URL that further includes the web service operation identifier that maps to the operation included in the interface description document.

12. The method of claim 9, further comprising:

identifying mutable elements in the interface description document; and

replacing at least one mutable element in the interface description document with information reflecting a current state of one or more routing nodes of a web services network infrastructure.

13. The method of claim 9 wherein the unique operation identifier maps to binding information associated with the web service.

14. The method of claim 9 wherein the interface description document includes a first binding defining the endpoint location and protocols for accessing the web service,

wherein the web services network infrastructure supports a second binding type, and

wherein the method further comprises replacing the first binding in the interface description document with a second binding defining the endpoint location of the web services network routing node and protocols for accessing the routing functionality of the routing node.

15. A system, comprising

a web services network management platform, having one or more processors, operative to:

receive, at a computing device, an interface description document associated with a web service;

identify one or more operations supported by the web service;

create by the computing device, for one or more identified operations, routing entity information for routing service operation requests associated with the web service;

add the routing entity information to a web services network directory;

modify the interface description document to replace, for one or more identified operations, endpoint location information corresponding to the one or more identified operations in the received interface description document with location information of a first routing node of the one or more routing nodes of the web services network infrastructure; and

transmit the modified interface description document in response to a request for the interface description document; and

one or more routing nodes, each operative to;

receive a request including a web service operation identifier;

access the web services network directory to locate information associated with the web service operation identifier; and

route the request using location information stored in the web services network directory.

16. The system of claim 15 wherein the location information of the first routing node comprises an IP address of the routing node in an encoded URL that further includes an operation identifier that maps to an identified operation of the web service.

17. The system of claim 15 wherein the routing entity information for the one or more identified operations includes unique operation identifiers corresponding to respective identified operations supported by the web service, and wherein the unique operation identifiers map to binding information associated with the web service.

18. The system of claim 15, wherein the web services network management platform is further operative to:

identify mutable elements in the interface description document; and

replace at least one mutable element in the interface description document with information reflecting a current state of one or more routing nodes of a web services network infrastructure.

19. The system of claim 15, wherein the unique operation identifier maps to binding information associated with the web service.

20. The system of claim 15, wherein the interface description document includes a first binding defining the endpoint location and protocols for accessing the web service,

wherein the web services network infrastructure supports a second binding type, and

wherein the method further comprises replacing the first binding in the interface description document with a second binding defining the endpoint location of the web services network routing node and protocols for accessing the routing functionality of the routing node.