JP4599456B2 - Service processing apparatus, system, program, and recording medium - Google Patents

Description

  The present invention relates to a service processing device, a system, a program, and a recording medium, and in particular, a service processing device that executes a requested service, a service processing system that includes a plurality of the service processing devices, and a computer that functions as the service processing device. And a recording medium on which the service processing program is recorded.

  In recent years, SOA (Service Oriented Architecture), which is a design method for constructing a large-scale system as a collection of “services”, has become widespread. In relation to this SOA, Patent Document 1 describes the establishment of data consistency across many databases when the SOA is applied to a system having many databases and linked.

  Further, in Patent Document 2, in a computer that executes a web service that realizes the SOA model, a control flow for authentication / authorization processing is provided independently of a flow of service providing processing, so that the service and the service A technique for realizing loose coupling of authentication / authorization processing services is disclosed.

  Patent Document 3 stores a service definition including a service ID, correspondence information between the business process ID and the service ID, stores the business process definition, searches the service definition using the input service as a search key, and sets the service ID. A technique for acquiring, retrieving a business process definition by using the service ID as a search key, acquiring the business process ID, and outputting corresponding information is disclosed.

Special table 2008-511934 gazette JP 2006-72548 A JP 2007-304951 A

  In a computer system constructed by applying SOA, a program is divided into functional units, and if a program that realizes a part of the divided individual functions has already been developed, the developed program Because it is constructed by diverting the system, programs (service processing units) that realize different functions from each other are connected in multiple stages by loose coupling, and each stage of service requests input to the computer system is linked by multiple stages of service processing units In general, the processing is performed. When a failure occurs in a computer system having such a configuration, there is a possibility that inconsistency may occur in data held by individual service processing units or data held in a database (DB) connected to a different service processing unit. is there.

  On the other hand, if a computer system with multiple stages of service processing units is provided with a function to guarantee data consistency, the design and development of the system becomes very complicated, and a large amount of man-hours are required. There is a problem of need. Patent Documents 1 to 3 do not disclose any technique for solving the above-described problem.

  The present invention has been made in consideration of the above facts, and has a simple configuration and can easily realize data consistency when a failure occurs, a service processing apparatus, a service processing system, a service processing program, and a recording medium Is the purpose.

In order to achieve the above object, a service processing apparatus according to the first aspect of the present invention is a service processing apparatus that is realized by a computer and constitutes a service processing system together with another service processing apparatus capable of transmitting and receiving information. When execution of a service is requested by receiving a service request with an ID added, if there is a local service corresponding to the service requested to be executed as a process related to the requested service, Process the service and store the processing result of the service in the storage unit in association with the service ID. If there is a lower service corresponding to the service requested to be executed, the service ID of the lower service is set. A service request with the generated service ID added is transmitted to the lower-level service processing device. A first function for performing processing for storing the processing result of the lower service in association with the generated service ID in the storage means and transmitting a response to the transmission source of the service request, processing result confirmation with the service ID added When confirmation of the processing result of the service is requested by receiving the request, the processing result of the service corresponding to the requested service is confirmed based on the information stored in the storage means. When confirmation of the processing result of the corresponding lower service is necessary, a processing result confirmation request with the service ID of the corresponding lower service is transmitted to the lower service processing apparatus, and the processing confirmed when the confirmation of the processing result is completed A second function for transmitting the result to the processing result confirmation request source, and a service to which the same service ID as the previously received service request is added. When a re-execution of a previously requested service is requested by receiving a service request, a sub service having idempotency among one or more services corresponding to the service requested to be re-executed With respect to the above, without confirming the processing result of the subordinate service having the idempotency, a service request is transmitted to the service processing apparatus that performs the subordinate service having the idempotency, For the subordinate service, the processing result of the non-ideal subordinate service is confirmed. If the confirmed processing result is “unknown” indicating that a response to the service request has not been received, the subordinate subordinate service the process attempts result confirmation request confirmation of the processing result by transmitting again to the service processing unit which performs, only when the "processing unfinished" is obtained as the processing result, the lower of said non-idempotent After transmitting a service request to the service processing apparatus that performs the service, a process for reconfirming the processing result of the subordinate service such as the non-defaming is performed . A third function for transmitting a response is provided.

  The service processing apparatus according to the first aspect of the present invention is realized by a computer and constitutes a service processing system together with other service processing apparatuses capable of transmitting and receiving information. The typical configuration of the service processing system is a configuration in which each service processing device is realized by different computers, but a part or all of the service processing devices are realized by the same computer. Also good. In addition, the service processing apparatus according to the first aspect of the present invention includes first to third functions described below.

  In other words, when the first function according to the present invention is requested to execute the service by receiving the service request to which the service ID is added, the first function is performed as a process related to the requested service. If there is a corresponding self service, the self service is processed, the processing result of the self service is stored in the storage unit in association with the service ID, and a lower-level service corresponding to the service requested to be executed is If it exists, a service request with the service ID generated and added with the service ID is transmitted to the lower service processing apparatus, and the processing result of the lower service is associated with the generated service ID and stored. This is a function that performs processing to be stored in and sends a response to the transmission source of the service request. Here, when the invention according to claim 1 is applied to each service processing device constituting the service processing system (when each service processing device has the first function described above), the highest-level service processing When requesting the execution of a service to a device, if there is a self-service corresponding to the requested service, the self-service is processed and a service request is transmitted to a lower-level service processing device as necessary. Then, even in the service processing device that has received the service request, the service request is transmitted to the service processing device as needed. As a result, the execution of services is automatically chained as necessary regardless of the number of service processing devices connected.

  In addition, the second function according to the present invention is based on the information stored in the storage unit when the confirmation of the processing result of the service is requested by receiving the processing result confirmation request to which the service ID is added. Confirm the processing result of the service corresponding to the service for which the confirmation of the processing result is requested, and if it is necessary to confirm the processing result of the corresponding lower service, send a processing result confirmation request with the service ID of the corresponding lower service added. This is a function for transmitting to the lower-level service processing apparatus and transmitting the confirmed processing result to the transmission source of the processing result confirmation request when the confirmation of the processing result is completed. Here, when the invention according to claim 1 is applied to each service processing device constituting the service processing system (when each service processing device has the second function described above), the highest level service processing When requesting confirmation of the processing result from the device, the processing result of the processing related to the requested service is confirmed, and if necessary, the processing result confirmation request is transmitted to the lower-level service processing device, and the processing result confirmation request is received. Even in the service processing apparatus, the processing result confirmation request is transmitted to the service processing apparatus at a lower level as necessary. As a result, regardless of the number of service processing devices connected, etc., the processing result confirmation request is notified after the processing results are automatically chained as necessary. In the case where no is returned, it is possible to check the processing result of the service that has previously requested execution.

In addition, the third function according to the present invention receives a service request to which the same service ID as the previously received service request is added, so that re-execution of a service that has been requested to be executed is requested. Among the one or more services corresponding to the service requested to be re-executed, for the subordinate service having idempotency, the idempotency is confirmed without confirming the processing result of the subordinate service having idempotency. sends a service request to the service processing apparatus for performing subservice with, for lower-level service for non-idempotent no idempotency, said check the processing result of the lower service non idempotent, confirm the processing result In the case of “unknown” indicating that a response to the service request has not been received, the processing result confirmation request is transmitted to a service processing apparatus that performs the non-defective lower level service. Processing trial result of the check again, as the processing result only when the "processing unfinished" is obtained, the after transmitting the service request to the service processing apparatus for subservice non idempotent, lower the non-idempotent This is a function of performing a process for reconfirming the processing result of the service, and transmitting a response according to the confirmed processing result to the transmission source of the service request when the process ends.

  Note that a service having idempotency is a service that can obtain the same result no matter how many times it is executed, such as a reference service (for example, a service that reads and outputs data from a database). On the other hand, a service that does not have idempotency is a service whose result changes each time it is executed, and an update-type service (for example, a service that adds a value to database data each time it is executed) corresponds to this service. Here, when the invention according to claim 1 is applied to each service processing device constituting the service processing system (when each service processing device has the above third function), a virtual function such as Regardless of whether the actual service is idempotent or not, a function that enables the same result to be obtained no matter how many times the service execution is requested is realized, and is requested before due to the occurrence of a failure, etc. If a response to the execution of the service is not returned, the service execution is requested again without considering whether there is a non-idempotent service among the corresponding lower services. Therefore, it is possible to simplify the configuration of the service processing system configured to include the service processing apparatus according to the present invention. In addition, when executing a subordinate service having idempotency, confirmation of the processing result of the subordinate service is omitted, so that the load on the computer that implements the service processing apparatus can be reduced.

  As described above, the service processing apparatus according to the first aspect of the present invention can easily guarantee data consistency when a failure occurs by providing the first to third functions described above. be able to. Further, when the invention according to claim 1 is applied to the individual service processing devices constituting the service processing system, the basic configuration of the individual service processing devices constituting the service processing system can be made the same. The system can have a simple configuration, and the man-hours required for design and development can be greatly reduced. Therefore, according to the first aspect of the present invention, it is possible to easily realize data consistency when a failure occurs with a simple configuration.

The service processing device according to the second aspect of the present invention is a service processing device that is realized by a computer and constitutes a service processing system together with another service processing device capable of transmitting and receiving information, and the service ID is notified and the service processing device Service execution means for performing processing related to the requested service when execution is requested, and processing result management means provided with storage means for storing the processing result of the service in association with the service ID. The service execution unit includes a service reception unit when there is a higher-level service processing device than the own device, and the service reception unit receives a service request to which a service ID is added from the higher-level service processing device. When execution of a service is requested, processing related to the requested service is performed. The processing result of the process is associated with the service ID and stored in the storage unit of the processing result management unit, and then a response is transmitted to the higher-level service processing device by the service receiving unit. A service ID generating unit that generates a service ID having uniqueness and a service calling unit when a lower-level service processing device exists, and the service requested to be executed is a lower-level service by the lower-level service processing device When the service is a service including the service request, the service ID generation unit generates a service ID of the lower service as a process related to the service requested to be executed, and a service request to which the generated service ID of the lower service is added. Transmitted by the service calling means to the lower-level service processing device, A process in which the service call means stores the processing result of the lower service notified by the response received from the lower service processing apparatus in the storage means of the processing result management means in association with the service ID of the lower service. A service processing device that performs a lower service having idempotency exists lower than the own device, and a lower service having the idempotency exists in a lower service corresponding to the service requested to be executed If the service call means sends a service request to the service processing apparatus that performs the lower service having the idempotency without confirming the processing result of the lower service having the idempotency with the process result management means. A service processing device that transmits and performs non-ideal subordinate services that do not have idempotency exists lower than its own device, And, if there is a subordinate service such as the non-defective in the subordinate service corresponding to the service requested to be executed, the processing result management means confirms the processing result of the subordinate subordinate service, When the confirmed processing result is “unknown” indicating that the response to the service request has not been received, the processing result management means transmits the processing result confirmation request to the service processing device that performs the non-defective lower level service. The service call means sends the service request to the service processing device that performs the non-defective lower-level service only when the processing result is confirmed again and “processing not yet completed” is obtained as the processing result. After that, a process for reconfirming the processing result of the non-defective lower level service with the processing result management means is performed. The response transmitted in accordance with the processing result of the check to the sender of the upper service processing device of the service requested by said processing result management means, when the upper service processing device than the device itself there is a processing result confirmation And a processing result confirmation request to which the service ID is added is received by the processing result confirmation unit from the higher-level service processing device, so that confirmation of the processing result is requested. The processing result of the service is confirmed based on the service ID, and when the confirmation of the processing result is completed, the confirmed processing result is notified to the upper service processing device by the processing result confirmation means, If there is a service processing device, a result confirmation calling means is provided, and the processing result of the lower service by the lower service processing device is confirmed. If necessary, a processing result confirmation request to which the service ID of the lower-level service to be confirmed is added is transmitted by the result confirmation calling unit to the lower-level service processing unit, and the lower-level service processing unit to the result confirmation calling unit. The notified processing result of the lower service is stored in the storage means in association with the service ID of the lower service.

  The service processing apparatus according to the second aspect of the present invention is realized by a computer and constitutes a service processing system together with another service processing apparatus capable of transmitting and receiving information, as in the first aspect of the present invention. A service processing apparatus according to a second aspect of the present invention includes the service execution unit and the processing result management unit.

  With the above configuration, when the service processing apparatus according to the second aspect of the present invention is requested to execute the service, the service execution unit performs processing related to the requested service. In addition, when there is a service processing device lower than the own device and the service requested to be executed is a service including a lower service by the lower service processing device, service ID generation is performed as processing related to the service requested to be executed. The service request of the lower service is generated by the means, the service request with the service ID of the generated lower service added is transmitted to the lower service processing apparatus by the service calling means, and the service calling means is received from the lower service processing apparatus. The processing result of the lower service notified by the response is stored in the storage means of the processing result management means in association with the service ID of the lower service. Thus, when the invention according to claim 2 is applied to each service processing apparatus constituting the service processing system (when each service processing apparatus is configured by the service processing apparatus according to the invention according to claim 2), In each service processing device that has received a service request from the service processing device, the service execution unit repeats the above processing in response to the received service request, thereby connecting the service processing devices. Regardless of the number, etc., execution of services is automatically chained as necessary.

  In addition, when there is a higher-level service processing device than the own device, the service execution unit receives the service request to which the service ID is added from the higher-level service processing device, and the service execution unit requests the service to be executed. The processing result of the processing is associated with the service ID and stored in the storage unit of the processing result management unit, and then a response is transmitted to the higher-level service processing device by the service reception unit. Thus, when the invention according to claim 2 is applied to each service processing apparatus constituting the service processing system (when each service processing apparatus is configured with the service processing apparatus according to the invention according to claim 2), In each service processing device that receives a response from the service processing device, the above processing is performed by the service execution unit, and the response is repeatedly transmitted to the higher-level service processing device, so that the number of service processing devices connected, etc. Regardless, responses to service requests are automatically chained.

  Further, the service processing apparatus according to the second aspect of the invention includes a processing result management unit including a storage unit for storing a service processing result in association with a service ID. When there is a higher-level service processing device than the own device, the processing result confirmation means receives the processing result confirmation request with the service ID added from the higher-level service processing device, so that confirmation of the processing result of the service is requested. Then, the processing result of the service for which the confirmation of the processing result is requested is confirmed based on the service ID. If there is a lower-level service processing device than the own device and it is necessary to check the processing result of the lower-level service by the lower-level service processing device, the processing result management means adds the service ID of the lower-level service to be checked The processed result confirmation request is transmitted to the lower-level service processing device by the result confirmation calling means. Thus, when the invention according to claim 2 is applied to each service processing apparatus constituting the service processing system (when each service processing apparatus is configured by the service processing apparatus according to the invention according to claim 2), In each service processing device that has received the processing result confirmation request from the service processing device at the processing result confirmation unit, the processing result management unit repeatedly performs the above processing in response to the received processing result confirmation request. Regardless of the number of service processing devices connected or the like, processing result confirmation requests are automatically chained as necessary.

  If there is a lower-level service processing device than the own device, the processing result management means associates the processing result of the lower service notified from the lower-level service processing device to the result confirmation calling means with the service ID of the lower service. And store it in the storage means. When there is a higher-level service processing device than the own device, the processing result management means notifies the higher-level service processing device of the confirmed processing result by the processing result confirmation means when the confirmation of the processing result is completed. Thus, when the invention according to claim 2 is applied to each service processing apparatus constituting the service processing system (when each service processing apparatus is configured with the service processing apparatus according to the invention according to claim 2), In each service processing device in which the processing result of the lower service is notified from the service processing device to the result confirmation calling unit, the processing result management unit repeats the above processing, so that the number of connected service processing devices, etc. Regardless of the situation, the processing result notification is automatically chained, and if the response to the previous service request has not been returned due to the occurrence of a failure, the processing result of the service that has previously requested execution is It becomes possible to confirm.

