JPH11102336A - Decentralized service system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To lighten the load on a server computer by moving only some objects of a client program to the server computer. SOLUTION: A communication object 146 of the client program 14 is connected to connection objects 240A to 240E of respective server programs. A connection analysis object 141 of the client program 14 selects a server computer (e.g. 2A) having many connections, a transfer object 142 transfers the communication object 146 to the server computer 2A, and a client-side repeating object 143 and a server-side repeating object (e.g. 242A) communicate with this object. Thus, only the program object (communication object) 146 which communicates with server programs 24A and 24B providing services of the server computers 2A and 2B is moved onto the computer where the services are performed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a distributed service system in which a plurality of computers provide a plurality of services, and more particularly, to a plurality of computers distributed and present on various networks such as the Internet and an intranet. The present invention relates to a technology effective when applied to a distributed service system that performs processing while connecting and using a plurality of services to be performed via a network.

[0002]

2. Description of the Related Art Conventionally, when a service provided by software running on a large computer is used, a terminal is connected to the large computer itself and the service program itself is used. The only data exchanged in was data entered by the user and data displayed as a result of calculation on the terminal.

[0003] Subsequently, with the development of networks, client-server programs have been used, and various data have been exchanged between fixed servers and clients via networks. In this case, the client program had to know in advance on which computer the service program was running, and the client program and the server program had a close link.

Subsequently, a distributed object technique was devised to dynamically find a computer that provides a service when executing a program. Object Managing Group
CORBA (Common Object Request Br)
In the oker Architecture), services are implemented by programs called several objects, and a mechanism for dynamically finding the computer on which the object exists is provided.

All of these techniques employ a mechanism for exchanging data between a client computer and a server computer providing a service via a network, and a program running on the client computer uses the service. In this method, data must be exchanged by connecting each service program running on the server computer via a network.

[0006] Further, in a process that does not require exchange with the client, such as displaying an intermediate result of the search to the client or receiving an instruction when searching the database, the client computer previously stores the search processing program in the target server. Transfer the connection to the computer, disconnect the connection, the program performs a search process on the server computer, and when the search process is completed, reconnects to the client computer and transfers the result to reduce the number of network connections and network traffic It has also been proposed to reduce emissions.

[0007]

In order to realize a system using a plurality of services on distributed computers using the conventional technology, if one server computer provides a plurality of services, The programs running on the client computers must connect to each service via the network to exchange data, and the cost of network connection increases in proportion to the number of services used. There is a problem that the processing time increases in proportion to the amount of data exchanged above.

[0008] In order to reduce the number of times of network connection and reduce network traffic, a program for transferring a process to a server computer can be performed without the intervention of a client as in a database search. At present, processing is supported, but processing that requires the intervention of a client is not supported. If programming is performed so as to be able to intervene with the client, the program has a large number of steps, and a load is imposed on the server computer. Especially,
In a distributed service system used by a plurality of clients, there is a problem that a considerable load is applied to a CPU, a memory, and the like of a server computer.

The present invention reduces the load on the server computer, reduces the number of network connections, and reduces network traffic when using a plurality of services running on one or more server computers. It is to provide a technology that can be realized.

[0010]

SUMMARY OF THE INVENTION Among the inventions disclosed in the present application, the outline of a representative one will be briefly described.
It is as follows.

In a distributed service system in which a plurality of server computers each having a server program for providing a service and a plurality of client computers each having a client program for receiving a service are distributed and connected via a network, the client computer A connection analysis program for analyzing whether to connect to the server computer, a communication program for connecting to the server program and communicating with a program in the server program, a transfer program for transferring the communication program to the server computer, a transferred communication program; Client consisting of a relay program that communicates with the client, an interface program that performs instruction processing with the client, and a main program that performs processing such as calculations A program, a connection log information of the communication program at the time of executing the client program, a terminal device including a CPU and a memory, a display device for displaying a result of the service, and an input for giving an instruction to start the program A server device comprising a CPU, a memory, a connection program for connecting and communicating with a client, a service program for performing service processing, and receiving the communication program from a client computer. And
A server program comprising a relay program for communicating with a relay program for a client program, a CPU,
A terminal device including a memory and a communication port are provided.

