JPH09231148A - Distributed system - Google Patents

Abstract

(57) [Abstract] [Problem] To provide a distributed system in which system resources can be effectively used by setting restrictions within a range that does not hinder operation and dynamically deleting and installing software. SOLUTION: The client 21 monitors the usage frequency record data 23 by the monitoring processing 24 according to the contents defined in the monitoring definition data 22, and when it judges that the function needs to be deleted, the function is deleted from the client 21. The result is stored in the function presence / absence data 25. At the next operation, it is reinstalled from the server 11. As a result, the resources used by the deleted function are released, and other functions can utilize the released resources. Further, this action can be simulated at the time of system design, the necessary resources at the time of system construction can be calculated, and the system having the minimum necessary resources can be constructed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a distributed system in which a server / client is composed of a plurality of computers.

[0002]

2. Description of the Related Art FIG. 22 shows a general distributed system, and the system operation method of the conventional system will be described below. In FIG. 22, reference numeral 71 denotes a distributed system server, and 81 clients are connected to this server by communication lines to form a distributed system.

In this system, the server always has the software of each function A1 to C1 that operates on the server, and each client always has the software of each function A to J that operates on each client separately from the server. However, the software resident in each server and client performs the processing for each input information via the transmission processing as needed.

In these systems, generally 1
Multiple clients are connected to a single server, and each client has all the functions, and some functions are used infrequently. All the above software is always installed.

Therefore, frequently operating functions have been dealt with by installing a large capacity resource from the time of system construction so that the resource cannot be used effectively or the performance is not affected.

[0006]

As described above, in the conventional distributed system, even if the function distribution of the system is taken into consideration, it is possible to sufficiently realize the function and load distribution, which is an advantage of the distributed system. There wasn't.

Therefore, in order to secure sufficient performance when all the functions are operating, each server and client have considerably large resources from the beginning of system construction, and since many clients are connected, the user needs always. The system was not adapted to.

In order to solve the above-mentioned problems, the present invention considers the features of each function, restricts each function within a range that does not hinder operation, and dynamically deletes and installs software. It aims at effective use of system resources and reduction of resources at the beginning of system construction.

[0009]

In order to achieve the above object, a distributed system according to [Claim 1] of the present invention is a system comprising a server and a client, in which the server has all the functions that operate in this system. It is composed of an installation software package in which software is packaged for each function, an installation process for installing each client in accordance with an installation request from the client, and a transmission process for transmitting with each client.

Also, the client refers to the monitoring definition data for monitoring the usage frequency of each function, the usage frequency record data recording the actual usage frequency of each function, the monitoring definition data and the usage frequency record data, and referring to each function. The monitoring process that monitors the usage frequency to reduce the number of functions, the function presence / absence data in which the monitoring process saves the monitoring result, and the next time an operation request is made to each function However, it is characterized by comprising an installation determination process for making an installation request to the server, a transmission process for receiving the installation software package from the server, and an installation process for receiving the installation software package from the transmission process and installing it on the client.

A distributed system according to [claim 2] of the present invention is a system comprising a server and a client, wherein the server is a software package for installation in which software of all the functions operating in the system is packaged for each function, and a client. In response to an installation request from the client, it is configured by an installation process for installing in each client and a transmission process for transmitting with each client.

Also, the client refers to the monitoring definition data for monitoring the operating time of each function, the running time record data for monitoring the operating time of each function, the monitoring definition data and the running time record data, and refers to each function. The monitoring process that monitors the travel time of each function to reduce the functions, the function presence data that the monitoring process saves the monitoring result, and the next time the operation request is sent to each function However, it is characterized by comprising an installation determination process for making an installation request to the server, a transmission process for receiving the installation software package from the server, and an installation process for receiving the installation software package from the transmission process and installing it on the client.

A distributed system according to [claim 3] of the present invention is a system comprising a server and a client, wherein the server is an installation software package in which software of all functions operating in this system is packaged for each function, and a client. In response to an installation request from the client, it is configured by an installation process for installing in each client and a transmission process for transmitting with each client.

