JPH10124432A - Client server system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a client server system which can grasp at an optional time the state of a mobile program module that moves in a network and is executed by one or plural information processors and also can perform the control of discontinuation, etc. SOLUTION: A server 30 includes a state table holding means 70 which holds the name and the state (under execution, under discontinuation, end of execution, movement, etc.) of a program module. A program execution means 50 registers the execution state of the program module to the means 70 via a state table management means 60. When a request is received from another machine for confirmation of the execution state of the program module, the execution state is acquired from the means 70. When other servers 35 and 36 are operating, the execution state of the program module is confirmed to a moving destination server and the answer of this server is sent back to a client. The execution state of the program module is confirmed against a discontinuation request, and an execution discontinuation instruction is sent to the server which is executing the program module. Then, the execution of the program module is discontinued.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a client-server system, and more particularly, to a client-server system using a mobile program module.

[0002]

2. Description of the Related Art In a client server system,
In a system that not only issues commands to the server, but also uploads program modules that operate on the server from the client side and receives the results of the operation, the client issues the commands and moves freely over the network to collect information. For example, a mobile program module called a "worm" that executes or executes a process, or an agent that moves a plurality of servers to accomplish one task is used.

For example, in a system proposed in Japanese Patent Application Laid-Open No. Hei 7-152699, a server determines the movement of a process. According to the publication, a computer system connected to a network detects the load situation, and outputs a move request to move a process to another computer system when the load amount exceeds a predetermined value. A system is described in which another computer system notifies that it will respond to a move request, and a computer system with a large load receives a move permission notification and moves a process to the computer system of the notification source. I have.

[0004] IEEE Personal Communications Decem
A paper published in ber 1995 (“The Use of Network
-Based Migrating User Agents for Personal Communic
ation Services ”) (referred to as Reference 1) proposes a system in which when a user moves with a terminal, a connection destination server is changed, and as a result, a user's program module (process) moves. .

Further, Japanese Patent Application Laid-Open No. 4-294655 proposes a configuration in which the state of an electronic mail (received, viewed, etc.) on the electronic mail receiving side of the electronic mail system can be referred to from the transmitting side. .

[0006]

However, the above-mentioned prior art has the following problems.

(1) The first problem is that once executed, the mobile program module remains executed even if it is no longer needed, and there is a useless process.

[0008] The reason is that in the above-mentioned prior art, because of the mobility and asynchronousness of the program module, a means for accessing the running or moving Worm or the agent from the client side, for example, checking the execution status This is because there is no means for stopping the execution.

(2) The second problem is that the client changes the operation in accordance with the status of the server, and cannot operate efficiently (a constant load state) as the whole system. Another problem is that the reliability of the program module on the user's network is low.

[0010] The reason is that the mobile program does not have means for checking the execution status of where and what is being executed.

(3) The third problem is the above-mentioned Japanese Patent Laid-Open No.
According to Japanese Patent No. 94655, when an e-mail recipient transfers an e-mail received to another person, the state of the e-mail at the transfer destination cannot be confirmed from the first e-mail sender.

The reason is described in the above-mentioned Japanese Patent Application Laid-Open No. 4-294655.
This is because the publication does not consider the transfer of e-mail and does not have a mechanism for tracing the outgoing mail management table from one to the next.

Accordingly, the present invention has been made in view of the above circumstances, and has as its object to check the execution status of a running worm or agent from a client side, for example, to confirm or cancel the execution status. An object of the present invention is to provide a client-server system capable of performing access.

Another object of the present invention is to provide a client-server system capable of confirming the execution status of where and what a mobile program is executing.

Still another object of the present invention is to provide a client server system capable of tracking a program module or the like moving between a plurality of terminals.

[0016]

In order to achieve the above object, the present invention provides an input / output means for receiving an input from a user and outputting necessary information to the user, and an input / output means for inputting the information from the input / output means. A client that selects a program module to be executed based on the information processing device, determines an execution order, and requests another information processing device connected to the network, and a program module requested by another information processing device connected to the network And a server that returns the execution result of the execution, the server determines the contents of the message received via the network, and distributes the message to a predetermined means of its own device, Network access means for transmitting data of its own device to an appropriate information processing device connected to the network Program module executing means for executing a program module transmitted from another information processing apparatus via the network, execution status table holding means for holding an execution status of a program, and execution for managing the execution status table holding means And a status table management means, wherein the execution status of the program module can be checked.

