Deploy callback system with bidirectional containers

• US 7,562,341 B2
• Filed: 05/24/2004
• Issued: 07/14/2009
• 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.
• Primary Examiner(s): WANG, JUE S
• Application Number:
  US10/852,978
• Publication Number:
  US 20050273787A1
• Time in Patent Office: 1,877 Days
• Field of Search: 717/100, 717/107
• US Class Current: 717/107
• 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 of a deploy service to receive status information relating to one or more of deploying of an application, and deploying of operations associated with the deploying of the application, wherein the operations are stored at a container in bi-directional communication with the deploy service via a container interface and a deploy communicator; 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 using a deploy callback implementation

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

6. The method of claim 1, wherein the deploy operations include one or more of 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 via a deploy service stub.

8. The method of claim 7, wherein the deploy callback stub is implemented in the deploy service.

9. The method of claim 1, further comprises implementing a filter to selectively filter the status information.

10. A system comprising:

a client computer system having a deploy listener of a deploy service to receive status information relating to one or more of deploying of an application, and deploying of operations associated with the deploying of the application, wherein the operations are stored at a container in bi-directional communication with the deploy service via a container interface and a deploy communicator, the container at a server coupled with the client; and

the container at the server to provide the status information to the deploy listener at the client.

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

12. The system of claim 10, 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.

13. The system of claim 10, wherein the status information comprises a state of each of a plurality of deploy operations relating to deployment of a component, the plurality of deploy operations includes one or more of deploy operation, start operation, stop operation, remove operation, and update operation.

14. The system of claim 10, wherein the component comprises one or more of an application, a standalone module, a library, an interface, and a service.

15. A machine-readable medium comprising instructions which, when executed, cause a machine to:

register a deploy listener of a deploy service to receive status information relating to one or more of deploying of an application, and deploying of operations associated with the deploying of the application, wherein the operations are stored at a container in bi-directional communication with the deploy service via a container interface and a deploy communicator; and

provide the status information to the deploy listener.

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

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

18. The machine-readable medium of claim 15, wherein the deploy listener is created using a deploy callback implementation interface.

19. The machine-readable medium of claim 15, wherein the deploying of the application is performed using a deploy tool.

20. The machine-readable medium of claim 15, wherein the deploy operations include one or more of deploy operation, start operation, stop operation, return operation, and update operation.

21. The machine-readable medium of claim 15, wherein status information is provided from one or more containers via a deploy callback stub via a deploy service stub.

22. The machine-readable medium of claim 15, wherein the deploy callback stub is implemented in the deploy service.

23. The machine-readable medium of claim 15, wherein the instructions which, when executed, further cause the machine to implement a filter to selectively filter the status information.