Single file update

• US 20050268297A1
• Filed: 05/25/2004
• Published: 12/01/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., Dimitrov, Dimiter G., Angelova, Rumiana G.
• Granted Patent: US 7,882,502 B2
• Time in Patent Office: Days
• US Class Current: 717/171
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A system and method are described for performing updating of an application using a single file update. In one embodiment, a request from a client is received at a server to amend a deployed application by updating a single file of the application. The request is received at a deploy service of the server. The file to be update is accessed and updated to amend the application. The transaction for successful updating of the file is committed to a database.

Claims

1. A method, comprising:

receiving a request from a client to amend a deployed application by updating a file of the application, wherein the request is received at a server having a deploy service and the application;

accessing the file to be updated;

updating the file to amend the application; and

committing a transaction relating to the updating of the file to a database.

2. The method of claim 1, further comprises providing notification to one or more servers in a cluster, the notification includes information relating to the commitment of the transaction to the database.

3. The method of claim 2, further comprises the one or more servers accessing the amended application at the database to synchronize information residing at the one or more servers with the amended application.

4. The method of claim 1, further comprising:

stopping the application prior to the updating of the file, if necessary, wherein the stopping of the updating of the file is indicated by a true signal; and

continuing the updating of the file, wherein the continuing of the updating of the file is indicated by a false signal.

5. The method of claim 1, further comprises verifying integrity of the application.

6. The method of claim 1, further comprising:

committing the transaction to the database if the integrity of the application is verified to be at or above an acceptable level; and

rolling back the transaction to a previous step if the integrity of the application is verified to be below the acceptable level.

7. The method of claim 6, further comprising:

providing a result having information relating to the commitment of the transaction to the database, the result is provided to the client from the deploy service at the server; and

providing an exception having information relating to the rolling back of the transaction, the exception is provided to the client from the deploy service at the server.

8. The method of claim 1, wherein the updating of the file comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the file.

9. The method of claim 1, wherein the file comprises one or more of the following:

a hypertext markup language (HTML) file and a JavaServer Page (JSP) file.

10. The method of claim 1, wherein the request is placed by the client using a deploy tool at the client, wherein the deploy tool is in communication with the deploy service at the server.

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

a client to place a request to initiate a transaction to perform an update of a file to amend an application having the file; and

a server coupled with the client, the server having a deploy service to receive the request from the client,

in response to the request, initiate the transaction to perform the update of the file, wherein the initiating of the transaction includes accessing the file to be updated, and

commit the transaction to a database if the transaction is successful, wherein the successful transaction indicates completion of the updating of the file.

12. The J2EE architecture of claim 11, wherein the deploy service is further to provide notification to one or more servers in a cluster, the notification includes information relating to the commitment of the transaction to the database.

13. The J2EE architecture of claim 11, wherein the deploy service is further to:

stop the application prior to the updating of the file, if necessary, wherein the stopping of the updating of the file is indicated by a true signal; and

continue the updating of the file, wherein the continuing of the updating of the file is indicated by a false signal.

14. The J2EE architecture of claim 11, wherein the deploy service is further to verify integrity of the application

15. The J2EE architecture of claim 14, wherein the deploy service is further to:

commit the transaction to the database if the integrity of the application is verified to be at or above an acceptable level; and

roll back the transaction to a previous step if the integrity of the application is verified to be below the acceptable level.

16. The J2EE architecture of claim 11, wherein the deploy service is further to:

provide a result to the client, the result having information relating to the commitment of the transaction to the database; and

provide an exception to the client, the exception having information relating to the rolling back of the transaction.

17. The J2EE architecture of claim 11, wherein the updating of the file comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the file.

18. A J2EE file update system, comprising:

a deploy tool at a client to place a request for initiating a transaction to perform an update of a file to amend an application having the file; and

a deploy service at the server coupled with the client, the deploy service to receive the request for initiating the transaction,

initiate the transaction to perform the updating of the file, wherein the initiating of the transaction includes accessing the file to be updated,

commit the transaction to a database if the transaction is successful, wherein the successful transaction indicates completion of the updating of the file, and

provide a result to the client, the result including information relating to the successful transaction.

19. The J2EE file update system of claim 18, wherein the deploy service is further to roll back the transaction if the transaction is unsuccessful, wherein the unsuccessful transaction includes information relating to an error with the updating of the file.

20. The J2EE file update system of claim 18, wherein the deploy service if further to provide notification to one or more servers in a cluster, the notification includes information relating to the commitment of the transaction to the database.

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

receive a request from a client to amend a deployed application by updating a file of the application, wherein the request is received at a server having a deploy service and the application;

access the file to be updated;

update the file to amend the application; and

commit a transaction relating to the updating of the file to a database.

22. The machine-readable medium of claim 21, wherein the sets of instruction, when executed by the machine, further cause the machine to provide notification to one or more servers in a cluster, the notification includes information relating to the commitment of the transaction to the database.

23. The machine-readable medium of claim 22, wherein the one or more servers to access the amended application at the database to synchronize information residing at the one or more servers with the amended application.

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

stop the application prior to the updating of the file, if necessary, wherein the stopping of the updating of the file is indicated by a true signal; and

continue the updating of the file, wherein the continuing of the updating of the file is indicated by a false signal.

25. The machine-readable medium of claim 21, wherein the sets of instruction, when executed by the machine, further cause the machine to verify integrity of the application.

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

commit the transaction to the database if the integrity of the application is verified to be at or above an acceptable level; and

roll back the transaction to a previous step if the integrity of the application is verified to be below the acceptable level.

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

provide a result having information relating to the commitment of the transaction to the database, the result is provided to the client from the deploy service at the server; and

provide an exception having information relating to the rolling back of the transaction, the exception is provided to the client from the deploy service at the server.

28. The machine-readable medium of claim 21, wherein the updating of the file comprises adding, removing, or modifying of one or more of the following:

modules, classes, and descriptive information corresponding to the file.

29. The machine-readable medium of claim 21, wherein the file comprises one or more of the following:

a hypertext markup language (HTML) file and a JavaServer Page (JSP) file.

30. The machine-readable medium of claim 21, wherein the request is placed by the client using a deploy tool at the client, wherein the deploy tool is in communication with the deploy service at the server.