Application loading and visualization

• US 20060041662A1
• Filed: 05/24/2004
• Published: 02/23/2006
• Est. Priority Date: 05/24/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Kovachka-Dimitrova, Monika M., Dimitrov, Dimiter G., Georgiev, Anton G., Tsiklovski, Radoslav S.
• Granted Patent: US 8,762,981 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

A system and method are described for performing application loading and visualization. In one embodiment, an application is accessed on a client to be deployed on the server. The client is in communication with machines having resources corresponding to the application. The application is then deployed on the server, and the deployed application on the server references a copy of the resources that already resides on the server.

Claims

1. A method, comprising:

accessing an application on a client to be deployed on a server, wherein the client is in communication with one or more machines having resources corresponding to the application; and

deploying the application on the server, wherein the application references a copy of the resources residing on the server.

2. The method of claim 1, further comprises maintaining the resources on the one or more machines while deploying the application on the server.

3. The method of claim 1, further comprises maintaining the resources on the one or more machines after deploying the application on the server.

4. The method of claim 1, further comprises providing a path using a deploy tool on the client to facilitate the deploying of the application.

5. The method of claim 4, wherein the deploy tool comprises a viewer having one or more of the following:

a graphical user interface (GUI)-based viewer and a Web-based viewer.

6. The method of claim 1, wherein the server comprises a deploy service to receive the application, the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

7. The method of claim 1, wherein the resources include one or more of the following:

components, files, directories, libraries, codes, and syntax associated with the application.

8. The method of claim 1, further comprises redeploying the application on the server, wherein the application references the copy of the resources residing on the server.

9. The method of claim 1, wherein the one or more machines include one or more remotely located computer systems coupled with the client over a network, the network.

10. The method of claim 1, accessing the resources corresponding to the application to perform a plurality of tasks including one or more of the following:

developing the application, amending the application, correcting the application, and checking integrity of the application.

11. A method, comprising:

creating a work folder on a client, the work folder to store information relating to amending an application residing on a server; and

deploying the information on the server to facilitate the amending of the application, the information including an application file.

12. The method of claim 11, further comprises inserting the information into the work folder prior to deploying the information on the server.

13. The method of claim 11, wherein the work folder includes a temporary work directory created using a deploy tool on the client.

14. The method of claim 13, wherein the deploy tool comprises a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer.

15. The method of claim 14, wherein the server comprises a deploy service to receive the work folder, the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

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

a deploy tool on a client to deploy an application on a server, wherein the client is in communication with one or more machines having resources corresponding to the application; and

a deploy service on the server, coupled with the client, to receive the application being deployed on the server, wherein the application references a copy of the resources already residing on the server.

17. The J2EE deployment architecture of claim 16, wherein the resources are maintained on the one or more machines during and after the deploying of the application, the one or more machines including one or more remotely located computer system coupled with the client over a network.

18. The J2EE deployment architecture of claim 16, wherein the deploy tool is further to facilitate the deploying of the application on the server, the deploy tool including a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer

19. The J2EE deployment architecture of claim 18, wherein the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

20. A J2EE deployment architecture, comprising:

a deploy tool on a client to create a work folder on the client, the work folder to store information relating to amending an application residing on a server, and to deploy the information contained in the work folder on the server to facilitate the amending of the application; and

a deploy service on the server coupled with the client, the deploy service to receive the information from the client, the information including an application file.

21. The J2EE deployment architecture of claim 20, wherein the deploy tool comprises a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer.

22. The J2EE deployment architecture of claim 20, wherein the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

23. A system, comprising:

a client having a deploy tool to deploy an application on a server, wherein the client is in communication with one or more machines having resources corresponding to the application, the one or more machines including remotely located computer systems coupled with the client over a network; and

the server coupled with the client, the server having a deploy service to receive the application being deployed on the server, wherein the application references a copy of the resources already residing on the server.

24. The system of claim 23, wherein the deploy tool is further to create a work folder on the client, the work folder to store information relating to amending an application residing on a server, and to deploy the information contained in the work folder on the server to facilitate the amending of the application, the information comprising an application file.

25. The system of claim 24, wherein the deploy service is further to receive the information from the client via the deploy tool.

26. The system of claim 23, wherein the application comprises one or more of the following:

a J2EE application and a non-J2EE application.

27. The system of claim 23, wherein the deploy tool comprises a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer.

28. The system of claim 23, wherein the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

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

access an application on a client to be deployed on a server, wherein the client is in communication with one or more machines having resources corresponding to the application; and

deploy the application on the server, wherein the application references a copy of the resources residing on the server.

30. The machine-readable medium of claim 29, wherein the sets of instruction, when executed by the machine, further cause the machine to maintain the resources on the one or more machines while deploying the application on the server, the one or more machines including one or more remotely located computer systems coupled with the client over a network.

31. The machine-readable medium of claim 29, wherein the sets of instruction, when executed by the machine, further cause the machine to maintain the resources on the one or more machines after deploying the application on the server.

32. The machine-readable medium of claim 29, wherein the sets of instruction, when executed by the machine, further cause the machine to provide a path using a deploy tool on the client to facilitate the deploying of the application.

33. The machine-readable medium of claim 32, wherein the deploy tool comprises a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer.

34. The machine-readable medium of claim 29, wherein the server comprises a deploy service to receive the application, the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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

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

create a work folder on a client, the work folder to store information relating to amending an application residing on a server; and

deploy the information work folder on the server to facilitate the amending of the application, the information including an application file.

36. The machine-readable medium of claim 35, wherein the sets of instruction, when executed by the machine, further cause the machine to insert the information into the work folder prior to deploying the information on the server.

37. The machine-readable medium of claim 35, wherein the work folder includes a temporary work directory created using a deploy tool on the client.

38. The machine-readable medium of claim 37, wherein the deploy tool comprises a viewer having one or more of the following:

a GUI-based viewer and a Web-based viewer.

39. The machine-readable medium of claim 38, wherein the server comprises a deploy service to receive the work folder, the deploy service is further to facilitate bi-directional communication between the client and the server using one or more of the following interfaces:

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