JP5404528B2 - Data processing apparatus, data processing method, and program - Google Patents

Description

  The present invention relates to a system that provides a service to a client device such as a Web service.

  In a technology for managing service connection and I / F (interface) such as a Web service and providing service cooperation, conventionally, a data type matching an I / F of a target service is embedded in a request, and the service execution server apparatus A method of converting and transferring a request has been used (for example, Patent Document 1).

  In addition, when calling a service according to a scenario, a method is used in which metadata is embedded in the scenario in advance, and the corresponding service execution server device is called when the user executes the next service defined in the scenario. (For example, Patent Document 2).

JP 2006-190008 A JP 2008-130033 A

  The conventional service cooperation technology is solved in that the request is appropriately transferred to the service execution server device, but there is a problem when processing such as transferring the result to the next service is necessary.

  In the prior art, the service call order can be controlled according to the scenario. However, the call itself is basically triggered by the user, and even when it is processed mechanically, a message that connects between services separately. Since a design or a new module is required, there is a problem that the development cost for mechanically linking services is high.

In addition, the I / F of the server device that executes the service does not necessarily match the I / F that is disclosed to the client device.
When a service execution server device is newly created, the I / F of the server device matches the I / F disclosed to the client device. However, if the server device that executes the service is an existing external system, the client side uses it. In some cases, the I / F disclosed to the client device may be designed to be different from the I / F of the server device.
Even in such a case, as in the case of inter-service cooperation, the conventional technology requires a message design and a new module for connecting different I / Fs (public I / F to the client device and I / F of the server device). It is.

The main object of the present invention is to solve the above-mentioned problems and to eliminate the need for message design and new module development for connecting the interface for the client device and the interface of the service execution server device. One of them.
One of the main objectives is to eliminate the need for message design and new module development for inter-service collaboration.
In addition, one of the main purposes is to perform inter-service cooperation simply by specifying the execution order of registered services.

The data processing apparatus according to the present invention
A data processing apparatus connected to a client apparatus that requests provision of a service and a service execution server apparatus that executes a service requested by the client apparatus;
One or more arguments and one or more return values are specified as client arguments and client return values, and the client argument data type is defined for each client argument, and the client return value data type is defined for each client return value A client request generated according to the client interface and having a specific data value set in each client argument is received from the client device, and a specific data value is set in each client return value generated according to the client interface. A client communication unit that transmits a client response to the client device;
One or more arguments and one or more return values are specified as server arguments and server return values, the server argument data type is defined for each server argument, and the server return value data type is defined for each server return value A server request generated according to the server interface and having a specific data value set in each server argument is transmitted to the service execution server device, and a specific data value is generated in each server return value generated according to the server interface. A server communication unit that receives a set server response from the service execution server device; and
Analyzing the data type defined for each client argument and each client return value of the client interface and the data type defined for each server argument and each server return value of the server interface, For each type, a common variable management unit that generates a common variable used in common for common data types,
A common variable substitution value storage unit for storing a data value assigned to each common variable;
Substitute the data value of each client argument of the client request into a common variable corresponding to each client argument and write it to the common variable substitution value storage unit. After the server response is received by the server communication unit, A client that acquires a substituted data value from the common variable substitution value storage unit, sets the acquired data value to a client return value corresponding to the common variable, and generates a client response according to the client interface A variable processing unit;
The server variable interface acquires the data value assigned to the common variable by the client variable processing unit from the common variable assigned value storage unit, sets the acquired data value to a server argument corresponding to the common variable, and the server interface A server variable processing unit that generates a server request according to the server response, assigns a data value of each server return value of the server response to a common variable corresponding to each server return value, and writes the same to the common variable substitution value storage unit Features.

  According to the present invention, a common variable is generated for a common data type in arguments and return values included in a client interface and a server interface, and a request issuance to a service execution server device and service execution are performed using the common variable. The server apparatus can respond to the execution result of the server apparatus, and it becomes unnecessary to design a message and develop a new module for connecting the interface of the client apparatus and the interface of the service execution server apparatus.

FIG. 3 is a diagram illustrating a configuration example of a service cooperation server device according to the first embodiment. FIG. 4 is a flowchart showing an operation example of the client apparatus according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a service disclosure unit according to the first embodiment. FIG. 3 is a flowchart showing an operation example of a common variable generation unit according to the first embodiment. FIG. 6 is a flowchart showing an operation example of a type mapping management unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a service I / F management unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a data type management unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a common variable input / output unit according to the first embodiment. FIG. 3 is a flowchart showing an operation example of a service connection unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of the service execution server device according to the first embodiment. FIG. 4 shows a processing sequence according to the first embodiment. FIG. 4 shows a processing sequence according to the first embodiment. The figure which shows the structural example of the service cooperation server apparatus which concerns on Embodiment 2. FIG. FIG. 9 is a flowchart showing an operation example of a service disclosure unit according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a scenario management unit according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a common variable generation unit according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a scenario control unit according to the second embodiment. FIG. 6 shows a processing sequence according to the second embodiment. FIG. 6 shows a processing sequence according to the second embodiment. FIG. 10 is a diagram illustrating a configuration example of a service cooperation server device according to a third embodiment. FIG. 10 is a flowchart showing an operation example of a variable conversion unit according to the third embodiment. FIG. 10 shows a processing sequence according to the third embodiment. FIG. 4 is a diagram illustrating an example of information managed by a data type management unit or the like according to the first embodiment. The figure which shows the hardware structural example of the service cooperation server apparatus which concerns on Embodiment 1-3.

Embodiment 1 FIG.
FIG. 1 is a system configuration diagram showing a method for connecting and disclosing one service according to the present embodiment.

In FIG. 1, a client device 100 is a computer device that executes a client program that calls a service.
That is, the client device 100 requests the service cooperation server device 200 to provide a service.

The service cooperation server device 200 is connected to the client device 100 and the service execution server device 300.
The service cooperation server device 200 is a server device that provides a service that can be used from the client device 100.
The service cooperation server device 200 is an example of a data processing device.

The service execution server device 300 is a server device from which the service cooperation server device 200 requests service processing.
That is, the service execution server device 300 executes the service requested by the client device 100.
The service execution server device 300 is also called a service entity.

In the service cooperation server device 200, the service disclosure unit 201 has a function of exposing a service use interface to the client device 100.
The service disclosure unit 201 receives a request (also referred to as a client request) from the client device 100, generates a response (also referred to as a client response) to the request from the client device 100, and transmits the response to the client device 100.
The service disclosure unit 201 is an example of a client communication unit.
Also, it becomes an example of a client variable processing unit together with a common variable input / output unit 206 described later.

The common variable generation unit 202 is a function that generates a common variable for execution of processing in a request from a client device.
The common variable is a variable used until a request from the client device 100 is processed in the service execution server device 300 via the service cooperation server device 200 and a response is returned to the client device 100.
That is, the common variable is a variable that is commonly handled in a series of flows from reception of a request to transmission of a response.
A common variable used exclusively for one request / response from the client apparatus 100 is generated and does not affect other requests / responses.
A method for generating the common variable will be described later.
The common variable generation unit 202 is an example of a common variable management unit together with a data type management unit 203, a type mapping management unit 204, and a service I / F management unit 205 described later.

The data type management unit 203 is a function that manages a data type (type) handled by a service managed by the service cooperation server device 200 and a mutual relationship between the types.
In the present embodiment and the following embodiments, the data type refers to the type of information handled by the service (data type). It is different from the data type in programs such as int type and char type.
For example, in the case of a service for retrieving a product name from a product number, the client device 100 issues a request specifying a specific value as an argument of “product number”, and the service cooperation server device 200 uses a specific value as a return value of “product name”. Specify and return a response. In this case, “product number” and “product name” are data types (data types), respectively.
That is, the data type of the argument included in the request from the client device 100, the data type of the return value included in the response to the client device 100, and the request (from the service cooperation server device 200 to the service execution server device 300) The data type of the argument included in the server request), the data type of the return value included in the response (also referred to as the server response) transmitted from the service execution server device 300 to the service cooperation server device 200, and This is a data type used in the following embodiments.
In this way, the data type management unit 203 performs “price”, “stock quantity”, “delivery date”, “production lot”, “employee number”, “employee name” in addition to the above “article number” and “article name”. ”,“ Department ”,“ Position ”,“ Sensor ID ”,“ Temperature ”,“ Humidity ”,“ Power consumption ”,“ Weight ”, etc. All arguments and return values in the service handled by the service cooperation server device 200 Manage the data type.

