JPH10240538A - Program loading system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve system performance and to improve the efficiency of a management job by managing a required program on a client by a using frequency, loading only the program of a high using frequency from a server and holding it in the client. SOLUTION: The client 20 is provided with a program library file 23 for storing the program of the high using frequency, a client program version management table 22 for holding the version number and using frequency of the program used by the client and a program loader 21 for inquiring the version number of the program to the server 10 at the time of using an optional program, loading the program held by the client itself when the version number matches with the version number of the one held by the server, loading the program transferred by the server when it does not match and storing the program of the high using frequency in the file of the client itself.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program loading method, and more particularly to a program loading method in a distributed information processing system including a server and a client.

[0002]

2. Description of the Related Art In a distributed information processing system called a server-client system, a single server centrally manages programs executed by a plurality of clients in a centralized manner, and responds to server management rules or client requests. The server sends the corresponding program.

For example, according to Japanese Patent Application Laid-Open No. Hei 5-233498, items displayed on the information display device of each branch are managed by the display item table managed by the host computer, and the contents of each item are updated. Occasionally, according to this display item table, the update data is transmitted only to the information display terminals of the necessary branches.

In Japanese Patent Application Laid-Open No. 63-280369, when a business program on the intelligent terminal side managed by the host computer is changed, a distribution management for managing an updated program list and a distribution state of each terminal is performed. An apparatus for receiving a program in the first processing after the terminal is turned on based on the information is shown.

[0005]

In the conventional program loading method as described above, the first problem is that when a large-scale system is constructed, the number of clients increases and the role of each client differs. When you are
Managing and maintaining the version control and distribution status of all clients and all programs running on them on the host computer would result in an excessive burden on the management department. The reason is that clients are frequently installed, and furthermore, the business categories assigned to the clients are dynamically changed, and the programs are changed in the course of the change. With these changes, it becomes necessary to maintain the distribution management information without fail, so that the host-centered management based on the distribution management information increases the work load of the management department.

A second problem is that the host load is concentrated at the time of starting. The reason is that the transfer is performed as part of the business start process when the power is turned on, so that, for example, a transfer request is received from all clients in the first business start time zone in the morning. In addition, despite the difference in the frequency of the program used depending on the role of the client and the department, unnecessary and urgent transfer is performed collectively, so that the transfer load of the system is further increased.

An object of the present invention is to improve the system performance by managing necessary programs on a client at a frequency of use, loading only frequently used programs from a server, and holding the programs at a client in order to improve the above-mentioned drawbacks. It is an object of the present invention to provide a program loading method for enhancing the efficiency of management work.

[0008]

According to the present invention, there is provided a program loading method for a distributed information processing system including a server and a client, wherein the server has the latest program of all programs used in the distributed information processing system. The version is maintained and the version number of each program is managed. When the version number matches the program held by the server itself in response to the inquiry about the program version number from the client, the fact is notified. If they do not match, the corresponding program stored is transferred to the client, and the client manages the version number and frequency of use of the program used by itself, and when using an arbitrary program, updates the version number of the program to the server. And the version number is the version number of the server When do the loads a program the client itself held, loads a program the server has transferred when they do not match, and the frequently used program so as to store the client's own files.

In the program loading method according to the present invention, the server includes a program library file for storing the latest version of all programs used in the distributed information processing system, and a server program version for storing the version number of each program. In response to an inquiry from the client about the program version number from the client, when the version number matches the program held by the server itself, the server notifies the server that the version number matches. When the version numbers do not match, the corresponding program held is notified. And a program loader that transfers the program to the client.

Further, in the program loading method according to the present invention, the program loader stores a program used in the distributed information processing system in the program library file and records the version number of the program in the server program version management table. A program registration updating unit, a version number determining unit that refers to the server program version management table to determine whether there is a program that matches the version number of the program queried by the client, and a determination result of the version number determining unit. A determination result transmitting unit for notifying the client; and a program loading unit for transferring a corresponding program stored in the program library file to the client when the determination results do not match.

In the program loading method according to the present invention, the client holds a program library file for storing a frequently used program among programs used by the client, and a version number and a usage frequency of the program used by the client. A client program version management table to be used, and when using an arbitrary program, the server inquires of the server about the version of the program. When the version matches the version of the one held by the server, the program held by the client itself is checked. And a program loader that loads the program transferred by the server when the names do not match, and stores a frequently used program in a file of the client itself.

Further, in the program loading method according to the present invention, the program loader refers to the use frequency updating means for recording the use frequency of the program used by the client in the client program version management table, and the client program version management table. A version inquiring means for acquiring the version number of the program and notifying the server of the version number, and a program loading means for loading a corresponding program from a program library file in accordance with the response of the server to the notification of the version number inquiring means. A program expanding means for expanding the program transferred from the server in a memory and recording the version number in a client program version management table, and when the frequency of use of the program exceeds a preset frequency of use. Means for storing the program in the program library file and recording the version number and frequency of use of the program in the client program version management table; and Deleting means for searching and deleting an infrequently used program from the program library file.

