Method and system for nondisruptive deployment during upgrading of enterprise systems

• US 20040139175A1
• Filed: 01/13/2003
• Published: 07/15/2004
• Est. Priority Date: 01/13/2003
• Status: Active Grant

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Inventors: Lin, Chih-Tsung
• Granted Patent: US 7,089,548 B2
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: G06F 8/656 while running

Abstract

A method and system that provides for near-zero downtime when updating enterprise system software in a client/server environment and elimination of the need to re-compile the client code with a new server component name as the new name can be addressed in a naming service. Client components will automatically connect to new-version enterprise server components that are backward compatible. Old-version client components will still work as new enterprise server components are deployed even if they are not backward compatible. Using a design with a step algorithm, the incompatibilities of client and enterprise server components are resolved. Client components automatically check a configuration file at initialization time or in parallel for the correct compatible version to use. Client rollback to the previous version is easily accomplished if bugs are found in the new deployment.

Claims

1. A method for nondisruptive updating of client/server systems comprising:

a. applying a step procedure combining generation of a unique identifier for a new server component with deployment and un-deployment of system components;

b. registering said unique identifier in a naming service;

c. generating a new configuration file from which to obtain the value of the next step;

d. providing for a new client component to be deployed accompanied by a system downtime equal to said new client component deployment time;

e. making said new configuration file available in place of a configuration file to said new client component with next step value now current step value;

f. accessing said new server component via said naming service using the new configuration file step value, and

g. providing for resumed use of the previous version if problems arise with the new server component.

2. The method for nondisruptive updating of claim 1, wherein said step procedure assures compatibility between the client component and said server component.

3. The method for nondisruptive updating of claim 1, wherein the step naming function

Current_Step:

;

={01} (value read from present configuration file)

Component_Ref;

;

={Component reference name which has been defined in interface}

Next_Step;

;

=(Current_Step) XOR (1)

Component_Name;

;

=Component_Ref+Next_Step

is a part of said step procedure.

4. The method for nondisruptive updating of claim 3, wherein the value of current step will iterate between 0 and 1.

5. The method for nondisruptive updating of claim 3, wherein said component name derived from said step naming function is said unique identifier.

6. The method for nondisruptive updating of claim 5, wherein said unique identifier is registered with said naming service when said new server component is first deployed.

7. The method for nondisruptive updating of claim 6, wherein said naming service contains the server components'"'"' names and addresses.

8. The method for nondisruptive updating of claim 7, wherein said server component name can be changed in said naming service rather than by re-compiling client code.

9. The method for nondisruptive updating of claim 1, wherein said system downtime is approximately measured in milliseconds to seconds depending on the size of said new client component.

10. The method for nondisruptive updating of claim 1, wherein said client component will automatically connect to said new enterprise component if they are backward compatible.

11. The method for nondisruptive updating of claim 10, wherein if said client component is backward compatible only the previous configuration file needs to be deployed to access the previous server component when problems arise.

12. The method for nondisruptive updating of claim 1, wherein redeployment of the previous client component in combination with said previous configuration file allows for said resumed use of previous version.

13. The method for nondisruptive updating of claim 1, wherein the said new client component can either initially load said new configuration file information or receive it in parallel from a secondary thread connection to the said new configuration file when accessing said new server component.

14. The method for nondisruptive updating of claim 1, wherein said previous server component can be un-deployed after a period of successful operation of said new server component.

15. A system for nondisruptive updating of client/server systems comprising of:

a. a means to apply a step procedure to combine generation of a unique identifier for a new server component with deployment and un-deployment of system components;

b. a means to register said unique identifier in a naming service;

c. a means to generate a new configuration file from which to obtain the value of the next step;

d. a means to deploy a new client component with an accompanying system downtime equal to said new client component deployment time;

e. a means to make said new configuration file available in place of a configuration file to said new client component with next step value now current step value;

f. a means to access said new server component via said naming service using the new configuration file step value, and

g. a means to provide for resumed use of the previous version if problems arise with the new server component.

16. The system for nondisruptive updating of claim 15, wherein said step procedure assures compatibility between the client component and said server component.

17. The system for nondisruptive updating of claim 15, wherein the step naming function

Current_Step:

;

={01} (value read from present configuration file)

Component_Ref;

;

={Component reference name which has been defined in interface}

Next_Step;

;

=(Current_Step) XOR (1)

Component_Name;

;

=Component_Ref+Next_Step

is a part of said step procedure.

18. The system for nondisruptive updating of claim 17, wherein the value of current step will iterate between 0 and 1.

19. The system for nondisruptive updating of claim 17, wherein said component name derived from said step naming function is said unique identifier.

20. The system for nondisruptive updating of claim 19, wherein said unique identifier is registered with said naming service when said new server component is first deployed.

21. The system for nondisruptive updating of claim 20, wherein said naming service contains the server components'"'"' names and addresses.

22. The system for nondisruptive updating of claim 21, wherein said server component name can be changed in said naming service rather than by re-compiling client code.

23. The system for nondisruptive updating of claim 15, wherein said system downtime is approximately measured in milliseconds to seconds depending on the size of said new client component.

24. The system for nondisruptive updating of claim 15, wherein said client component will automatically connect to said new enterprise component if they are backward compatible.

25. The system for nondisruptive updating of claim 24, wherein if said client component is backward compatible only the previous configuration file needs to be deployed to access the previous server component when problems arise.

26. The system for nondisruptive updating of claim 15, wherein redeployment of the previous client component in combination with said previous configuration file allows for said resumed use of previous version.

27. The system for nondisruptive updating of claim 15, wherein the said new client component can either initially load said new configuration file information or receive it in parallel from a secondary thread connection to the said new configuration file when accessing said new server component.

28. The system for nondisruptive updating of claim 15, wherein the said previous server component can be un-deployed after a period of successful operation of said new server component.