Systems and methods for compiling applications on a test server

• US 7,778,968 B2
• Filed: 10/31/2005
• Issued: 08/17/2010
• Est. Priority Date: 10/31/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Cherry, Sebastien
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): CONYERS, DAWAUNE A
• Application Number:
  US11/261,581
• Publication Number:
  US 20070100903A1
• Time in Patent Office: 1,751 Days
• Field of Search: 707/210, 717/168
• US Class Current: 707/611
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Methods and systems for synchronizing applications deployed on a test server are provided. The methods and systems may comprise a software application comprising a plurality of files deployed on a test server. After the software application is deployed on a test server, one of the plurality of files comprising the software application may be modified in a development environment. The methods and systems may comprise a synchronization manager operative to, after modification of the one of the plurality of files, synchronize only the modified file with the software application deployed on the test server.

Claims

1. A system for synchronizing files comprising:

a development server system comprising a development environment for developing a software application comprising a plurality of files;

a test server on which the files of the software application are deployed; and

a synchronization manager to, after modification of one of the files of the software application on the development system as indicated by an event raised by the development server system, automatically synchronize, immediately upon the modified file being persisted, only the modified file between the development system and the test server, the synchronization manager automatically restarting the software application on the test server after synchronization of a modified file of one or more pre-determined file types identified by a restart list of file extensions, wherein modification of some of the plurality of files which are not of the one or more pre-determined file types does not require the software application to be restarted, the restarting of the software application causing the software application to be refreshed with the modified file;

wherein the synchronization manager automatically locates files in the development system corresponding to files of software applications of a certain project type deployed on the test server, wherein upon creation of an application of the certain project type, subsequent files associated with the created application are located by the synchronization manager, wherein the synchronization manager recognizes files associated with more than one project type.

2. The system of claim 1, wherein the synchronization manager synchronizes the modified file of the software application in response to a user command.

3. The system of claim 1, wherein the synchronization manager determines whether any of the files comprising the software application has been modified by comparing timestamps associated with the files of the software application on the development system with timestamps associated with the respective files deployed on the test server.

4. The system of claim 1, wherein a user can prompt the synchronization manager to refrain from synchronizing the modified file.

5. The system of claim 1, wherein the synchronization manager restarts the software application deployed on the test server after synchronization.

6. The system of claim 5, wherein the synchronization manager initially installs the files comprising the software application on the test server.

7. The system of claim 1, wherein the pre-determined file type is chosen by a developer of the software application.

8. The system of claim 1, wherein the synchronization manager automatically synchronizes the modified file of the software application when modification to the modified file is made persistent.

9. The system of claim 1, wherein the synchronization manager indicates to a user that the modified file has been modified and needs to be synchronized with the respective file of the software application deployed on the test server when the modification to the file is made persistent.

10. The system of claim 1, wherein the synchronization manager synchronizes a file of the software application specified by the user.

11. The system of claim 1, wherein the synchronization manager monitors and synchronizes a plurality of applications between the development system and the test server.

12. A system as in claim 1, wherein at least a portion of the application files are compressed in a project zip file and the synchronization manager unpacks the project zip file and synchronizes each file contained in the zip file with the deployed application rather than synchronizing the project zip file.

13. A method for synchronizing software applications deployed on a test server comprising:

deploying a software application comprising a plurality of files from a development server system to a test server, at least a portion of the files for the software application having user-specified context parameters, the context parameters specifying parameters for registration with the application on the test server;

after deploying the software application on the test server, modifying one of the plurality of files on the development system;

determining, by a synchronization manager, which of the plurality of files comprising the software application have been modified since deployment of the software application on the test server;

raising, by the development system, an event identifying the modified file if the context parameters require an event to be raised;

automatically synchronizing only the modified file of the software application between the development system and the test server upon the event being raised; and

restarting the software application deployed on the test server after synchronization if the modified file is of a pre-determined type identified by a restart list of file extensions, wherein modification of some of the plurality of files does not require the software application to be restarted, the restarting of the software application causing the software application to be refreshed with the modified file

wherein the synchronization manager automatically locates files in the development system corresponding to files of software applications of the pre-determined type deployed on the test server, wherein upon creation of an application of the pre-determined type, subsequent files associated with the created application are located by the synchronization manager, wherein the synchronization manager recognizes files associated with more than one project type.

14. The method of claim 13, wherein determining which of the plurality of files comprising the software application have been modified comprises comparing timestamps associated with each of the plurality of files comprising the software application on the development system with timestamps associated with the plurality of respective files deployed on the test server.

15. The method of claim 13, further comprising automatically synchronizing the one modified file of the software application on the development system with the respective file deployed on the test server when modification of the modified file is made persistent.

16. The method of claim 13, further comprising notifying the synchronization manager of a modification made to one of the plurality of files.

17. A computer-readable medium which stores a set of instructions which when executed performs a method for synchronizing applications deployed on a test server, the method executed by the set of instructions comprising:

deploying a software application comprising a plurality of files from a development server system to a test server;

after deploying the software application on the test server, modifying one of the plurality of files on the development system;

determining, by a synchronization manager, which of the plurality of files comprising the software application have been modified by a user of a remote client and persisted on a storage device within the remote client since deployment of the software application on the test server;

raising, by the development system, an event identifying the modified file immediately upon persistence of the modified file;

automatically synchronizing only the modified file of the software application between the development system and the test server; and

restarting the software application deployed on the test server after synchronization if the modified file is of a pre-determined type identified by a restart list of file extensions, wherein modification of some of the plurality of files does not require the software application to be restarted, the restarting of the software application causing the software application to be refreshed with the modified file;

wherein the synchronization manager automatically locates files in the development system corresponding to files of software applications of the pre-determined type deployed on the test server, wherein upon creation of an application of the pre-determined type, subsequent files associated with the created application are located by the synchronization manager, wherein the synchronization manager recognizes files associated with more than one project type.