JP2001014156A - Dynamic switching method for decentralized object - Google Patents

Abstract

PROBLEM TO BE SOLVED: To switch a server object without stopping work in decentralized object environment by managing the versions of decentralized objects by making use of the functions of the decentralized objects. SOLUTION: A server object registers its version in a version management database 102 first. Then a search for whether or not there is an old server object having the same function is made. If not, the process is ended and the process of the original function of the server is performed. When there is an old server object, one new server object is started, the old server object is instructed to end instead, and the registration information of the corresponding server object is deleted from the version management database 102. The server object instructed to end is made to accept no request from a client thereafter and then a process needed to end the server object is performed. Consequently, the switching of the server objects is completed.

Description

DETAILED DESCRIPTION OF THE INVENTION

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a new server which eliminates a problem without interrupting a business in an environment in which processes of a number of server objects having the same function are activated by using distributed objects. The present invention relates to a distributed object dynamic switching method for switching to an object.

2. Description of the Related Art In the prior art, a method as disclosed in Japanese Patent Application Laid-Open No. 10-901405, "Software Maintenance Method" is used to manage source versions. Also, to guarantee the connection with the server object,
Japanese Patent Laid-Open No. 5-6275 discloses a technique for specifying a version in an interface, managing the version of the interface, connecting to the same version of the interface, and adding a method using a distributed object. Functional Extensions "
The method as shown in FIG. However, it does not manage the version of the object itself in consideration of operation. Therefore, in the related art, when there is an object to be switched, all servers are stopped and then a new object is started.

In the prior art, in the distributed object environment, since the version of the object itself is not managed, it is necessary to perform a careful operation when correctly replacing all with the version in which the defect is corrected. Yes, and the business had to be stopped temporarily. In other words, when fixing a bug and replacing the server object with a new one, it was necessary to stop all the old servers, suspend the service, and then start the new server. In this case, when switching to a new server, the service must be temporarily stopped. This has been a major problem in 24-hour operation. Therefore, it is an object of the present invention to perform version control of an object and solve this problem.

A server object is dynamically switched by using the function of a distributed object and managing the version of the object.
First, as a function, the server object always implements a "function for registering a version at startup" and a "function that can be terminated". Then, when starting the server, after registering the version, compare your version with the version of the server with the same function that has already been started, and if you find an old one, terminate the old server object. Instruct and launch a new version of the server. In addition,
The server object that has received the termination instruction prevents the server object in the middle of termination processing from accepting a request from the client, and terminates the process after performing processing necessary for terminating the server object. Thus, the switching of the server object is completed.

Embodiments of the present invention will be described below. All the server objects implement the functions described below and perform dynamic switching. First, a database for managing versions is prepared, and the server object registers the version in the database at the time of startup. In addition, the server object is enabled to receive a termination request, and in the termination processing, the server object registered at the time of activation is deleted. FIG. 1 shows the configuration of a system that executes the present invention. Several processes are running on the server object (101). These versions are recorded in the version control database (102). Now, a server object (103) of a new version of the server object in which the defect of the server object has been corrected is activated, and switching is performed. FIG. 2 shows a table structure of a version management database (102) for performing version management of server objects. It consists of a function name (201), a version (202), and a process ID (203) for identifying a server process, which are assigned to each function of the server object.
The processing performed at the time of starting the process in which the server object starts up will be described with reference to FIG. First, the server object registers its version in the version control database (102) (30).
1). Next, it searches for an old server object having the same function as itself (302). If not, the process is terminated (303), and the server performs its own function. If there is an old server object, replace the new server object with 1
Start (304), and instruct an end to the old server object instead, and delete the registration information of the corresponding server object from the version management database (102) (30).
Five). This process is repeated until all old server objects are gone. The server object that has received the termination instruction performs a deactivate operation of the POA function in CORBA so as not to receive a request from the client after that, performs processing necessary for terminating the server object, and terminates the process. This completes the switching of the server object. In FIG. 3 (302), the comparison of the version is made, not the comparison of the old and new, but the comparison of the same version as that of the user. Figure 3 (304) When launching a new server object, by taking the method of launching the same version as yourself instead of the new version, when the new one has a larger defect, the original version Or switch to a specific version. Also, when switching the server repeatedly, if the CPU load is large, immediately after switching one server object, the next server object is not switched immediately, and the system sleeps while the CPU load is high. It is also useful to prevent the overall load from increasing. If the switching process is performed when the server object starts, the load on the system increases and the server may take a long time to start.
When the server object is started, only the version of the server itself is registered, and the switching process is not performed. Instead, the switching process can be performed by another process. The processing performed in the switching processing will be described with reference to FIG. The data registered at the time of starting the server object is acquired from the version management database (102) as one of the started server objects from the version management database (401). When there are no unremoved items, the process ends (403). If it is not checked whether a server having the same function name as the server, that is, a server having the same function is older than the version, the next is taken out (404). If there is an old server, a new server object corresponding to the old server is started (405), and an end instruction is given to the old server (406). This switching process may be started by the operator when necessary, but it is more preferable that the switching process is registered as a process that is performed periodically as a regular task with a fixed period of time. When the number of processes of the server object is increased in order to reduce the work of the switching work, it is possible to add a judgment at the time of starting the server so that the switching can be performed by the same operation in operation. This will be described with reference to FIG. Before the version is registered in the process of FIG. 3 at the time of starting the process, the process shown in the flow of FIG. 5 is performed. First, it is determined whether an older version exists (501). If the old version does not exist, it is determined that the processing is to newly increase the server object process, and the processing is continued as it is.
If there is an old version, an end instruction is issued to the old version of the server object to be replaced as a switching process (502). After that, the process starts from the usual (301) in FIG. This makes it possible to make the operation of switching the server object having the defect corrected and the operation for newly starting the server object the same.

By implementing the function according to the present invention in the distributed object, there is an effect that the server object can be switched without stopping the business in the distributed object environment.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a system.

FIG. 2 is a diagram showing a table structure of a version management database.

FIG. 3 is a flowchart of a process when a server object is activated.

FIG. 4 is a flowchart of an update program when a version check is not performed at startup.

FIG. 5 is a flowchart of automating determination of a new startup and a switching process of a server.

Claims (2)

[Claims] In a distributed object environment, a server object version is managed by adding a function of managing a version of a server object and terminating an old object when the server object starts when an old object exists and starting a new object. A method for dynamically switching distributed objects, characterized by switching. 2. In the above-mentioned comparison of server object versions, if the version is different from the version when the server object is activated, not the version of the server, it is switched to the same version as the version of the server object to unify the version with the specific version. The method according to claim 1, wherein the switching is performed.