[0012] The connection analysis program may include means for analyzing which service the program of the client program connects to running on each server computer, and moving the program to the server computer having the largest number of connections. Prepare.

Further, the connection analysis program includes means for determining a server computer to make a maximum number of connections at the time of program execution by using connection log information of the communication program, and moving the program to the server computer.

By doing so, only a program object (communication object) that communicates with the server program that provides the service of the server computer is moved to the computer on which the service is running, so that a great load is imposed on the server computer. The number of times of network connection between the client and the server and the network traffic can be reduced without applying any additional processing, so that the response of the client program can be improved.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment according to the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a configuration of a distributed service system according to an embodiment of the present invention.

As shown in FIG. 1, the distributed service system according to the present embodiment includes a terminal device 10 including a CPU 11 and a memory 12, and an external storage device 13 in which a client program 14 and client connection log information 15 are stored.
A display device 16 for displaying the result of the service,
A client computer 1 comprising an input device 17 for giving an instruction to start a program and a communication port 18
Similarly, a terminal device 20A including a CPU 21A and a memory 22A, an external storage device 23A storing a server program 24A, a server computer 2A including a communication port 25A, and a terminal device 20B including a CPU 21B and a memory 22B. An external storage device 23B for storing the server program 24B, and a communication port 25B
And a network 4 for communicating data transmitted and received between the computers.

Next, a communication connection between the client computer 1 and the server computers 2A and 2B in the distributed service system of the present embodiment will be described.

FIG. 2 is a diagram showing an example of the configuration of the client program 14, the configuration of the server programs 24A and 24B, and the connection relationship between the client program 14 and the server programs 24A and 24B of the present embodiment.

As shown in FIG. 2, a client program 14 running on the client computer 1 transmits a connection analysis object 141 for analyzing which server computer 2 to connect to, and an object for connection with the server program 24 to the server computer 2. A transfer object 142 for transfer, a relay object 143 for communicating with the transferred object program, an interface object 144 for processing instructions with the user, a main object 145 for performing calculations and the like, and connection to the server program 24; And a communication object 146 that communicates with an object in the server program 24.

The server program 24A1 running on the server computer 2A receives a connection object 240A for performing communication by connecting to a client, a service object 241A for performing processing, a communication object 146 from the client, and a relay object 143 of the client program 14. Relay object 24 that communicates with
2A.

Similarly, the other server program 24A2
Connection object 2 that communicates by connecting to the client
40B, a service object 241B for processing, and a relay object 242B for receiving the communication object 146 from the client and communicating with the relay object 143 of the client program 14.

Still another server program 24A
3 also includes a connection object 240C for performing communication by connecting to the client, a service object 241C for performing processing, a relay object 242C for receiving the communication object 146 from the client, and communicating with the relay object 143 of the client program 14.

On the other server computer 2B, a connection object 240D for connecting and communicating with a client and a service object 241 for performing processing are also provided.
D, the communication object 146 is received from the client, and the relay object 1 of the client program 14 is received.
Server program 24B1 composed of a relay object 242D that communicates with the client 43, a connection object 240E that similarly connects to and communicates with the client, a service object 241E that performs processing, and a communication object 146 from the client.
Server program 24B2 including a relay object 242E communicating with the relay object 143 of No. 4
It is running.

The communication object 146 of the client program 14 connects to connection objects (240A to 240E) of each server program.

The connection analysis object 141 of the client program selects a server computer (for example, 2A) having a large number of connections, the transfer object 142 transfers the communication object 146 to the server computer 2A, and communicates with this object on the client side. And the relay object on the server side (for example, 242A).

