Phased upgrade of a computing environment

• US 7,263,698 B2
• Filed: 08/29/2002
• Issued: 08/28/2007
• Est. Priority Date: 08/29/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kompalli, Prasad, Pauly, Heinz, Wildhagen, Andreas, Kretz, Michael, Kessler, Jo
• Primary Examiner(s): Wood; William H.
• Application Number:
  US10/230,407
• Publication Number:
  US 20040044998A1
• Time in Patent Office: 1,825 Days
• Field of Search: 717168-173, 719312-313, 719/319, 719/329
• US Class Current: 717/170
• CPC Class Codes: G06F 8/656 while running

Abstract

Techniques are provided to permit a gradual or phased migration of a computing environment including groups of mobile clients to a new version of an application program such that the unavailability or downtime of any mobile client is minimized. In one general aspect, the techniques permit a mobile client to connect with an application server of the corresponding version for synchronization whether the mobile client is operating on the starting-version or the new or target-version of the application program and migrates the data between the two versions of the application program. A migration bridge between the starting-version and the target-version of the application program synchronizes the data in the two versions of the application program.

Claims

1. A computer-implemented method for operating two versions of an application program while in the process of upgrading from a starting-version application to a target-version application, a computing environment including one or more groups of mobile clients, the method comprising:

operating a starting-version application including stored instructions of the starting-version application and stored data associated with the starting-version application, the starting-version application being accessible to one or more starting-version mobile clients;

operating a target-version application including stored instructions of the target-version application and stored data associated with the target-version application, the target-version application being accessible to one or more target-version mobile clients;

sending from the starting-version application a data exchange message including one or more starting-version data modifications associated with the data exchange message, a starting-version data modification being based on a data modification made using one of the one or more starting-version mobile clients; and

in response to the data exchange message, storing the one or more starting-version data modifications associated with the data exchange message in the stored data associated with the target-version application such that the one or more starting-version data modifications are available to one of the one or more target-version mobile clients.

2. The method of claim 1 further comprising identifying one or more starting-version data modifications to be sent from the starting-version application.

3. The method of claim 1 further comprising:

modifying one or more of the starting-version mobile clients from accessing the starting-version application to accessing the target-version application; and

repeating the modifying until all starting-version mobile clients have been modified to access the target-version application.

4. The method of claim 1 wherein:

operating the starting-version application comprises operating a starting-version application using a first computer system, and

operating the target-version application comprises operating a target-version application using a second, different computer system.

5. The method of claim 1 wherein operating the starting-version application and the target-version application comprises using a single computer system to operate both applications.

6. The method of claim 1 wherein storing the one or more starting-version data modifications associated with the data exchange message in the stored data associated with the target-version application comprises:

having the target-version application validate the one or more starting-version data modifications associated with the data exchange message,

storing the one or more starting-version data modifications associated with the data exchange message such that the one or more starting-version data modifications are available to one of the one or more target-version mobile clients only when the one or more starting-version data modifications associated with the data exchange message are valid,

sending an acknowledgement message to the starting-version application, and

storing the one or more starting-version data modifications associated with the data exchange message such that the one or more starting-version data modifications are available to one of the one or more starting-version mobile clients only when the one or more starting-version data modifications associated with the data exchange message are valid.

7. The method of claim 1 wherein operating the target-version application comprises making the target-version application accessible to one or more target-version mobile clients and one or more on-line clients.

8. The method of claim 1 further comprising:

receiving a starting-version synchronization message and one or more starting-version data modifications associated with the starting-version synchronization message from a starting-version mobile client, and

copying the one or more starting-version data modifications associated with the starting-version synchronization message into the data exchange message.

9. The method of claim 8 further comprising:

copying the one or more starting-version data modifications associated with the data exchange message into a target-version synchronization message,

associating the one or more starting-version data modifications with the target-version synchronization message, and

sending the target-version synchronization message and the one or more starting-version data modifications associated with the target-version synchronization message to at least one of the one or more target-version mobile clients.

10. The method of claim 1 wherein the data exchange message comprises a first data exchange message, further comprising:

sending a second data exchange message from the target-version application along with one or more target-version data modifications associated with the second data exchange message; and

storing the one or more target-version data modifications associated with the second data exchange message in the stored data associated with the starting-version application such that the one or more target-version data modifications are available to at least one of the one or more starting-version mobile clients.