[0017]

Embodiments of the present invention will be described below. In a preferred embodiment of the present invention, an input / output means (10 in FIG. 1) for receiving an input from a user and outputting necessary information to the user, and an input / output means (10 in FIG. 1). A client (20 in FIG. 1) that selects a program module to be executed based on the input, determines an execution order, and requests a server (30 in FIG. 1) connected to the network, and a client (20 in FIG. 1) A server that executes the program module requested from 20) in FIG. 1 and returns the execution result (FIG. 1)
The server (30 in FIG. 1) includes:
Network access means (4 in FIG. 1) which determines the contents of the message received via the network, distributes the message to a predetermined means of its own device, and transmits the data of its own device to an appropriate server connected to the network.
0), program module execution means (50 in FIG. 1) for executing a program module transmitted from another device via the network, and status table holding means (70 in FIG. 1) for holding the execution status of the program. And a status table management means (60 in FIG. 1) for managing the execution status table holding means, which enables the execution status of the mobile program module in the server to be confirmed and the access control to stop the execution.

More specifically, the status table holding means (70 in FIG. 1) holds the actual status of the mobile program module, and includes the mobile program module name, the execution status (running, stopped, execution completed). ), And the movement status (whether or not to move, the destination).

Also, program execution means (50 in FIG. 1)
Registers the execution status of the mobile program module in the status table holding means (70 in FIG. 1) via the status table management means (60 in FIG. 1).

The network access means (40 in FIG. 1) receives the execution status confirmation request and the stop request from the client (20 in FIG. 1) and performs the respective processes.

When a request for confirming the execution status from the client (20 in FIG. 1) arrives at the network access means (40 in FIG. 1) of the server via the network, the execution status is confirmed from the status table holding means (70 in FIG. 1). To win.

If the execution status of the status table holding means is “execution completed” or “moved”, the execution status of the program module is being executed in another server. Client (Figure 1
To 20).

When a stop request is received from the client (20 in FIG. 1), after confirming the execution status, an execution stop command is sent to the server executing the corresponding mobile program module, and the server stops moving. Stop execution of type program module.

[0024]

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an embodiment of the present invention;

FIG. 1 shows a configuration of a client server system according to one embodiment of the present invention.

Referring to FIG. 1, this embodiment comprises a client 20 and an input / output means 10 for the client 20.
And a plurality of servers # 1 (3
0), # 2 to #n (35 to 36, collectively indicated by 31)
And is composed of

The server 30 includes a network access unit 40, a program execution unit 50, a status table management unit 60, a status table holding unit 70, and a server list holding unit 80.

The input / output means 10 is connected to a client 20 for transmitting and receiving data to and from the server 30, and transmits a command from a user to the server 30 via the client 20.
The result for the command from the server is received via the client 20 and presented to the user.

The client 20 stores program modules to be executed on the network. If the execution server name of the program module is known in advance, the server name on which the execution is executed is described in the program module.

Further, each of the servers # 1 to #n adds a server name to the executed program module.

Network access means 4 of server 30
No. 0 exchanges data with the client 20 and another server 31 via the network. Further, the network access means 40 sends messages from the client 20 and the other server 31 to the status table management means 60.
And the program module from the client 20 is sent to the program execution means 50.

The program execution means 50 executes the program module obtained through the network access means 40, and executes the program module.
When the execution stop instruction is received from, the execution of the program module is stopped. Then, the execution status of the program module is sent to the status table management means 60.

The status table management means 60 interprets the command received from the network access means 40, obtains the corresponding data from the status table holding means 70, and passes the data to the network access means 40. The status table management means 60 receives the execution status of the program module from the program execution means 50 and updates the status table holding means 70.

The status table holding means 70 is a database for holding the execution status of each program module.

The server list holding means 80 stores the server 30
And a list of server names that are capable of transferring program modules.

