JPH09160847A - Client server-type distribution processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method capable of adding a new usable function from a client without adding change to a server itself in a client/server-type data processing system. SOLUTION: The system 100 is provided with an interface converting mechanism 103 receiving a function calling request from a client. A conversion rule table 105 holding a conversion rule for converting the received function into sits of a server function calling request is provided and also conversion mechanism converting the received function calling into sets of the server function calling in accordance with the conversion rule of the conversion rule table 105 is provided.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server type distributed processing system (hereinafter abbreviated as "client / server type system"), and more specifically, to a client without changing the server program itself. The present invention relates to a client / server system that enables the addition of new functions that can be used from.

[0002]

2. Description of the Related Art As a data processing model in a distributed processing system in which distributed data processing devices are connected by a network, there is a client / server type system. The server provides the data processing function. The client calls the data processing function of the server according to the function calling procedure and requests the processing. As an example of the basic technology for constructing a client / server system, "Th
e Common Object Request Broker Architecture a
nd Specification, OBJECT MANAGEN
T GROUP and X / Open, 1993 "discloses a communication method between program modules on a distributed system and CORBA which is a standard specification of the system. In the above-mentioned CORBA, the interface of the function group provided by the server program is described in an interface definition language defined by the system, and based on this, a stub code and a skeleton code for hiding the details of the communication procedure via the distributed computer network. Is automatically generated. The stub code is a program code that hides the communication procedure in the client program. By incorporating the stub code, the client program can call the function without being aware of the process boundary and the computer boundary. Further, the skeleton code hides the communication procedure in the server program, and by incorporating this in the server program, the server program only needs to code the provided function itself.

[0003]

[Problems to be Solved by the Invention]
In the server type system, it is necessary to change the functions that can be used by the client at the operation stage of the system. For example,
Allow the client to request a new function call that combines multiple independent function calls,
An example is a case where an efficient function call or a simple function call is realized. In the conventional method of implementing a server in a client-server type system, for example, in the implementation using the skeleton code in the above CORBA, the type of function call and its interface are determined in advance and the server is implemented. However, with this method, it is not possible to predict in advance all the interfaces that the client will need in the future, and changing the functions provided by the server requires changing and recompiling the program. However, when a new client is added, it is not possible to easily change the server interface for the purpose of improving efficiency or simplifying function call. The present invention has been made in view of the above circumstances, and an object of the present invention is to solve the above problems in the related art and to enable a new program that can be used by a client without changing the server program itself. It is to provide a client-server system that enables addition of various functions.

[0004]

SUMMARY OF THE INVENTION An object of the present invention is to convert a received function into a set of server function call requests in a client / server type data processing system having an interface conversion mechanism for receiving a function call request from a client. A conversion rule table that holds conversion rules for performing the conversion is provided, and a conversion mechanism that converts the received function call into a set of server function calls according to the conversion rule of the conversion rule table is provided in the interface conversion mechanism. It is achieved by a client-server type system characterized by the following. Also,
A means for receiving an online conversion rule table change request using a remote function call provided by a client / server type system, interpreting the contents of the request, and a means for grasping the usage status of the conversion rules in the conversion rule table A conversion rule change permission / non-permission setting means, a conversion rule table change request, and a change rule table change permission / non-permission setting means. This is achieved by a client-server type system characterized by using a conversion rule management mechanism. Furthermore, in a client / server system that includes a server that manages interface information of functions provided by a server that configures the client / server system, a function that can accept the interface conversion mechanism by changing the conversion rule table This is achieved by a client-server type system characterized in that means for notifying the server of the change of the change is provided. Further, a client / server type characterized in that a conversion condition is provided in the conversion rule, and an interface conversion mechanism generating means for generating an interface conversion mechanism holding the conversion rule table therein is provided from the conversion rule table. Achieved by the system.

[0005]