Further, in the invention according to claim 2, the transmission of the service request to the lower-level service processing device is more specifically, the service processing device that performs the lower-level service having idempotency exists lower than the own device, and If there is a subordinate service having idempotency among the subordinate services corresponding to the service requested to be executed, the processing result management means does not check the processing result of the subordinate service having idempotency. A service processing device that performs a non-ideal subordinate service that does not have idempotency is transmitted to a service processing device that performs a subordinate service having equality by sending a service request by a service calling unit. If there is a non-idempotent subservice among the subservices corresponding to the service requested to be executed, Check the processing result in the processing result management unit, in the case of "unknown" indicating that confirmation processing result has not been received in response to the service request, the subservice of the non-idempotent the processing result management unit the confirmation of the processing result is attempted again by to transmit the processing result confirmation request to the service processing unit, only when the "processing unfinished" is obtained as the processing result, the service to the service processing apparatus for subservice non idempotent After the service request is transmitted by the calling unit, the processing result management unit is checked again with the processing result of the non-defective lower level service, and when the processing is completed, the service receiving unit A response corresponding to the confirmed processing result is transmitted to the higher-level service processing device.

  As a result, when the invention according to claim 2 is applied to each service processing apparatus constituting the service processing system, a function such as a virtual function is realized, and a response to the execution of the previously requested service is returned due to the occurrence of a failure or the like. In such a case, it is possible to request the execution of the service again without considering whether there is a service that does not have idempotency among the corresponding lower level services. It is possible to simplify the configuration of a service processing system including the service processing apparatus according to the invention. In addition, when executing a subordinate service having idempotency, confirmation of the processing result of the subordinate service is omitted, so that the load on the computer that implements the service processing apparatus can be reduced.

  Thus, since the service processing apparatus system according to the second aspect of the present invention includes the service execution unit and the processing result management unit, it is easy to guarantee data consistency when a failure occurs. be able to. Further, when the invention according to claim 2 is applied to the individual service processing devices constituting the service processing system, the basic configuration of the individual service processing devices constituting the service processing system can be made the same. The system can have a simple configuration, and the man-hours required for design and development can be greatly reduced. Therefore, according to the second aspect of the invention, it is possible to easily realize data consistency when a failure occurs with a simple configuration.

  In the invention described in claim 2, the service execution means includes a service processing device of a higher level and a service processing device of a lower level than the own device, as described in claim 3, for example. If the service requested to be executed when the means receives a service request from the higher-level service processing apparatus is a service for which a corresponding lower-level service exists, the service ID of the lower-level service generated by the service ID generation means The service request to which the service call unit is added is transmitted to the lower-level service processing device by the service calling unit, and after the service calling unit receives a response from the lower-level service processing device, the service reception unit transmits the response to the higher-level service processing device. It can be constituted as follows.

  Further, in the invention described in claim 2 or claim 3, the service execution means is requested to execute when the service requested to be executed is a service including its own service as described in claim 4, for example. As the processing related to the service, the processing of the own service can be performed, and the processing result of the own service can be associated with the notified service ID and stored in the storage unit of the processing result management unit.

  Further, in the invention according to any one of claims 2 to 4, the service execution means, when there are a plurality of service processing devices lower than the own device, as described in claim 5, for example, The number of means is the same as the number of lower-level service processing devices, and there are a plurality of lower-level service processing devices, and the service requested to be executed includes a plurality of lower-level services by the lower-level service processing devices When the service is a service, the service ID generation unit generates a service ID of a specific lower service by a specific lower service device among a plurality of lower service processing devices as a process related to the requested service. A service request to which the service ID of the specified lower service is added is sent to a specific service corresponding to a specific lower service device. The processing result of the specific lower service notified by the response received by the specific service calling means from the specific lower service processing apparatus is transmitted to the specific lower service processing apparatus by the service calling means. The processing associated with the service ID and stored in the storage means of the processing result management means is performed for each of a plurality of lower-level service processing devices (may be performed sequentially or in parallel). Can be configured. As a result, even when there are a plurality of service processing devices below a single service processing device, service execution is automatically chained to each of the plurality of lower-level service processing devices. Can do.

  Further, in the invention according to claim 5, the service execution means, as described in claim 6, for example, receives the processing result of the lower service notified by a response from any of the plurality of lower service processing devices. If there is an error, if there is a lower-level service processing device whose requested lower-level service is “processed” among a plurality of lower-level service processing devices, the service call corresponding to the lower-level service processing device It is preferable that the service request for canceling the “processed” lower service is transmitted to the lower service processing apparatus whose lower service is “processed” by the means. If the service requested to be executed is a service including a plurality of lower-level services by a plurality of lower-level service processing devices, there is a possibility that a problem such as data inconsistency may occur unless all the lower-level services are processed normally. . On the other hand, in the invention described in claim 6, since the service request for canceling the “processed” lower service is transmitted to the corresponding lower service processing apparatus, the execution of the service including a plurality of lower services is requested. Thus, when an error occurs in some of the plurality of lower services, it is possible to automatically prevent problems such as data inconsistencies.

  Further, in the invention according to claim 5, the service execution means, as described in claim 7, for example, receives the processing result of the lower service notified by a response from any of the plurality of lower service processing devices. In the case of an error, if there is a lower-level service processing device that has not yet transmitted a service request among a plurality of lower-level service processing devices, the service request by the service calling unit corresponding to the lower-level service processing device You may comprise so that transmission may be stopped. As a result, when a service including a plurality of lower services is requested to be executed and an error occurs in some of the plurality of lower services, a service request for requesting the execution of the lower services is wasted. Can be prevented.

  Further, in the invention according to any one of claims 2 to 7, there is a service processing apparatus lower than the own apparatus, and a program for causing a computer to function as the service processing apparatus operates on a BPEL platform. In this case, as described in claim 8, for example, the service execution means is generated each time the service ID is notified and the execution of the service is requested. It is realized by an instance that stores state information that represents and appropriately updates the state information according to a change in the progress state of the process, and each time the instance is newly generated, the newly generated instance Search for instances that have been created and have the same service ID, and the corresponding instance exists If copies the state information of the appropriate instance as the state information of the instance, it is preferably configured to perform processing in accordance with the copy condition information. As a result, in a configuration in which a program for causing a computer to function as a service processing apparatus operates on the BPEL platform, execution of a service that was previously requested is requested again, and the previous processing was stopped halfway In this case, starting this process from the continuation of the previous process can be realized by a simple process using the features of the platform of BPEL.

  Further, in the invention described in claim 2, the processing result management means includes, as described in claim 9, for example, a service processing device of a higher level and a service processing device of a lower level than the own device, respectively, and processing result confirmation When the means receives the processing result confirmation request from the higher-level service processing device, there is a lower service corresponding to the service for which the confirmation of the processing result is requested, and the corresponding lower service stored in the storage means When the processing result is “unknown”, a processing result confirmation request to which the service ID of the lower service is added is transmitted to the lower service processing device by the result confirmation calling device, and the processing result is transmitted from the lower service processing device to the result confirmation calling device. Is notified, the processing result of the service for which confirmation of the processing result is requested is passed to the higher-level service processing device by the processing result confirmation means. It can be configured to.

  Further, in the invention according to any one of claims 2 to 9, the service ID generation means, as described in claim 10, for example, a unique ID in which a different ID is set for each service processing device, and a service If there is no ID element generation means for generating an ID element including a request ID in which a different ID is set for each request and a higher-level service processing apparatus than the own apparatus, the ID element generated by the ID element generation means Service ID including the caller ID and the callee ID respectively set, and when there is a higher-level service processing device than the own device, the service added to the service request received from the higher-level service processing device The caller ID that sets the ID element set as the callee ID in the ID and the ID element generated by the ID element generation means are set. And ID element combining means for generating a service ID with the call destination ID, preferably is configured to include a.

  As a result, each ID element generated by the ID element generation means is ensured to be unique in units of at least the service processing device (ID element generation means) (guaranteed that it does not overlap with other ID elements). And uniqueness in units of individual service requests in the service processing apparatus (ID element generating means). Further, when the invention according to claim 10 is applied to each service processing device constituting the service processing system, the service received from the higher-level service processing device in each service processing device in which the higher-level service processing device exists Since the callee ID in the service ID added to the request matches the caller ID in the service ID added to the service request transmitted to the lower-level service processing device, even when a failure or the like occurs The service ID stored in the storage means of the processing result management means of each service processing device is referred to, and the service ID (call ID added to the corresponding service request) whose call destination ID matches the call source ID. ) In order, it is possible to grasp the processing history of the service requested to be executed.

  Further, in the invention described in claim 10, the ID element combination means generates the ID generated by the ID element generation means when there is no service processing apparatus higher than the own apparatus as described in claim 11, for example. A service ID including the original ID in which the element is set is generated, and if there is a higher-level service processing device than the own device, the service ID added to the service request received from the higher-level service processing device is set as the original ID It is preferable that the service ID including the original ID in which the ID element is set is generated. Thus, when the invention according to claim 11 is applied to each service processing apparatus constituting the service processing system, the service ID added to the corresponding service request has the same original ID. Based on whether or not the original IDs of the service IDs added to the individual service requests are the same, the corresponding service request can be identified, and as described above, the caller ID and callee ID of the service ID Even when it is difficult to follow the same service request based on the set ID element, the processing history of the requested service can be reliably grasped by referring to the original ID. .

  Further, in the invention according to claim 10 or claim 11, the ID element generation means is an execution unit assigned to an execution unit of a program for causing a computer to function as a service processing device as described in claim 12, for example. Preferably, an ID element including an ID is generated. Note that the execution unit may be any process, task, thread, or the like. Thereby, even when there are a plurality of the above execution units in a single computer, the service ID (at least the execution unit ID) added to the service request by each execution unit (service processing apparatus) is different. By referring to the execution unit ID of the service ID added to the service request, the corresponding service request is processed by any execution unit (service processing apparatus) of the plurality of service processing apparatuses. It is possible to judge whether

  Further, the service processing system according to the invention described in claim 13 is configured by providing a plurality of service processing devices according to any one of claims 1 to 12 so as to be able to send and receive information. As in the first aspect of the invention and the second aspect of the invention, it is possible to easily realize data consistency when a failure occurs with a simple configuration.

A service processing program according to a fourteenth aspect of the present invention is a service processing program for causing a computer to function as a service processing device that constitutes a service processing system together with other service processing devices capable of transmitting and receiving information, When the service ID is notified and the execution of the service is requested, a service execution unit that performs processing related to the requested service and a storage unit that stores the processing result of the service in association with the service ID are provided. Processing result management means, and the service execution means comprises service accepting means when there is a higher-order service processing apparatus than the own apparatus, and the service accepting means receives a service request to which a service ID is added. Service execution is requested by receiving from a higher-level service processing device. Then, a process related to the service requested to be executed is performed, and the processing result of the process is associated with the service ID and stored in the storage unit of the processing result management unit, and then the higher level is received by the service receiving unit. When a response is transmitted to the service processing apparatus of the apparatus, and there is a service processing apparatus lower than the own apparatus, the service processing apparatus includes service ID generation means for generating a unique service ID, and service call means. When the requested service is a service including a lower service by the lower service processing apparatus, the service ID generation unit generates a service ID of the lower service as a process related to the requested service, and generates the service ID A service request to which the service ID of the subordinate service added is added to the service call The processing result of the lower service notified by the response received from the lower service processing device by the service call means is associated with the service ID of the lower service and transmitted to the lower service processing device by the stage. A lower-level service corresponding to a service for which a service processing device that performs processing to be stored in the storage unit of the processing result management unit and performs a lower-level service having idempotency exists lower than the own device and is requested to be executed If there is a subordinate service having the idempotency in the network, the subordinate service having the idempotency is checked without confirming the processing result of the subordinate service having the idempotency with the processing result management means. A service request is transmitted to the service processing apparatus to be performed by the service calling means, and a non-ideal subordinate service having no idempotency If the service processing device that performs the service exists in a lower level than the own device, and the lower service such as the non-defective exists in the lower service corresponding to the service requested to be executed, the non-ideal The processing result management means confirms the processing result of the lower service to the processing result management means. If the confirmed processing result is “unknown” indicating that a response to the service request has not been received, the processing result management means performs the non-idempotency. confirmation of the processing result thereby transmitting the processing result confirmation request to the service processing unit which performs subservice was attempted again, only when the "processing unfinished" is obtained as the processing result, lower service of the non-idempotent after sending a service request by the service calling unit to the service processing apparatus for performing, to review the process result of the lower service of the non-idempotent in the processing result management unit It performs processing, and transmits a response to which the processing corresponding to the processing result of the check of the upper source of the service request to the service processing device by said service receiving means and ends, the processing result management means, than the local If there is a higher-level service processing device, the processing result confirmation means is provided, and the processing result confirmation means receives the processing result confirmation request to which the service ID is added from the higher-level service processing device. When the confirmation is requested, the processing result of the service for which the confirmation of the processing result is requested is confirmed based on the service ID, and when the confirmation of the processing result is completed, the confirmed processing result is processed by the processing result confirmation unit. The service processing device is notified, and if there is a lower-level service processing device than the own device, the service processing device is provided with a result confirmation calling means, When it is necessary to confirm the processing result of the lower service by the service processing device, a processing result confirmation request with the service ID of the lower service to be confirmed is transmitted to the lower service processing device by the result confirmation calling unit, The processing result of the lower service notified from the lower service processing device to the result confirmation calling unit is associated with the service ID of the lower service and stored in the storage unit.

  According to a fourteenth aspect of the present invention, there is provided a service processing program comprising: a computer constituting a service processing system together with another service processing apparatus capable of transmitting and receiving information as a service processing apparatus including the service execution means and the processing result management means. Since it is a program for functioning, when the computer executes the service processing program according to the invention described in claim 14, the computer functions as the service processing apparatus described in claim 2. As with the invention described in Item 2, it is possible to easily realize data consistency when a failure occurs with a simple configuration.

  A service processing program according to a fifteenth aspect of the present invention is a service processing program for causing a computer to function as a service processing device that constitutes a service processing system together with another service processing device capable of transmitting and receiving information, It makes it function as a service processing apparatus of any one of Claims 2-12.

  A service processing program according to a fifteenth aspect of the present invention provides a service processing apparatus according to any one of the second to twelfth aspects of the present invention, wherein a computer constituting a service processing system together with another service processing apparatus capable of transmitting and receiving information The service processing apparatus according to any one of claims 2 to 12, wherein the computer executes a service processing program according to the invention according to claim 15. As in the invention according to any one of claims 2 to 12, it is possible to easily realize data consistency when a failure occurs with a simple configuration. .