Next, the operation of this embodiment will be described with reference to FIG.

When the user issues a mobile program start command (11) from the input / output means 10 to the client 20, the client 20 transfers the mobile program module to the network access means 40 (21).

The network access means 40 transfers the mobile program module to the program execution means 50 (41).

The program executing means 50 executes the program module to perform the processing, and transmits the program status 51 to the status table managing means 60.

FIG. 2 shows an example of the program status 51. The program module name 201 (“calc2
2.exe ”), the client name 202 (“ Client A ”in FIG. 2) that loaded the program module,
It is composed of a place currently being executed and an execution status 203 ("in execution" in FIG. 2). FIG. 2 shows that “the program module calc22.exe from the client A is being executed on the server # 1”.

The status table management means 60 stores the received program status 51 as status data 61 in the status table holding means 70. The content of the status data 61 is the same as the content of the program status 51.

FIG. 3 shows an example of the contents of the situation table holding means 70. The status table holding unit 70 holds the status of a program module from a plurality of clients. FIG. 3 shows that the status table holding unit 70 holds a status 301 related to calc22.exe from the client A and a status 302 related to calc23.exe from the client B. The status types are "Running", "Execution completed", "Complete execution", "Stopping",
"Cancel" and the like.

The program execution means 50 notifies the status table management means 60 of the status 51 each time the execution status of the program module changes (for example, execution completion, execution stop, etc.).

When the execution of the program module is completed in the program execution means 50, the program module and the execution result are transferred to the network access means (52).

If it is determined that the program module needs to be moved from the program module to another server, the program execution means 50 acquires the destination from the program module, and determines the destination in the current program status ( As “moving”), it is stored in the situation table holding means 70 via the situation table management means 60.

The moving program module is transferred from the network access means 40 to one of the other servers 31. In the example shown in FIG. 1, it is assumed that the data is transferred to the server # 2 (35) (44). At the time of transfer of the program module, an execution result in the server 30 is added. Hereinafter, when a program module is referred to, it is assumed that an execution result is added to the program module.

The server # 2 (35) that has received the program module repeats the above-described series of flows in the server # 2 (35) from the reception of the program module by the network access means to the transfer to another server. Is finally transferred to the server #n (36) (3
2) Assuming that the execution of the program module has been completed, the server #n (36)
The execution result 33 of the program module is passed to the server 30, and a notification 34 of “complete execution completed” is given to the server 30 accessed first.

The network access unit 40 of the server 30 that has received the notification 34 of “complete execution completion” passes the status to the status table holding unit 70 as status data 61.

Referring to FIG. 4 and FIG. 5, a series of flow of program module movement and notification in this embodiment will be described.