BEST MODE FOR CARRYING OUT THE INVENTION In a client / server system according to the present invention, an interface conversion mechanism
It receives the function request message issued by the client program, interprets the function request message, and obtains the function name, argument string, and return value type. The conversion rule for the function name obtained as a result of the interpretation is searched from the conversion rule table, converted into a set of function calls of the server according to the corresponding conversion rule, and the functions provided by the server are sequentially called. After the completion of all calls, the return value or the result of the abnormal termination call is notified to the client program if necessary. In this system, by rewriting the conversion rule, it is possible to add a new function that can be used by the client without rewriting the server program. In addition, if a conversion rule management mechanism is added, the usage status of the conversion rules is grasped, and whether the conversion rules are changed or not is judged for each usage status. If the rule change is accepted,
It is possible to change the conversion rule table online by adding the conversion rule after the change while keeping the conversion rule in the used state.

Further, in the case of a client / server type system having a server for managing interface information,
The conversion rule management mechanism receives the conversion rule change request, executes the processing, and then notifies the server, which manages the interface information, of the change contents of the function provided by the interface conversion mechanism due to the change of the conversion rule table.
This facilitates the management of the interface information in the client / server type system and the management of the conversion rule table. Furthermore, when a rule selection condition is provided in the conversion rule, the conversion function used when the interface conversion mechanism converts the received request function into a set of server function call requests according to the conversion rule of the conversion rule table. When selecting a rule, by checking the conditions provided in the conversion rule and selecting one that satisfies the conditions from among the plurality of conversion rules, for example, under some specific plural conditions, different specific functions , You can switch the conversion rule to be used simply by changing the variable value related to the condition of the conversion operation without updating the conversion rule each time, and you can easily and efficiently change the provided function. Is possible. Further, in the case where the means for generating the interface conversion mechanism is used, for example, when there is no request for changing the conversion rule for the interface conversion mechanism, the interface conversion mechanism generation means causes the interface including the conversion rule table at that point in time. By generating the conversion mechanism, it is possible to improve the efficiency of the conversion operation on the assumption that the conversion rule table is not changed and to facilitate the management. Hereinafter, embodiments of the present invention will be described in more detail with reference to the drawings.

[0007]

1 is a diagram showing the configuration of a client / server system according to a first embodiment of the present invention. The client / server system 100 shown in this embodiment
Is connected to a plurality of computers 102a, 102b, ... In an information transmission network 108 such as a LAN (Local Area Network).
... are connected and the interface conversion mechanism 103, the server program 104, and the client program 109 are operated on those computers.
The interface conversion mechanism 103 has an interface called a pseudo server interface 106. The client program 109 is the pseudo server interface 10
6 can request a function call.

The interface conversion mechanism 103 receives a request from the client program 109 via the pseudo server interface 106, reads a conversion rule stored in a conversion rule table 105, which will be described later, and accordingly makes the above-mentioned request in the client / server type. System 1
00, the function is converted into a set of function calls of the server program 104 that can be used, and the function is executed. The conversion rule table 105 is usually stored in a file format in the permanent storage device 101a such as a magnetic disk device. By the system administrator or the like rewriting the contents of the file of the conversion rule table 105, the interface conversion mechanism 103 can change the type and operation of the function call provided to the client program 109 via the pseudo server interface 106.

FIG. 2 is a diagram showing a detailed structure of the interface conversion mechanism 103 and the conversion rule table 105, and FIG. 3 is a pseudo interface 1 by the client program 109 in the interface conversion mechanism 103.
It is a figure explaining the procedure of the conversion according to the conversion rule of the conversion rule table 105 of 06 call. The conversion procedure will be described below with reference to FIGS. The interface conversion mechanism 103 monitors arrival of a function call message from the client program 109 to the pseudo server interface 106, and starts conversion operation upon arrival of the message. The interface conversion mechanism 103 may be activated by the arrival of a message from the client program 109.

FIG. 4 illustrates the pseudo server function call message 400. The message 400 is the destination 40
1, function name 402, argument list 403, return value type 404
Contains information about. An address that uniquely specifies the interface conversion mechanism is entered in the destination 401. For example, when the client program requests the interface conversion mechanism to call the function "setXY" with two "long" type arguments, the "address of the interface conversion mechanism" is set as the destination. "SetXY" as the function name and two "long" as the argument list
, And a message of a byte string that can be communicated including information indicating that there is no return value as a return value type, and sends it.