11. The method of claim 10 further comprising:

receiving a target-version synchronization message and the one or more target-version data modifications associated with the target-version synchronization message from a target-version mobile client, and

copying the one or more target-version data modifications associated with the target-version synchronization message into the second data exchange message.

12. The method of claim 11 further comprising:

copying the one or more target-version data modifications associated with the second data exchange message into a starting-version synchronization message,

associating the one or more target-version data modifications with the starting-version synchronization message, and

sending the starting-version synchronization message and one or more target-version data modifications associated with the starting-version synchronization message to at least one of the one or more starting-version mobile clients.

13. The method of claim 11 wherein the structure of the second data exchange message is the same as the structure of the first data exchange message.

14. The method of claim 11 wherein the structure of the second data exchange message is different from the structure of the first data exchange message.

15. A computer-readable storage medium having embodied thereon a computer program configured to operate two versions of an application program while in the process of upgrading from a starting-version application to a target-version application, a computing environment including one or more groups of mobile clients, the medium comprising one or more code segments configured to:

operate a starting-version application accessible to one or more starting-version mobile clients, the starting-version application including stored instructions of the starting-version application and stored data associated with the starting-version application;

operate a target-version application accessible to one or more target-version mobile clients, the target-version application including stored instructions of the target-version application and stored data associated with the target-version application;

send from the starting-version application program a data exchange message including one or more starting-version data modifications associated with the data exchange message, a starting-version data modification being based on a data modification made using one of the one or more starting-version mobile clients; and

in response to the data exchange message, store the one or more starting-version data modifications associated with the data exchange message in the stored data associated with the target-version application such that the one or more starting-version data modifications are available to one of the one or more target-version mobile clients.

16. The medium of claim 15 further comprising one or more code segments configured to identify one or more starting-version data modifications to be sent from the starting-version application.

17. The medium of claim 15 wherein the one or more code segments configured to store the one or more starting-version data modifications associated with the data exchange message comprise one or more code segments configured to:

have the target-version application validate the one or more starting-version data modifications associated with the data exchange message,

store the one or more starting-version data modifications associated with the data exchange message such that the one or more starting-version data modifications are available to one of the one or more target-version mobile clients only when the one or more starting-version data modifications associated with the data exchange message are valid,

send an acknowledgement message to the starting-version application, and

store the one or more starting-version data modifications associated with the data exchange message such that the one or more starting-version data modifications are available to one of the one or more starting-version mobile clients only when the one or more starting-version data modifications associated with the data exchange message are valid.

18. The medium of claim 15 wherein the one or more code segments configured to operate the target-version application comprise one or more code segments configured to make the target-version application accessible to one or more target-version mobile clients and one or more on-line clients.

19. The medium of claim 15 further comprising one or more code segments configured to:

receive a starting-version synchronization message and one or more starting-version data modifications associated with the starting-version synchronization message from a starting-version mobile client, and

copy the one or more starting-version data modifications associated with the starting-version synchronization message into the data exchange message.

20. The medium of claim 19 further comprising one or more code segments configured to:

copy the one or more starting-version data modifications associated with the data exchange message into a target-version synchronization message,

associate the one or more starting-version data modifications with the target-version synchronization message, and

send the target-version synchronization message and the one or more starting-version data modifications associated with the target-version synchronization message to at least one of the one or more target-version mobile clients.

21. The medium of claim 15 further comprising one or more code segments configured to:

send a second data exchange message from the target-version application along with one or more target-version data modifications associated with the second data exchange message; and

store the one or more target-version data modifications associated with the second data exchange message in the stored data associated with the starting-version application such that the one or more target-version data modifications are available to at least one of the one or more starting-version mobile clients.

22. The medium of claim 21 further comprising one or more code segments configured to:

receive a target-version synchronization message and the one or more target-version data modifications associated with the target-version synchronization message from a target-version mobile client, and

copy the one or more target-version data modifications associated with the target-version synchronization message into the second data exchange message.

23. The medium of claim 22 further comprising one or more code segments configured to:

copy the one or more target-version data modifications associated with the second data exchange message into a starting-version synchronization message,

associate the one or more target-version data modifications with the starting-version synchronization message, and

send the starting-version synchronization message and one or more target-version data modifications associated with the starting-version synchronization message to at least one of the one or more starting-version mobile clients.