Time optimized replacement of a software application

• US 20040078793A1
• Filed: 12/01/2003
• Published: 04/22/2004
• Est. Priority Date: 01/19/2001
• Status: Active Grant

• Current Assignee: Nokia Siemens Networks GmbH & Company KG (Nokia Corporation)
• Original Assignee: Nokia Siemens Networks GmbH & Company KG (Nokia Corporation)
• Inventors: Krauss, Dietmar, Bragulla, Jurgen
• Granted Patent: US 7,340,738 B2
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57

Abstract

The invention relates to a method for replacing old software (10) that is in use with new software (12), which permits the maximum availability of the software. Said method is subdivided into a preparation phase (V) and an active phase (A). The preparation phase (V) take place during the operation of the old software (10). The active phase (A) is merely characterized by the execution of a MOVE command.

Claims

1. Method for performing a status change on at least one computer from an actual condition (16) to a target condition (18), the status change relating in particular to the replacement or initial operation of software, and which is subdivided into a preparation phase (V) and a subsequent active phase (A), the preparation phase (V) being executed in the actual condition (16) and having the following steps:

registering of control information (22) relating to the target condition (18),

automatic generation of at least one script (26) from the control information (22),

saving of the data for the target condition (18) to a cache directory,

and said status change being carried out during the active phase (A) by terminating operation in the actual condition (16) and applying the script (26) by means of which the data for the target condition (18) is relocated from the cache directory to a destination directory.

2. Method according to claim 1, characterized in that execution of the script(s) (26) is time-optimized.

3. Method according to at least one of the preceding claims, characterized in that an appropriate environment for the target condition (18) is generated automatically.

4. Method according to at least one of the preceding claims, characterized in that

the data for the target condition (18) is stored under automatically generated path names.

5. Method according to at least one of the preceding claims,

characterized in that

the computer is a computer within a cluster.

6. Method according to claim 5, characterized in that at least the active phase (A) takes place on the inactive sides of the cluster computers.

7. Method according to at least one of the preceding claims,

characterized in that the computer is a UNIX computer.

8. Method according to claim 7, characterized in that on completion of the active phase (A) the data for the target condition (18) is no longer in temporary storage, but is accessible in the destination directory by renaming a data tree root, in particular by means of a MOVE command.

9. Method according to at least one of the preceding claims, characterized in that

in addition the method optionally comprises the following step:

automatic restoration of the actual condition (16) after performing the status change, particularly by generating a backout package during the installation of a package (24).

10. Method according to at least one of the preceding claims, characterized in that

the data for the target condition (18) relates to a software package in which control information (24) has been incorporated.

11. Method according to claim 10, characterized in that the package (24) is unpacked in the cache directory.

12. Method according to at least one of the preceding claims, characterized in that

the status change involves installing new software (12) for the first time.

13. Method according to at least one of the preceding claims, characterized in that

the status change involves re-installing old software (10), in particular an upgrade and/or an update.

14. Method according to at least one of the preceding claims, characterized in that

the status change involves installing a patch for old software (10).

15. Method according to at least one of the preceding claims, characterized in that

the status change is performed automatically.

16. Program incorporating software code portions with which a method according to one of claims 1 to 15 is executed by a processor.

17. Arrangement for carrying out a method according to one of claims 1 to 15.