The type mapping management unit 204 is a function that manages the mapping between specific items of service I / F managed by the service cooperation server device 200 and the types of information managed by the data type management unit 203.
The service I / F management unit 205 is a function for managing an I / F of a service managed by the service cooperation server device 200.
As described above, the data type management unit 203, the type mapping management unit 204, and the service I / F management unit 205 are examples of the common variable management unit together with the common variable generation unit 202.

The common variable input / output unit 206 is a function for inputting / outputting a value to / from the common variable generated by the common variable generation unit 202.
As described above, the common variable input / output unit 206 is an example of the client variable processing unit together with the service disclosure unit 201.
The common variable input / output unit 206 is an example of a server variable processing unit together with a service connection unit 208 described later.

The common variable substitution value storage unit 207 stores the substitution value for the common variable generated by the common variable generation unit 202.
The common variable substitution value storage unit 207 is a partial area of a memory such as a RAM (Random Access Memory), for example, and is an area secured by the common variable generation unit 202 for storing the common variable.

The service connection unit 208 is a function for transmitting a request from the service cooperation server device 200 to the service execution server device 300.
The service connection unit 208 transmits a request (server request) to the service execution server device 300 based on a request (client request) from the client device 100, and receives a response (server response) from the service execution server device 300. Receive.
The response from the service execution server device 300 is the basis of the response to the client device 100 (client response).
The service connection unit 208 is an example of a server communication unit.
The service connection unit 208 is an example of a server variable processing unit together with the common variable input / output unit 206 as described above.

  The data type management unit 203, the type mapping management unit 204, and the service I / F management unit 205 may be separate servers.

  Next, before describing the operation of each function in detail, an outline of the operation of the service cooperation server device 200 according to the present embodiment will be described below.

In the present embodiment, the common variable generation unit 202 generates a common variable for data types that are common in arguments and return values included in the client interface of the client device 100 and the server interface of the service execution server device 300. .
The service disclosure unit 201 assigns an argument included in the request (client request) from the client device 100 to the common variable, and the service connection unit 208 requests the service execution server device 300 using the data value of the common variable as an argument. (Server request) is generated, and the return value included in the response (server response) of the service execution server device 300 is substituted into the common variable.
Then, the service disclosure unit 201 generates a response (client response) to the client device 100 using the data value of the common variable as a return value, and transmits the response to the client device 100.

More specifically, the service disclosure unit 201 receives a client request transmitted from the client device 100.
The client request is generated according to the client interface and includes one or more arguments as client arguments.
In the client interface, a client argument data type (data type) is defined for each client argument.
For this reason, the client request includes a client argument of a defined data type, and includes a specific data value as each client argument (for example, “123456” is used as the client argument of “product number”). include).
In addition, the service disclosure unit 201 transmits a client response to the client device 100 as a response to the client request.
The client response is generated according to the client interface, and one or more return values are included as client return values.
In the client interface, a client return value data type (data type) is defined for each client return value.
Therefore, the client response includes a client return value of a defined data type, and a specific data value is included as each client return value (for example, “ABC−” as the client return value of “product name”). XYZ "is included in the client response).

The service connection unit 208 transmits a server request generated based on the client request to the service execution server device 300.
The server request is generated according to the server interface, and one or more arguments are included as server arguments.
In this embodiment, it is assumed that the client interface and the server interface are different.
In the server interface, the server argument data type (data type) is defined for each server argument.
For this reason, the server request includes a server argument of a defined data type, and includes a specific data value as each server argument (for example, “123456” is the server request as the server argument of “product number”). include).
Further, the service connection unit 208 receives a server response from the service execution server device 300 as a response to the server request.
The server response is generated according to the server interface, and one or more return values are included as server return values.
In the server interface, the server return value data type (data type) is defined for each server return value.
For this reason, the server response includes a server return value of a defined data type, and includes a specific data value as each server return value (for example, “ABC− XYZ "is included in the server response).

The common variable generation unit 202 uses the data type management unit 203, the type mapping management unit 204, and the service I / F management unit 205 to define data defined for each client argument and each client return value of the client interface. The type and the data type defined for each server argument and each server return value of the server interface are analyzed, and a common variable used in common for the common data type is generated for each data type.
Further, the common variable generation unit 202 generates common variable association information indicating associations between client arguments, server arguments, and common variables, and associations between client return values, server return values, and common variables.
For example, if the client argument A and the server argument C are the data type “product number”, the common variable generation unit 202 generates the common variable a for the data type “product number”, and the client return value B and the server return value D are the data type. If “product name”, a common variable “b” is generated for the data type “product name”.
Then, the common variable generation unit 202 displays common variable association information indicating a correspondence between the client argument A, the server argument C, and the common variable a, and a correspondence between the client return value B, the server return value D, and the common variable b. Is generated.

In addition, the common variable generation unit 202 includes synonymous data when two or more synonymous data types (replaceable data types) that are mutually different data types but have a replaceable relationship are included. Generate the same common variable for the type.
Further, the common variable generation unit 202 displays common variable association information indicating the association between client arguments and server arguments and the association between client return values and server return values for common variables generated for synonymous data types. Is generated.
For example, if the data type of the client argument A is “product number” and the data type of the server argument C is “serial number”, the two do not match but have the same contents, and thus are synonymous (replaceable). The common variable generation unit 202 generates a common variable a for the data type “product number” of the client argument A and the data type “serial number” of the server argument C, and the correspondence between the client argument A, the server argument C, and the common variable a. The common variable association information indicating the attachment is generated.
The common variable generation unit 202 also generates information indicating that the data type of the client argument A is “product number” and the data type of the server argument C is “serial number”.

  As described above, the common variable substitution value storage unit 207 stores the substitution value for the common variable generated by the common variable generation unit 202.

The common variable input / output unit 206 inputs the data value of each client argument of the client request from the service disclosure unit 201, assigns the input data value to the common variable corresponding to the data type of each client argument, and sets the common variable substitution value Write to the storage unit 207.
Further, the common variable input / output unit 206 acquires the data value assigned to the common variable from the common variable assigned value storage unit 207 and passes it to the service connection unit 208.
The service connection unit 208 sets the data value acquired from the common variable input / output unit 206 as a server argument corresponding to the common variable, generates a server request according to the server interface, and transmits the server request to the service execution server device 300. .
According to the above example, the common variable input / output unit 206 assigns the data value “123456” of the client argument A to the common variable a and writes it to the common variable assigned value storage unit 207. The value “123456” of the common variable a is acquired from 207 and passed to the service connection unit 208 as the server argument C.
The service connection unit 208 sets “123456” as the server argument C and generates a server request.

Further, the common variable input / output unit 206 inputs the data value of each server return value of the server response from the service connection unit 208, and substitutes the input data value into the common variable corresponding to the data type of each server return value. Write to the common variable substitution value storage unit 207.
Further, the common variable input / output unit 206 acquires the data value assigned to the common variable from the common variable assigned value storage unit 207 and passes it to the service disclosure unit 201.
The service disclosure unit 201 sets the data value acquired from the common variable input / output unit 206 as a corresponding client return value, generates a client response according to the client interface, and transmits the client response to the client device 100.
According to the above example, the common variable input / output unit 206 assigns the data value “ABC-XYZ” of the server return value D to the common variable b and writes it to the common variable assignment value storage unit 207.
In addition, the value “ABC-XYZ” of the common variable b is acquired from the common variable substitution value storage unit 207 and passed to the service disclosure unit 201 as the data value of the client return value B.
The service disclosure unit 201 sets “ABC-XYZ” as the client return value B and generates a client response.

Next, the operation of the service cooperation server device 200 according to this embodiment will be described in detail.
The operation of each function will be described using a flowchart, and the overall operation combining the functions will be described using a sequence diagram.

FIG. 2 is a process flowchart in the client apparatus 100.
The client device 100 transmits a request to the service cooperation server device 200 and obtains the result (F0100).

FIG. 3 is a process flowchart in the service disclosure unit 201 of the service cooperation server device 200.
The service disclosure unit 201 receives a request (client request) from the client device 100 (F0200), notifies the common variable generation unit 202 of which service the request is for, and requests generation of the common variable. A reference to the common variable is acquired from the generation unit 202 (F0201).
The reference to this common variable is a common variable to which a client argument is assigned (a common variable whose value is to be read as a server argument) and a common variable to which a server return value is assigned (a common variable whose value is to be read as a client return value) Is an example of common variable association information.

The service disclosure unit 201 assigns the value of the client argument included in the request to the common variable using the common variable input / output unit 206 (F0202), and passes the reference to the common variable to the service connection unit 208 to request service execution. (F0203).
That is, the service disclosure unit 201 notifies the common variable input / output unit 206 of the data value of the client argument in association with the variable name of the target common variable, and the common variable input / output unit 206 corresponds the data value of the client argument. Is assigned to the common variable and written to the common variable assignment value storage unit 207.
Further, the service disclosure unit 201 assigns, to the service connection unit 208, a common variable (a common variable whose value should be read as a server argument) to which a client argument value is substituted and a common variable (client return) to which a server return value is substituted. A service execution is requested by notifying a reference (common variable association information) to a common variable indicating a common variable whose value is to be read).