Further, the client determines from the function presence / absence definition data whether or not to delete each function, and whether or not each function needs to be deleted at the end of the operation of each function from the function presence / absence definition data. Monitoring process to delete a function, when requesting the operation of each function, refer to the function presence / absence definition data to determine the installation requirement of each function, make an installation request to the server, and receive a software package for installation from the server It is characterized by comprising an installation process for receiving an installation software package from the process and the transmission process and installing it in the client.

In a distributed system according to [claim 4] of the present invention, in a system comprising a server and a client, the server is a software package for installation in which software of all the functions operating in this system is packaged for each function, and a client. In response to an installation request from the client, it is configured by an installation process for installing in each client and a transmission process for transmitting with each client.

The client is a monitoring type of each function,
Monitoring definition data for monitoring usage frequency and running time, operation record data recording the operation record of each function, monitoring definition data and operation record data, monitoring the operation record of each function, and deleting the function Monitoring process, function presence / absence data 25 in which the monitoring process saves the monitoring result, and next time when an operation request is made to each function, this feature presence / absence data is referenced to determine whether or not each function needs to be installed, and an installation determination process for making an installation request to the server , A transmission process for receiving the installation software package from the server, and an installation process for receiving the installation software package from the transmission process and installing it on the client.

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of a distributed system according to [Claim 1] of the present invention will be described below with reference to FIGS.

In FIG. 1, the server 11 includes an installation software package 12 in which software for all functions operating in this system is packaged for each function, and an installation process 13 for installing in each client in response to an installation request from the client. It is composed of a transmission process 14 for transmitting with each client.

Further, the client 21 has monitoring definition data 22 for monitoring the usage frequency of each function, usage frequency record data 23 recording the actual usage frequency of each function, monitoring definition data 22 and usage frequency record data 23. Monitoring process 2 that refers to to monitor the usage frequency of each function and reduce the function
4, data whether or not the monitoring process has a function of saving the monitoring result 2
5, next time operation request to each function This function presence data 25
Installation determination processing 2 that determines whether or not each function needs to be installed by referring to the
6, a transmission process 27 for receiving the installation software package from the server 11, and an installation process 28 for receiving the installation software package from the transmission process 27 and installing it in the client 21.

The operation will be described below. The monitoring process 24 of the client 21 is the monitoring definition data 2 shown in FIG.
2 is monitored in a monitoring cycle, and in the processing flow of FIG. 5, one of the functions is selected in step 501, and in step 502, whether or not the function is a monitoring target is monitored. Judgment based on "monitor / do not monitor" in the definition data.

If “No”, the process returns to the function selection of Step 501, and if “Monitor”, the next Step 50.
3, the usage counter of the usage frequency record data 23 shown in FIG. 3 and the monitoring usage frequency of the monitoring definition data 22 shown in FIG. 2 are compared in magnitude. If the monitoring usage frequency is larger than the usage counter, the corresponding function is selected in step 504. The function is deleted and the function of the function presence / absence data 25 shown in FIG. On the contrary, if the monitoring usage frequency is smaller than the usage counter, the usage counter is reset in step 505 to continue the monitoring.

The usage frequency record data 23 is used for each function 2A-
2J starts operation and counts up as one time until the end. As a result, the predefined function can be deleted from the client machine according to the frequency of use, and the used resource can be released.

When a function operation is requested, in FIG.
In step 601, the installation determination process 26 is performed as shown in FIG.
The function presence / absence data 25 is checked to determine whether or not the function has been installed. If the function is already installed, an operation request for the function is issued in the next step 603. If the function is not installed, in step 602. The installation process 28 is requested to install the function.

At the time of the installation request, in FIG. 7, the installation process 28 that has received the installation request requests the server 11 to install the function requested in step 701. The transmission process 27 that has received the installation request transmits the installation request to the server 11 in step 705.

The transmission processing 14 of the server 11 which has received the installation request from the client 21 is performed in step 70.
In step 7, the received software installation request is sent to the installation process 13. Upon receiving the installation request, the installation process 13 takes out the software of the corresponding function from the installation software package 12 in step 709, and in step 710, sends the software to the client 21 to the transmission process 14.
Request to send software to.

