Systems and Methods for Application Deployment

• US 20070180018A1
• Filed: 04/09/2007
• Published: 08/02/2007
• Est. Priority Date: 01/18/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Srinivasan, Sriram, Spotswood, Mark
• Granted Patent: US 7,702,740 B2
• Time in Patent Office: Days
• US Class Current: 709/200
• CPC Class Codes: G06F 8/61 Installation

Abstract

A system for deploying applications that comprises a data storage component capable of containing at least one application to be deployed and an administration component capable of deploying the application from the data storage component to a managed component. The managed component is capable of receiving the application from the data storage component preparing the received application for deployment on the managed component; and activating the deployment once the managed component is prepared. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for deploying applications, comprising:

a data storage component capable of containing at least one application to be deployed; and

an administration component capable of deploying the application from the data storage component to a managed component, the managed component capable of;

receiving the application from the data storage component;

preparing the received application for deployment on the managed component; and

activating the deployment once the managed component is prepared.

2. A system according to claim 1, wherein:

the managed component is further capable of;

initialing the received application for deployment on the managed component.

3. A system according to claim 1, wherein:

the managed component is further capable of;

starting or executing the deployment once the managed component is activated.

4. A system according to claim 1, further comprising:

a deployment tool for guiding the deployment of the application.

5. A system according to claim 1, wherein:

the administration component is further capable of deploying the application from the data storage component to additional managed components.

6. A system according to claim 1, wherein:

the administration component has a master deployer and the managed component has a slave deployer, the master deployer to send deployment information to the slave deployer and the slave deployer to manage the deployment on the managed component, the slave deployer to notify the administration component of the success of the deployment on the managed component.

7. A system according to claim 1, further comprising:

a staging directory that can be shared by the managed component and any other managed component to receive the deployment, the staging directory capable of holding the application until activated by the administration component.

8. A system according to claim 1, further comprising:

a production directory in communication with the managed server, the production directory adapted to hold the deployed application for the managed server.

9. A method for deploying applications, comprising:

containing in a data storage component at least one application to be deployed; and

deploying the application from the data storage component to a managed component, the managed component capable of;

receiving the application from the data storage component;

preparing the received application for deployment on the managed component; and

activating the deployment once the managed component is prepared.

10. A method according to claim 9, wherein:

the managed component is further capable of;

initialing the received application for deployment on the managed component.

11. A method according to claim 9, wherein:

the managed component is further capable of;

starting or executing the deployment once the managed component is activated.

12. A method according to claim 9, further comprising:

guiding the deployment of the application by using a deployment tool.

13. A method according to claim 9, wherein:

deploying the application from the data storage component to additional managed components.

14. A method according to claim 9, further comprising:

using a master deployer to send deployment information to a slave deployer;

using the slave deployer to manage the deployment on the managed component; and

notifying the success of the deployment on the managed component.

15. A method according to claim 9, further comprising:

using a staging directory that can be shared by the managed component and any other managed component to receive the deployment, the staging directory capable of holding the application until activated by the administration component.

16. A method according to claim 9, further comprising:

using a production directory in communication with the managed server, the production directory adapted to hold the deployed application for the managed server.

17. A method for deploying an application, comprising:

invoking a preparation operation on a new deployment of an application on a node on which an old deployment of the application is activating;

removing the old deployment of the application; and

activating the new deployment of the application on the node.

18. A method according to claim 17, further comprising:

determining whether the preparation operation has succeeded before activating the new deployment of the application.

19. A method according to claim 17, further comprising:

cancelling the preparation operation on a new deployment of the application on the node.

20. A method according to claim 17, further comprising:

invoking the preparation operation for additional nodes on which the application is to be deployed.

21. A method according to claim 20, further comprising:

activating the deployed application on the additional nodes.

22. A method according to claim 17, wherein:

invoking a preparation operation further comprises

executing an init phase in which the deployment descriptors are analyzed, and

executing a prepare phase in which the application is initialized.

23. A method according to claim 17, wherein:

activating the deployed application on the node further comprises;

executing an activate phase in which the node is informed it should prepare for requests on the application; and

executing a start phase in which the application is actually deployed and executable on the node.