Also, the service disclosure unit 201 acquires a service execution result (client return value) from the common variable input / output unit 206 (F0204), and generates a response (client response) according to the client interface based on the acquired execution result. The response is returned to the client device 100 (F0205).
That is, the service disclosure unit 201 receives a notification from the service connection unit 208 that a response from the service execution server device 300 has been obtained, and a common variable (client return) in which the value of the server return value is substituted into the common variable input / output unit 206. Common variable from which the value is to be read out), the client return value is acquired from the common variable input / output unit 206, a response (client response) is generated using the acquired value, and the response is sent to the client apparatus 100. return.

  FIG. 4 is a process flowchart in the common variable generation unit 202.

When the common variable generation unit 202 receives a common variable generation request from the service disclosure unit 201 (F0300), the common variable generation unit 202 inquires of the type mapping management unit 204 about a data type to be converted into a common variable for the service requested by the client device 100 (F0301). ).
Next, the common variable generation unit 202 generates a common variable from the obtained mapping data type list, and stores a synonymous data type (F0302).
Further, the common variable generation unit 202 generates a reference to the common variable (an example of common variable association information).
As described above, the common variable reference is information indicating a correspondence between the client argument, the server argument, and the common variable, and a correspondence between the client return value, the server return value, and the common variable.
The generated reference to the common variable is returned to the service disclosure unit 201 that is the caller (F0303).

  FIG. 5 is a processing flowchart in the type mapping management unit 204.

When receiving an inquiry about a data type to be converted into a common variable from the common variable generation unit 202 (F0400), the type mapping management unit 204 refers to the I / F of the corresponding service from the service I / F management unit 205 (F0401).
Next, the type mapping management unit 204 outputs a mapping list from the mapping information managed in the type mapping management unit 204 to the data type for arguments and return values to the service obtained from the service I / F (F0402). ).
The type of each type in the mapping list is acquired using the data type management unit 203, and the data type having the same meaning (the same type) is removed from the list (F0403).
At this time, the method of grouping the data types may be a method of selecting the first synonymous data type list or a method of selecting at random (for example, “Data A, Data B, Data C, Data D” exists in the data type list, and data A When data B and data C are synonymous, when the first is selected, the data is summarized as “data A, data D.” Since the selection rule is not particularly specified, even if “data B, data D” are randomly combined. Good).
The arranged data type list and the data type list removed because it is synonymous are returned (F0404).
More specifically, since the mapping information is also associated with the list, the list of “data A, data D” is, for example, “data A = client argument 1 (synonymous: data B = service A argument 1), data D = client return value (synonymous: data C = service A return value) ”.

FIG. 23 shows an example of information managed by the data type management unit 203, information managed by the type mapping management unit 204, and information managed by the service I / F management unit 205.
The data type management unit 203 manages the data type and the mutual relationship between the data types.
The service I / F management unit 205 manages arguments and return values in each interface.
The type mapping management unit 204 manages mapping information.
The mapping information is service I / F and data type mapping information.
The mapping list is a list of mappings obtained by subtracting mapping information from the argument / return value of the specified service I / F.
In the example of FIG. 23, the service I / F management unit 205 manages client interface information and service A interface information.
The client interface includes argument 1 (int type), argument 2 (int type), and return value 1 (int type). The service A interface includes argument 1 (string type) and argument 2 (int type). ), A return value 1 (string type) is included.
Also, the type mapping management unit 204 uses the client interface argument 1, argument 2, and return value data type (argument 1 = data type A, argument 2 = data type C, return value = data type D) as mapping information. In addition, the argument 1 and argument 2 of the service A interface and the data type of the return value (argument 1 = data type B, argument 2 = data type C, return value = data type E) are managed.
The data type management unit 203 manages data types that are synonymous as mutual relationships. Specifically, data type A and data type B are synonymous, and data type D and data type E are synonymous.
The type mapping management unit 204 generates a data type mapping list from these pieces of information.
That is, the type mapping management unit 204 has the same meaning as the argument 1 (data type A) of the client interface and the argument 1 (data type B) of the service A interface, and the argument 2 (data type C) of the client interface. The mapping list that the argument 2 (data type C) of the service A interface is the same data type, and the return value (data type D) of the client interface and the return value (data type E) of the service A interface are synonymous. Is generated.

  FIG. 6 is a processing flowchart in the service I / F management unit 205.

  When the service I / F management unit 205 receives the reference of the service I / F (F0500), the service I / F management unit 205 returns the I / F of the corresponding service from the identifier such as the service name (F0501).

FIG. 7 is a processing flowchart in the data type management unit 203.
When the data type management unit 203 receives a data type inquiry (F0600), it returns a synonymous (same type) data type list from the data types managed in the data type management unit 203 (F0601).

  FIG. 8 is a processing flowchart in the common variable input / output unit 206.

The common variable input / output unit 206 inputs an input / output inquiry for the common variable (F0700).
More specifically, the common variable input / output unit 206, when assigning a data value to a common variable, should assign the information of the inquiry source (whether it is the service disclosure unit 201 or the service connection unit 208) and the common variable. Enter the value and the corresponding I / F of the value (argument or return value).
Further, in the case of reading a data value from a common variable, information on the inquiry source (whether it is the service disclosure unit 201 or the service connection unit 208) and a corresponding I / F to be read (whether it is an argument or a return value) are input. .
Next, the common variable input / output unit 206 determines whether there is an assignment value to the common variable in F0700, and determines whether the process to be executed is input or output (F0701).
Specifically, when an assignment value to a common variable is input, the input is made at F0702.
On the other hand, when the assignment value to the common variable is not input, an output is made in F0702.

In the case of input in the determination of F0702, the common variable input / output unit 206 substitutes the value input from the inquiry source into the common variable of the variable name corresponding to the input I / F (F0703).
If the inquiry is an input from the service disclosure unit 201 (request input from the client), the value input from the service disclosure unit 201 is substituted into a common variable corresponding to the client argument.
If the inquiry is an input from the service connection unit 208 (response acquisition from the service entity), the value input from the service connection unit 208 is substituted into a common variable corresponding to the server return value.
On the other hand, if it is output in the determination of F0702, the data value is read from the common variable having the variable name corresponding to the I / F input from the inquiry source, and is output to the inquiry source (F0704).
If the inquiry is an output from the service connection unit 208 (request acquisition to the service entity), a data value (corresponding to a server argument) from a common variable with a variable name corresponding to the I / F input from the service connection unit 208 Is output to the service connection unit 208.
Further, when the inquiry is an output from the service disclosure unit 201 (acquisition of a response to the client), a data value (corresponding to a client return value) from a common variable having a variable name corresponding to the I / F input from the service disclosure unit 201 Is output to the service disclosure unit 201.

  FIG. 9 is a process flowchart in the service connection unit 208.