The transmission process 14 that has received the installation software transmits the installation software to the client 21 in step 708. The transmission process 27 of the client 21, which has received the installation software from the server 11, passes the installation software received in step 706 to the installation process 28, and the installation process 28 which receives the installation software proceeds to step 7
The software is installed in 02, the function of the function presence / absence data 25 is set to be installed in step 703, and the function is activated in step 704.

As a result, the function deleted by the client 21 can be operated again on the same client. When the system is started up, the monitoring definition data 22 shown in FIG.
Install only the functions that are set to "Not monitor" from the server.

In this way, the resources used by the deleted function are released, and other functions can utilize the released resources. Further, by simulating this action at the time of system design and optimally designing the monitoring definition data, it is possible to calculate the required resources at the time of system construction and to construct the system having the minimum necessary resources.

Next, an embodiment of a distributed system according to [Claim 2] of the present invention will be described with reference to FIGS. In FIG. 8, in contrast to the usage frequency monitoring in [claim 1], it is configured to have traveling time recording data 43 for monitoring the operating time of each function.

The operation will be described below. The monitoring process 44 of the client 21 is the monitoring definition data 42 shown in FIG. 9 at step 1000 in the processing flow of FIG.
Each function is monitored in the monitoring cycle of step 1001
Then, in the monitoring definition data 42 of FIG. 9, it is determined whether or not the function is a monitoring target, and for the function to be “monitored”, in step 1002, the running time of the running time record data 43 shown in FIG. The monitoring travel times of the monitoring definition data 42 of FIG. 9 are compared.

If the traveling time is longer than the monitoring traveling time, the traveling time is reset in step 1004 and the monitoring is continued. On the contrary, if the traveling time is shorter, this function is deleted in step 1003 and the function presence / absence data 25 shown in FIG. The relevant function of “is not installed”.

In the running time record data 43, the time is added as the running time of each function from the start to the end of each function. As a result, the predefined function can be deleted from the client machine according to its running time, and the used resources can be released.

When a function operation is requested, in FIG.
In step 601, the installation determination process 26 is performed as shown in FIG.
The function presence / absence data 25 is checked to determine whether or not the function has been installed. If the function is already installed, an operation request for the function is issued in the next step 603. If the function is not installed, in step 602. The installation process 28 is requested to install the function.

At the time of the installation request, in FIG. 7, the installation process 28 that has received the installation request requests the server 11 to install the function requested in step 701. The transmission process 27 that has received the installation request transmits the installation request to the server 11 in step 705.

The transmission processing 14 of the server 11 which has received the installation request from the client 21 is performed in step 70.
In step 7, the received software installation request is sent to the installation process 13. Upon receiving the installation request, the installation process 13 takes out the software of the corresponding function from the installation software package 12 in step 709, and in step 710, sends the software to the client 21 to the transmission process 14.
Request to send software to.

The transmission process 14 that has received the installation software transmits the installation software to the client in step 708. Transmission process 2 of the client 21 which received the installation software from the server 11
7 passes the installation software received in step 706 to the installation processing 28, and the installation processing 28 which received the installation software proceeds to step 702.
In step 703, the software is installed, the function in the function presence / absence data 25 is set as already installed, and in step 704, the function is activated.

As a result, the function deleted by the client 21 can be operated again on the same client. When the system is started up, the monitoring definition data 42 shown in FIG.
Install only the functions that are set to "Not monitor" from the server. In this way, the same operation as the invention according to [Claim 1] can be provided by using the running time of the function as a key.

Next, an embodiment of the distributed system according to [claim 3] of the present invention will be described with reference to FIGS. In FIG. 12, the server 11 is configured by the same means as the embodiment of FIG.

Further, the client 21 has the function presence / absence definition data 6 defining whether or not each function is to be deleted.
5. At the end of the operation of each function, the necessity of deletion of each function is determined from the function presence / absence definition data 65, and the monitoring process 64 for deleting the function of "installation required", the function presence / absence definition data 65 at the time of operation request of each function An installation determination process 26 for determining whether or not each function needs to be installed and making an installation request to the server 11, a transmission process 27 for receiving an installation software package from the server 11, and a transmission process 27
And an installation process 28 for receiving the installation software package from and installing it on the client 21.

