Dynamic component transfer

• US 7,440,996 B2
• Filed: 12/03/2002
• Issued: 10/21/2008
• Est. Priority Date: 12/10/2001
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Gebhart, Alexander
• Primary Examiner(s): Vu; Thong H
• Application Number:
  US10/309,415
• Publication Number:
  US 20030158915A1
• Time in Patent Office: 2,149 Days
• Field of Search: 709/203, 709/219, 709/225, 709/231, 709/223, 709/224, 709/229, 705/39, 705/78, 705/9, 705/14, 705/26, 705/27, 707/1, 707/513, 707/10, 707/104, 715/513, 717/173, 718/105
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 2209/5015 Service provider selection
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/4806 Task transfer initiation or dispatching
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Methods and apparatus, including computer program products. In one embodiment, a client server method includes storing components in a first server, storing a list of the components in a second server, requesting, by an application residing in a client, a component matching particular functioned requirements from the list, negotiating between the first server and the client, and executing the component in response to the negotiation.

Claims

1. A method for automatically using computer software components by an application on a client computer that is connected to a computer network, the method comprising:

deploying components on a first server;

registering the components in a second server;

sending a functionality specification from the client computer through the application to the second server, the functionality specification indicating functionality requested from the components registered in the second server;

searching in the second server for register entries that match the functionality specification and preparing a list of components that match the functionality specification;

returning the list of matching components to the application; and

executing one of the matching components under control of the application.

2. The method of claim 1 wherein the registering is performed with the second server being a Universal Description, Discovery and Integration (UDDI) server.

3. The method of claim 2 wherein the registering is performed by describing the component in a web service description language (WSDL).

4. The method of claim 3 wherein the registering is performed by describing a location of the component and an invocation of the component.

5. The method of claim 1 wherein the searching further comprises using a UDDI description in WSDL in the second server.

6. The method of claim 1 wherein returning the list further comprises performing a negotiation between the client computer and the first server.

7. The method of claim 6 wherein performing the negotiation further comprises using resource information about the client computer and the first server.

8. The method of claim 7 wherein using the resource information further comprises reading a text structure.

9. The method of claim 8 wherein using the resource information further comprises reading the text structure as an XML structure.

10. The method of claim 9 wherein reading the XML structure further comprises reading indications from a group including removeability, size, language, language version, disk capacity, processor speed, operating system, and details of applications.

11. The method of claim 6 wherein performing the negotiation further comprises at least one resource agent negotiating on the client computer, first server, or both.

12. The method of claim 11 wherein the resource agent further comprises a server-side agent and a client-side agent.

13. The method of claim 11 wherein the resource agent controls component execution.

14. The method of claim 1 wherein the executing further comprises accessing the matching component by a simple object access protocol (SOAP).

15. The method of claim 1 wherein the executing further comprises composing an application from a plurality of the registered components.

16. The method of claim 15 wherein composing the application comprises dynamically building the application using an application stub on the client computer.

17. A computer program product, tangibly stored on a computer-readable medium, comprising instructions operable to cause a programmable processor to carry out a method for automatically using computer software components by an application on a client computer, the method comprising:

deploying components on a first server;

registering the components in a second server;

sending a functionality specification from the client computer through the application to the second server, the functionality specification indicating functionality requested from the components registered in the second server;

searching in the second server for register entries that match the functionality specification and preparing a list of components that match the functionality specification;

returning the list of matching components to the application; and

executing one of the matching components under control of the application.

18. The product of claim 17 wherein the registering is performed with the second server being a Universal Description, Discovery and Integration (UDDI) server.

19. A first server comprising:

a storage device for storing components deployed on the first server which are registered on a second server; and

a network interface for communicating with an application on a client computer,

wherein the client computer sends a functionality specification through the application on the client computer to the second server, the functionality specification indicating functionality requested from the components registered in the second server,

wherein a list is returned by the second server to the application, the list being a list of components that are deployed on the first server and that are registered in the second server as matching the functionality specification, and

one of the matching components deployed on the first server is executed under control of the application.

20. A second server comprising:

a storage device for registering components on the second server which are deployed on a first server; and

a network interface for receiving a functionality specification from an application on a client computer, the functionality specification indicating functionality requested from the components registered on the second server,

wherein the second server is configured to search for register entries that match the functionality specification, prepare a list of components deployed on the first server that match the functionality specification, and return the list of matching components to the application, and

one of the matching components deployed on the first server is executed under control of the application.

21. A system comprising:

a first server comprising (i) a first storage device for storing components deployed on the first server and (ii) a first network interface for communicating with an application on a client computer; and

a second server comprising (i) a second storage device for registering the components deployed on the first server and (ii) a second network interface for receiving a functionality specification from the application on the client computer, the functionality specification indicating functionality requested from the components registered in the second server,

wherein the second server is configured to search for register entries that match the functionality specification, prepare a list of components deployed on the first server that match the functionality specification, and return the list of matching components to the application, and

one of the matching components deployed on the first server is executed under control of the application.