When the interface conversion mechanism 103 on the computer 102a receives the message 400, first,
The pseudo server interface function call message interpretation unit 201 interprets the function call message sent from the client program 109 (step 3).
01). That is, the function name 402, the argument list 403, and the return value type 404 are acquired from the message 400 that is a communicable byte string. Next, from the conversion rule table 105, the same function name 207 as the request function name 402 is obtained.
The conversion rule 204 is searched for (step 302). here,
Not only function name, but argument list 403 and return value type 40
4 may be included in the search condition. If the rule 204 is not found (step 303), the failure of the function call of the interface conversion mechanism is notified (step 30).
6), the process ends.

If found (step 303), the converted function call pattern 20 in the conversion rule 204 is converted.
In accordance with No. 6, the requested function is converted into a set of server functions, which are sequentially called (step 304). FIG. 5 shows a specific example of the conversion rule table. This conversion rule table 1
There are two conversion rules 204 in 05. The method of searching the conversion rule 204 having the same function name 207 as the request function name 207 (step 302) and converting the requested function (step 304) will be described in more detail with reference to FIG. The function name 402 of the request is “setXY”, and if the function name 207 of the conversion rule table 105 is searched for, the first conversion rule 204 can be found. Therefore, the requested function is converted according to the first conversion rule 204 (step 304).

In the example shown in FIG. 5, the function name "setXY".
The pseudo server function 205 with no return value, which has the arguments of "long X" and "long Y" in the above, calls the function "setX" without a return value of the argument "long X" to the server "obj1", and the server Converted to a call to the function "setY" with no return value of the argument "long Y" to "obj1",
Called in order. Argument list 2 of pseudo server function 205
08 and the argument names (“X” and “Y” in this case) in the argument list 212 of the function call pattern 206 after conversion represent the correspondence of the arguments at the time of conversion. This association can be performed during the function call after conversion and also for the return value. The conversion rule 204 of the function name 207 “doAB” in FIG. 5 is that the server “obj1” has no arguments, the return value “short” type function “doA” is called, and the server “obj1” has “do”.
A return value of "short" type "A" is used as an argument
It is converted into a call of the "ong" type function "doB", and as a return value of the pseudo server function "doAB", "l" of "doB"
It indicates that a return value of type "ong" is passed.

A set of server functions is called according to the converted function call pattern 206 (step 304).
After that, the end state of the function call, the return value, the error information, and the like are notified (step 305), and the process ends. According to the above-described embodiment, it is possible to realize a client-server type system that enables addition of a new function that can be used by a client without changing the server program itself. Although only one client program 109 exists in the above embodiment, it is clear that a plurality of client programs 109 may exist. It is also clear that a plurality of interface conversion mechanisms 103 and server programs 104 may exist in the client / server system 100.

Further, the server program 104 used by the interface conversion mechanism 103 is arranged on a computer.
There are no particular restrictions. Therefore, if the communication efficiency is taken into consideration, the interface conversion mechanism 103 and the server program 104 may be mounted in the same process on the same computer. May be arranged in a computer other than the computer in which the interface conversion mechanism 103 exists. Next, a second embodiment of the present invention will be described. The present embodiment is an embodiment that enables the conversion rule table 105 to be changed online. FIG. 6 shows the client according to the present embodiment.
It is a figure showing the structure of the principal part of a server type system. The client / server system 600 according to the present embodiment is
As a component of the system 100 shown in FIG.
A conversion rule management mechanism 601 and a rule management interface 602 are added. Further, the conversion procedure in the interface conversion mechanism 103 and the structure of the conversion rule table 105 are also different from those in the first embodiment.

FIG. 7 shows a detailed configuration diagram of the interface conversion mechanism 103, the conversion rule table 105, and the conversion rule management mechanism 601 according to this embodiment. In the conversion rule table 105 according to this embodiment, the conversion rule 204
In addition to the usage number counter 702, the change permission flag 70
3, a deletion target flag 704 is added. The usage number counter 702 represents the usage state of the conversion rule, and is used to control the deletion or modification of the conversion rule in use.
The change permission flag 703 holds a setting state of permission / non-permission of deletion or change of the conversion rule 204. The deletion target flag 704 indicates whether the conversion rule 204 is a deletion target. The conversion rule management mechanism 601 includes a rule management interface 602 and a conversion rule registration management unit 70.
Consists of one. The components of the interface conversion mechanism 103 are the same as those in the first embodiment described above.