According to a sixteenth aspect of the present invention, there is provided a recording medium on which a service processing program for causing a computer to function as a service processing apparatus constituting a service processing system together with other service processing apparatuses capable of transmitting and receiving information is recorded. When the service processing program requests the computer to execute a service by receiving a service request to which a service ID is added, the service processing program sets the service requested to be executed as a process related to the requested service. If there is a corresponding self service, the self service is processed, the processing result of the self service is stored in the storage unit in association with the service ID, and a lower service corresponding to the service requested to be executed If it exists, the service ID of the lower service is generated and generated. A service request to which a service ID is added is transmitted to a lower-level service processing apparatus, and the processing result of the lower-level service is stored in the storage means in association with the generated service ID, and the service request is transmitted to the source of the service request When a service result confirmation request is received by receiving a processing result confirmation request to which a service ID is added, a first function for transmitting a response, and a processing result is obtained based on the information stored in the storage means. If it is necessary to check the processing result of the service corresponding to the service for which the confirmation of the service is requested and the confirmation of the processing result of the corresponding lower service is necessary, the processing result confirmation request with the service ID of the corresponding lower service is added to the lower A second function that transmits to the service processing apparatus and transmits the confirmed processing result to the transmission source of the processing result confirmation request when the confirmation of the processing result is completed; and By receiving a service request to which the same service ID as the previously received service request is added, when a re-execution of a previously requested service is requested, it corresponds to the service requested to be re-executed. Among the one or more services, for the subordinate service having idempotency, the service processing apparatus that performs the subordinate service having idempotency without checking the processing result of the subordinate service having idempotency For non-ideal subservices that send a request and do not have idempotency, check the processing result of the non-ideal subordinate service, and confirm that the response to the service request is not received. In the case of “unknown” to represent, the processing result confirmation request is transmitted to the service processing apparatus that performs the non-defective lower-level service, and the confirmation of the processing result is retried, A process of confirming the processing result of the non-defaming subordinate service again after transmitting a service request to the service processing apparatus that performs the non-defying subordinate service only when “processing incomplete” is obtained as the processing result When the processing is completed, the service processing apparatus is provided with a third function for transmitting a response according to the processing result confirmed to the transmission source of the service request.

  According to a sixteenth aspect of the present invention, there is provided a recording medium for causing a computer constituting a service processing system together with another service processing apparatus capable of transmitting and receiving information to function as the service processing apparatus having the first to third functions. Since the service processing program is recorded, the computer reads out and executes the service processing program recorded on the recording medium according to the invention of claim 16 so that the computer reads the service processing program of claim 1. It functions as a processing device, and as in the first aspect of the invention, it is possible to easily ensure data consistency when a failure occurs with a simple configuration.

  The service processing program according to claim 14 or 15 is recorded on a recording medium according to the invention of claim 17. Thus, the computer constituting the service processing system together with another service processing apparatus capable of transmitting and receiving information reads out and executes the service processing program recorded in the recording medium according to the invention of claim 17, whereby the computer Will function as the service processing device according to any one of claims 2 to 12, and, similarly to the invention according to any one of claims 2 to 12, with a simple configuration, It is possible to easily realize data consistency when a failure occurs.

  As described above, according to the present invention, the first function for realizing the service execution chain, the service that has been requested to be executed before, in the service processing apparatus that constitutes the service processing system together with other service processing apparatuses capable of transmitting and receiving information. A second function that makes it possible to confirm the processing result of the second, and a third function that makes it possible to request the execution of the service again without considering the existence of a service having no idempotency when a failure or the like occurs. Since each of them is provided, it has an excellent effect that it is possible to easily realize data consistency when a failure occurs with a simple configuration.

The present invention also relates to a process related to a service requested to be executed when a service ID is notified to a service processing apparatus constituting a service processing system together with another service processing apparatus capable of transmitting and receiving information and execution of the service is requested. Service execution means, and a processing result management means having storage means for storing the service processing result in association with the service ID, and there is a service processing apparatus higher than the own apparatus. If there is a higher-level service processing device than the own device, the service reception means receives the service request from the higher-level service processing device, and the execution of the service is requested. After receiving the processing related to the service and storing the processing result in the storage means in association with the service ID, the service reception means Therefore, when a response is transmitted to the higher-level service processing device, there is a lower-level service processing device than the own device, and execution of a service including the lower-level service is requested by the lower-level service processing device, the service ID generation unit A service request to which the service ID of the lower-level service is generated and the generated service ID is added is transmitted to the lower-level service processing device by the service calling unit, and the service calling unit is notified by a response received from the lower-level service processing unit. The service processing apparatus that performs the process of storing the processing result of the lower service in association with the service ID of the lower service in the storage unit of the processing result management unit and that performs the lower service having idempotency than the own apparatus. Subordinate service corresponding to the service that exists in the lower level and requested to be executed When there is a subordinate service having idempotency, the service processing apparatus that performs the subordinate service having idempotency without confirming the processing result of the subordinate service having idempotency with the processing result management means A service processing device that transmits a service request by the service calling means and performs a non-idemless lower-level service that does not have idempotency exists lower than its own device, and the lower-level service corresponding to the service requested to be executed If there is a non-ideal subordinate service, confirm the processing result of the non-ideal subordinate service with the processing result management means, and confirm that the response to the service request is not received. In the case of “Unknown”, the processing result management means sends the processing result confirmation request to the service processing apparatus that performs the non-defective subordinate service by the processing result management means to confirm the processing result again. Was attempted, as the processing result only when the "processing unfinished" is obtained, after transmitting the service request by service calling means to the service processing apparatus for subservice non idempotent, processing subservice non idempotent A process is performed so that a result is confirmed again with the processing result management means, and when the processing is completed, a response according to the confirmed processing result is transmitted to the higher-level service processing device that is the transmission source of the service request by the service reception means. In addition, when there is a service processing apparatus higher than the own apparatus, the processing result confirmation means receives the processing result confirmation request with the service ID added from the upper service processing apparatus. When confirmation of the processing result of a service is requested, the processing result of the service for which confirmation of the processing result is requested is confirmed based on the service ID. When the confirmation of the processing result is completed, the processing result is notified to the upper service processing device by the processing result confirmation means, and there is a lower service processing device than the own device, and the processing result of the lower service by the lower service processing device When the confirmation of the result is necessary, a result confirmation request with the service ID of the lower service to be confirmed is transmitted to the lower service processing device by the result confirmation calling device, and the lower service processing device notifies the result confirmation calling device. Since the processing result of the lower service is stored in the storage means in association with the service ID of the lower service, it is easy to realize data consistency when a failure occurs with a simple configuration. It has an excellent effect of being able to.