In the client # 1, a program module to be requested to execute is selected (in FIG. 5, calc22.ex
e), the destination of the program module, and the order of movement (in FIG. 4, the order of server # 1 → server # 2 → server # 3 → server # 4) is added to the program module. .

The program module is handed over to the server # 1 for execution (401 in FIG. 4). At this time, the contents of the status table holding means 70 of the server # 1 are set to 5 in FIG.
01. The contents of the status table holding means 70 of the server # 1 shown by 501 in FIG. 5 are the same as the contents shown in FIG.

When the execution of the program module is completed in the server # 1, the status table holding means 70 of the server # 1 outputs information indicating that the execution has been completed in the server # 1 (server # 1), as indicated by 502 in FIG. 1: execution completed) is set.

Next, the program module is transferred to the server # 2 (402 in FIG. 4) and executed by the server # 2.
The contents of the status table holding means 70 of the server # 2 at this time are shown by 503 in FIG. In the status table holding means 70, the location and the execution status at the time are
"Server # 2: running", that is, a situation in which a program module is running on server # 2 is added.

When the execution of the program module in the server # 2 is completed, an execution completion notice is sent to the server # 1 (403 in FIG. 4), and the program module is transferred to the server # 2.
3 (404 in FIG. 4).

When the execution completion notification is received from the server # 2, the contents of the status table holding means 70 of the server # 1 are stored in the status table 504.
Shown in In the status table holding means 70 of the server # 1,
The status indicating the completion of the execution in the server # 2 is set.

Then, the server # 3 executes the program module. When the execution is completed, a complete execution completion notification is sent to the server # 1 (405 in FIG. 4), and the result of the program module is sent to the client # 1. It is returned (406 in FIG. 4). The contents of the status table holding means 70 of the server # 1 that has received the execution completion notification from the server # 3 are shown at 504 in FIG. As indicated by reference numeral 504 in FIG. 5, the status table holding unit 70 of the server # 1 indicates that the execution of the program module calc22.exe has been completed.

Next, a series of flows from when one server receives the program module to when the completion processing is performed will be described with reference to the flowchart of FIG.

When a program module is received (step 601), it is checked whether the program module is from a client or a server (step 602).

In the case of a program module from the client (see Y in step 602), the status table holding means is updated using the program module name and the client name (step 603). An example of the update is as shown in FIG.

Next, the received program module is executed (step 604), and when the execution is completed (see Y in step 605), the execution completion information is written into the status table holding means (step 606).

The server name is also recorded as an execution record in the program module, and the next transfer destination is obtained from the program module (step 607). If it cannot be obtained (N in step 608), the result is sent to the client. Return (step 609) and end.

When the next transfer destination can be obtained (step 6)
The program module is transferred to the transfer destination (step 610), and the process ends.

In the case of a program module transferred from another server (N in step 602), first, a start server name which is the name of the server on which this program module was executed is obtained from the program module (step 620). ), The execution of the program module is reported to the start server ("executing" message is passed) (step 621), and the program module is executed (step 622).

When the execution is completed (step 623), the next transfer destination is obtained from the program module (step 624). If the next transfer destination cannot be obtained (N in step 625), a complete execution completion notification is sent to the start server (step 626), the result is returned to the client (step 627), and the process ends.

When the next transfer destination has been acquired (step 6)
25, the start server is notified of the execution completion message (step 628), the program module is transferred to the transfer destination (step 610), and the process ends.

Next, referring to FIG.
The operation when the execution status confirmation message is received from will be described.

The execution status confirmation command (11) input via the input / output means 10 is passed to the network access means 40 via the client 20 (21).

The network access unit 40 requests the status management table management unit 60 to search for the execution status of the program module corresponding to the status management table management unit 60 (42).

The status management table 60 acquires the execution status of the corresponding program module from the status table holding means 70 (71), and transmits this to the network access means (62). Further, the network access means 40 informs the client 20 of the execution status (4
3), this is obtained by the input / output means 10 (22) and displayed.

If the execution status is not recorded in the status table holding means 70, the destination is checked by the following method.

(1) The past destination of the same module is searched from the status table holding means 70, and the execution status is sequentially inquired to the servers having the largest number of past moves.

(2) As a result, if the destination is unknown even if the execution status is inquired to all the servers, all the records described in the status table holding means are sequentially transferred to the server having the largest number of times of movement. Request module search.

(3) The server that has received the search request makes an inquiry about the presence or absence of movement using the method (1).
If the destination is unknown even if all the servers are inquired about the presence or absence of the movement, a search request is not made and an unknown notification is sent to the requesting server.

(4) When an unknown notification is received from all servers, an inquiry is made to all the servers registered in the server list holding means 80 as to whether or not the server has moved.

FIG. 7 shows an example of the server list 80. 1
The row stores the name of one server. In FIG. 7, “ServerA”, “ServerB”, “ob
Four servers “p” and “iten” are described.

The server list 81 sent from the server list holding means 80 to the network access means 40 has the same contents.

Next, an operation when the server 30 receives an execution stop request from the client 20 will be described with reference to FIG.

The execution stop request (11) input through the input / output means 10 is transmitted to the server 3 via the client 20.
0 to the network access means 40 (2
1).

After confirming the execution status, the network access means 40 sends an execution stop request to the server executing the corresponding program module when the server is found, and stops the execution of the program module in the server. The server 30 is notified of the execution stop, and the status of the status table holding unit 70 of the server 30 is set to “execution stop”.

The server 30 sends the result to the client 2
0, and the input / output means 10 displays it.