FIG. 8 illustrates the conversion procedure of the pseudo server function 205 according to the rules of the conversion rule table 105 in this embodiment. Hereinafter, using FIG. 7 and FIG.
The operation procedure of the interface conversion mechanism 103 will be described.
The interface conversion mechanism 103 monitors arrival of a function call message from the client program 109 to the pseudo server interface 106, and starts conversion operation upon arrival of the message. The interface conversion mechanism 103 may be activated by the arrival of a message from the client program 109. When the interface conversion mechanism 103 on the computer 102a receives the message 400, first,
The pseudo server interface function call message interpretation unit 201 interprets the function call message sent from the client program 109 (step 3).
01). It should be noted that this operation is the same as in the first embodiment described above.

Next, the interface conversion mechanism 103
From the conversion rule table 105, the deletion target flag 704
The conversion rule 204 having the same function name 207 as the function name 402 of the request which is not set is searched for (step 801).
If the conversion rule 204 is not found (step 8)
02) is notified of the failure of the function call of the interface conversion mechanism (step 809), and the processing ends. If found (step 802), 1 is added to the value of the number-of-uses counter 702 of the conversion rule 204 (step 803), and then the requested function is processed according to the function call pattern 206 after conversion in the conversion rule 204. To a set of server functions and call them sequentially (step 304). After the call is finished, 1 is subtracted from the value of the usage number counter 702 of the conversion rule 204 (step 80).
4).

In step 805, it is judged whether or not the deletion target flag 704 of the conversion rule 204 is set, and if the deletion target flag 704 is set and the value of the usage counter 702 is 0. (Step 80
6), the used conversion rule 204 is deleted from the conversion rule table 105. After that, the end state of the function call, the return value, error information, etc. are notified (step 80
8), the process ends. FIG. 9 shows the conversion rule management mechanism 6
01 indicates four types of function call messages 900 received via the rule management interface 602. The message types are the conversion rule registration message 910, the update message 920, and the deletion message 93.
0 and rule change permission setting message 940. The message destinations 901a, ..., 901, respectively
The address of the conversion rule management mechanism is entered in d.

FIG. 10 shows an operation procedure of the conversion rule management mechanism 601. The operation of the conversion rule management mechanism 601 will be described in detail below with reference to FIGS. 9 and 10. The client program 109 receives the conversion rule management mechanism 601 via the rule management interface 602.
Make a functional request to. The format of the function call message is
This is as shown in FIG. First, the function call message 9
00 is deciphered, and the processing is sorted according to the function names 902a, ..., 902d. It is determined whether the message is a conversion rule registration message (step 1010). If so, it is checked whether or not a rule relating to the same function as the conversion rule 903a given in the registration request message 910 is registered in the conversion rule table 105 (step 1011). If it has already been registered, the failure state of registration is notified (step 1013), and the process ends. If not registered, a new rule entry is added to the conversion rule table 105, and the conversion rule 903a specified by the registration message 910 is registered (step 1
012). After that, the fact that the registration is successful is notified (step 1014), and the process is ended.

If the conversion rule is not registered (step 1010), it is judged whether or not it is updated (step 102).
0). If so, the conversion rule table 105 stores the conversion rule 903 given in the update request message 920.
It is checked whether or not a rule relating to the same function as b is registered (step 1021). If not registered,
The update failure state is notified (step 1024), and the process ends. If it has been registered, the old process of the registered old rule is deleted (step 1100). FIG. 11 shows details of the old rule deletion process. The procedure of the deletion process of the specified old rule will be described below with reference to FIG. First, the value of the usage count counter 702 of the rule of the designated function in the conversion rule table 105 is obtained (step 1
101). Next, the state of the change permission flag 703 of the rule of the designated function in the conversion rule table 105 is obtained.
(Step 1102).

