JPH0954679A - Method for clip back from agent - Google Patents

Abstract

PROBLEM TO BE SOLVED: To put software back to its original version at a request from an agent side. SOLUTION: After software of new version is distributed from a submanager 1 to the agent 3, software is resent at a request made on the agent side or old software is processed on the agent side by using update difference information 5 to put the old software back to its original version.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for switching back from an agent in a computer network system or the like in which software can be distributed from a sub manager to an agent.

[0002]

2. Description of the Related Art Conventionally, in software distribution, a sub-manager checks a version of an agent, and if the versions are different, the versions are unified.

[0003]

However, in the above-mentioned conventional method, since the sub-manager uniformly unifies the versions, a problem occurs when the agent wants to use the original version of the software.

[0004]

The present invention is characterized in that after a new version of software is distributed from a sub-manager to an agent, the software can be returned to the original version according to a request from the agent.

[0005]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is an explanatory diagram showing an operational configuration of software distribution. As shown in this figure, the sub-manager 1, the database 2, the agent 3, and the communication line 4
The sub manager 1 can change the program of the agent 3 by distributing the software.

In the present invention, the system having the above configuration is used,
It is possible to switch back from the agent by executing a version check from the agent 3 side to the sub manager to cause the sub manager 1 to retransmit the correct software, or by using an update difference information file described later. . For example, if there is an error in the program updated by the distribution from the sub-manager 1, the agent 3 cannot use the program unless the program is restored to the original version. Therefore, the agent 3 side performs version matching with the sub-manager 1, and the sub-manager 1 resends the correct program so that the operation can always be performed in a normal state without interrupting the work. Become.

Further, when the update difference information file described in detail below is used, the version can be returned to the original version only by the processing on the agent 3 side. FIG. 2 is a flowchart of the update difference information file creation portion, and the procedure for creating the update difference information file will be described using this figure. First, the software to be distributed is sub-manager 1
Register above (Sa1).

In the case of the update software, each file is checked to see which of deletion / update / addition / same procedure is required to create the update software based on the already registered software. (Sa
2) In the update difference information file on the database 2, the file name and the type of deletion / update / addition of the software that has been deleted / updated / added are described (Sa
3, Sa4, Sa5).

FIG. 3 is a conceptual diagram of the update difference information file created as described above. When the version matching is performed by the agent 3, the sub-manager 1 updates the distribution target software and the update difference information file 5
Is distributed to the agent 3.

The software distributed to the agent 3 is registered in the designated directory, but the software to be replaced (deleted file / old version file) is saved in the save directory. Next, a method of switching back from the agent 3 will be described. For example, a problem occurred while activating the distributed software, and the operator wanted to restore the version of the software, but the sub-manager 1
It is assumed that the correct distribution of the program cannot be received from. In this case, the operator instructs the agent 3 to switch back only the agent 3.

FIG. 4 is a flow chart of switching back from the agent, and the switching back procedure will be described based on this flowchart. The agent checks the update difference information file 5 (Sb1), confirms the type of deletion / update / addition described in each file (Sb2), and executes processing for each type of deletion / update / addition according to this type information. To do. The files described as deleted or updated are moved to the specified directory and the overwritten original files are overwritten (Sb3, Sb4), and the files described as added are deleted from the specified directory (Sb5). ).

By this processing, the original version of the software before the update is restored in the designated directory in the agent 3, which may occur when the communication line 4 with the sub-manager 1 fails. Also, it will be possible to operate without stopping work for a long time.

[0013]

When the agent program wants to return to the original version, the agent side performs the version matching with the sub manager and the sub manager resends the correct program, so that it is always in a normal state. With the effect that can be operated in.

Furthermore, by using the update difference information file, it becomes possible to restore the program version to the original version by the processing only on the agent side, and it is possible to operate normally without interruption even in an emergency. Have the effect.

[Brief description of drawings]

[Figure 1] Illustration of the operational configuration of software distribution

FIG. 2 is a flowchart of an update difference information file creation part.

FIG. 3 is a conceptual diagram of an update difference information file.

FIG. 4 is a flowchart of switching back from the agent.

[Explanation of symbols]

 1 Sub-manager 2 Database 3 Agent 4 Communication line 5 Update difference information file

Claims (2)

[Claims] 1. A method for switching back from an agent, wherein the sub-manager resends the original software to the agent based on a request from the agent after distributing the new version of the software from the sub-manager to the agent. 2. When a new version of software is distributed from a sub-manager to an agent and the software of the agent is updated, the sub-manager creates an update difference information file describing the update contents and delivers it to the agent, A method of reverting from an agent, characterized in that the agent can revert the software to the original version based on the update difference information file.