When the service connection unit 208 receives a service execution request from the service disclosure unit 201 (F0800), the service connection unit 208 uses the common variable input / output unit 206 to acquire a value serving as a service argument from the common variable (F0801).
As described above, since the service connection unit 208 acquires the reference of the common variable from the service disclosure unit 201, the service connection unit 208 notifies the common variable input / output unit 206 of the output of the common variable in which the value to be read as the server argument is stored. can do. For the same reason, the input to the common variable to be substituted for the server return value can be notified to the common variable input / output unit 206 also when the server return value to be described later is substituted.
Next, the service connection unit 208 uses the value acquired from the common variable input / output unit 206 to cause the service execution server device 300 to execute a process to obtain a result (F0802).
That is, a value acquired from the common variable input / output unit 206 is set as a server argument, a request to the service execution server device 300 is generated, transmitted to the service execution server device 300, and a response is received from the service execution server device 300. Receive.
Next, the service connection unit 208 substitutes the result obtained from the service execution server device 300 into the common variable using the common variable input / output unit (F0803).
That is, the service connection unit 208 passes the server return value included in the response and the server return value (I / F) to the common variable input / output unit 206, and causes the server return value to be assigned to the common variable.
The common variable input / output unit 206 assigns the server return value to the corresponding common variable and writes it in the common variable assignment value storage unit 207.
Further, the service connection unit 208 notifies the service disclosure unit 201 that the response from the service execution server device 300 has been obtained.

FIG. 10 is a process flowchart in the service execution server apparatus 300.
The service execution server apparatus 300 receives a request (server request) from the service cooperation server apparatus 200, executes service processing, generates a response (server response) indicating the result, and returns the response to the service cooperation server apparatus 200 ( F0900).

  The overall operation combining the respective functions will be described in the case where the client device 100 uses the service of the service execution server device 300 disclosed on the service cooperation server device 200.

FIGS. 11 and 12 are sequence diagrams illustrating operations in which the client device 100 uses the service of the service execution server device 300 disclosed on the service cooperation server device 200.
The operation until the client device 100 obtains the service execution result will be described using this.

The client apparatus 100 transmits a request according to the client interface disclosed by the service disclosure unit 201 (S0100).
The service disclosure unit 201 receives the request and requests the common variable generation unit 202 to generate a common variable corresponding to the service called (the service requested by the request) (S0101).

The common variable generation unit 202 inquires of the data type list used in the service called by the type mapping management unit 204 (S0102).
The type mapping management unit 204 acquires the I / F of the corresponding service from the service I / F management unit 205 (S0103 to S0104), and acquires the mapping between the argument and the return value I / F and the type from the service I / F. (S0105).
A data type list synonymous with each data type obtained from the mapping is acquired from the data type management unit 203 (S0106 to S0107), and synonymous types are collected from the I / F and type mapping list (S0108).
The collected data type list and a data type list synonymous with each data type in the list are returned to the common variable generation unit 202 (S0109).
The common variable generation unit 202 generates a common variable from the obtained data type list (S0110).
At this time, a synonymous data type list is also stored.
That is, the common variable generation unit 202 generates the same common variable for the same data type. The same common variable is also generated for synonymous data types.
The common variable generation unit 202 returns a reference to the generated common variable to the service disclosure unit 201 (S0111).

  The service disclosure unit 201 converts the client argument of the request into a common variable using the common variable input / output unit 206 from the obtained reference to the common variable (S0112 to S0113), and notifies the service connection unit 208 of the reference to the common variable. A service execution is requested (S0114).

Based on the reference to the common variable acquired from the service disclosure unit 201, the service connection unit 208 acquires a value for requesting the service to be executed (the value of the server argument) from the common variable input / output unit 206 (S0115 to S0116). Then, a request to the service execution server device 300 is generated using the acquired value, the request is transmitted to the service execution server device 300, and a service execution result is obtained from the service execution server device 300 (S0117 to S0118).
Here, since the values obtained from the common variable input / output unit 206 are grouped with synonymous types according to the service I / F when the common variable is generated, a value to be used for the request is obtained.
The service connection unit 208 converts the result obtained by executing the service into a common variable using the common variable input / output unit 206 (S0119 to S0120), and returns execution completion to the service disclosure unit 201 (S0121).
The service disclosure unit 201 acquires an execution result (a client return value) from the common variable input / output unit 206 (S0122 to S0123), generates a response to the client device 100 from the acquired value, and sends the generated response to the client device. Return to 100 (S0124).
Here, since the values obtained from the common variable input / output unit 206 are grouped with synonymous types according to the service I / F when the common variable is generated, the value to be used for the response can be obtained as in the case of S0115. become.

As described above, information necessary to execute a service (service I / F and types of argument / return value types and their mapping) is managed, and synonymous data is collected into a common variable within a series of linkage processes. By doing so, it is possible to eliminate the need for an internal message design for cooperation.
Here, the internal message design for cooperation is from when the service cooperation server device receives the request until it is transferred to the service execution server device, and until the processing result from the service execution server device is returned to the client device. This corresponds to a data format design.
In accordance with the interface, the design of how many bytes to how many bytes should be used as an area for storing an argument if it is byte data, what schema should be used if it is XML (Extensible Markup Language) data Such a design is required.
In this embodiment, a common variable is generated in accordance with the interface, so that such a design is not necessary.

  In addition, since the common variable has a temporary storage area secured by the common variable generation unit, it can be operated independently for simultaneous requests from a plurality of clients.

As described above, in the present embodiment,
Means for publishing services available from any client, means for managing service I / F, means for managing information types and interrelationships, means for managing I / F and type mapping, and processing Apparatus for executing service cooperation using a server having means for acquiring a common temporary storage area in the process, means for inputting / outputting information to / from the temporary area, and means for connecting to the service execution server apparatus Explained.

Embodiment 2. FIG.
In the first embodiment described above, the service cooperation server device 200 cooperates so that one type of service can be executed from the client. Next, an embodiment in which a plurality of services are cooperated will be described. .

  FIG. 13 is a system configuration diagram showing a method for connecting and linking two services.

In FIG. 13, the functions changed / added from the system configuration diagram (FIG. 1) of the first embodiment are a service disclosure unit 201, a common variable generation unit 202, a scenario management unit 209, and a scenario control unit 210. The same as in the first embodiment.
The service cooperation server device 200 is connected to a service execution server device A301 and a service execution server device B302.
The service execution server device A301 and the service execution server device B302 execute the service in the same manner as the service execution server device 300 in the first embodiment, but the internal service processes are different.
Further, a server interface specific to each of the service execution server device A301 and the service execution server device B302 is provided.
In addition, when not distinguishing service execution server apparatus A301 and service execution server apparatus B302, it describes with the service execution server apparatus 300. FIG.

The service publishing unit 201 has a function of publishing a service use interface to the client apparatus 100 and publishing a scenario for executing a plurality of services as a service.
The common variable generation unit 202 is a function that generates a common variable for service execution in a request from the client device 100 and each service execution in the scenario.
The scenario management unit 209 is a function that manages the execution order of services as a service execution scenario (also simply referred to as a scenario).
The scenario control unit 210 is a function that executes services in the order set in the scenario.
The scenario management unit 209 and the scenario control unit 210 are examples of a cooperative service management unit.
The scenario management unit 209 may be a separate server.
In addition, not only the execution order but also an execution flow such as execution conditions, conditional branching, and specification of a service to be called in the case of an error is specified in the scenario. specify.

Also in this embodiment, the service disclosure unit 201 is an example of a client communication unit and a client variable processing unit, and a common variable generation unit 202, a data type management unit 203, a type mapping management unit 204, a service I / F management. A unit 205 is an example of a common variable management unit.
The common variable input / output unit 206 is an example of a client variable processing unit and a server variable processing unit, and the service connection unit 208 is an example of a server communication unit and a server variable processing unit.

  Next, the operation of the service cooperation server device 200 according to the present embodiment will be outlined with a focus on differences from the first embodiment.

The scenario management unit 209 corresponds to the case where the request (client request) from the client device 100 is analyzed, and the service requested in the request is a cooperation service realized by cooperation of two or more service execution server devices. Select a service execution scenario from multiple service execution scenarios.
As described above, the service execution scenario indicates a service execution order in two or more service execution server devices (cooperation service execution server devices) that realize the cooperation service.
In addition, the common variable generation unit 202 includes data types defined for each client argument and each client return value of the client interface, and each server argument and each server of the server interface of each cooperative service execution server device 300. Analyzes the data type defined for the return value and generates a common variable for each data type.