Then, by checking whether the value of the usage number counter 702 is 0 or more, it is judged whether or not the rule of the designated function is in use (step 1103). If it is not in use, it is judged from the state of the change permission flag 703 whether or not the change is permitted (step 1110). When the change is permitted, the designated old rule is deleted from the conversion rule table 105 (step 1111), the success of the rule deletion is notified (step 1112), and the process is ended. If the change is not permitted (step 1110), the failure to delete the designated old rule is notified (step 1122), and the process is terminated.

On the other hand, when the rule of the designated function is in use (step 1103), it is judged from the state of the change permission flag 703 whether or not the change in use is permitted (step 1120). If permitted, the deletion target flag 704 of the designated old rule in the conversion rule table 105 is set (step 1121), the success of the rule deletion is notified (step 1112), and the process ends. If the change is not permitted (step 1120), the failure of deleting the specified old rule is notified.
(Step 1122), the process ends. The "old rule deletion process" 1100 of FIG. 11 is executed as described above. Next, it is determined whether the deletion has succeeded (step 1022). If the deletion fails, the update failure status is notified (step 1024), and the processing ends.

If the deletion is successful, a new rule entry is added to the conversion rule table 105, and the conversion rule 903d designated by the registration message 920 is registered (step 1023). After that, the fact that the update has succeeded is notified (step 1025), and the process ends. If the conversion rule is not updated (step 1020), it is determined whether the conversion rule is deleted (step 1030). If so, it is checked whether or not a rule relating to the same function as the conversion rule 903c given in the deletion request message 930 is registered in the conversion rule table 105 (step 103).
1). If it is not registered, the update failure state is notified (step 1033) and the process is terminated. If it has been registered, the old process of the registered old rule is deleted (step 1100).

Next, it is judged whether or not the deletion is successful.
(Step 1032). If the deletion fails, the update failure status is notified (step 1033) and the processing ends.
If the deletion is successful, notify success (step 10
34) and ends. If the conversion rule is not deleted (step 1030), it is determined whether the conversion rule is a change permission / non-permission setting request (step 1040). Otherwise, notify the failure status of the function call (step 10
50), the process ends. If so, it is checked whether or not the rule 904 designated by the message 940 is registered in the pseudo server function 205 of the conversion rule table 105 (step 1041). If not registered,
Notify the failure state of request setting (step 1043),
The process ends. If registered, the change permission flag 703 of the designated rule 204 in the table is set in the designated setting content 905 (step 1042).

The states that can be designated include, for example, "can be changed at any time" and "cannot be changed while using a rule".
Finally, notify that the setting was successful (Step 10
44), the process ends. The above is the description of the second embodiment of the present invention in which the conversion rule can be changed online. In this embodiment, the conversion rule management mechanism 601 and the interface conversion mechanism 103 are arranged on the same computer 102a. However, since both mechanisms can refer to the same conversion rule table 105 by using a remote file access mechanism or the like. If they are available, they may be placed on different computers.
Further, in consideration of the ease of management and the maintainability of programs, the conversion rule management mechanism 601 and the interface conversion mechanism 10
3 may be implemented in the same process.

The online change process of the conversion rule 204 of the client / server system 1200 including the interface information server 112 will be described below with reference to FIGS. 12 and 13. FIG. 12 shows a client / server system 1200 in which the interface information server 112 exists. The interface information server 112 manages information on the interface 107 of the function group provided by the server including the pseudo server interface 106 on the client / server type system 1200.
The interface information here is usually a function name, argument list, and return value of a function that can be called via the interface. If you change the conversion rule 204,
The functions available to the client 110 via the pseudo server interface 106 change. Therefore, the conversion rule 204 is changed and the interface information server 112 is changed.
Will be notified of the change.

FIG. 13 shows the processing procedure of the conversion rule registration message 910, the update message 920, the deletion message 930, and the rule change permission setting message 940 in the conversion rule management mechanism 601 in the third embodiment of the present invention. Explaining. The difference from the procedure of the second embodiment shown in FIG. 10 is that a procedure of information registration of the pseudo server interface 106 to the interface information server 112 is added. More specifically, the conversion rule registration success notification 1014 and the update success notification 102 are given.
5. Immediately before the successful notification of deletion (step 1034), the pseudo server interface 105 after registration, update, and deletion
A procedure 1301 for notifying the interface information server 112 of the above information is added. Pseudo server interface 10
The interface information of No. 6 is the conversion rule table 105.
Function name 207 of the pseudo server function 205 of No. 20, argument list 20
8. Information about the return value 209, which is notified to the interface information server 112.