FIG. 3 shows the connection analysis object 141 used in the client program 14 of this embodiment.
5 is a configuration example of client connection log information 15;

The client connection log information 15 includes a name 151 of a client program, a name 152 of a communication object to be connected, a name 153 of a server computer of a connection destination, a name 154 of a server program of a connection destination,
Name 1 of the connection object of the server program to be connected
55 are stored.

FIG. 4 shows an example of an object position table used by the client program 14 of this embodiment to search for a location where an object to be secured in a memory exists during execution.

As shown in FIG. 4, the object position table 40 stores a set of a communication object name 401 and a computer name 402 in which the communication object exists. When the client program starts, the computer names stored in the object position table 40 are all the client computers 1. When the transfer object 142 has moved the communication object 146, it is replaced with the name of the destination server computer.

Next, the above-described client program 1
4 will be described. FIG. 5 is a flowchart showing the operation of the client program 14 running on the client computer 1 of the present embodiment.

First, when the client program is started, the connection analysis object 141 analyzes the communication object 146 in the client program 14 and determines the transfer destination of the communication object 146 from the client connection log information 15 (step 501).

Then, it is checked whether or not the communication object 146 is to be moved (step 502). If the communication object 146 is not to be moved, the communication object 146 is executed to connect to the server program 24 (step 503). Add connection information (step 50
4) After that, the processing of the main object 145 is started (step 505). When the processing of the main object 145 ends, the connection with the server program 24 is disconnected (step 506), and the processing ends. Communication object 14
6, the transfer object 142 connects to the relay object 143 of the server program 24 (step 507), and transfers the communication object 146 to the transfer destination server computer 2 (step 508).
Update the object position table 40 (step 5
09). Thereafter, when the processing of the client program 14 starts and the communication object 146 is executed, the execution of the communication object 146 moved to the server computer 2 is performed by the relay object 242 of the server computer 2 via the relay object 143 of the client. Request (step 510). Thereafter, the processing of the main object 145 is executed, and when the processing is completed, the relay object 242 of the server program 24 is notified of the end of the connection (step 511), and the object position table 40 is set.
Is discarded from the memory (step 512), and the process ends.

FIG. 6 is a flowchart showing the operation of the connection analysis object 141 of the client program 14 running on the client computer 1 of this embodiment.

The connection analysis object 141 analyzes the communication object 146 in the client program 14 (step 601), and determines the connection destination server computer name 153, the connection destination server program name 154, and the connection destination server program object name 155. Take out. Next, the client connection log information 15 is read (step 602), and the object position table 40 is initialized from the above information (step 603). The number of connections to the server computer 24 is calculated from the analysis result and the client connection log information 15 (step 604),
It is checked whether the number of connections is one (step 60).
5). If the connection is made only once from the client computer 1, the process is terminated. Otherwise,
The transfer object 142 is requested to transfer the communication object 146 to the computer having the largest number of connections (step 606), and the process ends.

FIG. 7 is a flowchart showing the operation of the transfer object 142 running on the client computer 1 of the embodiment.

When requested to transfer the communication object 146 from the connection analysis object 141 (step 701), the transfer object 142 connects to the relay object 242 of the corresponding server program 24 (step 7).
02), the communication object 146 is transferred (step 703). Thereafter, the communication path ID (step 704) used for the connection is passed to the relay object 143, and the process ends.

FIG. 8 is a flowchart showing the operation of the relay object 143 operating on the client computer 1 of this embodiment.

