Deploy callback system

• US 20050273787A1
• Filed: 05/24/2004
• Published: 12/08/2005
• Est. Priority Date: 05/24/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kovachka-Dimitrova, Monika M., Angelova, Rumiana G.
• Granted Patent: US 7,562,341 B2
• Time in Patent Office: Days
• US Class Current: 719/310
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system and method are described for facilitating communication between a server and a client using a deploy callback system. In one embodiment, deploy listener is registered to receive status information regarding deployment of application or deploy operations relating to the deployment of the application. Such status information is provided to the deploy listener.

Claims

1. A method, comprising:

registering a deploy listener to receive status information relating to one or more of the following;

deploying an application and deploy operations associated with the deploying of the application; and

providing the status information to the deploy listener.

2. The method of claim 1, wherein the receiving of the status information is performed continuously using a first thread of a plurality of threads.

3. The method of claim 2, wherein the plurality of threads includes a second thread for deploying of the application.

4. The method of claim 1, wherein the deploy listener is created on a client using a deploy callback implementation application programming interface (API).

5. The method of claim 1, wherein the deploying of the application is performed using a deploy tool at the client.

6. The method of claim 1, wherein the deploy operations include one or more of the following:

deploy operation, start operation, stop operation, return operation, and update operation.

7. The method of claim 1, wherein status information is provided from one or more containers via a deploy callback stub to the client via a deploy service stub.

8. The method of claim 7, wherein the deploy callback stub is implemented in a deploy service on one or more servers.

9. The method of claim 1, further comprises implementing a filter to selectively filter the status information, wherein the filter is implemented on the client or on the one or more servers.

10. A method, comprising:

creating a deploy listener on a client, the deploy listener is to receive status information;

adding the deploy listener on a client using a deploy callback implementation API; and

registering the deploy listener with a deploy service on a server.

11. The method of claim 10, wherein the status information includes information relating to one or more of the following:

deploying of an application and deploy operations associated with the deploying of the application.

13. The method of claim 10, wherein the deploy callback implementation API is further to create the deploy listener.

14. The method of claim 11, further comprising:

performing the deploy operations on one or more containers on the server; and

providing the status information from the one or more containers to the deploy listener on the client.

15. The method of claim 14, wherein the providing of the status information is performed using a container API and a deploy callback stub.

12. The method of clam 11, wherein the deploy operations include one or more of the following:

deploy operation, start operation, stop operation, return operation, and update operation.

16. A Java 2 Enterprise Edition (J2EE) architecture, comprising:

a client having a deploy listener to receive status information relating to one or more of the following;

deploying an application and deploy operations associated with the deploying of the application; and

a server to continuously provide the status information to the client.

17. The J2EE architecture of claim 16, wherein the deploy listener is created on the client using a deploy callback implementation API.

18. The J2EE architecture of claim 16, wherein the server to continuously provide the status information using a deploy callback stub and a container API on the server.

19. The J2EE architecture of claim 16, wherein the deploying of the application is performed using a first thread of a plurality of threads on a deploy tool.

20. The J2EE architecture of claim 16, wherein the server provides the status information using a second thread of the plurality of threads on the deploy tool.

21. A deploy callback system, comprising:

a deploy listener on a client to receive status information from a container on a server, wherein the deploy listener is created on the client using a deploy callback implementation API; and

a deploy service in communication with the deploy listener and the container to facilitate a communication between the deploy listener and the container.

22. The deploy callback system of claim 21, wherein the communication between the deploy listener and the container is bi-directional, the communication is performed using one or more of the following interfaces:

a deploy service API and a container API.

23. The deploy callback system of claim 21, wherein the deploy listener to receive the status information continuously from the container using a thread of a plurality of threads.

24. The deploy callback system of claim 21, wherein a deploy callback stub is implemented on a server having the container, the deploy callback stub is used to route the status information from the container to the deploy listener.

25. The deploy callback system of claim 21, wherein the status information comprises entity, the plurality of deploy operations includes one or more of the following:

deploy operation, start operation, stop operation, remove operation, and update operation.

26. The deploy callback system of claim 21, wherein the entity comprises one or more of the following:

an application, a standalone module, a library, an interface, and a service.

27. A machine-readable medium having stored thereon data representing sets of instructions which, when executed by a machine, cause the machine to:

register a deploy listener to receive status information relating to one or more of the following;

deploying an application and deploy operations associated with the deploying of the application; and

provide the status information to the deploy listener.

28. The machine-readable medium of claim 27, wherein the receiving of the status information is performed continuously using a first thread of a plurality of threads.

29. The machine-readable medium of claim 28, wherein the plurality of threads includes a second thread for deploying of the application.

30. The machine-readable medium of claim 27, wherein the deploy listener is created on a client using a deploy callback implementation API.

31. The machine-readable medium of claim 27, wherein the deploying of the application is performed using a deploy tool at the client.

32. The machine-readable medium of claim 27, wherein the deploy operations include one or more of the following:

deploy operation, start operation, stop operation, return operation, and update operation.

33. The machine-readable medium of claim 27, wherein status information is provided from one or more containers via a deploy callback stub to the client via a deploy service stub.

34. The machine-readable medium of claim 27, wherein the deploy callback stub is implemented in a deploy service on one or more servers.

35. The machine-readable medium of claim 27, wherein the sets of instructions, when executed by the machine, further cause the machine to implement a filter to selectively filter the status information, wherein the filter is implemented on the client or on the one or more servers.