The conversion rule 204 will be described below with reference to FIG.
A fourth embodiment of the present invention will be described in which the rule selection condition 1401 is added. FIG. 14 shows rule selection condition 1.
The structure of the conversion rule 204 to which 401 is added is shown. In this embodiment, the pseudo server interface 1 of the interface conversion mechanism 103 is accompanied by the change of the conversion rule 204.
The procedure 304 for converting the function requested to 06 to the set of functions of the server and sequentially calling them is changed. Conversion rule table 1 with rule selection condition 1401 shown in FIG.
05, using the pseudo server interface 1 of the present embodiment
A procedure for converting a request function for 06 to a set of server functions and sequentially calling them will be described. It is assumed that the function name of the request to the pseudo server interface 106 is “setXY”.

In the conversion rule table 105, "setX
There is a “Y” conversion rule 204. Therefore, the requested function is converted according to this conversion rule. Conversion rule 204
, There are two converted function call patterns 208 according to the condition 1401. The function call pattern 208 selects the one that satisfies the condition 1401. The condition 1401 may be, for example, a condition regarding a value of a variable in the interface conversion mechanism 103 or a condition regarding a value externally given as an environment variable or the like. As a result of the selection according to the condition 1401, after one function call pattern after conversion is obtained, it is converted into a set of server functions of the embodiment shown in FIG.
The function is called by the same procedure as (step 304).

An embodiment of the client / server system 1500 including the interface conversion mechanism 103 having the static conversion rule table 1501 will be described below with reference to FIG. In the third embodiment shown in FIG. 12, the interface conversion mechanism 103 includes a static conversion rule table 1501 in the execution program (binary code). Therefore, when changing the conversion rule 204,
The interface conversion mechanism 103 including the changed static conversion rule table 1501 is generated. Except for this point, it is the same as the first embodiment. FIG. 16 illustrates generation of the interface conversion mechanism 103 incorporating the static conversion rule table 1501 by the interface conversion mechanism generator 1601. Interface conversion mechanism generator 1
601 generates the interface conversion mechanism 103 in which the given conversion rule table 105 is incorporated as a static rule table 1501.

FIG. 16 illustrates a case where the interface conversion mechanism generator 1601 is arranged on the computer 102e independent of the client / server system 1500. In this case, the target conversion rule table 105 is obtained from the system 1500 by some method, and the interface conversion mechanism 103 including the static conversion rule table 1501 is generated on the computer 102e. After that, the interface conversion mechanism 103 is set to the target client
Place in a server-type system. The interface conversion mechanism generator 1601 does not necessarily have to be placed on a computer independent of the system 1500, and may be placed on the client / server type system 1500.

In this embodiment, the interface conversion mechanism 103 and the server program 104 are the same computer 1.
Although it is arranged on 02a, it may be arranged on a different computer. Also, in consideration of communication efficiency, the interface conversion mechanism 103 and the server program 104 may be mounted in the same process. The above embodiments are merely examples of the present invention, and it goes without saying that the present invention is not limited to these embodiments.

[0034]

As described above in detail, according to the present invention, there is provided a client / server type system which enables addition of a new function available from a client without changing the server program itself. It has a remarkable effect that it can be realized. More specifically, the following effects can be obtained. (1) Conventionally, for example, when considering a communication efficiency and combining a plurality of functions provided by a server, it was necessary to rewrite and recompile the server program code.
According to the present invention, by rewriting the conversion rule table, it becomes possible to add a new function available from the client. (2) Further, according to the present invention, it becomes possible to rewrite the conversion rule table online, and
When a conversion rule is in use, it is possible to accept a request to change the conversion rule table while holding the conversion rule in use, and also to set a flag indicating permission / non-permission of change for each conversion rule. As a result, it becomes possible to arbitrate changes in the contents of the conversion rule table, which facilitates management of the conversion rule table.