When the relay object 143 is activated, it receives a communication path ID from the transfer object 142 (step 801). Thereafter, when the client program 14 requests execution of the communication object 146 (step 802), the execution of the communication object 146 transferred to the relay object 242 of the server program 24 via the communication path corresponding to the communication path ID. A request is made (step 803). Then, it waits for a communication request from the main object 145 of the client program 14 or a communication from the relay object 242 of the server program 24 (step 804), and checks whether it is a communication request from the main object 145 of the client program 14 (step 804). 805) If it is from the main object 145, the request content is transferred to the relay object 242 of the server computer 2 as it is (step 806). If the communication is from the relay object 242 of the server program 24, the received data is returned to the main object 145 of the client program 14 as a result (step 807), and the processing is repeated from step 804.

FIG. 9 is a flowchart showing the operation of the main object 145 running on the client computer 1 of this embodiment.

When executing the processing of the communication object 146, the main object 145 requests a connection to the relay object 143 (step 901), and obtains an ID indicating a communication path (step 902). Thereafter, it is determined whether the process is performed using the ID of the communication path (step 90).
3) In the case of the process using the channel ID, a process request is made to the relay object 143 (step 904), and otherwise, the normal process is performed in the client computer 1 (step 905), and the process is repeated from step 903.

FIG. 10 is a flowchart showing the operation of the server program 24 running on the server computer 2 of this embodiment.

When the server program 24 is activated, it performs initial settings (step 1001), executes the connection object 240, and waits for a connection from the client program 14 (step 1002). When the connection object 240 is connected from the client, an instruction is received from the client program 14 (step 1003),
Check whether it is a disconnection command (step 10)
04). If it is not a disconnection command, the service object 24
1 is performed (step 1005), and the result is returned to the client program via the relay object 242 (step 1006). Thereafter, the process is repeated from step 1003. If a command to disconnect the connection is received, the communication path is disconnected (step 1007), and the process is repeated from step 1002.

FIG. 11 is a flowchart showing the operation of the connection object 240 running on the server computer 2 of this embodiment. The connection object 240 waits for a connection from the communication object 146 of the client program 14 (step 1101), checks whether or not the connection is from the client computer 1 via the network (step 1102). Create ID to create communication object 14
6 (step 1103), and then receives a command via a communication channel (step 1104), checks whether it is a communication end command (step 1105), and if not, requests the service object 241 to perform processing. Then, the result is returned to the communication object 146 of the client program 14 via the communication path (step 1107), and the processing is repeated from step 1104. If it is a termination command, the communication path is disconnected (step 11).
08), and repeat from step 1101. If the connection is from the transferred communication object 146, a memory area for command transfer is secured (step 1109).
A command is received from the communication object 146 via this memory area (step 1110), and it is checked whether the command is a communication end command (step 1111). If the command is not an end command, a process is requested to the service object 241 (step 1112). Is written into the data transfer memory area (step 1113), and step 1110 is executed.
Repeat from If it is the end command, the memory area is released (step 1114), and the processing is repeated from step 1101.

FIG. 12 is a flowchart showing the operation of the relay object 242 operating on the server computer 2 of this embodiment.

The relay object 242 waits for a connection from the transfer object 142 of the client program 14 (step 1201), and when it is connected, receives the communication object 146 (step 1202).
D is returned (step 1203). Thereafter, the process waits for communication from the relay object 143 of the client program 14 (step 1204), checks whether the command is a connection execution command (step 1205), and executes the received communication object 146 if the command is a connection execution command (step 1206). , Is repeated from step 1204. If it is not a connection execution command, it is checked whether it is a connection termination command (step 1207), and if not, a request is made to the service object 241 for processing (step 1).
208), and returns the processing result to the relay object 143 of the client (Step 1209), and returns to Step 120
Repeat from 4. When the connection end command is received, the transferred communication object 146 terminates the connection (step 1210), releases the communication object 146 from the memory (step 1211), and further communicates with the relay object 143 of the client program 14. (Step 1212), and repeat from step 1201.

Therefore, as described above, when the client program connects to the server program and proceeds with the processing, the communication object which is a communication part of the client program is moved to the server computer, and the client program and the server program are transferred. By allowing communication processing to be performed only in the server computer, connection costs for communication processing and network traffic for data communication can be reduced.
The response of the client program can be improved.