The common variable input / output unit 206 acquires the data value of the client argument assigned to the common variable from the common variable assigned value storage unit 207.
Then, the service connection unit 208 corresponds to the data value acquired by the common variable input / output unit 206 in correspondence with the common variable in the server interface of the cooperative service execution server device 300 in the first order in the scenario service execution order. The server request to the first order linkage service execution server apparatus 300 is generated according to the server interface of the first order linkage service execution server apparatus 300, and the first order linkage service execution server apparatus 300 is set. Send to.
Every time the service connection unit 208 receives a server response until the server response from the cooperative service execution server device 300 in the last order, the common variable input / output unit 206 sets each server return value of the received server response. The assigned data value is assigned to a common variable corresponding to each server return value and written to the common variable assignment value storage unit 207, and the data value assigned to the common variable is acquired from the common variable assignment value storage unit 207. The service connection unit 208 sets the data value acquired by the common variable input / output unit 206 as a server argument corresponding to the common variable in the server interface of the subsequent cooperative service execution server device 300 in the scenario service execution order. In accordance with the server interface of the subsequent cooperative service execution server device 300, the subsequent cooperative service execution It generates a server request to the server apparatus 300 repeats the operation of sending to the subsequent cooperative service executing server device 300.
The subsequent cooperation service execution server device 300 includes not only the cooperation service execution server device 300 in the next order in the service execution order of the scenario, but also the cooperation service execution server device 300 in the next order or later.
Further, the scenario control unit 210 notifies the service connection unit 208 of the subsequent cooperative service execution server device 300 every time the service connection unit 208 receives a server response.
The service connection unit 208 uses the server parameter of the server interface of the subsequent cooperative service execution server device 300 notified by the scenario control unit 210 of the data value acquired by the common variable input / output unit 206 from the common variable substitution value storage unit 207. To generate a server request to the subsequent linked service execution server device.

  Then, after the server response from the cooperative service execution server device 300 in the last order in the service execution order of the scenario is received and the server return value included in the service response is stored in the common variable substitution value storage unit 207, The common variable input / output unit 206 acquires the data value assigned to the common variable from the common variable assigned value storage unit 207, and the service disclosure unit 201 uses the data value acquired by the common variable assigned value storage unit 207 as the common value. The client response value corresponding to the variable is set and a client response is generated according to the client interface, and is transmitted to the client device 100.

Next, the operation of the service cooperation server device 200 according to this embodiment will be described in detail.
The operation of each function will be described using a flowchart, and the overall operation combining the functions will be described using a sequence diagram.
Hereinafter, only the functions different from those of the first embodiment will be described for the operation of each function.

  FIG. 14 is a process flowchart in the service disclosure unit 201.

The service disclosure unit 201 receives a request from the client device 100 (F1000), and if the service requested by the request is a cooperation service, acquires a scenario corresponding to the request from the client device 100 from the scenario management unit 209. A list of services in the scenario is obtained (F1001).
The service list shows the execution order of services.
Next, the service disclosure unit 201 passes the service list to the common variable generation unit 202, requests generation of the common variable, and acquires a reference to the common variable (F1002).
The reference to the common variable is an example of the common variable association information.
In the present embodiment, the reference of the common variable refers to the association between the client argument and the server argument of the cooperation service execution server device in the first order and the common variable, the server return value and the server of the cooperation service execution server device in the last order. The association between the return value and the common variable and the association between the server return value of each cooperation service execution server device, the server argument of the subsequent cooperation service execution server device, and the common variable are shown.

  The service publishing unit 201 substitutes the client argument of the request into a common variable using the common variable input / output unit 206 (F1003), and passes the reference to the common variable and the scenario to the scenario control unit 210 to request scenario execution ( F1004), the scenario execution result is acquired from the common variable input / output unit 206 (F1005), and it is returned to the client device 100 as a response (F1006).

  FIG. 15 is a processing flowchart in the scenario management unit 209.

When the scenario management unit 209 receives the scenario content acquisition from the service disclosure unit 201 (F1100), the scenario management unit 209 returns the scenario content corresponding to the request notified from the service disclosure unit 201 (F1101).
That is, the scenario management unit 209 selects a scenario that realizes the cooperation service requested by the request notified from the service disclosure unit 201 from among a plurality of scenarios.

  FIG. 16 is a process flowchart in the common variable generation unit 202.

When the common variable generation unit 202 receives a request for generating a common variable together with the service list from the service disclosure unit 201 (F1200), the type mapping management unit 204 instructs each service included in the service list acquired from the service disclosure unit 201 for each service. The data type to be converted into a common variable is inquired (F1201).
Next, the common variable generation unit 202 generates a common variable from the obtained mapping data type list, and also stores a synonymous data type (F1202).
Further, the reference to the generated common variable is returned to the service disclosure unit 201 that is the caller (F1203).
In the present embodiment, the common variable generation unit 202 uses the data type management unit 203, the type mapping management unit 204, and the service I / F management unit 205 for each service shown in the service list, and uses the client interface. The data type defined for each client argument and each client return value, and the data type defined for each server argument and each server return value of the server interface of each cooperative service execution server device 300 Analyze and generate a common variable for each data type.
Then, the common variable generation unit 202 generates a common variable reference according to the service execution order shown in the service list.
As described above, specifically, the common variable generation unit 202 associates the client argument with the server argument of the cooperation service execution server device in the first order and the common variable, the client return value and the cooperation service in the last order. Reference of the common variable indicating the correspondence between the server return value of the execution server device and the common variable, and the correspondence between the server return value of each linkage service execution server device, the server argument of the subsequent linkage service execution server device, and the common variable Is generated.

  FIG. 17 is a process flowchart in the scenario control unit 210.

When the scenario control unit 210 receives a scenario execution request together with the target scenario from the service disclosure unit 201 (F1300), the service is executed using the service connection unit 208 in accordance with the service execution order indicated in the scenario. (F1301).
That is, whenever the service connection unit 208 receives a server response, the scenario control unit 210 receives a notification that the server response has been received from the service connection unit 208, refers to the service execution order of the scenario, and The subsequent linked service execution server apparatus 300 is notified.
In the service connection unit 208, the server return value assigned to the common variable from the common variable substitution value storage unit 207 via the common variable input / output unit 206 is used as the server argument value of the subsequent cooperative service execution server device 300. The acquired data value is set in the corresponding server argument, a request (server request) is generated according to the server interface of the subsequent cooperative service execution server device 300, and is transmitted to the subsequent cooperative service execution server device 300.
Further, the scenario control unit 210 acquires a value for determination from the common variable input / output unit 206 if there is a designation such as a conditional branch in the scenario (for example, “if the return value of the service A is 0 or more”). And execute the following services:
That is, the scenario management unit 209 creates a scenario in which the destination of the next server request branches to two or more cooperation service execution server devices 300 according to a specific server return value of the server response from the specific cooperation service execution server device 300. May be selected.
When a branch occurs due to the server return value of the server response received by the service connection unit 208, the scenario control unit 210 determines that the branch destination linked service from among the two or more linked service execution server devices based on the server return value. Select an execution server device.
Which server return value is to be subjected to branch determination is specified in the request from the client device 100 or the execution result of any service.
When the data value (server return value) subject to branch determination is stored in the common variable substitution value storage unit 207, the scenario control unit 210 stores data values (servers) subject to branch determination in the common variable input / output unit 206. Return value) is acquired, and the data value (server return value) that is the object of branch determination is acquired from the common variable input / output unit 206.
Then, the scenario control unit 210 compares the server return value with the branch determination condition, and selects the branch destination cooperative service execution server device.
For example, when the condition “shift to service A if the value of the server return value subject to branch determination is 0 and shift to service B otherwise” is set in the scenario, the scenario control unit 210 The branch destination cooperative service execution server device is selected depending on whether the target data value is 0 or not.
The scenario control unit 210 notifies the service connection unit 208 of the selected cooperative service execution server device.
Then, when the service connection unit 208 inputs the data value assigned to the common variable from the common variable input / output unit 206, the service connection unit 208 uses the server interface of the branch destination cooperative service execution server device 300 selected by the scenario control unit 210. A server request to the branch destination cooperative service execution server device 300 is generated by setting the server argument corresponding to the common variable.

  The client apparatus 100 uses the service A of the service execution server apparatus A301 and the service B of the service execution server apparatus B302 published on the service cooperation server apparatus 200 in a scenario in cooperation with each other by combining the functions. The operation will be described.

FIG. 18 and FIG. 19 show an operation in which the client apparatus 100 uses the service A of the service execution server apparatus A301 and the service B of the service execution server apparatus B302 that are disclosed on the service cooperation server apparatus 200 in a scenario. It is a sequence diagram.
The operation until the client device 100 obtains the service execution result will be described using this.
The part which becomes the sequence similar to Embodiment 1 is simplified.

