JPH0573517A - Client and server coupling device - Google Patents

Abstract

(57) [Abstract] [Purpose] The present invention relates to a client / server connecting device for connecting a client unit requesting a service and a server unit providing a service in a client / server model distributed processing. Providing this will facilitate distributed system development. [Configuration] A name server unit 15 that manages server unit information based on a service class identifier generated when a system generates a service interface, a system automatic connection processing unit 13a that selects and connects a server unit based on a service class identifier, and a user Client connection unit 13 including designated connection processing unit 13b and user selection connection processing unit 13c
With this configuration, the user can select the optimum connection process for the system, and by selecting the automatic connection, the client / server connection process can be easily realized.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server connecting device for connecting a client unit requesting a service and a server unit providing a service in a client / server model distributed processing system of computers connected by a network. Is.

[0002]

2. Description of the Related Art In recent years, a client / server connection device has been called a remote procedure call.
It is widely used when developing a distributed processing system using the. As an example of such a client / server connection device, a general device is "Building distributed systems with remote system" by Steve Wilber et al.
procedure call "by Steve Wilbur and Ben Bacarisse
in IEEE Software Engineering Journal, September 1
987, pages 148-159.) And a representative example is grapevine ("Implementing remote proc").
edures calls, "by Andrew D. Birrel and Bruce Nels
on in ACM Trans. on Computer Systems, Vol. 2, No.
Grapevin mentioned in 1, Feb. 1984, pp. 35-39.
The one using e) is known.

A conventional client / server connecting device will be described below. FIG. 7 is a block diagram of a conventional client / server connecting device. In FIG.
Reference numeral 71 is a client unit that requests a service, 72 is a server unit that provides a service to the client unit 71, 73 is a client connection unit that provides a connection function to the client unit 71, and 74 is a connection function to the server unit 72. A server connection unit to be provided, 75 is a name server unit that manages service information of the server unit 72 and network position information, and 76 is a server unit information storage unit that stores service information of the server unit 72 and network position information. is there.

The operation of the client / server connecting device configured as described above will be described below. First, when the server unit 72 is activated and can provide a service, the server unit 72 requests the server connection unit 74 to register the user-defined service information defined by the user for the server unit.

Upon receiving the request, the server connection unit 74 adds system runtime information such as position information on the network and registers it in the server unit information storage unit 76 managed by the name server unit 75. The name server unit manages this server unit information based on the name defined by the user.

This registration process is performed when all the server units 72 that provide various services on the network are activated and the services can be provided. At this time,
The name server unit 75 owns the information about all the server units that can provide the service at this point.
When you want to receive the service requested by the client unit 71,
The client unit 71 requests the client connection unit 73 to connect to the server unit that provides the corresponding service based on the name defined by the user.

In response to this request, the client connection unit 73
Requests the name server unit 75 to retrieve and retrieve the information of the server unit that provides the corresponding service from the server unit information storage unit 76 based on the user-defined name.
Upon receiving this result, the client connection unit 73 returns all the searched server unit information to the client unit 71. The client unit 71 selects an optimum server unit from the contents of the server unit information group and requests the client connection unit 73 to connect to the selected server unit 72.
The client connection unit 73 connects the client unit 71 and the server unit 72 via the server connection unit of the server unit 72 based on the server unit information of the selected server unit 72.

[0008]

However, in the above-mentioned conventional configuration, since the service information is managed based on the name defined by the user, maintenance of the name used by the user in the entire system on the network is performed. It must be made. Therefore, even when a plurality of server units that provide the same service are operated, the classification and grouping are designed based on the name defined by the user, and the connection process based on the design is performed. Must be incorporated into.

As a result, the name change has a great influence on the system, and it takes a lot of time to maintain the system. In addition, even when there are a plurality of server units that provide the same service and any server unit may be used, the user must describe the selection process in the client unit.

As described above, in the conventional example, the client
In the distributed processing system development of the server model, the user has to develop the concatenation process based on the name including the design of the name, and it takes a lot of time to develop and change the concatenation process. I had.