The operation will be described below. The function presence / absence definition data 65 of the client 21 is
It defines whether or not each of the functions 2A to 2J is always installed. Each function from 2A to 2J is
After the operation ends, the monitoring process 64 is notified of the operation end.

The monitoring process 64 which has received the operation end notification from each of the functions 2A to 2J is step 1401 in FIG.
In step 1402, it is determined whether or not the function for which the end notification has been made is "installation required" in the function presence / absence definition data 65, and the operation completion notification is received from each of the functions 2A to 2J. If so, the function is deleted in step 1403, and if installation is not required, the process ends.

As a result, the resources used after the completion of the operation of this function can be released. In addition, at the time of requesting the operation of the function, in FIG. 15, the installation determination processing 26 refers to the function presence / absence definition data 65 of FIG. 13 in step 1501, and when the function is not required to be installed, the operation of the function is performed in step 603. A request is made, and if "installation is required", a request for installation of the function is made to the installation process 28 at step 602.

At the time of the installation request, in FIG. 16, the installation process 28 that has received the installation request requests the server 11 to install the function requested in step 701. The transmission process 27 that has received the installation request transmits the installation request to the server 11 in step 705.

The transmission processing 14 of the server 11, which has received the installation request from the client 21, is step 70.
The software installation request received in step 7 is sent to the installation process 13. Upon receiving the installation request, the installation process 13 takes out the software of the corresponding function from the installation software package 12 in step 709, and requests the transmission process 14 to send the software to the client 21 in step 710.

The transmission processing 14 that has received the installation software transmits the installation software to the client in step 708. The transmission process 27 of the client 21, which has received the installation software from the server 11, passes the installation software received in step 706 to the installation process 28, and the installation process 28 which receives the installation software proceeds to step 70.
2 install the software, then step 70
In step 4, the function is activated.

As a result, the function deleted by the client 21 can be operated again on the same client. It should be noted that at the time of system startup, only the functions for which "installation required / not required" in the function presence / absence definition data 65 shown in FIG.

As described above, in the apparatus configured as shown in FIG. 12, the client 21 performs the installation determination process according to the contents defined in the function presence / absence definition data 65.
The monitoring process 64 deletes the function at the end of its operation, and installs it when the function is requested to restart.

By applying this to the function A and the function B which do not function on the client at the same time, the resources used by the respective functions are released at the end of the operation of the functions, and the other functions are released at the time of the operation. Resources can be utilized. In the above example, the resource required for system construction is the resource with the larger resource required for each of function A and function B, and it is possible to construct a system in which the resource required for the entire system is reduced.

Next, an embodiment of a distributed system according to [claim 4] of the present invention will be described with reference to FIGS. In FIG. 17, the server 11 is configured by the same means as the embodiment of FIG.

Further, the client 21 has monitoring definition data 82 for monitoring the monitoring type of each function, usage frequency and running time, operation record data 83 recording the operation record of each function, monitoring definition data 82 and operation record data. 83, the monitoring process 84 for monitoring the function of each function and deleting the function, the function presence / absence data 25 for storing the monitoring result by the monitoring process, and the function presence / absence data 2 at the time of the operation request to each function next time 2
5, the installation determination processing 2 that determines whether or not each function needs to be installed and requests the server 11 to install.
6, a transmission process 27 for receiving the installation software package from the server 11, and an installation process 28 for receiving the installation software package from the transmission process 27 and installing it in the client 21.

Monitoring definition data 82 of the client 21
In FIG. 18, each of the functions 2A to
Defines whether or not 2J is deleted at the end of operation, and the function that is not deleted at the end of operation defines whether or not to monitor the running time or frequency of use, and defines its monitoring cycle and monitoring data. doing.

That is, in * A of FIG. 18, it is defined whether or not to dynamically delete / install. * B is * A
Is effective when is not deleted at the end. The contents of * 1 are usage frequency monitoring and running time monitoring. * 2 is the monitoring usage frequency when * 1 is the usage frequency monitoring, and * 1 is the monitoring travel time when the traveling time is monitored.