The client apparatus 100 transmits a request according to the client interface disclosed by the service disclosure unit 201 (S0200).
The service disclosure unit 201 acquires the corresponding scenario from the scenario management unit 209 (S0201 to S0202), and passes the service list in the scenario to the common variable generation unit 202 and requests to generate a common variable (S0203).

The common variable generation unit 202 inquires the data type to the type mapping management unit 204 for each service in the scenario (S0204: same as S0102 to S0109 in FIG. 11), and generates a common variable (S0205: same as S0110 in FIG. 11). .
The common variable generation unit 202 returns a reference to the generated common variable to the service disclosure unit 201 (S0206: the same as S0111 in FIG. 11).

  The service disclosure unit 201 uses the common variable input / output unit 206 from the obtained reference to the common variable to convert the request content into a common variable (S0207: similar to S0112 to S0113 in FIG. 11), and executes the scenario to the scenario control unit 210. A request is made (S0208).

The scenario control unit 210 requests the service connection unit 208 to execute service A according to the scenario (S0209). At this time, the common variable reference storing the server argument and server return value of the service A is passed from the scenario control unit 210 to the service connection unit 208.
Based on the reference of the common variable acquired from the scenario control unit 210, the service connection unit 208 acquires a value for requesting the service to be executed (the value of the server argument) from the common variable input / output unit 206, and the acquired value is The service execution server device A301 is used to generate a request, the request is transmitted to the service execution server device A301, the service execution result is obtained from the service execution server device A301, and the common variable input / output unit 206 is used to obtain the common variable. The result (server return value) is substituted for (S0210: the same as S0115 to S0120 in FIG. 11).

When the service connection unit 208 returns execution completion (S0211), the scenario control unit 210 proceeds to the next service execution. If there is a branch or the like in the scenario, the common variable input / output unit 206 is used to obtain a value used for the determination. (S0212). In this sequence, the process proceeds to the next service execution.
As in the case of execution of service A (S0209 to S0211), the scenario control unit 210 passes the reference of the common variable storing the server argument and server return value of the service B to the service connection unit 208, and executes the service B (S0213). ~ S0215).
At this time, even if it is necessary to acquire the value (server argument value) necessary for execution of service B from the execution result (service return value) of service A, the execution result (server return value) of service A is common. Since it is variable and the request content to the service B is acquired from the common variable, a value to be used for the request is obtained.
When the scenario is completed, the scenario control unit 210 returns execution completion to the service disclosure unit 201 (S0216).
The service disclosure unit 201 acquires an execution result (client return value) using the common variable input / output unit 206 (S0217: similar to S0122 to S0123 in FIG. 11), and generates a response to the client device 100 from the acquired value. The generated response is returned to the client device 100 (S0218).

As described above, information necessary to execute a service (service I / F and types of argument / return value types and their mapping) is managed, and synonymous data is collected into a common variable within a series of linkage processes. As a result, even when multiple services such as scenario execution are linked, the internal message design can be made unnecessary.
Further, since the contents of the scenario are contents such as the execution order, and there is no need to be aware of the I / F between services, it is possible to reduce the cost of refurbishing when a change occurs in the scenario.

  As described above, in the present embodiment, the service cooperation apparatus including the means for managing the service cooperation scenario and the means for controlling the scenario has been described.

  Further, in the present embodiment, the service cooperation apparatus has been described that includes means for controlling a conditional branch or the like based on information in the temporary storage area in the means for controlling the scenario.

Embodiment 3 FIG.
In the second embodiment described above, when a plurality of services are linked, the services are linked. However, an embodiment in which value conversion is required between the linked services next is shown. .

  FIG. 20 is a system configuration diagram showing a method for converting values between linked services.

  In FIG. 20, the function added from the system configuration diagram (FIG. 13) of the second embodiment is a variable conversion unit 211, and other functions are the same as those of the second embodiment.

The variable conversion unit 211 has a function of converting a value according to a data type when inputting / outputting to / from a common variable.
The conversion by the variable conversion unit 211 is, for example, to convert a weight value expressed in tons into a kilogram notation.
The variable conversion unit 211 is an example of a data conversion unit.

Specifically, the variable conversion unit 211 inputs a data value to be stored in the common variable substitution value storage unit 207 from the common variable input / output unit 206, and the data format of the data value (ton notation, kilogram notation, etc.) When the data value is read out from the common variable substitution value storage unit 207 to determine whether it matches the data format used in the service disclosure unit 201 or the service connection unit 208, and the data format does not match In addition, the data format of the data value is converted into a data format used by the service disclosure unit 201 or the service connection unit 208.
Further, the variable conversion unit 211 inputs the data value acquired by the common variable input / output unit 206 from the common variable substitution value storage unit 207, and the data format of the data value is the service disclosure unit 201 or the service connection. It is determined whether or not the data format used by the unit 208 matches, and if the data format does not match, the data format of the data value used by the service disclosure unit 201 or the service connection unit 208 is determined. Convert to
Since the variable conversion unit 211 has information synonymous with the reference to the common variable (reference of the common variable from the request reception of the client device 100 to the response transmission of the client device 100), for each common variable Next, the data format when used as an argument or a return value can be determined.

Also in this embodiment, the service disclosure unit 201 is an example of a client communication unit and a client variable processing unit, and a common variable generation unit 202, a data type management unit 203, a type mapping management unit 204, a service I / F management. A unit 205 is an example of a common variable management unit.
The common variable input / output unit 206 is an example of a client variable processing unit and a server variable processing unit, and the service connection unit 208 is an example of a server communication unit and a server variable processing unit.
Further, the scenario management unit 209 and the scenario control unit 210 are examples of a cooperative service management unit.

Next, the operation will be described.
The operation of each function will be described using a flowchart, and the overall operation combining the functions will be described using a sequence diagram.
Regarding the operation of each function, only functions different from those of the second embodiment will be described.

FIG. 21 is a processing flowchart in the variable conversion unit 211.
When the variable conversion unit 211 receives input / output to / from the common variable (F1400), the process is divided depending on whether the target common variable completely matches the input / output data type (F1401).

If the data types match completely, the variable conversion unit 211 assigns or acquires the value as it is (F1402). If the data types do not match completely, the variable conversion unit 211 changes the synonym type information stored together with the common variable to the matching type. It is converted and assigned or acquired (F1403).
For example, in the conversion between tons and kilograms, the variable conversion unit 211 performs conversion that multiplies the data value by 1000 or 1/1000.

The client apparatus 100 uses the service A of the service execution server apparatus A301 and the service B of the service execution server apparatus B302 published on the service cooperation server apparatus 200 in a scenario in cooperation with each other by combining the functions. The operation will be described.
Here, unlike the case of the second embodiment, when the return value of service A is passed to service B, the type (data format) is not completely matched.

FIG. 20 illustrates a common variable among operations in which the client apparatus 100 uses the service A of the service execution server apparatus A301 and the service B of the service execution server apparatus B302 that are disclosed on the service cooperation server apparatus 200 in a scenario. It is the sequence diagram which showed only the input / output part.
Most of the entire operation is the same as in the case of the second embodiment (FIGS. 18 and 19), and only the input / output portion to the common variable is different. explain.

First, input of values will be described.
When the common variable input / output unit 206 requests the variable conversion unit 211 to substitute a value (S0300), the variable conversion unit 211 uses the type of the common variable (data to be used as an argument or a return value when it is read next time). Compared with the format), it is checked whether direct substitution is possible (S0301).
If direct assignment is not possible, the value is converted from the synonymous type stored together with the common variable to an assignable type and assigned (S0302), and assignment completion is returned to the common variable input / output unit 206.

Next, output of values will be described.
When the common variable input / output unit 206 requests the variable conversion unit 211 to refer to the value (S0304), the variable conversion unit 211 refers to the type of the common variable and the type that the value wants to reference (data format used as an argument or a return value). Is checked (S0305).
If the type is different, the value is converted from the synonymous type stored together with the common variable to the target type (S0306), and the converted value is returned to the common variable input / output unit 206 (S0307).

As described above, information necessary to execute a service (service I / F and types of argument / return value types and their mapping) is managed, and synonymous data is collected into a common variable within a series of linkage processes. By integrating the multiple services such as scenario execution, even if it is necessary to convert the value, it can be automatically converted by using the variable conversion unit, eliminating the need for internal message design. be able to.
In addition, since the contents of the scenario are contents such as the execution order, and there is no need to be aware of the I / F between services, when the scenario is changed, the renovation cost is suppressed as in the case of the second embodiment. Can do.