That is, according to the program loading method of the present invention, the program loader on the client manages the distributed program with the program version management information,
Since the required program is notified to the server program loader, the server program loader manages only the version of the program and does not need to manage the distribution status.

Further, the program loader of the client manages the version number of the program used and stored on the client and checks the version number on the server. Therefore, if the version number has not changed, the program loader does not load the program from the server. Therefore, there is no particular pressure on the communication load.

Further, since the load occurs when the updated program is used for the first time on the client, the load does not concentrate when the system is started.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of the present invention. In the figure, a program loading method according to the present invention holds the latest versions of all programs used in a distributed information processing system including a server and a client, manages the version number of each program, and executes a program version from the client. A server 10 for notifying when the version number matches the program held by the server itself in response to the number inquiry, and transferring the held program to the client when the version numbers do not match; It manages the version number and frequency of use of the used programs, queries the server for the version number of the program when using an arbitrary program, and when the version number matches the version number of the one held by the server, the client itself Loads the program held by, and if there is no match Load the program whose serial server has transferred, and a client 20 to store the most frequently used programs in its own file.

Here, the server 10 includes a program library file 13 for storing the latest versions of all programs used in the distributed information processing system, and a server program version management table 1 for storing the version numbers of each program.
In response to the inquiry about the program version number from the client, when the version number matches the program held by the server itself, a notification to that effect is sent. When the version numbers do not match, the corresponding program held is notified. A program loader 11 for transferring the data to the client.

The program loader 11 stores a program to be used in the distributed information processing system in the program library file and records the version number of the program in the server program version management table. A version number judging unit 11c for judging the presence or absence of a program that matches the version number of the program inquired by the client with reference to the server program version management table; A result transmitting unit 11d; and a program loading unit 1 for transferring a corresponding program stored in the program library file to the client when the determination result does not match.
1b.

The client 20 stores a program library file 23 for storing frequently used programs among programs used by the client 20, and a client program version management table 22 for storing the version number and the frequency of use of the programs used by the client. When using an arbitrary program, the server queries the server for the version number of the program, and when the version number matches the version number of the one held by the server, loads the program held by the client itself and does not match. A program loader 21 for loading the program transferred by the server and storing a frequently used program in a file of the client itself.

The program loader 21 includes a use frequency updating unit 21d for recording the frequency of use of the program used by the client in the client program version management table, and the program loader 21 refers to the client program version management table. Version number inquiry means 21c for acquiring a version number and notifying the server of the version number
Program loading means 21 for loading a corresponding program from a program library file in accordance with a response of the server to the notification of the version number inquiry means.
b, a program expanding means 21e for expanding a program transferred from the server in a memory and recording the version number in a client program version management table, and when the use frequency of the program exceeds a preset use frequency, A program registration / updating means 21a for storing a program in the program library file and recording the version number and frequency of use of the program in the client program version management table; and a timer 21g for periodically starting the client program version management table Deletion means 21 for searching and deleting infrequently used programs from the program library file
f.

FIG. 2 is an explanatory diagram showing the format of the program version management table. FIG. 2A shows an example of the server program version management table 12, in which a program name and its version number are recorded. FIG. 2B shows an example of the client program version management table 22, in which a program name, its version number, and the number of times of use are similarly recorded.

FIG. 3 is an explanatory diagram showing the format of the program library file 13 described above. In the figure, the program library file 13 stores a main body of each program following a table showing the program name and its version number. Note that the program library file 23 is also configured in the same format as described above.

FIG. 4 is a flowchart showing the operation of the above-described program loading method. The operation of the present invention will be described with reference to FIG.

First, the program loader 21 receives a request for calling a program in order to start a business on the client 20 (step 31).
d records the use frequency of the program in the client program version management table 22 (step 32).

Next, the version number inquiry means 21 c sends the client 20 to the program loader 11 of the server 10 based on the information in the client program version management table 22.
An inquiry is made as to whether the version of the program in the above program library file 23 matches the version on the server 10. The client program version management table 22 describes the program name, the version number of the program in the program library file, and the calling frequency.
If the program is not in the client program library file 23, the version number is set to 0 (steps 33 and 34).

The version number judging means 11c of the program loader 11 of the server obtains the version number of the program in the program library file 13 of the server from the server program version management table 12, and the version number of the program corresponds to the program version number on the client. It is compared whether they match (step 35).

If they do not match, the program is loaded using the program loading means 11b, and the program version management information and the program are transmitted to the client program loader 21 by the determination result transmitting means 11d (step 36). If they match, only the status is notified to the client program loader 21 by the determination result transmitting means 11d.

The program loading means 21e of the program loader on the client receives the response from the server program loader 11 by the version number inquiry means 21c, and if the version number of the program matches the program version number on the server, A program loading means 21b
Is loaded from the program library file 23 of the client (steps 37 and 38). If they do not match, the program returned as one of the responses is expanded in the memory (step 39).

Subsequently, the program registration updating means 21a
Determines the frequency of use in the client program version management table (step 40), stores the program in the program library file 23 if the program is frequently used, and stores the program name and version number in the client program version management table. Update (step 41,
42).

As described above, the communication load between the server and the client can be reduced by loading the program from the program library file on the client.