Further, by moving only a part of the object of the client program to the server computer, the load on the server computer can be reduced as compared with the conventional method in which the client program itself is moved.

Note that the server program 24 and the client program 14 described above may be provided to general users on a storage medium such as a floppy disk, CD / ROM, or ROM. In this case, in addition to these processes, the program can be provided to the user in combination with another program such as a GUI program.

As an alternative means provided by the above-mentioned storage medium, it may be provided for a fee through a network such as the Internet.

As described above, the present invention has been specifically described based on the above embodiments. However, the present invention is not limited to the above embodiments, and it is needless to say that various changes can be made without departing from the gist of the present invention. It is.

[0052]

The effects obtained by the representative ones of the inventions disclosed in the present application will be briefly described as follows.

When using a plurality of services running on one or more server computers, some objects of the client program are moved to the server computer, and the communication processing between the client program and the server program is performed by the server. By performing the processing only in the computer, it is possible to reduce the load on the server computer, to reduce the number of network connections, and to reduce network traffic.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a distributed service system according to an embodiment of the present invention.

FIG. 2 is a diagram for explaining the configuration and connection relationship between a client program and a server program according to the embodiment;

FIG. 3 is a diagram illustrating an example of client connection log information.

FIG. 4 is a diagram showing an example of an object position table.

FIG. 5 is a flowchart showing the operation of a client program.

FIG. 6 is a flowchart showing an operation of a connection analysis object of the client program.

FIG. 7 is a flowchart showing an operation of a transfer object of the client program.

FIG. 8 is a flowchart showing the operation of the relay object of the client program.

FIG. 9 is a flowchart showing the operation of the main object of the client program.

FIG. 10 is a flowchart showing the operation of a server program.

FIG. 11 is a flowchart showing an operation of a connection object of the server program.

FIG. 12 is a flowchart showing an operation of a relay object of the server program.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Client computer, 2A, 2B ... Server computer, 10 ... Terminal device, 11, 21A, 21B ...
CPU, 12, 22A, 22B ... memory, 13, 23
A, 23B: external storage device, 14: client program, 15: client connection log information, 16: display device, 17: input device, 18, 25A, 25B: communication port, 24A, 24B: server program, 141: connection analysis Object, 142 ... transfer object, 143
... Relay object, 144 ... Interface object, 145 ... Main object, 146 ... Communication object, 240A-E ... Connection object, 241
A to E: service objects, 242A to E: relay objects.

Claims (3)

[Claims] 1. A distributed service system in which a server computer having a server program for providing a service and a client computer having a client program for receiving a service are respectively distributed and connected via a network, wherein the client computer comprises: A connection analysis program for analyzing which server computer to connect to, a communication program for connecting to the server program and communicating with a program in the server program, a transfer program for transferring the communication program to the server computer, and a transferred communication A client consisting of a relay program that communicates with the program, an interface program that performs instruction processing with the client, and a main program that performs processing such as calculations Connection program, connection log information of the communication program at the time of execution of the client program, a terminal device including a CPU and a memory, a display device for displaying a result of the service, and an instruction for starting the program. An input device and a communication port, the server computer includes a terminal device including a CPU and a memory, a connection program for connecting and communicating with a client, and a service program for performing service processing.
A server program comprising a relay program for receiving the communication program from a client computer and communicating with a relay program for the client program;
A distributed service system comprising: a terminal device including a PU and a memory; and a communication port. 2. The distributed service system according to claim 1, wherein the connection analysis program analyzes which service the program of the client program runs on each server computer, and determines the number of connections. A distributed service system comprising means for moving a program to the most server computer. 3. The distributed service system according to claim 2, wherein the connection analysis program uses the connection log information of the communication program to determine a server computer that makes a maximum number of connections when executing the program. A distributed service system comprising means for moving a program to a server computer.