It is a schematic block diagram which shows the hardware constitutions of the service processing system which concerns on this embodiment. It is explanatory drawing explaining a SOA reference model. It is a conceptual diagram explaining the processing sequence of the service processing part at the time of service request reception. It is a conceptual diagram explaining the process sequence of the service process part at the time of a process result confirmation request | requirement reception. It is a functional block diagram which shows the software structure of the service processing system which concerns on this embodiment. It is a flowchart which shows a service reception part process. It is a flowchart which shows an example of a process execution part process (an ignorance call, no compensation). It is a flowchart which shows an example of a process execution part process (calling idempotency, no compensation, internal retry). It is a flow chart which shows an example of processing execution part processing (calling idempotent, with compensation). It is a flowchart which shows an example of a process execution part process (an unequal call, with compensation, an internal retry). It is a flowchart which shows a service ID production | generation part process. It is a flowchart which shows a service call part process. It is a flowchart which shows a process result confirmation part process. It is a flowchart which shows a management part process. It is a flowchart which shows a result confirmation calling part process. It is a conceptual diagram which shows an example of the system and transition of service ID. It is explanatory drawing for demonstrating the effectiveness of OSID in service ID. It is explanatory drawing explaining implementation | achievement of functions, such as a virtual bag, in BPEL. It is a sequence diagram which shows an example of the sequence of the whole service processing system when execution of a service is instruct | indicated. It is a sequence diagram which shows the other example of the sequence of the whole service processing system when execution of a service is instruct | indicated. It is a sequence diagram which shows the other example of the sequence of the whole service processing system when execution of a service is instruct | indicated. It is a sequence diagram which shows an example of the sequence of the whole service processing system when execution of a service is instruct | indicated in multiple times. It is a sequence diagram which shows an example of the sequence of the whole service processing system when confirmation of a process result is instruct | indicated.

  Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 shows a service processing system 10 according to the present embodiment. The service processing system 10 is configured by connecting a plurality of service processing servers 12 and a plurality of application servers 14 via a computer network 16.

  Each application server 14 includes a CPU 14A, a memory 14B composed of ROM, RAM, etc., a storage unit 14C composed of HDD (Hard Disk Drive), etc., and a network I / F (interface) unit 14D. It is connected to the computer network 16 via the F unit 14D. Each application server 14 is a computer constituting a part of another existing computer system (in addition, as another existing computer system, for example, a core system of a financial institution (a deposit system or other In the storage unit 14C of each application server 14, different application programs for providing a predetermined service for another existing computer system are installed.

  On the other hand, each service processing server 12 includes a CPU 12A, a memory 12B composed of ROM, RAM, etc., a storage unit 12C composed of an HDD, etc., and a network I / F (interface) unit 12D, and a network I / F unit 12D. To the computer network 16. In addition, a service processing program is installed in the storage unit 12C, and a processing status table (described later) is also stored. The service processing program corresponds to the program according to the present invention, and the service processing server 12 functions as a later-described service processing unit (service processing apparatus according to the present invention) when the CPU 12A executes the service processing program.

  In FIG. 1, it is possible to request the service processing server 12 functioning as the highest service processing unit among the plurality of service processing servers 12 to execute the service to the highest service processing unit. As an example of the device, a mode is shown in which a keyboard 18 on which an operator can input arbitrary information and a display 20 on which arbitrary information can be displayed are connected. In this aspect, when the operator operates the keyboard 18, the operator requests execution of the service to the highest-level service processing unit, and the processing result of the service requested to be executed is displayed on the display 20 and visually recognized by the operator. The However, the present invention is not limited to the mode shown in FIG. 1, and the service processing server 12 functioning as the highest-level service processing unit is a device that requests the highest-level service processing unit to execute the service. May be connected. Examples of the device that requests execution of the service include a batch job controller, another computer system, the Internet, and a web server. In this aspect, execution of a service is directly requested from the device to the highest-level service processing unit without an operator's operation or the like, and the processing result of the service requested to be executed is transferred from the highest-level service processing unit to the device. Be notified directly.

  Next, the operation of this embodiment will be described. The service processing system 10 according to the present embodiment applies SOA, divides a service to be provided in units of functions, and has developed a function among the divided functions (in this embodiment, connected to the service processing system 10). The service provided by each individual application server 14 corresponds to that), and is constructed by using it, and the service processing server 12 (which is realized by the service processing unit) realizing different functions is sparse. A plurality of stages are connected by coupling, and each service request input to the service processing system 10 is configured to be processed in cooperation by a plurality of stages of service processing units. In addition, the service processing system 10 according to the present embodiment stores each service processing server 12 so that the service processing unit realized by each service processing server 12 conforms to the reference model shown in FIG. A service processing program to be installed in the section 12C has been developed.

  Hereinafter, the reference model of the service processing unit will be described first. In this reference model, the service processing unit includes functional blocks of a management unit 24, a process execution unit 26, a service reception unit 28, a service ID generation unit 30, a service call unit 32, a process result confirmation unit 34, and a result confirmation call unit 36. The functions that the service processing unit should have in order to ensure data consistency when a failure or the like occurs in the service processing system 10 by defining the function for each functional block. It prescribes.

  In the reference model of the service processing unit, the management unit 24 stores a processing status table 38 (here, the storage unit is a management unit for storing the processing status table 38 and the like in the storage area of the storage unit 12C). 24), and the processing result of the service requested to be executed by the service processing unit (the corresponding self service and lower service) is associated with the service ID for identifying the service. And a function for requesting the result confirmation calling unit 36 to confirm the processing result of the lower service when it is necessary to confirm the processing result of the lower service. In addition, when the service ID is notified and the execution of the service is requested, the process execution unit 26 executes the process of the own service if there is a self service corresponding to the requested service, and the corresponding lower service is If there is a service ID, the service ID generation unit 30 generates a service ID and requests the service call unit 32 to execute a lower service.

  In addition, the service reception unit 28 is provided when a higher-level service processing unit exists, and when a service execution is requested by receiving a service request with a service ID added from the higher-level service processing unit, It has a function of requesting the process execution unit 26 to execute the service requested to be executed, and transmitting a response to the upper service process unit after the process is completed. The service ID generation unit 30 is provided when a lower-level service processing unit exists, and has a function of generating a unique service ID in response to a request from the processing execution unit 26. Further, when there are subordinate service processing units, the same number of service calling units 32 as the subordinate service processing units are provided, and a service request with the service ID of the subordinate service added in response to a request from the processing execution unit 26 Is transmitted to the lower-level service processing unit.

  The processing result confirmation unit 34 is provided when a higher-level service processing unit exists, and receives a processing result confirmation request to which a service ID is added from the higher-level service processing unit, thereby confirming the processing result of the service. Is requested, the processing result of the service for which the confirmation of the processing result is requested is confirmed with the management unit 24 using the service ID, and when the confirmation of the processing result is completed, the confirmed processing result is notified to the higher-level service processing unit. It has a function to do. Further, the result confirmation calling unit 36 is provided in the same number as the lower-level service processing units when the lower-level service processing unit exists, and confirms the processing result by adding the service ID of the lower-level service to be confirmed when requested. It has a function of transmitting a request to a lower-level service processing unit.

  Next, each functional block of the service processing unit (the management unit 24, the process execution unit 26, the service reception unit 28, the service ID generation unit 30, the service call unit 32, the process result check unit 34, and the result check call unit 36) is described above. A typical processing sequence in the service processing unit that is realized by providing the above functions will be described.

  When the service processing unit in which the higher-level service processing unit exists receives a service request from the higher-level service processing unit, the processing sequence shown in FIG. Processing is performed. That is, when a service request with a service ID added is received from a higher-level service processing unit (see (1)), the service reception unit 28 notifies the service execution unit 26 of the service ID and requests execution of the service. (Refer to (2)). The process execution unit 26 confirms the process result of the service requested to be executed with the management unit 24 (see (3)). If the confirmed processing result is “processed”, a response is immediately returned to the service reception unit 28 (see (12)), but the confirmed processing result is “unfinished” and corresponds to the service requested to be executed. If there is a service to be processed, the process of the service is executed, and the processing result is associated with the service ID and recorded in the processing status table 38 (see (4)).

  If there is a lower service corresponding to the service requested to be executed and the lower service is not “processed”, the process execution unit 26 causes the service ID generation unit 30 to generate the service ID of the lower service. (See (5)), and record the service ID of the generated lower-level service in the processing status table 38 (see (6)). The service call unit 32 is notified of the service ID of the lower service and the execution of the lower service is requested (see (7)). As a result, the service calling unit 32 transmits a service request to which the service ID of the notified lower service is added to the lower service processing unit (see (8)). When a response is received from the lower-level service processing unit (see (9)), the processing result of the lower-level service notified by the received response is recorded in the processing status table 38 (see (10)), and the processing end is processed. The execution unit 26 is notified (see (11)). In response to this, the process execution unit 26 notifies the service reception unit 28 of the processing result (see (12)), and the service reception unit 28 notifies the processing result by transmitting a response to the higher-level service processing unit (( 13)).

  Further, when a service processing unit in which a higher-level service processing unit exists receives a processing result confirmation request from the higher-level service processing unit, in the service processing unit that has received the service request, the functional blocks are linked to each other in FIG. Processing is performed in the processing sequence shown in FIG. That is, when a processing result confirmation request is received from a higher-level service processing unit (see (1)), the processing result confirmation unit 34 receives each service corresponding to the service for which confirmation of the processing result is requested by the received processing result confirmation request. The processing result is confirmed with the management unit 24 (see (2)). If there is no lower service whose processing result is `` unknown '' in each corresponding service, a response is immediately returned to the upper service processing unit (see (8)), but there is a lower service whose processing result is `` unknown '' If so, the corresponding result confirmation calling unit 36 is requested to confirm the processing result of the lower service (see (3)).

  When the confirmation of the processing result of the lower service is requested, the result confirmation calling unit 36 transmits a processing result confirmation request to the lower service processing unit (see (4)). Further, when a response notifying the processing result of the lower service is received from the lower service processing unit (see (5)), the processing result of the notified lower service is recorded in the processing status table 38 (see (6)), The processing result confirmed by the management unit 24 is notified to the processing result confirmation unit 34 (see (7)). In response to this, the processing result confirmation unit 34 transmits a response notifying the processing result including the processing result of the notified lower service to the upper service processing unit (see (8)).

  Next, an example of the software configuration of the service processing system 10 constructed in accordance with the reference model of the service processing unit will be described with reference to FIG. As shown in FIG. 5, in the service processing system 10 according to the present embodiment, five service processing units are divided into three layers (three levels), and three services in the third layer (third level). Each processing unit is connected to a single service processing unit on the second layer (second stage), and a single service processing unit on the second layer (second stage) is connected to a single first layer (first stage). Connected to the service processing unit.

  Since the service processing unit in the first layer (the highest level) does not have a higher-level service processing unit, the service reception unit 28 and the processing result confirmation unit 34 are omitted from the reference model of the service processing unit. In the following, the highest-level service processing unit is referred to as “requester 42” for convenience. When the keyboard 18 and the display 20 are connected to the service processing server 12 that functions as the requester 42, the requester 42 sends the service processing unit to a lower-level service processing unit in accordance with an instruction input by operating the keyboard 18 by the operator. A service request and a processing result confirmation request are transmitted, and a processing result and the like are displayed on the display 20 based on a response from a lower-level service processing unit. If a device (for example, a batch job controller, another computer system, the Internet, or a web server) that requests execution of a service is connected to the service processing server 12 that functions as the requester 42, the requester 42. To receive a request from the device, send a service request or a processing result confirmation request to a lower service processing unit in response to the received request, and send a processing result or the like based on a response from the lower service processing unit. The process of notifying is performed.

  In addition, since the service processing unit in the second layer has three lower-level service processing units, three sets of the service calling unit 32 and the result confirmation calling unit 36 are provided. In the present embodiment, the second-layer service processing unit program has been developed as a program that operates on a BPEL (Business Process Execution Language) platform called a BPEL engine. A predetermined program that functions as the platform is also installed in the storage unit 12C of the functioning service processing server 12. Hereinafter, the service processing unit in the second layer is referred to as “BPEL 44” for convenience. The BPEL 44 transmits a service request or a processing result confirmation request to a lower individual service processing unit according to the service request or processing result confirmation request received from the requester 42, or a process for guaranteeing data consistency when a failure occurs. I do.

  Further, in the third layer, as three service processing units, a service processing unit not connected to another existing computer system (application server 14 thereof) and a package as an existing another computer system are provided. There is a service processing unit connected to the system 66 (the application server 14) and a service processing unit connected to the storage system 68 (the application server 14) as another existing computer system. . Since these service processing units have no lower-level service processing units, the service calling unit 32 and the result confirmation calling unit 36 are omitted from the reference model of the service processing unit.

  Among the three service processing units in the third layer, the service processing unit that is not connected to the existing system is a service processing unit that realizes a certain service by the processing performed by the processing execution unit 26 alone. The service processing unit is referred to as “provider 46” for convenience.

  Of the three service processing units in the third layer, the service processing unit connected to the package system 66 (the application server 14 thereof) has a function for controlling the interface between the service processing system 10 and the package system 66. As a block, an ID conversion unit 52 that assigns a number unique to the package system 66 as an ID that replaces the service ID in the service processing system 10, and a package system 66 that includes a function of performing mutual conversion of data formats, respectively. A package call unit 54 and a result check call unit 56 are provided for executing services and checking processing results through communication. Hereinafter, the service processing unit is referred to as “package wrapper 48” for convenience.

  Of the three service processing units in the third layer, the service processing unit connected to the depository system 68 (the application server 14 thereof) has a function for controlling the interface between the service processing system 10 and the depository system 68. As a block, a terminal management unit 58 that assigns a terminal number that is an ID unique to the deposit system 68 as an ID that replaces the service ID in the service processing system 10 and a function that performs mutual conversion of data formats are provided. Therefore, an MB communication unit 60 and a transaction status inquiry unit 62 for executing a service by communicating with the system 68 and confirming the processing result (transaction status inquiry) are provided. Hereinafter, the service processing unit is referred to as “MB wrapper 50” for convenience.

  In this embodiment, for convenience of explanation, the service provided by the provider 46 among the provider 46, the package wrapper 48, and the MB wrapper 50, which are the third level service processing units of the service processing system 10, and the MB wrapper Services provided by 50 (and deposit system 68) are idempotent, while services provided by package wrapper 48 (and package system 66) are not idempotent. And Note that a service having idempotency is a service whose result is the same no matter how many times it is executed, such as a service that reads and outputs data stored in a certain area of a DB (database). A service that does not have idempotency (a service that is not idempotent) is a service whose result differs every time it is executed. For example, a numerical value stored in a certain area of the DB is incremented by 1 every time it is executed. Examples include services that output results.

  In FIG. 5, the service reception unit 28 is a service reception unit according to the present invention, the service ID generation unit 30 is a service ID generation unit according to the present invention, and the service call unit 32 is a service call unit according to the present invention. The process execution unit 26, the service reception unit 28, the service ID generation unit 30 and the service call unit 32 are the process execution unit according to the present invention, and the process result confirmation unit 34 is the process result confirmation unit according to the present invention. 36 corresponds to the result confirmation calling unit according to the present invention, and the management unit 24, the processing result confirmation unit 34, and the result confirmation calling unit 36 correspond to the processing result management unit according to the present invention. The BPEL 44, the provider 46, the package wrapper 48, and the MB wrapper 50 correspond to the “service processing apparatus having a higher-level service processing apparatus” according to the present invention, and the requester 42 and the BPEL 44 correspond to the “lower Corresponds to a service processing apparatus in which a service processing apparatus exists.

  Next, processing in each functional block of the service processing unit will be described with reference to the flowcharts of FIGS. The service processing unit in which the higher-level service processing unit exists receives a service request for requesting execution of the service and a processing result confirmation request for requesting confirmation of the processing result of the service that has requested execution. A service reception unit 28 is provided in the service processing unit in which the higher-level service processing unit exists, and the service reception unit 28 receives the service request shown in FIG. 6 when receiving a service request from the higher-level service processing unit. Process.

  In this service reception unit process, first, in step 80, a service request message is received from the upper service processing unit, and in the next step 82, status information indicating that the service request message has been received from the upper service processing unit. Then, the received message is stored in the processing status table 38 of the management unit 24. Note that the received message is attached with the service ID of the service requested to be executed, and the service ID is also stored in the processing status table 38 by the above processing. In the next step 84, the content of the received message is checked, and it is determined whether or not the content of the received message is appropriate. If the determination is negative, the process proceeds to step 86, an error message is set in the response message to be transmitted to the upper service processing unit, and the process proceeds to step 90.

  On the other hand, if the content of the received message is appropriate, the determination in step 84 is affirmed and the process proceeds to step 88, where the service ID added to the received message of the service request is used as an argument of the process execution unit 26. Call API and request execution of service. Thereby, the process execution unit 26 performs process execution unit processing (described later). When the process execution unit process by the process execution unit 26 is completed and the process result of the service requested to be executed is notified, the notified process result is set in a response message to be transmitted to the upper service process unit, and then the process proceeds to step 90. Transition. In step 90, the response message generated in step 86 or 88 is transmitted to the upper service processing unit. In step 92, status information indicating that the response message has been transmitted to the higher-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the transmitted response message, and the service reception unit process is terminated.

  Next, a process execution unit process performed by the process execution unit 26 when a service execution is requested will be described. The contents of the process execution unit process include the presence / absence of a higher-level service processing unit, the presence / absence and number of lower-level service processing units, the presence / absence of inequality of lower-level services by lower-level service processing units, and the execution of services. A call that uses a virtual idempotency function (a function that ensures that the same result is obtained no matter how many times the execution of the service is requested, regardless of whether the actual service has idempotency) Depending on the conditions such as whether or not to perform a compensation process (to be described later), or a call that does not use the virtual idempotent function (hereinafter referred to as non-idempotent call) It is very different. For this reason, below, the typical process in the process execution part 26 of BPEL44 is demonstrated in order with reference to FIGS. 7-10 as an example of a process execution part process. Note that the process execution unit processes shown in FIGS. 7 to 10 all require that the provider 46, the package wrapper 48, and the MB wrapper 50 each execute a service that requires the execution of a lower level service. It is assumed. The idempotency flag (FLG) is also passed to the process execution unit 26 as an argument when the process execution unit 26 is called, and the idempotency call and the unequal call are distinguished depending on whether the value of the idempotency flag is 1 or 0. .

  The process execution unit process shown in FIG. 7 is a process execution unit process under the condition that the execution of the service is requested by the idempotent call to the process execution unit 26 of the BPEL 44 and the compensation process is not performed by the process execution unit 26. It is an example. In the aspect shown in FIG. 7, the program of the process execution unit 26 is divided into a process execution unit API and a business program. The process execution unit API is a program that performs a standard process among the processes for realizing the functions of the process execution unit 26. In the example of FIG. 7, the lower-level service processing units (in this example, the provider 46, the package wrapper 48, and the Response time-out monitoring from the MB wrapper 50 (monitoring whether a response unreceived state has continued for a specified time or more after sending a service request), retrying a service request to a lower service processing unit (for example, processing) Process execution unit, such as resending service requests when the result is `` unknown '', etc.), monitoring the number of retries (processing as `` abnormal '' when the number of transmissions of service requests etc. reaches the specified number) Performed by API.

  As described above, by dividing the program of the process execution unit into the process execution unit API and the business program, the process execution unit API is converted into a component, and the process execution unit 26 having different processing contents of the business program is developed. By diverting the componentized processing execution unit API, the program developer can concentrate on the development of the business program, so that the burden on the program developer can be reduced and the time required for the program development can be reduced.

  In FIG. 7, a process realized by a business program among the programs of the process execution unit 26 (hereinafter, this process is simply referred to as a process execution unit process) is activated by being called from outside via the process execution unit API. . In the idempotent call using the virtual niece function and the like, there is a possibility that the execution of the service with the same service ID may be repeatedly requested. The management unit 24 is inquired about the processing result (situation) when the previous execution of the service with the notified service ID is requested. In the next step 202, based on the information notified from the management unit 24, it is determined whether or not the process when the execution of the service with the same service ID was previously requested is “processing”. Control is returned to the process execution unit API.

  Also, if the process when the execution of the service with the same service ID was requested last time is not “processing” (if the execution of the service with the service ID passed as an argument has not been requested in the past, If the processing when the execution of the ID service is requested last time is complete (this condition is met), the process proceeds to step 204. Since the subordinate service 1 has idempotency, in step 204, regardless of the processing status of the subordinate service 1, the subordinate service 1 has been designated as a subordinate service corresponding to the service with the service ID delivered as the argument this time. The lower service 1 (in this case, regardless of whether the lower service 1 has been executed in the past as a lower service corresponding to the service with the service ID delivered as an argument) The service calling unit 32 corresponding to the lower service 1 is instructed to execute the lower service by the provider 46. As a result, the service calling unit 32 corresponding to the lower service 1 performs service calling unit processing (described later), and a service request is transmitted to the provider 46.

  If the execution of the service with the service ID delivered as an argument has not been requested in the past, the service ID generated as an argument is notified to the service ID generation unit 30 prior to the instruction to the service calling unit 32. The processing status table 38 requests the generation of the service ID of the lower service 1 and associates the service ID of the lower service 1 generated by the service ID generation unit 30 with the service ID delivered as an argument through the management unit 24. Is also stored, and the service calling unit 32 is notified of the service ID of the lower-level service 1. If execution of a service with the same service ID has been requested in the past, the service ID of the lower service 1 corresponding to the information notified from the management unit 24 is extracted prior to the instruction to the service calling unit 32. The process of notifying the extracted service ID to the service calling unit 32 is also performed.

  Further, when the processing result is notified from the service calling unit 32 corresponding to the lower service 1, in the next step 206, the processing is branched according to the notified processing result. That is, when the notified processing result is “unknown” or “processing not yet completed”, the control is returned to the processing execution unit API. In this case, processing such as retry and monitoring of the number of retries is performed by the process execution unit API. Further, when the notified processing result is “business error”, the processing result is “business error” and is notified to the caller of the processing execution unit 26 through the processing execution unit API. In this case, transmission of a service request requesting execution of the lower services 2 and 3 is skipped.

  On the other hand, if the notified processing result is “processed”, the processing of the lower-level service 1 has been completed normally, and the process proceeds to step 210. Since the lower level service 2 (here, the lower level service by the package wrapper 48) does not have idempotency, first, in step 210, the service ID delivered as an argument is notified to the management unit 24, and the notified service ID is sent. The management unit 24 is inquired about the processing result (status) of the service. In the next step 212, based on the information notified from the management unit 24, the processing result when the lower-level service 2 has been executed in the past as a lower-level service corresponding to the service with the service ID delivered as an argument this time. And the process branches according to the determined processing result. If it is found in the previous steps 200 and 202 that the execution of the service with the service ID delivered as an argument has not been requested in the past, the execution of step 210 is skipped, and the processing result in step 212 is You may make it determine with "processing unfinished."

  The processing result determined in step 212 is “unknown” or “cannot be confirmed” (for example, the management unit 24 requests the result confirmation calling unit 36 to confirm the processing result of the lower service 2 but the communication link with the package wrapper 48. In the case where the process is not established, etc.), the control is returned to the process execution unit API. In this case, processing such as a retry (for confirming the processing result) and monitoring the number of retries is performed by the processing execution unit API. Further, when the determined processing result is “business error”, the caller of the processing execution unit 26 is notified through the processing execution unit API that the processing result is “business error”. In this case, transmission of a service request for requesting execution of the lower service 3 is skipped. If the determined processing result is “processed”, transmission of a service request for requesting execution of the lower service 2 is skipped, and the process proceeds to step 220.

  On the other hand, if the determined processing result is “processing not yet completed”, the process proceeds to step 214, and the service ID generated as an argument is first notified to the service ID generation unit 30 to request generation of the service ID of the lower service 2. The service ID of the lower service 2 generated by the service ID generation unit 30 is stored in the processing status table 38 in association with the service ID delivered as an argument through the management unit 24, and the service ID of the lower service 2 Is notified to the service calling unit 32 corresponding to the lower service 2 and the execution of the lower service 2 is instructed. As a result, the service calling unit 32 corresponding to the lower service 2 performs service calling unit processing (described later), and a service request is transmitted to the package wrapper 48.

  In addition, when the processing result is notified from the service calling unit 32 corresponding to the lower service 2, in the next step 216, the processing is branched according to the notified processing result. That is, when the notified processing result is “unknown” or “processing not yet completed”, the control is returned to the processing execution unit API. In this case, processing such as retry and monitoring of the number of retries is performed by the process execution unit API. Further, when the notified processing result is “business error”, the processing result is “business error” and is notified to the caller of the processing execution unit 26 through the processing execution unit API. In this case, transmission of a service request for requesting execution of the lower service 3 is skipped.

  On the other hand, if the notified processing result is “processed”, the processing of the lower-level service 2 is also completed normally, and the process proceeds to step 220. Since the lower service 3 has idempotency, the execution of the lower service 3 (here, the lower service by the MB wrapper 50) is executed in step 220 regardless of the processing status of the lower service 3 as in the previous step 204. To the service calling unit 32 corresponding to the lower service 3. As a result, the service calling unit 32 corresponding to the lower service 3 performs service calling unit processing (described later), and a service request is transmitted to the MB wrapper 50.

  If the execution of the service with the service ID delivered as an argument has not been requested in the past, the service ID generated as an argument is notified to the service ID generation unit 30 prior to the instruction to the service calling unit 32. The processing status table 38 requests the generation of the service ID of the lower service 3 and associates the service ID of the lower service 3 generated by the service ID generation unit 30 with the service ID delivered as an argument through the management unit 24. And the process of notifying the service calling unit 32 of the service ID of the lower service 3 is also performed. If execution of a service with the same service ID has been requested in the past, the service ID of the lower service 3 corresponding to the information notified from the management unit 24 is extracted prior to the instruction to the service calling unit 32. The process of notifying the extracted service ID to the service calling unit 32 is also performed.

  When the processing result is notified from the service calling unit 32 corresponding to the lower service 3, the process branches in the next step 222 according to the notified processing result. That is, when the notified processing result is “unknown” or “processing not yet completed”, the control is returned to the processing execution unit API. In this case, processing such as retry and monitoring of the number of retries is performed by the process execution unit API. Further, when the notified processing result is “business error”, the processing result is “business error” and is notified to the caller of the processing execution unit 26 through the processing execution unit API. On the other hand, if the notified processing result is “processed”, the processing of the lower-level service 3 is also completed normally, so that the processing result is “processed” through the process execution unit API. Notify the caller of the execution unit 26.

  Next, only the process execution unit process shown in FIG. 8 will be described, which is different from the process execution unit process shown in FIG. In the process execution unit process shown in FIG. 8, similar to the process execution unit process shown in FIG. 7, execution of a service is requested by an idempotent call to the process execution unit 26 of the BPEL 44, and the process execution unit 26 performs compensation processing. The processing execution shown in FIG. 7 corresponds to the condition that it is not performed, and the monitoring of the retry of the service request to the lower service processing unit and the number of retries is performed by the business program instead of the processing execution unit API. Part processing.

  That is, in the processing execution unit process shown in FIG. 8, in step 204, the service calling unit 32 corresponding to the lower service 1 is instructed to execute the lower service 1, and the service calling unit 32 corresponding to the lower service 1 is notified in step 206. If the processed result is “unknown” or “processing not yet completed”, it is determined in step 208 whether or not the number of times the service request has been transmitted to the provider 46 that performs the lower service 1 has reached a specified value. Then, it is determined whether or not to retransmit (retry) the service request to the provider 46. If the number of service request transmissions to the provider 46 is less than the prescribed value, the process returns to step 204, and the service call unit 32 corresponding to the lower service 1 is instructed to execute the lower service 1 again, whereby the service request is sent to the provider 46. Let it be resent. When the number of service request transmissions to the provider 46 reaches a specified value, the process execution unit API notifies the caller of the process execution unit 26 that the process result is “unknown” or “unprocessed”. . In this case, transmission of a service request requesting execution of the lower services 2 and 3 is skipped.

  In the process execution unit process shown in FIG. 8, the service process result (situation) is inquired to the management unit 24 in step 210, and the process result of the lower service 2 determined in step 212 is “unknown” or “cannot be confirmed”. If there is, and in step 214, the service calling unit 32 corresponding to the lower service 2 is instructed to execute the lower service 2, and the processing result notified from the service calling unit 32 corresponding to the lower service 2 in step 216 is “ If “unknown” or “unprocessed”, it is determined in step 218 whether the number of times the processing result of the lower service 2 has been confirmed or the number of times the service request has been transmitted to the package wrapper 48 has reached a specified value. By doing so, it is determined whether or not the above processing is performed again. Since the lower service 2 does not have idempotency, if the number of times the processing result of the lower service 2 is confirmed or the number of times the service request is transmitted to the package wrapper 48 is less than the specified value, the process returns to step 210, The processing after the processing result confirmation of 2 is performed again. If the number of times the processing result of the lower service 2 is confirmed or the number of times the service request is transmitted to the package wrapper 48 reaches a specified value, the processing result is “Unknown” or “Processing not completed”. Notification is made to the caller of the process execution unit 26 through the section API. In this case, transmission of a service request for requesting execution of the lower service 3 is skipped.

  In the process execution unit process shown in FIG. 8, the service call unit 32 corresponding to the lower service 3 is instructed to execute the lower service 3 in step 220, and the service call unit 32 corresponding to the lower service 3 is notified in step 222. If the processed result is “unknown” or “processing not completed”, it is determined in step 224 whether or not the number of times the service request has been transmitted to the MB wrapper 50 that performs the lower-level service 3 has reached a specified value. Thus, it is determined whether or not to retransmit (retry) the service request to the MB wrapper 50. If the number of service request transmissions to the MB wrapper 50 is less than the specified value, the process returns to step 220, and the service call unit 32 corresponding to the lower service 3 is instructed to execute the lower service 3 again, thereby providing the service to the MB wrapper 50. Causes the request to be resent. When the number of service request transmissions to the MB wrapper 50 reaches a specified value, the process execution unit API notifies the caller of the process execution unit 26 that the process result is “unknown” or “unprocessed”. To do.

  Next, only the processing execution unit processing shown in FIG. 9 that is different from the processing execution unit processing shown in FIG. 7 will be described. The process execution unit process shown in FIG. 9 corresponds to the condition that the execution of the service is requested by the idempotent call to the process execution unit 26 of the BPEL 44 and the process execution unit 26 performs the compensation process. Processing such as monitoring of response timeout from the service processing unit, retry of service requests to lower service processing units, and monitoring of the number of retries is performed by the processing execution unit API in the same manner as the processing execution unit processing shown in FIG. Is called.

  In the process execution unit process shown in FIG. 9, the service process result (situation) is inquired to the management unit 24 in step 210, and the process result of the lower service 2 determined in step 212 is “business error”; In step 214, the service calling unit 32 corresponding to the lower service 2 is instructed to execute the lower service 2. In step 216, the processing result notified from the service calling unit 32 corresponding to the lower service 2 is “business error”. If so, go to Step 230. In this case, among the lower services corresponding to the service with the service ID delivered as the argument this time, the processing result of the lower service 1 is “processed”, while the processing result of the lower service 2 is “business error”. Since the processing has not been completed, there is a contradiction in the data.

  Therefore, in step 230, in order to ensure data consistency, the service call unit 32 corresponding to the lower service 1 is notified of the same service ID as that in the previous step 204 as the service ID of the lower service 1. Instructs transmission of a service request for requesting execution of a process for canceling the process previously executed as the lower service 1 of the service ID. As a result, the service calling unit 32 corresponding to the lower service 1 performs service calling unit processing (described later), and the service request is transmitted to the provider 46. Then, the process of canceling the previously executed process is performed by the provider 46, so that if there is data updated by the previously executed process, the data is restored to the original data, and the inconsistency of the data is resolved ( Data consistency is ensured).

  Further, when the processing result is notified from the service calling unit 32 corresponding to the lower service 1, in the next step 232, the processing is branched according to the notified processing result. That is, when the notified processing result is “processed”, the processing result is “business error” and is notified to the calling source of the processing execution unit 26 through the processing execution unit API. When the notified processing result is “business error”, “processing not yet completed”, or “unknown”, the processing execution unit API notifies the caller of the processing execution unit 26 that the processing result is “cancellation failure”. . In this case, the process of resolving the data inconsistency and ensuring the consistency is performed by another process such as a batch process.

  In the process execution unit process shown in FIG. 9, the service call unit 32 corresponding to the lower service 3 is instructed to execute the lower service 3 in step 220, and the service call unit 32 corresponding to the lower service 3 is notified in step 222. If the processed result is “business error”, the process proceeds to step 226. In this case, among the lower services corresponding to the service with the service ID delivered as an argument this time, the processing results of the lower services 1 and 2 are “processed”, whereas the lower service 3 has the processing result “business error” Since the processing is not yet completed, there is a contradiction in the data.

  Therefore, in step 226, in order to ensure data consistency, the service call unit 32 corresponding to the lower service 2 is notified of the same service ID as in the previous step 214 as the service ID of the lower service 2. Instructs the transmission of a service request for requesting execution of a process for canceling the process previously executed as the lower service 2 of the service ID. As a result, the service calling unit 32 corresponding to the lower-level service 2 performs service calling unit processing (described later), and the service request is transmitted to the package wrapper 48. Then, the process for canceling the previously executed process is performed by the package wrapper 48, and if there is data updated by the previously executed process, the data is restored to the original data.

  Further, when the processing result is notified from the service calling unit 32 corresponding to the lower service 2, in the next step 228, the processing is branched according to the notified processing result. When the notified processing result is “business error”, “processing not yet completed”, or “unknown”, the calling result of the processing execution unit 26 is notified through the processing execution unit API that the processing result is “cancellation failure”. In this case, the process of resolving the data inconsistency and ensuring the consistency is performed by another process such as a batch process. If the notified processing result is “processed”, the process proceeds to step 230, and the above-described processing is performed in step 230, so that a service request for requesting execution of processing that cancels the previously executed processing is sent to the provider. 46 is also transmitted. Then, the process of canceling the previously executed process is also performed by the provider 46, and if there is data updated by the previously executed process, the data is restored to the original data, thereby eliminating the data inconsistency ( Data consistency is ensured).

  Subsequently, the processing execution unit process illustrated in FIG. 10 will be described only with respect to differences from the processing execution unit process illustrated in FIGS. 7 to 9. The process execution unit process shown in FIG. 10 corresponds to the condition that the process execution unit 26 of the BPEL 44 is requested to execute the service by an unequal call and the process execution unit 26 performs the compensation process. Further, in the process execution unit process shown in FIG. 10, similar to the process execution unit process shown in FIG. 7, processing such as a retry of a service request to a lower service processing unit and monitoring of the number of retries is performed by the business program. On the other hand, timeout monitoring is performed by the process execution unit API.

  In non-idempotent calls that do not use the virtual idempotency function, the execution of the service with the same service ID is not requested more than once, so steps 200 and 202 are omitted in the process execution unit process shown in FIG. First, in step 204, the service calling unit 32 corresponding to the lower service 1 is instructed to execute the lower service 1. Further, when the processing result notified from the service calling unit 32 corresponding to the lower service 1 in the next step 206 is “unknown” or “processing not yet completed”, as in the processing execution unit processing shown in FIG. In 208, it is determined whether or not to retransmit (retry) the service request to the provider 46. If the number of service request transmissions to the provider 46 is less than the prescribed value, the process returns to step 204, and the service call unit 32 corresponding to the lower service 1 is instructed to execute the lower service 1 again, whereby the service request is sent to the provider 46. Let it be resent. When the number of service request transmissions to the provider 46 reaches a specified value, the process execution unit API notifies the caller of the process execution unit 26 that the process result is “unknown” or “unprocessed”. . In this case, transmission of a service request requesting execution of the lower services 2 and 3 is skipped.

  Further, in the process execution unit process shown in FIG. 10, when the processing result notified from the service calling unit 32 corresponding to the lower service 1 is “processed” in step 206, the process is changed to the lower service 2 in the next step 236. The corresponding service calling unit 32 is instructed to execute the lower service 2. Further, when the processing result is notified from the service calling unit 32 corresponding to the lower service 2, the process proceeds to step 238, and the process branches according to the notified processing result of the lower service 2. That is, if the notified processing result is “business error”, the process proceeds to step 230 and cancels the processing previously executed by the provider 46 in accordance with the execution request of the lower service 1 as in the processing execution unit processing shown in FIG. Processing is performed by the provider 46. If the notified processing result is “processed”, the process proceeds to step 220.

  On the other hand, when the notified processing result is “unknown” or “processing not yet completed”, the lower-level service 2 does not have idempotency, and the process execution unit process shown in FIG. 10 is called by an unequal call. In step 240, the management unit 24 is inquired about the processing result of the lower service 2, and the processing result of the lower service 2 is determined in the next step 242, and the processing is branched according to the determined processing result. If the processing result of the lower service 2 is switched to “business error” through the processing of steps 240 and 242, the process proceeds to step 230. Further, when the processing result of the lower service 2 is switched to “processed” through the processing of steps 240 and 242, the process proceeds to step 220. When the processing result of the subordinate service 2 is “unknown”, it is difficult to determine how to deal with it, but as a result of reconfirming the processing result as described above, the processing result is switched to “business error” or “processed” Makes it easier to decide what to do. If the processing result of the lower service 2 determined in step 242 is “unknown” or “cannot be confirmed”, the process returns to step 240 and the processes of steps 240 and 242 are performed again.

  On the other hand, if the processing result of the lower level service 2 determined in step 242 is “processing not completed”, the process proceeds to step 244 to determine whether or not to retransmit the service request to the package wrapper 48 (retry). . If the number of service request transmissions to the package wrapper 48 is less than the specified value, the process returns to step 236 and the service call unit 32 corresponding to the lower service 2 is instructed to execute the lower service 2 again. To resend the service request. When the number of service request transmissions to the package wrapper 48 reaches a specified value, the process execution unit API informs the caller of the process execution unit 26 that the process result is “unknown” or “unprocessed”. Notice. In this case, transmission of a service request for requesting execution of the lower service 3 is skipped.

  In step 220, the service calling unit 32 corresponding to the lower service 3 is instructed to execute the lower service 3. Further, when the processing result notified from the service calling unit 32 corresponding to the lower service 3 in the next step 222 is “unknown” or “processing not yet completed”, as in the processing execution unit processing shown in FIG. In 224, it is determined whether or not to retransmit (retry) the service request to the MB wrapper 50. If the number of service request transmissions to the MB wrapper 50 is less than the specified value, the process returns to step 220, and the service call unit 32 corresponding to the lower service 3 is instructed to execute the lower service 3 again, thereby providing the service to the MB wrapper 50. Causes the request to be resent. When the number of service request transmissions to the MB wrapper 50 reaches a specified value, the process execution unit API notifies the caller of the process execution unit 26 that the process result is “unknown” or “unprocessed”. To do.

  In the process execution unit process shown in FIG. 10, if the process result notified from the service calling unit 32 corresponding to the lower service 3 in step 222 is “business error”, the process proceeds to step 226, and the process shown in FIG. Similar to the execution unit process, the package wrapper 48 performs a process of canceling the process previously executed by the package wrapper 48 in accordance with the execution request of the lower service 2, and then the provider 46 precedes the execution request of the lower service 1. The provider 46 performs processing for canceling the processing executed in step S3. When the notified processing result is “processed”, the process execution unit API notifies the caller of the process execution unit 26 that the process result is “processed”.

  7 to 10 show the process execution unit process when there is no own service corresponding to the service requested to be executed, but there exists the own service corresponding to the service requested to be executed. The process execution unit 26 executes the process of the corresponding own service, and stores the process result in the process status table 38 in association with the service ID delivered as an argument.

  In addition, a service ID generation unit 30 is provided in a service processing unit in which a lower-level service processing unit exists. The service ID generation unit process shown in FIG.

  In this service ID generation unit process, first, in step 100, an ID unique to a service processing unit (own service processing unit) including itself (service ID generation unit 30) is acquired as a requester unique ID. As an ID unique to the own service processing unit, for example, the network ID of the service processing server 12 in which the own service processing unit is operating can be applied. In step 102, the ID assigned to the process executing the service processing program for realizing the service processing unit is acquired as the process ID. In step 104, a different ID is determined each time a service ID is generated as the ID for each request. As the ID for each request, for example, a simple serial number or the time when the ID is determined can be applied. In step 106, as an ID element obtained by combining the IDs, an ID element in which the requester unique ID, the process ID, and the request ID are arranged in series is generated as shown in FIG. 16A as an example.

  In the next step 108, it is determined whether or not the own service processing unit is the highest-level service processing unit in which no higher-level service processing unit exists. If the determination is affirmative, the process proceeds to step 110, and a new ID for each request (an ID different from the ID for each request determined in the previous step 214) is determined. In the next step 112, the new request ID determined in step 110 is combined with the requester unique ID acquired in the previous step 100 and the process ID acquired in the previous step 102, and a new ID element (second ID element). As shown in FIG. 16A, the service ID according to this embodiment is composed of an original service ID (OSID), a caller service ID (SSID), and a callee service ID (NSID). In 114, the ID element generated in the previous step 106 is set as the original service ID and the caller service ID, and a service ID is generated in which the second ID element generated in step 112 is set as the callee service ID. (See also the service processing unit A shown in FIG. 16 (B)), and notifies the generated service ID to the processing execution unit 26 and ends the process.

  As described above, the service ID generated by the service ID generation unit 30 provided in the highest-level service processing unit includes the ID element set in the original service ID and the call source service ID, and the call destination service ID. The ID elements to be set are not limited to different ones, and a service ID in which the same ID elements are all set for the original service ID, the caller service ID, and the callee service ID may be generated.

  On the other hand, if there is a higher-level service processing unit than the self-service processing unit and the self-service processing unit is not the highest-level service processing unit, the determination in step 108 is negative and the process proceeds to step 116. If the own service processing unit is not the highest-level service processing unit, the service execution unit 26 notifies the service ID added to the service request received by the own service processing unit from the higher-level service processing unit. The ID element set as the original service ID and the ID element set as the call destination service ID are extracted from the service ID notified from the process execution unit 26. In step 118, the ID element set as the original service ID in the notified service ID is set as the original service ID, and the ID element set as the call destination service ID in the notified service ID is set as the call source. A service ID is set by setting the service ID, and the ID element generated in the previous step 216 is set as the call destination service ID (see also the service processing units B to D shown in FIG. 16B). The service ID is notified to the process execution unit 26, and the process ends.

  In the service processing system 10 according to the present embodiment, the service ID generation unit 30 is provided in each service processing unit in which a lower-level service processing unit exists, and the service ID generation unit 30 generates a service ID. However, as described above, by including the requester unique ID in the ID element, the ID element generated by the service ID generation unit 30 of each service processing unit has at least the individual service processing unit as a unit. Uniqueness is ensured. Further, by including the ID for each process in the ID element, the ID element generated by the service ID generation unit 30 of each service processing unit is also ensured uniqueness within each service processing unit. Therefore, the ID element generated by the service ID generation unit 30 of each service processing unit is ensured uniqueness within the service processing system 10 (guaranteed not to overlap with other ID elements). Therefore, it is not necessary to perform numbering processing with exclusive control in order to generate an ID element (service ID) in which uniqueness is ensured, and the performance of the service processing system 10 by performing numbering processing with exclusive control. Can be prevented from significantly decreasing.

  Note that since the process ID is included in the ID element, the service added to the service request even when a plurality of processes functioning as the same service processing unit exist in the single service processing server 12. By referring to the process ID of the ID, it is possible to determine which service processing unit of the plurality of service processing units has processed the corresponding service request.

  In addition, by performing the above service ID generation unit process, the service ID transferred from the highest level service processing unit to the lower level service processing unit transitions as shown in FIG. The original service ID is constant, and the caller service ID of the service ID (added to the service request) that is output from a certain service processing unit in which a higher-level service processing unit exists (from the higher-level service processing unit) The same ID element as the callee service ID in the received service ID is set, and the caller service ID of the service ID output from the certain service processing unit can identify the certain service processing unit An ID element is set. As a result, even when a failure occurs in the service processing system 10 and an unprocessed service request stays in a specific service processing unit, the caller service ID is added to the service ID added to the staying service request. Can be identified from the ID element set as, and this identification process can be identified by the corresponding service ID (caller service ID is the same as the callee service ID). By repeating while tracing the service ID), it is possible to grasp the processing history of the service request that has not been processed yet.

  If the service ID is composed only of the call source service ID and the call destination service ID, for example, as shown in FIG. 17, a service request is sent from the service processing unit A via the service processing units B and C to perform service processing. After the information is transmitted to the parts D and E, when the failure occurs in the service processing parts B and C, and the information recorded in the service processing parts B and C is lost, If a service ID consisting only of an ID and a call destination service ID is recorded, it is impossible to trace the same service request based on the ID element set in the call source ID and the call destination ID of the service ID. Is possible. On the other hand, by adding the original service ID to the service ID, the information corresponding to the same service request can be obtained by referring to the original ID even when a failure occurs. For example, by searching and extracting information corresponding to the same service request using the original service ID as a key by batch processing or the like, processing for resolving data inconsistencies and performing consistency is performed. Is possible.

  The service processing unit in which the lower-level service processing unit exists has the same number of service calling units 32 as the lower-level service processing units. The service calling unit 32 receives the service ID of the lower-level service from the processing execution unit 26. Is notified and the service call unit process shown in FIG. 12 is performed each time execution of a lower-level service is requested. In this service call unit process, first, in step 130, a service request message requesting the lower-level service processing unit to execute the lower-level service is created. The service ID of the lower service notified from the process execution unit 26 is added to this message. In the next step 132, the service request message created in step 130 is transmitted to the corresponding lower-level service processing unit. In step 134, status information indicating that a service request message has been transmitted to the corresponding lower-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the transmitted message.

  When a response message is transmitted from the corresponding lower-level service processing unit to the service request message transmitted in step 132, the response message transmitted from the lower-level service processing unit is received in the next step 136. In step 138, status information indicating that a response message for the service request has been received from the lower-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the received response message. The received response message includes information indicating the service ID of the lower service and the processing result of the lower service, and the information is also stored in the processing status table 38 by the above processing. In step 140, the process execution unit 26 is notified that the response message for the service request has been received from the lower service processing unit together with the service ID of the lower service and the processing result of the lower service set in the received response message. Then, the service calling unit process is terminated.

  In addition, a processing result confirmation unit 34 is provided in a service processing unit in which a higher-level service processing unit exists, and this processing result confirmation unit 34 receives a processing result confirmation request message from a higher-level service processing unit. The processing result confirmation unit processing shown in FIG. 13 is performed. In this processing result confirmation unit processing, first, in step 150, a processing result confirmation request message is received from the upper service processing unit, and in the next step 152, a processing result confirmation request message is received from the upper service processing unit. Is stored in the processing status table 38 of the management unit 24 together with the received electronic message. In the next step 154, the content of the received message is checked, and it is determined whether or not the content of the received message is appropriate. If the determination is negative, the process proceeds to step 156, an error message is set in the response message transmitted to the higher-level service processing unit, and the process proceeds to step 160.

  On the other hand, if the content of the received message is appropriate, the determination in step 154 is affirmed, the process proceeds to step 158, and the service of the service subject to processing result confirmation added to the received message of the processing result confirmation request The ID is extracted, the extracted service ID is notified to the management unit 24, and the processing result of the corresponding service is inquired to the management unit 24. As a result, the management unit 24 performs management unit processing (described later). When the management unit process by the management unit 24 is completed and the inquired processing result is notified, the notified processing result is set in a response message to be transmitted to the higher-level service processing unit, and then the process proceeds to step 160. In step 160, the response message generated in step 156 or step 158 is transmitted to the higher-level service processing unit. In step 162, status information indicating that the response message has been transmitted to the higher-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the transmitted response message, and the processing result confirmation unit process is terminated.

  Further, the management unit 24 receives the service ID from the processing result confirmation unit 34 or the processing execution unit 26, and performs the management unit process shown in FIG. 14 every time there is an inquiry about the processing result of the service of the notified service ID. .

  In this management unit process, first, in step 170, the processing status table 38 is searched using the service ID notified from the processing result confirmation unit 34 or the processing execution unit 26 as a key, and the processing status is associated with the notified service ID. The processing result information registered in the table 38 (information representing the processing results of the corresponding own service and lower service) is extracted. In the next step 172, the extracted processing result information is referred to, and it is determined whether or not a lower level service whose processing result is “unknown” exists in the service corresponding to the notified service ID. When there is no lower service corresponding to the service for which the processing result is to be confirmed (the service with the notified service ID), or there is a corresponding lower service, the processing result of the lower service is “processed” or the like. In this case, the determination is negative, the process proceeds to step 176, the process result represented by the process result information extracted in step 170 is notified to the process result confirmation unit 34 or the process execution unit 26 that is the inquiry source, and the process ends. If the notified service ID is not registered in the processing status table 38, information indicating that the service ID has not been registered is notified to the inquiry source.

  If there is a lower service corresponding to the service for which the processing result is to be confirmed and the processing result of the lower service is “unknown”, the determination in step 172 is affirmed and the process proceeds to step 174, and the processing result Is notified to the result confirmation calling unit 36 corresponding to the lower service whose “unknown” is the service ID of the lower service whose processing result is “unknown”, and requests confirmation of the processing result of the corresponding lower service. As a result, the result confirmation calling unit 36 performs result confirmation calling unit processing (described later). When the result confirmation calling unit process in the result confirmation calling unit 36 is completed and the processing result of the lower service confirmed by the result confirmation calling unit 36 is notified, the process returns to step 172. As a result, if there are a plurality of lower-level services whose processing results are “unknown” in the service corresponding to the service whose processing results are to be confirmed, step 174 is repeated, and the processing results of all corresponding lower-level services are confirmed. Is performed by the corresponding result confirmation calling unit 36. If the determination in step 172 is negative, the process proceeds to step 176 where the processing result of the service subject to processing result confirmation including the processing result of the lower service notified from the result confirmation calling unit 36 is displayed. 34 or the process execution unit 26, and the process ends.

  In the service processing unit in which the lower-level service processing unit exists, the same number of result confirmation calling units 36 as the lower-level service processing units are provided. The result confirmation calling unit 36 receives the service of the lower service from the management unit 24. Each time the ID is notified and confirmation of the processing result of the lower service is requested, the result confirmation calling unit processing shown in FIG. 15 is performed. In this result confirmation calling unit process, first, in step 180, a processing result confirmation request message for requesting the lower service processing unit to notify the lower service processing result is created. Note that the service ID of the lower service notified from the management unit 24 is added to this message. In the next step 182, the processing result confirmation request message generated in step 180 is transmitted to the corresponding lower-level service processing unit. In step 184, status information indicating that the processing result confirmation request message has been transmitted to the corresponding lower-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the transmitted message.

  When a response message is transmitted from the corresponding lower-level service processing unit to the message of the processing result confirmation request transmitted at step 182, the response message transmitted from the lower-level service processing unit is received at the next step 186. In step 188, status information indicating that a response message for the processing result confirmation request has been received from the lower-level service processing unit is stored in the processing status table 38 of the management unit 24 together with the received response message. The received response message includes information indicating the service ID of the lower service and the processing result of the lower service, and the information is also stored in the processing status table 38 by the above processing. In step 190, the management unit 24 is notified that the response message for the processing result confirmation request has been received from the lower-level service processing unit, together with the service ID of the lower-level service set in the received response message and the processing result of the lower-level service. Then, the processing result confirmation calling unit processing is terminated.

  In the above description, the functions of the service processing unit have been described separately for each functional block for convenience. However, a service processing program that causes each service processing server 12 to function as a service processing unit is divided for each functional block. Or may be integrated.

  In addition, by constructing individual service processing units in accordance with the reference model, most of the processing in the individual service processing units is routine processing, and among the programs that implement the service processing unit, the service reception unit 28 In addition, the program for realizing the service ID generating unit 30, the service calling unit 32, the processing result confirming unit 34, the result confirming calling unit 36, and the processing executing unit API among the programs realizing the processing executing unit 26 should be made into components. Is possible. As a result, the program developer can develop a service processing program by diverting the componentized program, and a program that realizes different specific processing for each service processing unit (for example, a business program of the processing execution unit 26). Therefore, the burden on the program developer can be greatly reduced, and the time required for program development can be greatly shortened.

  Among the service processing units in the service processing system 10, since the service processing program runs on the BPEL platform in the BPEL 44, a processing execution unit that realizes a function such as a virtual bag by using a function provided by the BPEL. 26 programs can be developed more easily. That is, every time a certain program is called, the BPEL platform generates a process (also referred to as an instance) for executing the called program, and corresponds to the generated process in the storage area of the storage means such as the memory 12B. In addition to setting an argument at the time of calling in a predetermined area (called BO (Business Objects)), state information indicating the progress of processing in the generated process is also set, and according to changes in the progress of processing in the corresponding process It provides a function to update state information as appropriate.

  Therefore, by using the above function, as shown in FIG. 18 as an example, among the programs of the service processing unit, at least a program that functions as the processing execution unit 26 (the program or service that functions as the service reception unit 28 in the program) When a program that functions as the calling unit 32 may be included) with the service ID and the idempotent flag as arguments and started, another process that is generated with the same service ID as the own process is called If it is configured to check whether or not it exists (see also “process result check” in FIG. 18), whether or not the service request corresponding to the current call is a retransmission of a service request received in the past. Can be easily confirmed. In addition, when there is another process generated with the same service ID as the argument of the above program as an argument, the corresponding other process (if there are multiple corresponding other processes, the latest When the service request corresponding to this call is received last time, the status information is copied from the BO of (the last generated other process) (see also “BO copy” in FIG. 18). Inheriting the state of this process, starting from the continuation of the previous process can be realized with a simple process. In addition, when there is a non-defective lower level service corresponding to the service requested to execute the above program, the processing result of the lower level service is confirmed. By configuring so as to skip (see also “executed?” In FIG. 18), a function such as a virtual bag can be realized by a simple process. In this way, by utilizing the features of the BPEL platform, the development load of the service processing program can be further reduced.

  Further, in the service processing system 10 according to the present embodiment, when each service processing unit receives a service request or a processing result confirmation request, it performs processing in the processing sequence shown in FIG. 3 or FIG. The service request and the processing result confirmation request transmitted by the processing unit are chained over a plurality of stages of service processing units. Hereinafter, a processing sequence of the service processing system 10 as a whole when a service request or a processing result confirmation request is transmitted from the highest-level service processing unit will be described. In the following, it is assumed that the target service is a service that requires the execution of the lower level service by each of the provider 46, the package wrapper 48, and the MB wrapper 50.

  FIG. 19 shows an example of a sequence in the case where execution of a service is instructed to the highest-level service processing unit (requester 42). In this sequence, when the requester 42 is instructed to execute the service, the service ID generation unit 30 of the requester 42 generates a service ID of the lower-level service (service ID to be transmitted to the BPEL 44) (step 260 in FIG. 19 is also performed). The service request is sent to the BPEL 44 by the service calling unit 32 of the requester 42.

  The process execution unit 26 of the BPEL 44 that has received the service request performs the process of the own service when the service corresponding to the requested service exists (see also step 262 in FIG. 19), and the service ID. The generation unit 30 generates the service ID of the lower-level service 1 (the service ID to be transmitted to the provider 46) (see also step 264 in FIG. 19), calls the service call unit 32 corresponding to the provider 46, and the service corresponding to the provider 46 The calling unit 32 transmits a service request to the provider 46. In the provider 46 that has received the service request, the processing of the requested lower-level service 1 is performed by the processing execution unit 26 (see also step 266 in FIG. 19), and a response is transmitted to the BPEL 44 by the service reception unit 28 after the processing is completed. .

  When the response from the provider 46 is received and the processing result is “processed”, the process execution unit 26 of the BPEL 44 uses the service ID generation unit 30 to transmit the service ID of the lower-level service 2 (the service transmitted to the package wrapper 48). ID) is generated (see also step 268 in FIG. 19), the service call unit 32 corresponding to the package wrapper 48 is called, and the service request is sent to the package wrapper 48 by the service call unit 32 corresponding to the package wrapper 48 Let In the package wrapper 48 that has received the service request, the processing of the requested lower-level service 2 is performed in cooperation with the package system 66 (see also step 270 in FIG. 19). A response is sent to BPEL 44.

  When the response from the package wrapper 48 is received and the processing result is “processed”, the process execution unit 26 of the BPEL 44 transmits the service ID of the lower service 3 to the MB wrapper 50 by the service ID generation unit 30. Service ID) is generated (see also step 272 in FIG. 19), the service call unit 32 corresponding to the MB wrapper 50 is called, and the service request is sent to the MB wrapper 50 by the service call unit 32 corresponding to the MB wrapper 50. In the MB wrapper 50 that has received the service request, the processing of the requested lower-level service 3 is performed in cooperation with the deposit system 68 (see also step 274 in FIG. 19), and the BPEL 44 is performed by the service reception unit 28 after the processing is completed. A response is sent to

  In the BPEL 44, when the response from the package wrapper 48 is received and the processing result is “processed”, the processing execution unit 26 notifies the service reception unit 28 of the processing result, and the service reception unit 28 notifies the requester 42. Send a response to notify the processing result. As a result, the requester 42 performs processing to output the processing result (“processed”) of the service instructed to be executed (see also step 276 in FIG. 19). As described above, service requests are chained from the top-level requester 42 to the provider 46, the package wrapper 48, and the MB wrapper 50 via the BPEL 44, whereby the instructed service is executed.

  Next, a sequence when a failure occurs in the service processing system 10 will be described. In the sequence shown in FIG. 20, a failure occurs immediately after the BPEL 44 transmits a service request to the package wrapper 48, and the response is received from the package wrapper 48 because the transmitted service request is not received by the package wrapper 48. This is the sequence when the timer has timed out without being transmitted. In the sequence shown in FIG. 20, the illustration of the retransmission of the service request from the BPEL 44 to the package wrapper 48 is omitted, but even if the service request is retransmitted to the package wrapper 48 a predetermined number of times, If no response is received, control returns from the business program of the process execution unit 26 of the BPEL 44 to the process execution unit API.

  Here, the process execution unit API may notify the requester 42 via the service reception unit 28 that the process result of the service requested to be executed is “unknown (timeout / retry count exceeded)”. In the sequence shown in FIG. 20, the processing result of the lower service 2 by the package wrapper 48 is inquired to the management unit 24. In this case, the processing result of the lower service 2 is “unknown”, and therefore corresponds to the package wrapper 48. The result confirmation calling unit 36 transmits a processing result confirmation request from the BPEL 44 to the package wrapper 48. If the failure of the service processing system 10 has been resolved during this time, the processing result confirmation request is received by the package wrapper 48 and the lower level service corresponding to the service ID notified by the processing result confirmation unit 34 of the package wrapper 48 is received. The processing result of 2 is confirmed. In this case, since the processing result is “processing incomplete”, a processing result notification notifying that the processing result is “processing incomplete” is transmitted from the package wrapper 48 to the BPEL 44.

  When the processing result notification from the package wrapper 48 is received and it is confirmed that the processing result is “processing incomplete”, the processing execution unit 26 of the BPEL 44 calls the service calling unit 32 corresponding to the package wrapper 48 to call the service calling The service request is transmitted again from the BPEL 44 to the package wrapper 48 by the unit 32. Thereby, in the package wrapper 48, the processing of the requested lower-level service 2 is performed in cooperation with the package system 66 (see also step 270 in FIG. 20). Subsequent sequences are the same as those in FIG.

  Further, the sequence shown in FIG. 21 is a case where a business error occurs as a result of the processing of the subordinate service 3 requested by the service request received by the MB wrapper 50 from the BPEL 44 in cooperation with the deposit system 68 (FIG. 21). 21 (see also step 275 of FIG. 21). In this case, a response notifying that the processing result is “business error” is transmitted from the MB wrapper 50 to the BPEL 44. When this response is received by the BPEL 44, the processing execution unit 26 of the BPEL 44 indicates that the lower service 1 by the provider 46 and the lower service 2 by the package wrapper 48 are “processed” and the lower service 3 by the MB wrapper 50 is “business”. In order to resolve the data inconsistency due to the error, the service ID of the corresponding lower service 2 is first recognized (see also step 282 in FIG. 21), and the lower service 2 executed by the package wrapper 48 first. A service request (denoted as “cancel request” in FIG. 21) requesting execution of the process for canceling the process is transmitted to the package wrapper 48 by the service calling unit 32. As a result, the package wrapper 48 performs a cancellation process for canceling the processing of the lower-level service 2 that has been normally executed in cooperation with the package system 66 (see also step 284 in FIG. 21).

  When receiving a response to the service request (cancellation request) from the package wrapper 48, the process execution unit 26 of the BPEL 44 recognizes the service ID of the corresponding lower service 3 (see also step 286 in FIG. 21). A service request (represented as “cancel request” in FIG. 21) for requesting execution of processing for canceling the processing of the lower-level service 3 previously executed by the MB wrapper 50 is transmitted to the MB wrapper 50 by the service calling unit 32. As a result, the MB wrapper 50 performs a cancellation process for canceling the processing of the lower-level service 2 that has been normally executed in cooperation with the deposit system 68 (see also step 288 in FIG. 21).

  When the response to the service request (cancellation request) is received from the MB wrapper 50, the process execution unit 26 of the BPEL 44 notifies the service reception unit 28 of the processing result, and the service reception unit 28 transmits the response to the requester 42 and processes it. Notify the result. As a result, the requester 42 performs processing to output the processing result of the service instructed to be executed (the service for which execution has been instructed is “cancelled” indicating that the service has been canceled due to a business error occurring in the middle). (See also step 276 in FIG. 19).

  In the sequence shown in FIG. 22, a failure occurs immediately after the BPEL 44 transmits a service request to the MB wrapper 50, and a response is transmitted from the MB wrapper 50 because the transmitted service request is not received by the MB wrapper 50. In this case, the service request is retransmitted from the requester 42 to the BPEL 44. If the processing execution unit 26 of the BPEL 44 is configured as shown in FIG. 18 described above, the processing execution unit 26 of the BPEL 44 is the same as its own process upon reception of the service request from the requester 42. A process for confirming whether or not there is another process generated with the service ID as an argument is performed (see also step 290 in FIG. 22). Is a retransmission of a service request received in the past.

  Next, the state information stored in the BO of the corresponding process is copied to the BO of the own process (see also step 292 in FIG. 22). Then, the process execution unit 26 performs a process of executing the service requested by the retransmitted service request. In this embodiment, the service provided by the provider 46, the MB wrapper 50 (and the deposit system 68) The services provided by the package wrapper 48 (and the package system 66) are not idempotent, while the services provided by the A service request is transmitted only to the MB wrapper 50, and for the package wrapper 48, the transmission of the service request is skipped based on the processing result of the corresponding lower service being “processed”. As a result, a function such as a virtual bag is realized.

  FIG. 23 shows an example of a sequence when the requester 42 is instructed to confirm the processing result. In this sequence, when confirmation of the processing result is instructed, the management unit 24 of the requester 42 confirms the processing result of the service to be confirmed. If the processing result is “unknown”, the service ID of the service to be confirmed is recognized. (See also step 296 in FIG. 23), and the result confirmation calling unit 36 of the requester 42 transmits a processing result confirmation request to the BPEL 44. The BPEL 44 that has received the processing result confirmation request from the requester 42 confirms the processing result of the corresponding service by the management unit 24 in accordance with the request from the processing result confirmation unit 34 (see also step 298 in FIG. 23). The processing result of the lower level service is also confirmed (see also step 298 in FIG. 23).

  Here, when a lower service whose processing result is “unknown” exists in the corresponding lower service (here, it is assumed that the processing result of the lower service provided by the MB wrapper 50 is “unknown”). ) The result confirmation calling unit 36 corresponding to the lower service whose processing result is “unknown” is called by the management unit 24, and the result confirmation calling unit 36 performs processing to the corresponding lower service processing unit (in this example, the MB wrapper 50). Send a result confirmation request. When the BPEL 44 receives the processing result notification from the lower service processing unit, the processing result confirmation unit 34 of the BPEL 44 transmits the processing result notification to the requester 42. As a result, the requester 42 performs a process of outputting the process result of the service instructed to confirm the process result (see also step 276 in FIG. 23). As described above, even when the confirmation of the processing result is instructed, the processing result confirmation request is transmitted from the requester 42 to the BPEL 44, and the processing result confirmation request is chained to the lower-level service processing unit as necessary. The processing result of the instructed service is confirmed.

  In the above description, as the service processing system according to the present invention, five service processing units are divided into three layers (three levels), and three service processing units in the third layer (third level) are arranged in the second layer ( The second level (single stage) is connected to each single service processing unit, and the second level (second level) single service processing unit is connected to the first level (first level) single service processing unit. The service processing system 10 having the above-described configuration has been described as an example. However, the total number and the number of service processing units, and the number of service processing units in each level (each layer) are not limited to the above. Needless to say, the present invention can also be applied to a service processing system having a connected configuration.

  In the above description, the service processing program for realizing the second-stage (second-layer) service processing unit operates on the BPEL platform. However, the present invention is not limited to this. The service processing system according to can be constructed without using BPEL.

  In the above description, the mode in which the individual service processing units are realized by different computers (service processing server 12) has been described. However, the present invention is not limited to this. The present invention can also be applied to an aspect in which each functions as a service processing unit.

  In the above description, the service processing program corresponding to the program according to the present invention is stored (installed) in the storage unit 12C of the service processing server 12 in advance. However, the program according to the present invention is a CD-ROM, It is also possible to provide in a form recorded on a recording medium such as a DVD-ROM. The recording medium in this aspect corresponds to the recording medium according to the present invention.

DESCRIPTION OF SYMBOLS 10 Service processing system 12 Service processing server 12C Storage part 14 Application server 24 Management part 26 Process execution part 28 Service reception part 30 Service ID generation part 32 Service calling part 34 Processing result confirmation part 36 Result confirmation calling part 38 Processing status table 42 Requester 46 Provider 48 Package wrapper 50 MB wrapper 66 Existing system 68 Existing system

Claims (17)

A service processing device that is realized by a computer and constitutes a service processing system together with other service processing devices capable of transmitting and receiving information,
When service execution is requested by receiving a service request to which a service ID is added, if there is a local service corresponding to the service requested to be executed as a process related to the service requested to be executed, Process the own service, store the processing result of the own service in the storage unit in association with the service ID, and if there is a lower service corresponding to the service requested to be executed, the service ID of the lower service A service request with the generated service ID added thereto is transmitted to the lower-level service processing device, and the processing result of the lower-level service is associated with the generated service ID and stored in the storage means, A first function for sending a response to the request source;
When the confirmation of the processing result of the service is requested by receiving the processing result confirmation request to which the service ID is added, based on the information stored in the storage means, the service for which the confirmation of the processing result is requested Confirm the processing result of the corresponding service, and if it is necessary to confirm the processing result of the corresponding lower service, send the processing result confirmation request with the service ID of the corresponding lower service to the lower service processing device A second function for transmitting the confirmed processing result to the transmission source of the processing result confirmation request when the result confirmation is completed;
When a service request to which the same service ID as the previously received service request is added is received, and a re-execution of a service that has been requested to be executed again is requested, the service requested to be re-executed Among the corresponding one or more services, for a subordinate service having idempotency, a service processing apparatus that performs the subordinate service having idempotency without confirming the processing result of the subordinate service having idempotency For a non-ideal subordinate service that does not have idempotency, the processing result of the non-ideal subordinate service is confirmed, and a response to the service request is received for the confirmed processing result. In the case of “unknown” indicating that the processing result is confirmed, the processing result confirmation request is transmitted to the service processing apparatus that performs the non-defective subordinate service, thereby confirming the processing result again. And confirmation only when the "processing unfinished" is obtained as the processing result, after transmitting the service request to the service processing apparatus for subservice non idempotent, the processing result of the lower service of the non-idempotent again A service processing apparatus having a third function for performing a process to transmit a response according to the confirmed processing result to the service request transmission source when the process is completed. A service processing device that is realized by a computer and constitutes a service processing system together with other service processing devices capable of transmitting and receiving information,
Service execution means for performing processing related to the requested service when the service ID is notified and the execution of the service is requested;
Processing result management means comprising storage means for storing service processing results in association with service IDs;
With
The service execution unit includes a service reception unit when a higher-level service processing device exists than the own device, and the service reception unit receives a service request to which a service ID is added from the higher-level service processing device. When the execution of the service is requested, the process related to the requested service is performed, and the processing result of the process is associated with the service ID and stored in the storage unit of the processing result management unit. A service ID generating means for transmitting a response to the higher-level service processing apparatus by the service receiving means and generating a service ID having uniqueness when a service processing apparatus lower than the own apparatus exists; and a service calling means The service requested to be executed includes a lower-level service by the lower-level service processing device. If the service is a service, the service ID generation unit generates a service ID of the lower service as a process related to the service requested to be executed, and a service request with the generated service ID of the lower service is added to the service The processing result of the lower service transmitted by the calling means to the lower service processing apparatus and notified by the response received from the lower service processing apparatus by the service calling means is associated with the service ID of the lower service. A service processing device that performs processing to be stored in the storage unit of the processing result management unit and that performs a lower service having idempotency exists in a lower level than the own device, and corresponds to a service that is requested to be executed There is a subservice with the above idempotency in the service In this case, without confirming the processing result of the subordinate service having the idempotency with the processing result management unit, the service calling unit transmits a service request to the service processing apparatus that performs the subordinate service having the idempotency, A service processing apparatus that performs non-idempotent subservices that do not have idempotency exists lower than the self-apparatus, and the non-idempotent subservices are among the subordinate services corresponding to the services that are requested to be executed. If present, confirm the processing result of the non-defective lower level service with the processing result management means, and if the confirmed processing result is “unknown” indicating that a response to the service request has not been received The processing result management means sends the processing result confirmation request to the service processing apparatus that performs the non-defective lower level service, and tries to confirm the processing result again. Only when the processing result is “unprocessed” , after the service call means transmits the service request to the service processing apparatus that performs the non-defective subordinate service, The processing result management means is checked again, and when the processing ends, a response corresponding to the processing result confirmed by the service receiving means to the higher-level service processing device is transmitted by the service receiving means. And
The processing result management means includes processing result confirmation means when there is a higher-level service processing apparatus than the own apparatus, and the processing result confirmation means sends a processing result confirmation request to which a service ID is added. When the confirmation of the processing result of the service is requested by receiving from the device, the processing result of the service for which the confirmation of the processing result is requested is confirmed based on the service ID, and the processing confirmed when the confirmation of the processing result is completed The result is notified to the higher-level service processing device by the processing result confirmation unit, and when there is a lower-level service processing device than the own device, a result confirmation calling unit is provided, and processing of the lower-level service by the lower-level service processing device When it is necessary to confirm the result, a processing result confirmation request with the service ID of the lower-level service to be confirmed is sent to the result confirmation caller. The processing result of the lower service transmitted from the lower service processing device to the result confirmation calling unit is stored in the storage unit in association with the service ID of the lower service. Let the service processing equipment.   The service execution means is executed when a higher-order service processing apparatus and a lower-order service processing apparatus exist, respectively, and the service reception means receives a service request from the higher-order service processing apparatus. If the requested service is a service for which a corresponding lower service exists, a service request with the service ID of the lower service generated by the service ID generation means is added to the lower service by the service calling means. 3. The service processing device according to claim 2, wherein the service processing unit transmits a response to the higher-level service processing device after the service calling unit receives a response from the lower-level service processing device.   When the service requested to be executed is a service including the own service, the service execution means performs the process of the own service as a process related to the service requested to be executed, and displays the processing result of the own service. The service processing apparatus according to claim 2 or 3, wherein the service processing apparatus performs processing to be stored in the storage unit of the processing result management unit in association with the notified service ID.   The service execution unit includes the same number of service call units as the lower-level service processing devices when there are a plurality of lower-level service processing devices, and includes a plurality of lower-level service processing devices. When the service that is present and requested to be executed is a service that includes a plurality of lower services by the plurality of lower service processing devices, the plurality of lower service processes are performed as the processing related to the service requested to be executed. The service ID generation unit generates a service ID of a specific lower service by a specific lower service device among the devices, and generates a service request to which the generated service ID of the lower service is added. The specific lower-level service processing device by a specific service calling means corresponding to the device The processing result of the specific lower service notified by the response received from the specific lower-level service processing device by the specific service calling means is associated with the service ID of the specific lower-level service and the The service processing apparatus according to claim 2, wherein the processing stored in the storage unit of the processing result management unit is performed for each of the plurality of lower-level service processing apparatuses.   If the processing result of the lower service notified by a response from any of the plurality of lower-level service processing devices is an error, the service execution means includes the plurality of lower-level service processing devices. If there is a lower-level service processing apparatus whose requested lower-level service is “processed”, the service calling unit corresponding to the lower-level service processing apparatus requests cancellation of the “processed” lower-level service. The service processing apparatus according to claim 5, wherein the service request is transmitted to a lower-level service processing apparatus whose lower-level service is “processed”.   If the processing result of the lower service notified by a response from any of the plurality of lower-level service processing devices is an error, the service execution means includes the plurality of lower-level service processing devices. 6. The service processing apparatus according to claim 5, wherein if there is a lower-level service processing apparatus that has not transmitted a service request, transmission of the service request by the service calling unit corresponding to the lower-level service processing apparatus is stopped. When there is a service processing device lower than its own device, and a program for causing a computer to function as a service processing device operates on the BPEL platform,
The service execution means is generated each time a service ID is notified and a service execution is requested, holds the notified service ID, stores state information indicating the progress of the process, and the progress of the process This is realized by an instance that appropriately updates the state information in accordance with the change of the state, and each time the instance is newly generated, the newly generated instance retains the same service ID generated in the past. The instance is searched, and if the corresponding instance exists, the state information of the corresponding instance is copied as the state information of the own instance, and processing is performed according to the copied state information. The service processing apparatus according to claim 1.   The processing result management means includes a higher-order service processing apparatus and a lower-level service processing apparatus, and the processing result confirmation means receives a processing result confirmation request from the higher-order service processing apparatus. If there is a lower service corresponding to the service for which confirmation of the processing result is requested and the processing result of the corresponding lower service stored in the storage means is “unknown”, the service of the lower service The processing result confirmation request to which the ID is added is transmitted to the lower service processing device by the result confirmation calling unit, and the processing result is notified from the lower service processing device to the result confirmation calling unit. The processing result confirming means notifies the higher-level service processing device of the processing result of the service requested to be confirmed. The placing of the service processing devices. The service ID generation means
An ID element generating means for generating an ID element including a unique ID that sets an ID that differs for each service processing device and a request ID that sets an ID that differs for each service request;
If there is no higher-level service processing apparatus than the own apparatus, a service ID including a caller ID and a callee ID respectively set with the ID elements generated by the ID element generation unit is generated, and higher than the own apparatus If there is a service processing apparatus, a caller ID in which an ID element set as a callee ID is set in the service ID added to the service request received from the higher-level service processing apparatus, and the ID element generation ID element combination means for generating a service ID including a callee ID in which the ID element generated by the means is set;
The service processing apparatus according to claim 2, comprising:   The ID element combination means generates a service ID including an original ID in which the ID element generated by the ID element generation means is set when there is no higher-level service processing apparatus than the own apparatus. If a higher-level service processing device exists, a service ID including an original ID in which an ID element set as an original ID is set to the service ID added to the service request received from the higher-level service processing device is generated. The service processing apparatus according to claim 10.   12. The service processing apparatus according to claim 10, wherein the ID element generation unit generates an ID element including an execution unit ID assigned to an execution unit of a program for causing the computer to function as the service processing apparatus.   A service processing system in which a plurality of service processing devices according to claim 1 are provided so that information can be transmitted and received. A service processing program that causes a computer to function as a service processing device that constitutes a service processing system together with another service processing device capable of transmitting and receiving information,
The computer,
Service execution means for performing processing related to the requested service when the service ID is notified and the execution of the service is requested;
Processing result management means comprising storage means for storing service processing results in association with service IDs;
With
The service execution unit includes a service reception unit when a higher-level service processing device exists than the own device, and the service reception unit receives a service request to which a service ID is added from the higher-level service processing device. When the execution of the service is requested, the process related to the requested service is performed, and the processing result of the process is associated with the service ID and stored in the storage unit of the processing result management unit. A service ID generating means for transmitting a response to the higher-level service processing apparatus by the service receiving means and generating a service ID having uniqueness when a service processing apparatus lower than the own apparatus exists; and a service calling means The service requested to be executed includes a lower-level service by the lower-level service processing device. If the service is a service, the service ID generation unit generates a service ID of the lower service as a process related to the service requested to be executed, and a service request with the generated service ID of the lower service is added to the service The processing result of the lower service transmitted by the calling means to the lower service processing apparatus and notified by the response received from the lower service processing apparatus by the service calling means is associated with the service ID of the lower service. A service processing device that performs processing to be stored in the storage unit of the processing result management unit and that performs a lower service having idempotency exists in a lower level than the own device, and corresponds to a service that is requested to be executed There is a subservice with the above idempotency in the service In this case, without confirming the processing result of the subordinate service having the idempotency with the processing result management unit, the service calling unit transmits a service request to the service processing apparatus that performs the subordinate service having the idempotency, A service processing apparatus that performs non-idempotent subservices that do not have idempotency exists lower than the self-apparatus, and the non-idempotent subservices are among the subordinate services corresponding to the services that are requested to be executed. If present, confirm the processing result of the non-defective lower level service with the processing result management means, and if the confirmed processing result is “unknown” indicating that a response to the service request has not been received The processing result management means sends the processing result confirmation request to the service processing apparatus that performs the non-defective lower level service, and tries to confirm the processing result again. Only when the processing result is “unprocessed” , after the service call means transmits the service request to the service processing apparatus that performs the non-defective subordinate service, The processing result management means is checked again, and when the processing ends, a response corresponding to the processing result confirmed by the service receiving means to the higher-level service processing device is transmitted by the service receiving means. And
The processing result management means includes processing result confirmation means when there is a higher-level service processing apparatus than the own apparatus, and the processing result confirmation means sends a processing result confirmation request to which a service ID is added. When the confirmation of the processing result of the service is requested by receiving from the device, the processing result of the service for which the confirmation of the processing result is requested is confirmed based on the service ID, and the processing confirmed when the confirmation of the processing result is completed The result is notified to the higher-level service processing device by the processing result confirmation unit, and when there is a lower-level service processing device than the own device, a result confirmation calling unit is provided, and processing of the lower-level service by the lower-level service processing device When it is necessary to confirm the result, a processing result confirmation request with the service ID of the lower-level service to be confirmed is sent to the result confirmation caller. The processing result of the lower service transmitted from the lower service processing device to the result confirmation calling unit is stored in the storage unit in association with the service ID of the lower service. A service processing program for functioning as a service processing device. A service processing program that causes a computer to function as a service processing device that constitutes a service processing system together with another service processing device capable of transmitting and receiving information,
A service processing program for causing the computer to function as the service processing device according to any one of claims 2 to 12. A recording medium recorded with a service processing program that causes a computer to function as a service processing device that constitutes a service processing system together with another service processing device capable of transmitting and receiving information,
The service processing program causes the computer to
When service execution is requested by receiving a service request to which a service ID is added, if there is a local service corresponding to the service requested to be executed as a process related to the service requested to be executed, Process the own service, store the processing result of the own service in the storage unit in association with the service ID, and if there is a lower service corresponding to the service requested to be executed, the service ID of the lower service A service request with the generated service ID added thereto is transmitted to the lower-level service processing device, and the processing result of the lower-level service is associated with the generated service ID and stored in the storage means, A first function for sending a response to the request source;
When the confirmation of the processing result of the service is requested by receiving the processing result confirmation request to which the service ID is added, based on the information stored in the storage means, the service for which the confirmation of the processing result is requested Confirm the processing result of the corresponding service, and if it is necessary to confirm the processing result of the corresponding lower service, send the processing result confirmation request with the service ID of the corresponding lower service to the lower service processing device A second function for transmitting the confirmed processing result to the transmission source of the processing result confirmation request when the result confirmation is completed;
When a service request to which the same service ID as the previously received service request is added is received, and a re-execution of a service that has been requested to be executed again is requested, the service requested to be re-executed Among the corresponding one or more services, for a subordinate service having idempotency, a service processing apparatus that performs the subordinate service having idempotency without confirming the processing result of the subordinate service having idempotency For a non-ideal subordinate service that does not have idempotency, the processing result of the non-ideal subordinate service is confirmed, and a response to the service request is received for the confirmed processing result. In the case of “unknown” indicating that the processing result is confirmed, the processing result confirmation request is transmitted to the service processing apparatus that performs the non-defective subordinate service, thereby confirming the processing result again. And confirmation only when the "processing unfinished" is obtained as the processing result, after transmitting the service request to the service processing apparatus for subservice non idempotent, the processing result of the lower service of the non-idempotent again A recording medium that functions as a service processing apparatus having a third function of performing a process to be performed and transmitting a response according to the confirmed processing result to the transmission source of the service request when the process is completed.   16. A recording medium on which the service processing program according to claim 14 or 15 is recorded.

Images