In the present embodiment, the description has been made by taking as an example the case where the service cooperation shown in the second embodiment is present, but the conversion by the variable conversion unit 211 is also performed when there is no service cooperation shown in the first embodiment. It can be performed.
That is, the conversion by the variable conversion unit 211 is performed when the data format differs between the client argument and the server argument, or when the data format differs between the client return value and the server return value.

  As described above, in the present embodiment, the service cooperation apparatus provided with the means capable of converting the temporary storage area into an appropriate type and inputting / outputting information has been described.

Finally, a hardware configuration example of the service cooperation server device 200 shown in the first to third embodiments will be described.
FIG. 24 is a diagram illustrating an example of hardware resources of the service cooperation server device 200 illustrated in the first to third embodiments.
Note that the configuration in FIG. 24 is merely an example of the hardware configuration of the service cooperation server device 200, and the hardware configuration of the service cooperation server device 200 is not limited to the configuration described in FIG. There may be.

In FIG. 24, the service cooperation server device 200 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, a processing unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
The “common variable substitution value storage unit 207” described in the first to third embodiments is realized by the RAM 914 or the like.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

  The communication board 915 is connected to the network. For example, the communication board 915 is connected to a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), and the like.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the service cooperation server device 200 is activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  In the program group 923, programs that execute the functions described as “˜unit” (other than “common variable substitution value storage unit 207” hereinafter) and “˜means” in the description of the first to third embodiments. Is remembered. The program is read and executed by the CPU 911.

In the description of the first to third embodiments, the file group 924 includes “determination of”, “determination of”, “comparison of”, “substitution of”, “acquisition of”, and “update of”. ”,“ Setting of ”,“ registration of ”,“ selection of ”, etc., information, data, signal values, variable values, and parameters indicating the results of the processing are represented by“ ˜file ”or“ ˜ It is stored as each item of “Database”.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
In addition, arrows in the flowcharts described in the first to third embodiments mainly indicate input / output of data and signals, and the data and signal values are the memory of the RAM 914, the flexible disk of the FDD904, the compact disk of the CDD905, and the magnetic field. Recording is performed on a recording medium such as a magnetic disk of the disk device 920, other optical disks, mini disks, DVDs, and the like. Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

Further, in the description of the first to third embodiments, what is described as “to part” and “to means” may be “to circuit”, “to device”, and “to device”. It may be “˜step”, “˜procedure”, “˜processing”.
That is, the data processing method according to the present invention can be realized by the steps, procedures, and processes shown in the flowcharts described in the first to third embodiments.
In addition, what is described as “˜unit” and “˜means” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” and “to means” in the first to third embodiments. Alternatively, the procedures and methods of “to part” and “to means” in the first to third embodiments are executed by a computer.

  As described above, the service cooperation server device 200 shown in the first to third embodiments includes a CPU as a processing device, a memory as a storage device, a magnetic disk, a keyboard as an input device, a mouse, a communication board, and a display device as an output device, A computer including a communication board and the like, and as described above, functions indicated as “˜unit” and “˜means” are realized by using these processing devices, storage devices, input devices, and output devices.

  100 client device, 200 service cooperation server device, 201 service disclosure unit, 202 common variable generation unit, 203 data type management unit, 204 type mapping management unit, 205 service I / F management unit, 206 common variable input / output unit, 207 common Variable substitution value storage unit, 208 service connection unit, 209 scenario management unit, 210 scenario control unit, 211 variable conversion unit, 300 service execution server device, 301 service execution server device A, 302 service execution server device B.

Claims (14)

