Phased upgrade of a computing environment

• US 20040044703A1
• Filed: 11/22/2002
• Published: 03/04/2004
• Est. Priority Date: 08/29/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kretz, Michael, Kessler, Jorg, Kompalli, Prasad, Pauly, Heinz, Wildhagen, Andreas
• Granted Patent: US 7,171,432 B2
• Time in Patent Office: Days
• US Class Current: 707/203
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99954 Version management

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 system comprising:

a first processing system including (a) stored instructions of a first version of an application program, (b) stored data associated with the first version of the application program, and (c) a processor to execute the stored instructions of the first version,

a second processing system including (a) stored instructions of a second version of the application program, (b) stored data associated with the second version of the application program, and (c) a processor to execute the stored instructions of the second version,

at least one of the first and second processing systems including a port through which user devices are served, and

an upgrade bridging facility having a portion associated with the first processing system and a portion associated with the second processing system to carry data modification messages between the two processing systems.

2. The system of claim 1 wherein the first version is a current version and second version is an upgrade version.

3. The system of claim 1 wherein the upgrade bridging facility includes at least one migration bridge associated with at least one of the first and second processing systems.

4. The system of claim 3 wherein each of the processing systems is associated with a migration bridge.

5. The system of claim 4 also including a communication link between the migration bridges of the respective processing systems.

6. The system of claim 3 wherein the migration bridge includes inbound and outbound flow management facilities.

7. The system of claim 3 wherein the migration bridge is configured to send, from the first processing system to the second processing system, a data exchange message including at least one data modification.

8. The system of claim 3 wherein the migration bridge is configured to receive, from the first processing system at the second processing system, a data exchange message including at least one data modification and to cause the data modification to be stored in association with the second version of the application program.

9. The system of claim 3 wherein the migration bridge is configured to cause the data modification to be stored in association with the second version of the application program after the data modification has been validated.

10. The system of claim 1 also including a mobile client capable of communication with at least one of the first and second processing systems.

11. The system of claim 1 also including an on-line client capable of communication with at least one of the first and second processing systems.

12. The system of claim 1 in which the first version comprises a current version of the application program, the second version comprises an upgrade version of the application program, and the data modification messages carry data modifications made to the stored data associated with one of the versions for use in association with the other version, and the system also includes mobile clients and on-line clients that are capable of communication with at least one of the first and second processing systems to access stored data that has been updated in accordance with the data modifications.

13. The system of claim 2 also including mobile clients of the current version and the second processing system is further configured to store current-version data modifications associated with the data exchange message in association with the upgrade version of the application program such that the current-version data modifications are available to the mobile clients of the upgrade version of the application program.

14. The system of claim 4 wherein the migration bridges associated with the two processing systems are running on a common computer system.

15. The system of claim 4 wherein a processor of the first migration bridge and a processor of the second migration bridge are the same processor.

16. The system of claim 1 wherein the upgrade bridging facility is configured to identify at least one data modification of the first version of the application program.

17. The system of claim 3 the migration bridge is configured to send, from the second processing system to the first processing system, a data exchange message including at least one data modification.

18. The system of claim 3 wherein the migration bridge is configured to receive, from the second processing system at the first processing system, a data exchange message including at least one data modification and to cause the data modification to be stored in association with the first version of the application program.

19. The system of claim 18 wherein the migration bridge is configured to cause the data modification to be stored the in association with the first version of the application program after the data modification has been validated.

20. The system of claim 3 also including mobile clients of the upgrade version and the first processing system is further configured to store upgrade-version data modifications associated with the data exchange message in association with the current version of the application program such that the upgrade-version data modifications are available to the mobile clients of the upgrade version of the application program.

21. An apparatus comprising

a processor, and

media bearing data associated with a version of an application program, the version comprising at least one of a starting version and a target version, the data being subject to data modifications,

the media also bearing program instructions capable of causing the processor to generate data modification messages based on the data modifications for communication to a processing system associated with the other of the starting version and the target version for use in connection with an upgrade of the application program from the starting version to the target version.

22. The apparatus of claim 21 in which the program instructions are capable of causing the apparatus to provide a migration bridge facility.

23. The apparatus of claim 22 in which the program instructions are capable of causing the apparatus to provide an outbound flow management facility and an inbound flow management facility.

24. The apparatus of claim 21 in which the program instructions are capable of causing the apparatus to provide a transfer service facility.

25. The apparatus of claim 21 in which the program instructions:

receive a synchronization message including at least one data modification, and

send a data exchange message including at least one data modification.

26. The apparatus of claim 25 in which the program instructions:

receive the synchronization message including at least one data modification at an outbound flow management facility, and

send a data exchange message including at least one data modification from an outbound flow management facility.