(3) Further, according to the present invention, in the client / server system having the interface information server, the interface information server is automatically notified of the contents of the change of the pseudo server interface due to the change of the conversion rule table. By providing the conversion rule management mechanism with the mechanism, it becomes easy to manage the conversion rule table. (4) Further, according to the present invention, the conversion rule to be used can be switched according to the conditions. Therefore, if you want to provide different specific functions under some specific multiple conditions, you can change the variable value related to the conversion operation condition without changing the conversion rule each time. It is possible to switch the conversion rule to be used. That is, it is possible to easily and efficiently change the provided function. (5) Further, according to the present invention, a mechanism for automatically generating an interface conversion mechanism having a static conversion rule table incorporated therein from the conversion rule table is provided, and for example, the interface conversion mechanism is requested to change the conversion rule. When there is no such problem, the interface conversion mechanism generator automatically generates the interface conversion mechanism including the static conversion rule table, so that the conversion operation can be made efficient and the management can be facilitated.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a client / server type system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing configurations of an interface conversion mechanism and a conversion rule table in the embodiment shown in FIG.

FIG. 3 is a flowchart related to processing of a pseudo server function call in the embodiment shown in FIG.

FIG. 4 is a diagram showing a configuration example of a pseudo server function call message.

FIG. 5 is a diagram showing a configuration example of a conversion rule table.

FIG. 6 is a diagram showing a configuration of a client / server type system according to a second embodiment of the present invention.

7 is a diagram showing configurations of an interface conversion mechanism and a conversion rule table in the embodiment shown in FIG.

FIG. 8 is a flowchart related to the processing of calling a pseudo server function in the embodiment shown in FIG.

FIG. 9 is a diagram showing a configuration example of a function call message of a conversion rule management mechanism.

10 is a flowchart related to the processing of function call of the conversion rule management mechanism in the embodiment shown in FIG.

FIG. 11 is a flow chart related to deletion processing of an old conversion rule of the conversion rule management mechanism.

FIG. 12 shows a client according to the third embodiment of the present invention.
It is a figure which shows the structure of a server type system.

13 is a flowchart related to the processing of function call of the conversion rule management mechanism in the embodiment shown in FIG.

FIG. 14 is a diagram showing a configuration example of a conversion rule table according to a fourth embodiment of the present invention.

FIG. 15 shows a client according to a fifth embodiment of the present invention.
It is one block diagram of a server type system.

16 is a diagram illustrating generation of an interface conversion mechanism by the interface conversion mechanism generator in the embodiment shown in FIG.

[Explanation of symbols]

 102a to 102e Computer 103 Interface conversion mechanism 104 Server program 105 Conversion rule table 106 Pseudo server interface 107 Server interface 108 Network 109 Client program 204 Conversion rule 601 Conversion rule management mechanism 1501 Static conversion rule table 1601 Interface conversion mechanism generator

Claims (5)

[Claims] 1. A client having an interface conversion mechanism for receiving a function call request from a client.
In the server type data processing system, a conversion rule table holding conversion rules for converting the accepted function into a set of server function call requests is provided, and
A client / server type distributed processing system, wherein a conversion mechanism for converting a received function call into a set of server function calls according to the conversion rule of the conversion rule table is provided in the interface conversion mechanism. 2. In addition to the above-mentioned respective means, a means for receiving an online change request of a conversion rule table and interpreting the contents of the request, a means for grasping the usage status of the conversion rule in the conversion rule table, and a conversion A means for setting permission / non-permission of rule change for each use situation, a means for changing the conversion rule table, and a means for making a change to the conversion rule table in accordance with the setting content of change permission / non-permission of the change rule. The client / server type distributed processing system according to claim 1, wherein the distributed processing system is provided. 3. In addition to the above-mentioned respective means, a server for managing interface information of a function group provided by the server is provided,
3. The client-server distributed processing according to claim 2, further comprising means for notifying a server that manages the interface information of a change in a function that can be accepted by the interface conversion mechanism due to a change operation of the conversion rule table. system. 4. A means for switching a plurality of conversion rules by providing a rule selection condition in the conversion rule, in addition to the respective means.
The client / server type distributed processing system according to any one of 1. 5. A means for generating an interface conversion mechanism, which holds the conversion rule table therein, from the conversion rule table is provided in addition to the respective means. The described client / server distributed processing system.