The operation will be described below. Monitoring process 8
4 is composed of two processes shown in FIGS. 20 and 21. First, in FIG. 20, the monitoring process 22 monitors each function at the monitoring cycle of the monitoring definition data 82 shown in FIG. 18, and the process of FIG. In the flow, step 2001
Then, in step 2002, the function which is judged "whether or not to delete at the end of operation" in the monitoring definition data 82 of FIG.
It is determined whether or not to monitor with the monitoring definition data 82,
In the monitoring function, in step 2003, it is determined whether to monitor the traveling time or the usage frequency.
The function for monitoring the traveling time using the operation record data 83 shown in FIG. 2 performs the traveling monitoring process in the same manner as in [claim 2] in step 2004, and the function for monitoring the use frequency in step 2005 is the same as in claim 1. Similarly, the usage frequency monitoring process is performed.

Next, in FIG. 21, the monitoring process 22 receives an end notification from each of the functions 2A to 2J at the end of the operation, and in step 2101, the function indicates "delete at end" in the monitoring definition data 82 shown in the monitoring definition data 18. “Yes / No” is determined, and in step 2102, the function that is “deleted” at the end of the operation is deleted, and the function presence / absence data 2
The function of No. 5 is set to "not installed".

As a result, [claim 1] to [claim 3]
The invention according to can be applied to each function, and can be deleted from the client machine to release the used resources.

When a function operation is requested, in FIG.
In step 601, the installation determination process 26 is performed as shown in FIG.
The function presence / absence data 25 is checked to determine whether or not the function has been installed. If the function is already installed, an operation request for the function is issued in the next step 603. If the function is not installed, in step 602. The installation process 28 is requested to install the function.

At the time of the installation request, in FIG. 7, the installation process 28 which has received the installation request requests the server 11 to install the function requested in step 701. The transmission process 27 that has received the installation request transmits the installation request to the server 11 in step 705.

The transmission processing 14 of the server 11 which has received the installation request from the client 21 proceeds to step 70.
In step 7, the received software installation request is sent to the installation process 13. Upon receiving the installation request, the installation process 13 takes out the software of the corresponding function from the installation software package 12 in step 709, and in step 710, sends the software to the client 21 to the transmission process 14.
Request to send software to.

The transmission process 14 that has received the installation software transmits the installation software to the client in step 708. Transmission process 2 of the client 21 which received the installation software from the server 11
7 passes the installation software received in step 706 to the installation processing 28, and the installation processing 28 which received the installation software proceeds to step 702.
In step 703, the software is installed, the function in the function presence / absence data 25 is set as already installed, and in step 704, the function is activated.

As a result, the function deleted by the client 21 can be operated again on the same client. It should be noted that, at the time of system startup, only the functions that are “not deleted at the end” and “not monitored” in the monitoring definition data 82 shown in FIG. 18 during the startup process are installed from the server.

In the apparatus constructed as shown in FIG. 17,
When the inventions according to [Claim 1], [Claim 2] and [Claim 3] are taken into consideration in consideration of the characteristics and importance of each function and used in combination, more effective use of resources and system construction The required resources can be reduced.

[0062]

As described above, in the distributed system of the present invention, the server has the installation software package and the installation processing, and the client has the function usage frequency monitoring means, the installation means, and the means for defining the monitoring definition data. By having the function, it is possible to delete a function that is rarely used from the client machine when not needed, and it is possible to effectively use the resources of the client machine, and it is possible to reduce the resources of the entire client machine. .

In the distributed system of the present invention, the server has the installation software package and the installation process, and the client has the function running time monitoring means, the installation means, and the means for defining the monitoring definition data. It is possible to delete a function with a short running time from the client machine when not needed, to effectively use the resources of the client machine, and to reduce the resources of the entire client machine.

In the distributed system of the present invention, the server has the installation software package and the installation processing, and the client has the installation means and the means for defining the function presence / absence definition data. It can be deleted from the machine, the resources of the client machine can be effectively used, and the resources of the entire client machine can be reduced.