27. The apparatus of claim 25 in which the program instructions send the data exchange message to the other of the starting version and the target version for use in connection with an upgrade of the application program from the starting version to the target version.

28. The apparatus of claim 25 in which the program instructions send the data exchange message to a transfer service facility.

29. The apparatus of claim 21 in which the program instructions:

receive a data exchange message including at least one data modification; and

send a synchronization message including at least one data modification.

30. The apparatus of claim 29 in which the program instructions:

receive the data exchange message including at least one data modification at an inbound flow management facility, and

send the synchronization message including at least one data modification from an inbound flow management facility.

31. The apparatus of claim 29 in which the program instructions receive the data exchange message including at least one data modification from a transfer service facility.

32. The apparatus of claim 29 in which the program instructions receive the data exchange message including at least one data modification from the other of the starting version and the target version for use in connection with an upgrade of the application program from the starting version to the target version.

33. The apparatus of claim 21 wherein the apparatus and at least one of the starting version and the target version are running on a common computer system.

34. A system comprising:

a first migration bridge associated with a starting version of an application program, the first migration bridge comprising a processor connected to a storage device, the processor of the first migration bridge being configured to;

receive a starting-version synchronization message and starting-version data modifications associated with the starting-version synchronization message;

create a data exchange message based on the starting-version synchronization message,

associate the starting-version data modifications with the data exchange message,

send the data exchange message to a second migration bridge associated with a target version of the application program, the second migration bridge comprising a processor connected to a storage device, the processor of the second migration bridge being configured to;

receive the data exchange message,

create a target-version synchronization message based on the data exchange message,

associate the starting-version data modifications associated with the data exchange message with the target-version synchronization message, and

send the target-version synchronization message and the starting-version data modifications associated with the target-version synchronization message to the target version of the application program;

the target version of the application program being stored on a machine-accessible medium and including program instructions that when executed;

receive the target-version synchronization message and the starting-version data modifications associated with the target-version synchronization message,

determine whether the starting-version data modifications associated with the target-version synchronization message are valid, and

store the starting-version data modifications associated with the target-version synchronization message in association with the target version of the application program such that the starting-version data modifications are available to users of the target version of the application program.

35. The system of claim 34 wherein the processor of the second migration bridge being configured to only store the starting-version data modifications associated with the target-version synchronization message in association with the target version of the application program such that the starting-version data modifications are available to users of the target version of the application program when the starting-version data modifications are valid.

36. The system of claim 34 wherein:

the processor of the second migration bridge being further configured to send a synchronization notification message associated with the data exchange message to the first migration bridge after the starting-version data modifications have been validated; and

the processor of the first migration bridge being further configured;

receive the synchronization notification message, and

store the starting-version data modifications associated with the data exchange message in association with the starting version of the application program such that the starting-version data modifications are available to users of the starting version of the application program.

37. The system of claim 34 wherein at least one of the users of the target version of the application program or the users of the starting version of the application program includes a mobile client user.

38. A computer-readable medium or propagated signal having embodied thereon a computer program comprising one or more code segments configured to:

receive data associated with a version of an application program, the version comprising at least one of a starting version and a target version, the data being subject to data modifications; and

generate data modification messages based on the data modifications for communication to a processing system associated at least one of a starting version and a target version for use in connection with an upgrade of the application program from the starting version to the target version.

39. The medium or signal of claim 38 in which the one or more code segments are configured to:

receive a synchronization message including at least one data modification, and

send a data exchange message including at least one data modification.

40. The medium or signal of claim 39 in which the one or more code segments are configured to:

receive the synchronization message including at least one data modification at an outbound flow management facility, and

send a data exchange message including at least one data modification from an outbound flow management facility.

41. The medium or signal of claim 39 in which the one or more code segments are configured to send the data exchange message to the other of the starting version and the target version for use in connection with an upgrade of the application program from the starting version to the target version.

42. The medium or signal of claim 39 in which the one or more code segments are configured to send the data exchange message to a transfer service facility.

43. The medium or signal of claim 38 in which the one or more code segments are configured to:

receive a data exchange message including at least one data modification; and

send a synchronization message including at least one data modification.

44. The medium or signal of claim 43 in which the one or more code segments are configured to:

receive the data exchange message including at least one data modification at an inbound flow management facility, and

send the synchronization message including at least one data modification from an inbound flow management facility.

45. The medium or signal of claim 43 in which the one or more code segments are configured to receive the data exchange message including at least one data modification from a transfer service facility.

46. The medium or signal of claim 43 in which the one or more code segments are configured to receive the data exchange message including at least one data modification from the other of the starting version and the target version for use in connection with an upgrade of the application program from the starting version to the target version.