The present invention solves the above-mentioned problems of the prior art. While providing the flexibility of the conventional client / server connection system, the connection processing of the client unit can be easily incorporated, and the client / server model It is an object of the present invention to provide a client / server connection device that can easily develop a distributed processing system.

[0012]

In order to achieve this object, the present invention provides a server section for providing a service, a client section for requesting the service of the server section, user-defined service information of the server section and system execution time. A server section information storage section that stores server section information consisting of information in service class identifier units generated by the system when a service interface is generated, and server section information stored in the server section information storage section is managed based on the service class identifier. A name server unit, and a service class identifier and a server unit information which are internally generated and internally owned by the system when a service interface is generated via the name server unit, are registered and deleted in the server unit information storage unit at the request of the server unit, and a client Server connection provided for each server unit that performs connection processing with departments And server part information stored in the server part information storage part via the name server part with the service class identifier generated internally by the system at the time of generating the service interface as a key in response to the service request from the client part. And selecting one server unit from the server unit group that can provide the requested service, and a system automatic connection processing unit provided for each client unit that connects with the selected server unit, In response to the service request from the client unit, the server unit information storage unit via the name server unit with the user-defined service information specified at the time of request and the service class identifier internally generated and internally owned by the system when the service interface is generated. The requested service can be provided by searching the server part information stored in In response to a user-specified connection processing unit provided for each client unit that connects with the selected server unit and a server unit information request from the client unit, It is possible to search the server section information stored in the server section information storage section through the name server section using the service class identifier internally generated and owned by the system when the service interface is generated, and provide the requested service. A user selection connection processing unit provided for each client unit that returns information of a server unit group to the client unit as a result, and the client unit connects with one server unit selected from the server unit group. It is configured with and.

[0013]

According to the present invention, the server system information is managed based on the service class identifier generated by the system when the service interface is generated, so that the user can manage the name unless the user uses the name in the user-defined service information. You don't have to. Further, in the connection processing, the system automatic connection processing unit, the user-specified connection processing unit, and the user-selected connection processing unit are provided, and by making it possible to select which connection processing function to use, the service provided by the user-developed system is provided. Depending on the attribute of, the optimum concatenation process can be selected and incorporated. Especially, when the system automatic concatenation process or the user-specified concatenation process is selected, the client unit can execute the client / server connection without considering the concatenation process. Link processing can be easily realized, and a client / server model distributed processing system can be easily developed.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram of a remote procedure call (RPC) system using a client / server connection device according to an embodiment of the present invention. In FIG. 1, 11 is a client unit that requests a remote procedure call service, 12 is a server unit that provides a remote procedure call service to the client unit 11, 13 is a client connection unit that provides a connection function to the client unit 11, 13a Is a system automatic connection processing unit for performing connection processing in the system automatic connection mode, 13b is a user specified connection processing unit for performing connection processing in a user specified connection mode, 13c
Is a user selection connection processing unit that performs connection processing in the user selection connection mode, 14 is a server connection unit that provides a connection function to the server unit 12 and a function that registers and deletes server unit information, and 15 provides services on the network. A name server unit that manages server unit information of all server units 12 based on service class identifiers, 16 is a server unit information storage unit that stores server unit information in service class identifier units, and 17 is a service interface of the server units. Is a service interface definition defining 18 and 18 is a class generation unit for generating a service class identifier from the service interface definition 17.

The operation of the client / server connecting device configured as described above will be described.

The service class identifier is uniquely attached to the service interface definition.
At the time of generating the client connection unit 13 and the server connection unit 14, the class generation unit 18 reads and generates the service interface definition and incorporates it into each connection unit.

The service registration process of the server unit 12 is performed as shown in the flow chart of FIG. When the server unit 12 can provide the service to the client unit, the server unit 12 sets the user-defined service information including the name of the object managed by the server unit 12 and its attribute (step 21), A service start request is issued to the server connection unit 14 (step 22).