24. A method according to claim 17, further comprising:

switching application directories from a staging directory to a production directory when deploying an application.

25. A method according to claim 17, further comprising:

switching a class loader when deploying an application.

26. A method for concurrently deploying an application on multiple nodes, comprising:

contacting a master deployer on an administration server using a deployment tool;

passing to the administration server the path to a source containing an application to be deployed;

sending the path to a slave deployer for each node on which the application is to be deployed;

pulling the application from the source into a staging directory using the slave deployer and attempting to load the application;

informing the master deployer of the success of each load; and

directing the slave deployer to execute one of activating the applications or cancelling the deployment.

27. A machine readable medium having instructions stored thereon that when executed cause a system to:

contain in a data storage component at least one application to be deployed; and

deploy the application from the data storage component to a managed component, the managed component capable of;

receiving the application from the data storage component;

preparing the received application for deployment on the managed component; and

activating the deployment once the managed component is prepared.

28. A machine readable medium according to claim 27, wherein:

the managed component is further capable of;

initialing the received application for deployment on the managed component.

29. A machine readable medium according to claim 27, wherein:

the managed component is further capable of;

starting or executing the deployment once the managed component is activated.

30. A machine readable medium according to claim 27, having instructions stored thereon that when executed cause a system further to:

guide the deployment of the application by using a deployment tool.

31. A machine readable medium according to claim 27, having instructions stored thereon that when executed cause a system further to:

deploy the application from the data storage component to additional managed components.

32. A machine readable medium according to claim 27, having instructions stored thereon that when executed cause a system further to:

use a master deployer to send deployment information to a slave deployer;

use the slave deployer to manage the deployment on the managed component; and

notify the success of the deployment on the managed component.

33. A machine readable medium according to claim 27, having instructions stored thereon that when executed cause a system further to:

use a staging directory that can be shared by the managed component and any other managed component to receive the deployment, the staging directory capable of holding the application until activated by the administration component.

34. A machine readable medium according to claim 27, having instructions stored thereon that when executed cause a system further to:

use a production directory in communication with the managed server, the production directory adapted to hold the deployed application for the managed server.

35. A machine readable medium for deploying an application having instructions stored thereon that when executed cause a system to:

invoke a preparation operation on a new deployment of an application on a node on which an old deployment of the application is activating;

remove the old deployment of the application; and

activate the new deployment of the application on the node.

36. A machine readable medium according to claim 35, having instructions stored thereon that when executed cause a system further to:

determine whether the preparation operation has succeeded before activating the new deployment of the application.

37. A machine readable medium according to claim 35, having instructions stored thereon that when executed cause a system further to:

cancel the preparation operation on a new deployment of the application on the node.

38. A machine readable medium according to claim 35, having instructions stored thereon that when executed cause a system further to:

invoke the preparation operation for additional nodes on which the application is to be deployed.

39. A machine readable medium according to claim 38, having instructions stored thereon that when executed cause a system further to:

activate the deployed application on the additional nodes.

40. A machine readable medium according to claim 35, wherein:

the preparation operation further comprises

executing an init phase in which the deployment descriptors are analyzed, and

executing a prepare phase in which the application is initialized.

41. A machine readable medium according to claim 35, wherein:

the activation of the deployed application on the node further comprises;

executing an activate phase in which the node is informed it should prepare for requests on the application; and

executing a start phase in which the application is actually deployed and executable on the node.

42. A machine readable medium according to claim 35, having instructions stored thereon that when executed cause a system further to:

switch application directories from a staging directory to a production directory when deploying an application.

43. A machine readable medium according to claim 35, having instructions stored thereon that when executed cause a system further to:

switch a class loader when deploying an application.

44. A machine readable medium for concurrently deploying an application on multiple nodes, having instructions stored thereon that when executed cause a system further to:

contact a master deployer on an administration server using a deployment tool;

pass to the administration server the path to a source containing an application to be deployed;

send the path to a slave deployer for each node on which the application is to be deployed;

pull the application from the source into a staging directory using the slave deployer and attempting to load the application;

inform the master deployer of the success of each load; and

direct the slave deployer to execute one of activating the applications or cancelling the deployment.