Next, the processing when the program is updated will be described in detail.

When updating a program registered in the program library file of the server, the update is performed via the program registration / update means 11a of the server. At this time, the program registration updating means 11a also updates the version number in the server program version management table 12.

When the program is updated and the client inquires the version number for the first time, the version number on the client does not match the version number on the server. New programs are transferred. Here, the server program loader does not need to manage which program has been transferred to which client. That is,
The latest program is delivered to the client without the intervention of the operator.

When a task to be processed by the client is newly added, since the corresponding program does not exist in the client program library file, the version number of the corresponding program is 0 in the client program version management table. . Therefore, when the version number is inquired to the program loader of the server, the latest version of the program is returned. When this task is routinely processed, the frequency of use of the program on the client program version management table increases, and the program development means 2
1e stores the program in a program library file. At this time, the program version number is set in the client program version management table for the first time.

Thereafter, the data is loaded from the client program library file, and the communication load is reduced.
There is no need for the server to manage the distribution destination of the program in consideration of the client's business.

When there is no longer any task to be processed by the client, the frequency of use of the program on the client program version management table decreases. At this time,
The timer 21g at a fixed time interval activates the deleting unit 21f. The deletion unit 21f deletes the less frequently used programs from the client program library file, and sets the version number on the client program version management table to zero.

As described above, the unnecessary program is automatically released from the client program library file, so that the server does not need to be aware of the client's business and manage the deletion of the program.

[0039]

As described in detail above, according to the program loading method of the present invention, the client manages the program used by itself and holds the frequently used program in its own file. Server-side program management can be greatly reduced. That is, the server manages the version number of each program, but does not need to manage the program used by each client.

Further, since the program is transferred from the server in accordance with the request of the client, there is no need to transfer the program unnecessarily and urgently. Therefore, since the program distribution can be distributed, intensive transfer is reduced, and the system load can be reduced. That is, there is an effect that the system performance is improved and the management work is made more efficient.

[Brief description of the drawings]

FIG. 1 is a block diagram showing one embodiment of the present invention.

FIG. 2 is an explanatory diagram showing an example of a program version management table.

FIG. 3 is an explanatory diagram showing an example of a program library file.

FIG. 4 is a flowchart showing an operation of a program loading method according to the present invention.

[Explanation of symbols]

 Reference Signs List 10 server 11, 21 program loader 11a, 21a program registration / update means 11b, 21b program load means 11c version number determination means 11d determination result transmission means 12 server program version management table 13, 23 program library file 20 client 21c version number inquiry means 21d Usage frequency updating means 21e Program expanding means 21f Deleting means 21g Timer 22 Client program version management table

Claims (5)

[Claims] 1. In a program loading method for a distributed information processing system including a server and a client, the server holds the latest version of all programs used in the distributed information processing system and manages the version number of each program. In response to the inquiry about the program version number from the client, when the version number matches the program held by the server itself, a notice to that effect is given;
When the version numbers do not match, the corresponding program stored is transferred to the client, and the client manages the version number and frequency of use of the program used by itself, and the version number of the program when using an arbitrary program To the server, and when the version number matches the version number of the one held by the server, loads the program held by the client itself. When the version number does not match, loads the program transferred by the server. A high load program in a file of the client itself. 2. The program loading method according to claim 1, wherein the server stores a program library file for storing the latest versions of all programs used in the distributed information processing system, and a server for storing a version number of each program. In response to the program version management table and the program version number inquiry from the client, when the version number matches the program held by the server itself, this is notified, and when the version numbers do not match, the corresponding version is held. And a program loader for transferring the program to the client. 3. The program loading method according to claim 2, wherein the program loader stores a program used in the distributed information processing system in the program library file, and stores a version number of the program in the server program version management table. Program registration updating means for recording, version number determining means for referring to the server program version management table to determine whether or not there is a program that matches the version number of the program queried by the client, and determination by the version number determining means A program comprising: a determination result transmitting unit that notifies a result to the client; and a program loading unit that transfers a corresponding program stored in the program library file to the client when the determination result does not match. Load method. 4. The program loading method according to claim 1, wherein the client stores a program library file storing a frequently used program among programs used by the client, a version number and a use frequency of the program used by the client. And a client program version management table for storing the version of the program, and inquiring the server about the version of the program when using an arbitrary program, and when the version matches the version of the version stored in the server, the client itself stores the version A program loader for loading a program, loading the program transferred by the server when the names do not match, and storing a frequently used program in a file of the client itself. 5. The program loading method according to claim 4, wherein said program loader records usage frequency of a program used by said client in said client program version management table, and said client program version management table. Version inquiring means for obtaining the version number of the program by referring to the server and notifying the server of the version number, and a program loader for loading the corresponding program from a program library file in accordance with the server's response to the notification of the version number inquiring means Means, program expansion means for expanding the program transferred from the server in a memory and recording the version number in a client program version management table, and when the frequency of use of the program exceeds a preset frequency of use. Means for storing the program in the program library file and recording the version number and frequency of use of the program in the client program version management table; and A program loading method comprising: a deletion unit for searching and deleting a program which is not frequently used from the program library file.