A data processing apparatus connected to a client apparatus that requests provision of a service and a service execution server apparatus that executes a service requested by the client apparatus;
One or more arguments and one or more return values are specified as client arguments and client return values, and the client argument data type is defined for each client argument, and the client return value data type is defined for each client return value A client request generated according to the client interface and having a specific data value set in each client argument is received from the client device, and a specific data value is set in each client return value generated according to the client interface. A client communication unit that transmits a client response to the client device;
One or more arguments and one or more return values are specified as server arguments and server return values, the server argument data type is defined for each server argument, and the server return value data type is defined for each server return value A server request generated according to the server interface and having a specific data value set in each server argument is transmitted to the service execution server device, and a specific data value is generated in each server return value generated according to the server interface. A server communication unit that receives a set server response from the service execution server device; and
Analyzing the data type defined for each client argument and each client return value of the client interface and the data type defined for each server argument and each server return value of the server interface, For each type, a common variable management unit that generates a common variable used in common for common data types,
A common variable substitution value storage unit for storing a data value assigned to each common variable;
Substitute the data value of each client argument of the client request into a common variable corresponding to each client argument and write it to the common variable substitution value storage unit. After the server response is received by the server communication unit, A client that acquires a substituted data value from the common variable substitution value storage unit, sets the acquired data value to a client return value corresponding to the common variable, and generates a client response according to the client interface A variable processing unit;
The server variable interface acquires the data value assigned to the common variable by the client variable processing unit from the common variable assigned value storage unit, sets the acquired data value to a server argument corresponding to the common variable, and the server interface A server variable processing unit that generates a server request according to the server response, assigns a data value of each server return value of the server response to a common variable corresponding to each server return value, and writes the same to the common variable substitution value storage unit Characteristic data processing device. The common variable management unit
Generating common variable mapping information indicating the mapping between the client argument, the server argument, and the common variable, and the mapping between the client return value, the server return value, and the common variable;
The client variable processing unit
Substituting the data value of each client argument of the client request into the corresponding common variable based on the association between the client argument and the common variable indicated in the common variable association information,
The data value assigned to the common variable is acquired from the common variable assigned value storage unit, and the acquired data value is handled based on the correspondence between the client return value and the common variable indicated in the common variable association information. Set to the client return value
The server variable processing unit
The data value assigned to the common variable is acquired from the common variable assignment value storage unit, and the acquired data value is associated based on the association between the server argument and the common variable indicated in the common variable association information. Set in the server argument,
2. The data value of each server return value of the server response is assigned to the corresponding common variable based on the association between the server return value and the common variable indicated in the common variable association information. The data processing apparatus described. The common variable management unit
Analyzing the data types defined for each client argument and each client return value of the client interface and the data types defined for each server argument and each server return value of the server interface, If two or more replaceable data types that have different data types but are mutually replaceable are included, generate the same common variable for the replaceable data types,
Generating common variable association information indicating a correspondence between a client argument and a server argument and a correspondence between a client return value and a server return value for the common variable generated for the replaceable data type The data processing apparatus according to claim 2. The data processing device further includes:
From the client variable processing unit or the server variable processing unit, input a data value to be stored in the common variable substitution value storage unit,
Whether or not the data format of the data value matches the data format when the data value is next read from the common variable substitution value storage unit and used in the client variable processing unit or the server variable processing unit Judging
The data conversion unit for converting the data format of the data value into a data format used in the client variable processing unit or the server variable processing unit when the data formats do not match. 4. The data processing device according to any one of 3. The data processing device further includes:
From the client variable processing unit or the server variable processing unit, the client variable processing unit or the server variable processing unit inputs a data value acquired from the common variable substitution value storage unit,
Determining whether the data format of the data value matches the data format used when the data value is used in the client variable processing unit or the server variable processing unit;
The data conversion unit for converting the data format of the data value into a data format used in the client variable processing unit or the server variable processing unit when the data formats do not match. 5. The data processing device according to any one of 4. The data processing device includes:
Connected to a plurality of service execution server devices each having its own server interface,
The data processing device further includes:
Two or more cooperative service execution server devices that analyze the client request and realize the cooperative service when the service requested in the client request is a cooperative service realized by cooperation of two or more service execution server devices A service management unit for selecting a service execution scenario indicating the service execution order in
The common variable management unit
Data types defined for each client argument and each client return value of the client interface, and for each server argument and each server return value of the server interface of each cooperative service execution server device Analyze the data type, generate a common variable for each data type,
The client variable processing unit
After the server response from the cooperative service execution server device in the last order in the service execution order of the service execution scenario is received, the data value assigned to the common variable is obtained from the common variable assignment value storage unit and obtained. Set the data value to the client return value corresponding to the common variable and generate a client response according to the client interface,
The server variable processing unit
The server value of the cooperative service execution server device in the first order in the service execution order is acquired from the common variable assignment value storage unit data value assigned to the common variable by the client variable processing unit A server request corresponding to the first order linkage service execution server device according to the server interface of the first order linkage service execution server device is set in the server argument corresponding to the common variable in
Every time the server communication unit receives a server response until the server response from the linked service execution server device in the last order, the data value of each server return value of the received server response is a common variable corresponding to each server return value. Is assigned to the common variable substitution value storage unit, the data value assigned to the common variable is acquired from the common variable substitution value storage unit, and the acquired data value is the subsequent cooperative service in the service execution order. Generating a server request to the subsequent cooperative service execution server device according to the server interface of the subsequent cooperative service execution server device by setting the server argument corresponding to the common variable in the server interface of the execution server device; The data processing device according to claim 1, wherein the data processing device is a data processing device. The cooperative service management unit
Each time the server communication unit receives a server response, the server variable processing unit is notified of a subsequent cooperative service execution server device in the service execution order,
The server variable processing unit
The data value acquired from the common variable substitution value storage unit is set in the server argument of the server interface of the subsequent cooperative service execution server device notified by the cooperative service management unit, and sent to the subsequent cooperative service execution server device. The data processing apparatus according to claim 6, wherein a server request is generated. The common variable management unit
Correspondence between client arguments and server arguments and common variables of first-order linkage service execution server device, association of client return values and server return values and common variables of last-order linkage service execution server device, and each linkage Generate common variable association information indicating the association between the server return value of the service execution server device, the server argument of the subsequent linked service execution server device, and the common variable;
The client variable processing unit
Substituting the data value of each client argument of the client request into the corresponding common variable based on the association between the client argument and the common variable indicated in the common variable association information,
The data value assigned to the common variable is acquired from the common variable assigned value storage unit, and the acquired data value is handled based on the correspondence between the client return value and the common variable indicated in the common variable association information. Set to the client return value
The server variable processing unit
The data value assigned to the common variable by the client variable processing unit is acquired from the common variable assigned value storage unit, and the acquired data value is the first linked service execution server device indicated in the common variable association information. Based on the association between the server argument and the common variable, set the server argument that is supported in the server interface of the linked service execution server device in the first order,
Each time the server communication unit receives a server response,
Based on the association between the server return value of the cooperative service execution server device that is the transmission source of the server response indicated in the common variable association information and the common variable, the common data value corresponding to each server return value of the server response Assign to a variable,
A data value assigned to a common variable is acquired from the common variable assignment value storage unit, and the acquired data value is set to a server argument and a common variable of a subsequent cooperative service execution server device indicated in the common variable association information, 8. The data processing apparatus according to claim 6, wherein the server argument corresponding to the server interface of the subsequent cooperative service execution server apparatus is set based on the association. The common variable management unit
Data types defined for each client argument and each client return value of the client interface and data defined for each server argument and each server return value of the server interface of each cooperative service execution server device Analyzing the type, if two or more replaceable data types are included that are different from each other but replaceable, generate the same common variable for the replaceable data type,
Common that shows the correspondence between client arguments and server arguments, the correspondence between client return values and server return values, and the correspondence between server return values and server arguments for common variables generated for replaceable data types The data processing apparatus according to claim 8, wherein variable association information is generated. The data processing device further includes:
From the client variable processing unit or the server variable processing unit, input a data value to be stored in the common variable substitution value storage unit,
Whether or not the data format of the data value matches the data format when the data value is next read from the common variable substitution value storage unit and used in the client variable processing unit or the server variable processing unit Judging
7. A data conversion unit for converting the data format of the data value into a data format used by the client variable processing unit or the server variable processing unit when the data formats do not match. The data processing device according to any one of 9. The data processing device further includes:
From the client variable processing unit or the server variable processing unit, the client variable processing unit or the server variable processing unit inputs a data value acquired from the common variable substitution value storage unit,
Determining whether the data format of the data value matches the data format used when the data value is used in the client variable processing unit or the server variable processing unit;
7. A data conversion unit for converting the data format of the data value into a data format used by the client variable processing unit or the server variable processing unit when the data formats do not match. The data processing apparatus according to any one of 10. The cooperative service management unit
Depending on the data value of the specific server return value of the server response from the specific cooperative service execution server device, there may be a case where a service execution scenario is selected in which the destination of the next server request branches to two or more cooperative service execution server devices. ,
When the data value of the server return value of the server response received by the server communication unit is a data value that causes a branch of the transmission destination of the server request in the service execution scenario, two or more linked services based on the data value Select the branch destination linked service execution server device from the execution server devices,
The server variable processing unit
The data value assigned to the common variable is acquired from the common variable assignment value storage unit, and the acquired data value is determined in the server interface of the branch destination cooperative service execution server device selected by the cooperative service management unit. 12. The data processing apparatus according to claim 6, wherein a server request is generated for the branch destination cooperative service execution server apparatus by setting the server argument corresponding to the common variable. A data processing method performed by a client device that requests service provision and a computer connected to a service execution server device that executes a service requested by the client device,
One or more arguments and one or more return values are specified as client arguments and client return values, and the client argument data type is defined for each client argument, and the client return value data type is defined for each client return value The client receives from the client device a client request that is generated according to the client interface and has a specific data value set in each client argument, and is generated according to the client interface and is specific to each client return value A client communication step in which the computer transmits a client response to the client device;
One or more arguments and one or more return values are specified as server arguments and server return values, the server argument data type is defined for each server argument, and the server return value data type is defined for each server return value The server sends a server request generated in accordance with the server interface and a specific data value set in each server argument to the service execution server device, and is generated in accordance with the server interface and specified in each server return value. A server communication step in which the computer receives a server response in which a data value is set from the service execution server device; and
The computer defines a data type defined for each client argument and each client return value of the client interface and a data type defined for each server argument and each server return value of the server interface. A common variable management step for analyzing and generating, for each data type, a common variable used in common for the common data type;
The computer stores a common variable substitution value storage step for storing a data value assigned to each common variable in a predetermined common variable substitution value storage area;
After the computer substitutes the data value of each client argument of the client request into a common variable corresponding to each client argument and writes it to the common variable substitution value storage area, and after the server response is received by the server communication step The data value assigned to the common variable is acquired from the common variable assigned value storage area, the acquired data value is set to the client return value corresponding to the common variable, and the client response is performed according to the client interface. Client variable processing step to generate
The computer acquires the data value assigned to the common variable by the client variable processing step from the common variable assignment value storage area, and sets the acquired data value as a server argument corresponding to the common variable. A server variable processing step of generating a server request in accordance with the server interface, assigning a data value of each server return value of the server response to a common variable corresponding to each server return value, and writing the same into the common variable assignment value storage area; A data processing method characterized by comprising: A client device that requests provision of a service, and a computer connected to a service execution server device that executes a service requested by the client device;
One or more arguments and one or more return values are specified as client arguments and client return values, and the client argument data type is defined for each client argument, and the client return value data type is defined for each client return value A client request generated according to the client interface and having a specific data value set in each client argument is received from the client device, and a specific data value is set in each client return value generated according to the client interface. A client communication step of transmitting a client response to the client device;
One or more arguments and one or more return values are specified as server arguments and server return values, the server argument data type is defined for each server argument, and the server return value data type is defined for each server return value A server request generated according to the server interface and having a specific data value set in each server argument is transmitted to the service execution server device, and a specific data value is generated in each server return value generated according to the server interface. A server communication step of receiving a set server response from the service execution server device;
Analyzing the data type defined for each client argument and each client return value of the client interface and the data type defined for each server argument and each server return value of the server interface, For each type, a common variable management step for generating a common variable used in common for common data types,
A common variable substitution value storage step for storing a data value assigned to each common variable in a predetermined common variable substitution value storage area;
Substitute the data value of each client argument of the client request into a common variable corresponding to each client argument and write it to the common variable substitution value storage area. After the server response is received by the server communication step, A client that acquires a substituted data value from the common variable substitution value storage area, sets the acquired data value to a client return value corresponding to the common variable, and generates a client response according to the client interface Variable processing steps;
The server variable interface acquires the data value assigned to the common variable by the client variable processing step from the common variable assignment value storage area, sets the acquired data value as a server argument corresponding to the common variable, and the server interface And generating a server request according to the server response, substituting the data value of each server return value of the server response into a common variable corresponding to each server return value, and writing to the common variable substitution value storage area. A program characterized by

Images