The server connection unit 14 adds system runtime information including system information such as the network address, logical address, and protocol of this server to the user-defined service information (step 23), and sends it to the name server unit 15. Then, a request is made to register the server section information and the service class identifier in the server section information storage section 16 (step 24). The name server unit 15 registers it in the server unit information storage unit based on the service class identifier (step 25), and returns the result to the server connection unit 13.

At this time, if the same service class identifier is already registered in the server section information storage section, this server section information is registered next to the last entry of the already registered server section information of the same service class. To do. If the service class identifier is not registered yet, the service class identifier and the server section information are registered in the server section information storage section. The server connection unit 14 inspects the result of the registration process (step 26), and the server unit information storage unit 16
When the server section information is correctly stored in, the server connecting section 13 waits for a connection request from the client section 11 (step 27). If it is not stored correctly, the reason is notified to the server unit (step 28).

FIG. 3 shows the server part information 31 of one server part 12 and the configuration 32 of the server part information storage part. As described above, the user-defined service information of the server part information 31 is generally composed of the name of the object managed by the server part and its attributes, and the server part runtime information is the network address and the logical address of the server part. , System information such as protocol.

The configuration 31 of the server section information storage section stores the server section information collectively for each service class using the service class identifier as a key. Further, when the service provision of the server unit is ended, the server unit 12 issues a service deletion request to the server connection unit 13. The server connection unit 13 requests the name server unit 15 to delete this server unit information from the server unit information storage unit 16 based on the service class identifier and the server unit runtime information. Upon receiving the processing result from the name server unit 15, the server connection unit 13 notifies the server unit of the result.

Next, the connection processing of the client unit will be described. The client connection unit 13 includes a system automatic connection processing unit 13a, a user-specified connection processing unit 13b, and a user selection connection processing unit 13c, and operates in each mode. The client connection unit 13 is set to a default connection processing mode, which may be any of a system automatic connection processing mode, a user-specified connection processing mode, and a user selection processing mode.

The client unit 11 sets an appropriate mode from the above three types to the client connection unit according to the function required by the system. The operation of each processing unit in each mode will be described below.

First, FIG. 4 shows the operation of the system automatic connection processing unit.
This will be described with reference to the processing flow chart of FIG. The client unit 11 issues a remote procedure call service request to the client connection unit 13 (step 4).
1). The system automatic connection processing unit 13a of the client connection unit 13 that has received this request requests one server unit information satisfying the service request from the name server unit 15 based on the service class identifier (step 42). The name server unit 15 is the server unit information storage unit 1.
The server section information of the server section satisfying the service requested from 6 is searched based on the received service class identifier (step 43), and the result is searched by the client connection section 1
3 to the system automatic connection processing unit 13a (step 44).

The system automatic connection processing unit 13a checks this result (step 45), and if there is a corresponding server unit, the system automatic connection processing unit 13a detects the corresponding server unit 12 based on the system runtime information of the received server unit information. A connection request is issued to the server connection unit 14 and client / server connection processing is performed (step 46). If there is no corresponding server unit, this is notified to the client unit 11 (step 49). The result of the connection processing is judged (step 47), and if the connection is successful, the remote procedure call service is performed (step 48). In the case of connection failure, in order to request the server part information of the next server part that satisfies the service request from the name server part 15, step 4
The process from 2 is repeated.

In the present embodiment, the name server unit 15
In contrast, one server service information is requested at one time, but in consideration of efficiency, a plurality of server service information is requested at one time, this information is maintained in the client connection unit 13, and the connection fails. In this case, the server service information of the next server unit in the maintained server service information group may be used for connection. Further, in the case of connection failure, the maximum number of times of alternative reconnection request may be designated, and if the number of times exceeds this number, an error may be notified to the client unit.

