Application cloning

• US 20050278338A1
• Filed: 05/25/2004
• Published: 12/15/2005
• Est. Priority Date: 05/25/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kovachka-Dimitrova, Monika M., Todorova, Mariela T.
• Granted Patent: US 7,877,735 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order

Abstract

A system and method are described for performing application cloning. In one embodiment, on a client, an application that is already deployed on a server is accessed and then cloned into another application by assigning a new name to the application. The clone application is then deployed on the server where the application and the clone application are simultaneously run.

Claims

1. A method, comprising:

accessing a first application on a client, wherein the first application is deployed on a first server;

cloning the first application into a second application by assigning a new name to the first application;

deploying the second application on the first server; and

simultaneously running the first application and the second application on the first server.

2. The method of claim 1, wherein the cloning of the first application into the second application includes assigning a new Web alias to the first application.

3. The method of claim 1, further comprises running a performance test on the second application, the performance test includes:

measuring one or more components of the second application;

estimating the one or more components of the second application; and

compiling a second result based on the measurement and estimation of the one or more components of the second application.

4. The method of claim 3, wherein the running of the performance test further comprises:

comparing the second result relating to the one or more components of the second application with a first result relating to one or more components of the first application; and

selecting from the first application and the second application based on the comparison of the first result with the second result.

5. The method of claim 1, further comprising

amending the second application;

and

deploying the second application on the first server to overwrite the first application.

6. The method of claim 5, wherein the amending of the second application comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the second application.

7. The method of claim 1, further comprising:

cloning the first application into a third application by assigning a new name to the first application; and

deploying the third application on the first server; and

simultaneously running the first application and the third application on the first server.

8. The method of claim 7, wherein the cloning of the first application into the third application includes assigning a new Web alias to the first application.

9. The method of claim 1, further comprises cloning the second application into a forth application by:

assigning a new name to the second application;

assigning a new Web alias to the second application; and

deploying the forth application on the first server.

10. The method of claim 1, further comprises deploying on a second server one or more of the following applications:

the first application, the second application, the third application, and the forth application.

11. The method of claim 1, further comprises simultaneously running on the first server any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

12. The method of claim 1, further comprises simultaneously running on the second server any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

13. The method of claim 11, further comprises running a performance test at the first server on any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

14. The method of claim 11, further comprises running a performance test at the second server on any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

15. A J2EE architecture, comprising:

a client coupled with a first server, the client to

access a first application at the client, the first application deployed on a first server,

clone the first application into a second application by assigning a new name to the first application,

deploy the second application on the first server, wherein the second application is a clone application of the first application; and

the first server to simultaneously run the first application and the second application on the first server, the first server to regard the first application and second application as distinct applications.

16. The J2EE architecture of claim 15, wherein the cloning of the first application into the second application includes assigning a new Web alias to the first application at the client.

17. The J2EE architecture of claim 15, wherein the client is further to run a performance test on the second application, the performance test includes:

measuring one or more components of the second application;

estimating the one or more components of the second application; and

compiling a second result based on the measurement and estimation of the one or more components of the second application.

18. The J2EE architecture of claim 17, wherein the running of the performance test further comprises:

comparing the second result relating to the one or more components of the second application with a first result relating to one or more components of the first application; and

selecting from the first application and the second application based on the comparison of the first result with the second result.

19. The J2EE architecture of claim 15, wherein the client is further to:

amending the second application; and

deploying the second application on the first server to overwrite the first application.

20. The J2EE architecture of claim 19, wherein the amending of the second application comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the second application.

21. The J2EE architecture of claim 15, wherein the client comprises a deploy tool, and the first server includes a deploy service in bi-directional communication with the deploy tool.

22. A J2EE application cloning system, comprising:

a deploy tool at a client to initiate a transaction to perform cloning of a first application into a second application, the deploy tool to access the first application, wherein the first application is deployed on a first server,

assign a new name to the first application,

assign a new Web alias to the first application, and

deploy the second application on the first server, wherein the second application is a clone application of the first application; and

a deploy service at the first server coupled with the client, the deploy service to receive the second application from the client via the deploy tool,

regard the first application and the second application as distinct from each other, and

simultaneously run the first application and the second application on the first server.

23. The J2EE application cloning system of claim 22, wherein the client, via the deploy tool, is further to:

amend the second application, wherein the amending of the second application comprises adding, removing, or modifying of one or more of the following;

modules, classes, and descriptive information corresponding to the second application; and

deploying the second application on the first server to overwrite the first application.

24. The J2EE application cloning system of claim 22, wherein the client is further to clone the first application or the second application into one or more clone applications.

25. The J2EE application cloning system of claim 24, wherein the client is further to deploy on one or more servers in a cluster one or more of the following:

the first application, the second application, and the one or more clone applications.

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

access a first application on a client, wherein the first application is deployed on a first server;

clone the first application into a second application by assigning a new name to the first application;

deploy the second application on the first server; and

simultaneously run the first application and the second application on the first server.

27. The machine-readable medium of claim 26, wherein the cloning of the first application into the second application includes assigning a new Web alias to the first application.

28. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to run a performance test on the second application, the performance test includes:

measuring one or more components of the second application;

estimating the one or more components of the second application; and

compiling a second result based on the measurement and estimation of the one or more components of the second application.

29. The machine-readable medium of claim 28, wherein the running of the performance test further causes the machine to:

compare the second result relating to the one or more components of the second application with a first result relating to one or more components of the first application; and

select from the first application and the second application based on the comparison of the first result with the second result.

30. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to:

amend the second application; and

deploy the second application on the first server to overwrite the first application.

31. The machine-readable medium of claim 30, wherein the amending of the second application comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the second application.

32. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to:

clone the first application into a third application by assigning a new name to the first application; and

deploy the third application on the first server; and

simultaneously run the first application and the third application on the first server.

33. The machine-readable medium of claim 32, wherein the cloning of the first application into the third application includes assigning a new Web alias to the first application.

34. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to clone the second application into a forth application by:

assigning a new name to the second application;

assigning a new Web alias to the second application; and

deploying the forth application on the first server.

35. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to deploy on a second server one or more of the following applications:

the first application, the second application, the third application, and the forth application.

36. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to simultaneously run on the first server any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

37. The machine-readable medium of claim 26, wherein the sets of instruction, when executed by the machine, further cause the machine to simultaneously run on the second server any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

38. The machine-readable medium of claim 36, wherein the sets of instruction, when executed by the machine, further cause the machine to run a performance test at the first server on any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.

39. The machine-readable medium of claim 36, wherein the sets of instruction, when executed by the machine, further cause the machine to run a performance test at the second server on any combination of one or more of the following applications:

the first application, the second application, the third application, and the forth application.