Method and system for nondisruptive deployment during upgrading of enterprise systems
First Claim
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. using a 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;
d. generating a new configuration file having the values of Current_Step and Next_Step;
e. providing for a new client component to be deployed accompanied by a system downtime equal to said new client component deployment time;
f. making said new configuration file available to said new client component by setting the value of Next_Step to the value of Current_Step;
g. accessing said new server component via said naming service using the step values in the new configuration file, andh. providing for resumed use of the previous version if problems arise with the new server component.
1 Assignment
0 Petitions
Accused Products
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.
36 Citations
26 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. using a 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;d. generating a new configuration file having the values of Current_Step and Next_Step; e. providing for a new client component to be deployed accompanied by a system downtime equal to said new client component deployment time; f. making said new configuration file available to said new client component by setting the value of Next_Step to the value of Current_Step; g. accessing said new server component via said naming service using the step values in the new configuration file, and h. providing for resumed use of the previous version if problems arise with the new server component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. 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 use a 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;d. a means to generate a new configuration file having the values of Current_Step and Next_Step; e. a means to deploy a new client component with an accompanying system downtime equal to said new client component deployment time; f. a means to make said new configuration file available to said new client component by setting the value of Next_Step to the value of Current_Step; g. a means to access said new server component via said naming service using, the step values in the new configuration file, and h. a means to provide for resumed use of the previous version if problems arise with the new server component. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26)
-
Specification