Furthermore, by combining the inventions according to [Claim 1], [Claim 2] and [Claim 3], the distributed system of the present invention is less frequently operated by the invention according to [Claim 3]. For functions that are not required to be ready to start when an operation is requested, they can be installed in functional units only during operation. [Claim 1] and [Claim 2]
According to the invention of claim 1, the monitoring definition data of the client can define the usage frequency and the travel time for each function, and it is possible to utilize the resource and reduce the resource in consideration of the character, the importance, the required performance and the like of each function.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of a distributed system according to [claim 1] of the present invention.

FIG. 2 is a configuration diagram of monitoring definition data according to [claim 1] of the present invention.

FIG. 3 is a configuration diagram of usage frequency record data according to [claim 1] of the present invention.

FIG. 4 is a configuration diagram of function presence / absence data in [claim 1], [claim 2], and [claim 4] of the present invention.

FIG. 5 is a monitoring process flow in [claim 1] of the present invention.

FIG. 6 is an installation determination processing flow in [claim 1], [claim 2], and [claim 4] of the present invention.

FIG. 7 is an installation processing flow in [claim 1], [claim 2], and [claim 4] of the present invention.

FIG. 8 is a configuration diagram of an embodiment of a distributed system according to [claim 2] of the present invention.

FIG. 9 is a configuration diagram of monitoring definition data according to [claim 2] of the present invention.

FIG. 10 is a configuration diagram of traveling time recording data according to [claim 2] of the present invention.

FIG. 11 is a monitoring process flow in [claim 2] of the present invention.

FIG. 12 is a configuration diagram of an embodiment of a distributed system according to [claim 3] of the present invention.

FIG. 13 is a configuration diagram of function presence / absence definition data according to [claim 3] of the present invention.

FIG. 14 is a monitoring processing flow in [claim 3] of the present invention.

FIG. 15 is an installation determination processing flow in [claim 3] of the present invention.

FIG. 16 is an installation processing flow in [claim 3] of the present invention.

FIG. 17 is a configuration diagram of an embodiment of a distributed system according to [claim 4] of the present invention.

FIG. 18 is a configuration diagram of monitoring definition data according to [claim 4] of the present invention.

FIG. 19 is a configuration diagram of motion record data according to [claim 4] of the present invention.

FIG. 20 is a monitoring process flow (1) according to [claim 4] of the present invention.

FIG. 21 is a monitoring processing flow (2) according to [claim 4] of the present invention.

FIG. 22 is a configuration diagram of a conventional distributed system.

[Explanation of symbols]

11 server 12 installation software package 13 installation process 14 transmission process 21 client 22, 42, 82 monitoring definition data 23 usage frequency record data 24, 44, 64, 84 monitoring process 25 function presence / absence data 26 installation determination process 27 transmission process 28 installation Processing 43 Running time recording data 65 Function presence / absence definition data 83 Operation recording data 2A, 8A Function A 2B, 8B Function B 2C, 8C Function C 2J, 8J Function J 8D Function D

Claims (4)

[Claims] 1. In a system comprising a server having all the functions of the system and a client in which some of the functions of the system operate, the server has a software package for installation of all the functions, and the client monitors the operation frequency of each function. The distributed system is characterized by effectively using the resources of the client by having the function of deleting the function having a low operation frequency from the client and reinstalling it from the server at the next operation. 2. In a system comprising a server having all the functions of the system and a client in which some of the functions of the system operate, the server has a software package for installation of all the functions, and the client monitors the running time of each function. A distributed system characterized by effectively using the resources of the client by deleting the function with a short running time from the client and re-installing it from the server at the next operation. 3. In a system consisting of a server having all the functions of the system and a client in which some of the functions of the system operate, the server has a software package for installation of all the functions, and the client uses the software according to the characteristics of the function. A distributed system characterized in that the software of the function is installed only from the server only when the function is used, and the function of deleting the function when not in use is used to effectively utilize the resources of the client. 4. In a system comprising a server having all the functions of the system and a client in which some of the functions of the system operate, the server has a software package for installation of all the functions, and the client uses the software according to the characteristics of the functions. Functions with a low frequency, functions with a short running time, and when not in use Software for that function is deleted from the client,
A distributed system characterized by effectively using the resources of the client by having a function to be installed from the server at the time of next operation or use.