Deploy service implementation

• US 20060037030A1
• Filed: 05/24/2004
• Published: 02/16/2006
• 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,735,097 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/61 Installation

Abstract

A system and method are described for implementing and using a deploy system for deployment of entities. In one embodiment, a deploy service is implemented as a module on a J2EE engine to perform deployment services on a container on the J2EE engine. The deployment services include deploying one or more entities on the container which includes a J2EE container and/or a non-J2EE container.

Claims

1. A method, comprising:

implementing a deploy service to perform deployment services, wherein the deploy service includes a module on a Java 2 Enterprise Edition (J2EE) engine; and

performing the deployment services on a container at the J2EE engine by deploying one or more entities on the container, wherein the container includes one or more of the following;

a J2EE container and a non-J2EE container.

2. The method of claim 1, wherein the one or more entities include one or more of the following:

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

3. The method of claim 1, wherein the deployment services further include performing deploy operations relating to the deploying of the one or more entities or the deploy operations include one or more of the following:

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

4. The method of claim 1, further comprises receiving a request from a client to perform the deployment services on the container at the J2EE engine, wherein the J2EE engine includes a J2EE server.

5. The method of claim 1, wherein the deploy service is further to facilitate communication between the client and the J2EE server at which the deployment services are being performed.

6. The method of claim 1, wherein the implementation of the deploy service is performed using a deploy tool at the client.

7. The method of claim 4, wherein the request from the client is placed using the deploy tool at the client.

8. The method of claim 1, wherein the deploy service is further to manage the application.

9. The method of claim 1, wherein the container is to manage components of the application.

10. The method of claim 1, further comprises implementing a deploy context to manage components of the server including one or more of the following:

the library, the service, and the interface.

11. The method of claim 1, wherein the deploy service is further to:

register the container if it is active; and

unregister the container if it is inactive.

12. The method of claim 1, further comprises:

committing the deployment services at the container; and

committing the deployment services at a database.

13. A J2EE architecture, comprising:

a server having a deploy service and one or more containers, the deploy service to perform deployment services on the one or more containers by deploying one or more entities on the one or more containers, the one or more containers include one or more of the following;

J2EE containers and non-J2EE containers; and

a client coupled with the server, the client to place a request with the server to perform the deployment services on the one or more containers.

14. The J2EE architecture of claim 13, wherein the deploy service is further to facilitate communication between the server and the client via one or more of the following:

a deploy service application programming interface (API) and a container API.

15. The J2EE architecture of claim 13, wherein the one or more entities include one or more of the following:

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

16. The J2EE architecture of claim 13, wherein the deploy services further include performing deploy operations relating to the deploying of the one or more entities, the deploy operations include one or more of the following:

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

17. The J2EE architecture of claim 13, wherein the request is placed using a deploy tool at the client.

18. The J2EE architecture of claim 13, wherein the client comprises a visual administrator to receive status information relating to the deploy operation, the visual administrator includes a viewer having one or more of the following:

a Graphical User Interface (GUI)-based viewer and a Web-based viewer.

19. A deploy system, comprising:

a deploy service module to perform deployment services on one or more containers at a J2EE server, the performing of the deployment services includes deploying one or more entities on the one or more containers;

the one or more containers in communication with the deploy service, the one or more containers to provide status information relating to the deployment services to a client via the deploy service; and

the client coupled with the J2EE server, the client to request the performing of the deployment services and to receive the status information.

20. The deploy system of claim 19, wherein the deploy service module further includes an interface to facilitate bi-directional communication between the client and the one or more containers.

21. The deploy system of claim 20, wherein the interface includes one or more of the following:

a deploy service API, a container API, and a deploy callback API.

22. The deploy system of claim 20, wherein the one or more containers comprise J2EE containers and non-J2EE containers.

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

implement a deploy service to perform deployment services, wherein the deploy service includes a module on a J2EE engine; and

perform the deployment services on a container at the J2EE engine by deploying one or more entities on the container, wherein the container includes one or more of the following;

a J2EE container and a non-J2EE container.

24. The machine-readable medium of claim 23, wherein the one or more entities include one or more of the following:

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

25. The machine-readable medium of claim 23, wherein the deployment services further include performing deploy operations relating to the deploying of the one or more entities or the deploy operations include one or more of the following:

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

26. The machine-readable medium of claim 23, wherein the sets of instructions, when executed by the machine, further cause the machine to receive a request from a client to perform the deployment services on the container at the J2EE engine, wherein the J2EE engine includes a J2EE server.

27. The machine-readable medium of claim 23, wherein the deploy service is further to facilitate communication between the client and the J2EE server at which the deployment services are being performed.

28. The machine-readable medium of claim 23, wherein the implementation of the deploy service is performed using a deploy tool at the client.

29. The machine-readable medium of claim 26, wherein the request from the client is placed using the deploy tool at the client.

30. The machine-readable medium of claim 23, wherein the deploy service is further to manage the application.

31. The machine-readable medium of claim 23, wherein the container is to manage components of the application.

32. The machine-readable medium of claim 23, wherein the sets of instructions, when executed by the machine, further cause the machine to implement a deploy context to manage components of the server including one or more of the following:

the library, the service, and the interface.

33. The machine-readable medium of claim 23, wherein the deploy service is further to:

register the container if it is active; and

unregister the container if it is inactive.

34. The machine-readable medium of claim 23, wherein the sets of instructions, when executed by the machine, further cause the machine to commit the deployment services at the container;

and

commit the deployment services at a database.