Next, the processing of the user-specified connection processing section is shown in FIG.
This will be described with reference to the processing flow chart of FIG. The client unit 11 requests the client connection unit 13 to specify the condition of the requested user-defined service information and connect to the server unit that can provide this service (step 51). Upon receiving this request, the user-specified connection processing unit 13b of the client connection unit 13 uses the service class identifier and the user-defined service information to set one server unit information that satisfies the service condition specified for the name server unit 15. Is requested (step 52). The name server unit 15 searches the server unit information of the server unit satisfying the service condition designated from the server unit information storage unit 16 based on the service class identifier and the user-defined information (step 53), and links the result to the client. The data is transferred to the user-specified connection processing unit 13b of the unit 13 (step 54). The user-specified connection processing unit 13b checks the result (step 55), and if the corresponding server unit exists, the server connection unit of the corresponding server unit 12 based on the system runtime information of the received server unit information. A connection request is issued to 14, and client / server connection processing is performed (step 56). If there is no corresponding server unit, the result is notified to the client unit 11 (step 58). The result of the connection process is notified to the client unit 11 (step 57), and if the connection is successful, the client unit 11 can execute the remote procedure call service.

Finally, the processing of the user selection connection processing section will be described with reference to the processing flow chart of FIG. The client unit 11 requests the server unit information of all the server units that provide the requested service to the client connection unit 13 (step 61). Upon receiving this request, the user selection connection processing unit 13c of the client connection unit 13 requests all server unit information of the corresponding service from the name server unit 15 based on the service class identifier (step 62). The name server unit 15 searches the server unit information storage unit 16 for the server unit information of all the server units that provide the corresponding service based on the service class identifier (step 63), and retrieves all the searched information. (Step 64). Upon receiving this information, the user selection connection processing unit 13c delivers all the information to the client unit 11 (step 65). The client section 11 refers to the received all server section information and selects the optimum server section 12 from all the server sections that provide the requested service (step 66). The client unit 11 specifies the server unit information of the selected server unit and issues a connection request to the user selection connection processing unit 13c of the client connection unit 13 (step 67). User selection connection processing unit 13c
Issues a connection request to the server connection unit 14 of the requested server unit 12 based on the contents of the system runtime information of the server unit information, and performs the client / server connection process (step 68). The result of the connection process is notified to the client unit 11 (step 69), and if the connection is successful, the client unit 11 can execute the remote procedure call service.

These three types of connection processing modes described here can be dynamically changed from the client unit 11 while the system is operating, and thereby the flexibility of the system can be enhanced.

As described above, according to the present embodiment, the server system information is managed by the system based on the service class identifier generated when the service interface is generated, and unless the user uses the name in the user-defined service information. , No need to manage names. Further, in the linking process, the system automatic linking processing unit, the user-specified linking processing unit, and the user-selected linking processing unit are provided, and by making it possible to select which linking processing function to use,
Depending on the attribute of the service provided by the system developed by the user, the optimum connection processing can be selected and incorporated. Especially, when the system automatic connection processing or user-specified connection processing is selected, the client unit considers the connection processing. You can easily realize client / server connection processing without
A system using remote procedure call can be easily developed.

[0031]

As described above, according to the present invention, the server system information is managed based on the service class identifier generated by the system when the service interface is generated, so that the user does not use the name in the user-defined service information. No need to manage names. Further, in the connection processing, the system automatic connection processing unit, the user-specified connection processing unit, and the user-selected connection processing unit are provided, and by making it possible to select which connection processing function to use, the service provided by the user-developed system is provided. Depending on the attribute of, you can select and incorporate the optimal concatenation process, especially if you select system automatic concatenation process or user specified concatenation process,
The client unit can easily realize the client / server connection processing without considering the connection processing, and can realize the excellent client / server connection apparatus that can easily develop the distributed processing system of the client / server model. It is a thing.

[Brief description of drawings]

FIG. 1 shows a client according to a first embodiment of the present invention.
Overall configuration diagram of server connection device

FIG. 2 shows a client according to the first embodiment of the present invention.
Registration process flow chart of the server section of the server connection device

FIG. 3 shows a client according to the first embodiment of the present invention.
Server part information diagram of server connection device