On the other hand, if the server executing the program module cannot be found, a failure result is sent to the client 20, and the input / output means 10 displays it.

Next, an operation when the server 30 receives an execution stop message from the client 20 will be described with reference to FIG.

The execution stop command (11) input via the input / output means 10 is transmitted to the server 3 via the client 20.
0 to the network access means 40 (2
1).

Network access means 4 of server 30
0 sends an execution status confirmation message to the server itself.

When the server on which the corresponding program module is executed can be identified by the above-described method, and when the server is the own server, the program execution means 50
(41), the execution is stopped, and the result is transmitted to the client 20 (43).

If the server is not the server itself, the server 30 sends an execution stop command to the server on which the corresponding program module is being executed. If the server on which the corresponding program module is executed cannot be identified, the server 30 sends a failure notification to the client 20 (4
3), the input / output means 10 displays this.

Next, an operation when the server receives the execution stop instruction message will be described with reference to FIG.

When the network access means 40 receives the execution stop instruction message, it sends an execution stop instruction to the program module execution means 50 to stop the execution.

The server sends a request message (execution status confirmation,
Execution stop, execution stop instruction),
This will be described below with reference to the flowchart of FIG.

The server's network access means 40 receives the message (step 801).

If the received message is an execution confirmation message (see Y in step 802), the current execution status of the program module whose execution status is to be checked is searched from the status table holding unit 70 (step 803). ).

If the corresponding program module name exists in the status table holding unit 70 and the status is not “complete execution completed” (see Y in step 804), the execution status is returned to the message transmission source (step 804). 80
9), end the processing.

When the corresponding program module name does not exist in the status table holding means 70 (step 804)
From the status table holding means 70, the corresponding program module whose execution has been completely completed in the past is
Search for which server is running (Step 8
05).

If the corresponding program module exists (see Y in step 806), the execution status is checked with the server in the descending order of the number of executions from the search result of the program module (step 80).
7).

When the execution status is returned from the server that has performed the confirmation (see Y in step 808), the execution status is returned to the request source (step 809), and the process is terminated.

If the corresponding program module does not exist (see N in step 806), and if no execution status is returned from any of the confirmed servers (see N in step 808), the server list holding means 8
The execution status of each server held at 0 is checked (step 810).

When the execution status is returned from the server that has performed the confirmation (see Y in step 811), the execution status is returned to the requestor (step 809), and the process is terminated.

On the other hand, if the execution status is not returned from any of the confirmed servers (N in step 811), “execution status unknown” is returned (step 812).
The process ends.

When the execution status is returned to the message sender (step 809), if certainty is to be provided, it is necessary to check whether the server described in the execution status is actually executed. There is.

As a result of the check, if it is found that the execution has not been performed (if the execution has already been completed in the server), the processing of step 804 and below is performed.

Further, if the message is not an execution status confirmation message in the message determination processing in step 802, the process proceeds to step 820, and if the message is an execution stop message (see Y in step 820), the corresponding program is sent to its own server. The execution status of the module is checked (step 821).

The server executing the corresponding program module and its execution status are specified (step 82).
If the server is its own server (see Y in step 824), the program is stopped via the program module executing means 50, a stop success notification is returned (step 827), and the process ends. I do.

If the server executing the corresponding program module is not its own server (N in step 824), an execution stop instruction message is sent to the server executing the corresponding program module (step 825). , And the process ends.

If the server executing the corresponding program module cannot be specified (N in step 822), a failure notification is returned (step 823), and the process is terminated.

If it is determined in step 820 that the message is not an execution stop message, the process proceeds to step 826, and
If the message is an execution stop instruction message (see Y in step 826), the program is stopped via the program module executing means 50, a stop success notification is returned (step 827), and the process ends.

In the case of other messages (see N in step 826), the processing is terminated.

FIG. 9 shows an example of data added to the program module. Program module name 901
(“Calc22.exe” in FIG. 9), the name of the server on which the program module is to be executed and its order 902, and the executed server name 903 (“obp” in FIG. 9). Along with the server and is updated.

[0108]

As described above, according to the present invention,
It is possible to know at any time the status of mobile program modules moving on the network,
It is possible to control the suspension of execution of mobile program modules, etc., increasing the reliability of program modules on the user's network, reducing unnecessary program processes, enabling quick processing, and improving system performance This has the effect of causing

[Brief description of the drawings]

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

FIG. 2 is a diagram showing an example of the contents of a program status in one embodiment of the present invention.

FIG. 3 is a diagram showing an example of the contents of a status table holding unit in one embodiment of the present invention.

FIG. 4 is a diagram for explaining one embodiment of the present invention;
FIG. 9 is a diagram illustrating a processing flow of movement of a program module and coordination operation of a server.

FIG. 5 is a diagram for explaining one embodiment of the present invention;
FIG. 7 is a diagram illustrating an example of a change in data held by a status table holding unit.

FIG. 6 is a flowchart showing an operation from when a server receives a program module until execution is completed in an embodiment of the present invention.

FIG. 7 is a diagram illustrating an example of data held by a server list holding unit according to an embodiment of the present invention.

FIG. 8 is a flowchart showing an operation after a server receives a message in one embodiment of the present invention.

FIG. 9 is a diagram showing an example of data added to a program module in one embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Input / output means 11 Input information 20 Client 21 Client message 22 Output information 30 Server 31 Server group 32 Inter-server message 33 Result notification 34 Inter-server message 35 Server 36 Server 40 Network access means 41 Program module and its instruction 42 Status operation message 43 result notification 50 program execution means 51 program status 60 status table management means 61 status data 62 searched status data 70 status table holding means 71 status data 80 server list holding means 81 server list 201 program module name 202 client name 203 program module Execution status 301 execution status of calc22.exe 302 execution status of calc23.exe 401 program module 40 2 Program module 403 Notification of execution status 404 Program module 405 Notification of execution status 406 Result notification 501 Contents of status table 502 Contents of status table 503 Contents of status table 504 Contents of status table 505 Contents of status table 901 Program module name 902 Program module execution Server name and order 903 Executed server name

Claims (7)

[Claims] An input / output means for receiving an input from a user and outputting necessary information to the user, and selecting a program module to be executed based on the input from the input / output means and determining an execution order. A client that requests another information processing device connected to the network to execute the program module requested by the other information processing device connected to the network and returns an execution result. In the client server system, the server determines the content of the message received via the network, distributes the message to a predetermined unit of the own device, and transmits the data of the own device to an appropriate information processing connected to the network. Network access means for transmitting to the device; and another information processing device via the network. A program module execution unit for executing the transmitted program module; an execution status table holding unit for holding an execution status of the program; and an execution status table management unit for managing the execution status table holding unit. A client-server system characterized in that the execution status of the client can be checked. 2. In the server, the program module execution means may execute the program module execution at any time.
The client server system according to claim 1, wherein the client module is configured to be able to stop the program module being executed, and the program module can be stopped at any time from the client. 3. The method according to claim 1, wherein the execution status table management means of the server is traced so that program modules executed one after another on a plurality of servers can be tracked and the execution status of the program modules can be confirmed. The client server system according to claim 1, wherein: 4. When a program module is moved from one server to another server, the execution status of the program, such as program execution and execution completion, is reported to the server which first started execution of the program module. 2. The client server system according to claim 1, wherein 5. When the server receives the confirmation message of the execution status of the program module, the server stores the program module in the execution status table holding means of the server from the past execution status even if there is no corresponding program. 2. The client server system according to claim 1, wherein a server name that is likely to be executed is searched for, and an execution status of the program module is acquired. 6. When the server receives the program module execution status confirmation message and there is no program corresponding to the execution status table holding means, the server can execute the program module even from a past execution status. When the server name which can be identified cannot be specified,
Query all servers in the server list,
2. The client server system according to claim 1, wherein an execution status of the program module is obtained. 7. A client-server system in which a server controls execution of a program module uploaded from a client side, and the program module moves between a plurality of servers and is executed. Information on the execution status, execution location, and the client of the program module, and can be controlled by monitoring the execution status of the program module on the server and stopping the execution of the program module in response to a request from the client side. The client server system characterized by the above-mentioned.