FIG. 4 shows a client according to the first embodiment of the present invention.
System automatic connection mode process flow chart of the client unit of the server connection device

FIG. 5 shows a client according to the first embodiment of the present invention.
User specified connection mode process flow diagram of the client unit of the server connection device

FIG. 6 is a diagram illustrating a client according to the first embodiment of the present invention.
User selection connection mode process flow diagram of the client unit of the server connection device

FIG. 7 is an overall configuration diagram of a conventional client / server connection device.

[Explanation of symbols]

11 client unit 12 server unit 13 client connection unit 13a system automatic connection processing unit 13b user specified connection processing unit 13c user selection connection processing unit 14 server connection unit 15 name server unit 16 server unit information storage unit 21 server unit user-defined service information setting Processing 22 Server section service start request issue processing 23 Server connection section service class identifier and system runtime information addition processing 24 Server connection section registration request processing 25 Name server section registration processing 26 Server connection section registration processing result inspection processing 27 Server connection section connection Wait process 28 Server connection part error notification process 31 Server part information structure 32 Server part information storage part 41 Client part remote procedure call service request process 42 Client connection part server part information request process 43 Name server part Server section information storage section search processing 44 Name server section search result transfer processing 45 Client connection section search result inspection processing 46 Client connection section connection request processing 47 Client connection section connection processing result inspection processing 48 Client connection section remote procedure call service processing 49 Client Connection error notification processing 51 Client connection request processing 52 Client connection server information request processing 53 Name server server information storage search processing 54 Name server search result transfer processing 55 Client connection search result inspection processing 56 Client connection Part connection request process 57 Client connection part connection process result notification process 58 Client connection part error notification process 61 Client part server part information request process 62 Client connection part server part information request process 6 Name server part server part information storage part search process 64 name server part search result transfer process 65 client connection part search result notification process 66 client part server part selection process 67 client part connection request process 68 client connection part connection request process 69 client connection part Connection processing result notification processing 71 Client unit 72 Server unit 73 Client connection unit 74 Server connection unit 75 Name server unit 76 Server unit Information storage unit

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Nobuaki Tanaka 1006 Kadoma, Kadoma, Osaka Prefecture Matsushita Electric Industrial Co., Ltd. (72) Yoshihiko Suzuki, 1006 Kadoma, Kadoma City, Osaka Matsushita Electric Industrial Co., Ltd.

Claims (1)

[Claims] 1. A system that generates a server section that provides a service, a client section that requests the service of the server section, and server section information that includes user-defined service information of the server section and system runtime information when the service interface is generated. A server unit information storage unit that stores the service unit identifiers, a name server unit that manages the server unit information stored in the server unit information storage unit based on the service class identifier, and a service interface via the name server unit. It is provided for each server unit that registers and deletes the service class identifier and the server unit information that the system generates and internally owns at the time of generation in the server unit information storage unit at the request of the server unit and the connection process with the client unit. Service request from the server connection unit and client unit It is possible to search the server section information stored in the server section information storage section through the name server section using the service class identifier internally generated and owned by the system when the interface is generated, and provide the requested service. A single server unit from a group of server units, and a system automatic connection processing unit provided for each client unit that connects with the selected server unit,
In response to the service request from the client unit, the server unit information storage unit via the name server unit with the user-defined service information specified at the time of request and the service class identifier internally generated and internally owned by the system when the service interface is generated. It is provided for each client unit that searches the server unit information stored in, selects one server unit from the server unit group that can provide the requested service, and connects with the selected server unit. In response to the user-specified concatenation processing unit and the server unit information request from the client unit, the server unit information storage unit via the name server unit using the service class identifier generated internally by the system when the service interface is generated and internally owned as a key. It is possible to search the server part information stored in and to provide the requested service. A user selection connection processing unit provided for each client unit that returns information of the server unit group to the client unit as a result, and the client unit connects to one server unit selected from the server unit group. A client / server coupling device comprising: