JP5978008B2 - Transaction management system, transaction management method, and transaction management program - Google Patents

Description

  The present invention relates to a transaction management system, a transaction management method, and a transaction management program for supporting the handling of errors that occur in some processes when a plurality of processes are executed in cooperation.

  An error may occur when various types of information processing are executed in the information processing system based on the processing request received from the client terminal. It is desirable to respond quickly and efficiently to such errors. Therefore, a technique for performing rollback or reprocessing without returning an error to the request source when an error occurs has been studied (for example, see Patent Document 1). In the technique described in this document, a request proxy device proxying a request for a first server from a request source terminal, a request information management device receiving and storing terminal request information from the request proxy device, a back-end server, or It is composed of a connection proxy device that acts as a proxy for processing requests from the first server to other external devices and manages connection information. Then, the request proxy device detects a failure in the server, reads the terminal request information from the request information management device, and transmits it to the second server. The second server continues the transaction processing that constitutes the request from the request source terminal using the terminal request information. When transmitting a processing request to the back-end server or the external device to the connection proxy device, the processing result is transmitted to the request proxy device using the connection information.

  In addition, such information processing may be performed in the host system by combining a plurality of individual processes. Therefore, a data transfer system for transferring data from the client terminal to the host system has also been studied (see, for example, Patent Document 2). In the technique described in this document, the tightening management server that has received the message executes a tightening process. Then, this message is stored in the transmission message storage unit, and a message transmission process is executed via the main HUB in the operating state. And in this document, in order to complete the transaction of one transaction message, it is described that a transaction flow (cooperation processing) combining a plurality of individual processes is performed. Here, the linkage process is a process in which a plurality of individual processes (for example, sales management for each branch office, customer information file management (CIF) for each customer, account management, etc.) are continuously handled as a series of transactions. .

Japanese Patent Laying-Open No. 2008-27189 (first page, FIG. 1) JP 2009-237789 A (first page, FIG. 1)

  By the way, there are various causes of the error, and there are a business error that occurs when conditions necessary for executing information processing are not consistent, a system error that occurs due to a system failure, and the like. The way of handling varies depending on the type of error. Here, the cancellation method differs between the business error and the system error even when the already executed processing is canceled. That is, in the case of a business error, it is possible to cancel on the premise of a sound system, but in the case of a system error, a failure has occurred in the system, and therefore, a response different from the business error is required.

In the cooperation process described in Patent Document 2, the order of the individual processes constituting the cooperation process is important, and it is necessary to consider the order of cancellation even when canceling.
The present invention has been made in view of the above-described problems, and an object of the present invention is to support efficient responses to errors generated in some processes when a plurality of processes are executed in cooperation. To provide a transaction management system, a transaction management method and a transaction management program.

In order to solve the above problems, the invention described in claim 1 is performed in cooperation with a transaction terminal, a control unit connected to an execution device that executes individual processing for transaction, and for transaction. A cooperation information storage unit that stores information related to a plurality of individual processes, an execution information storage unit that records completion information of individual processes executed in response to a transaction message received from the transaction terminal, and a record in the cooperation information storage unit A transaction management system comprising: a management unit that monitors an execution status of an application execution unit that executes a linked application that executes a linked process , wherein the control unit corresponds to a transaction message received from the transaction terminal the cooperative application, then start the application execution means for executing the individual process, said application executing means, before by the cooperative application For the individual process specified in the cooperation information storage unit, the processing request for the individual process is sequentially transmitted to the execution device, and when the individual process is completed, the completion information about the individual process is displayed as the execution information. When the application execution means detects an error in a part of the individual processing of the cooperation processing combining a plurality of individual processing , the completion information is recorded in the execution information storage unit by the cooperation application. The executed individual process is identified, a cancellation request message for canceling the executed individual process in the cooperation process is sequentially generated, and the flow cancellation process is transmitted to the execution device, and the management unit executes the application When a system error is detected in the cooperative application being executed by the execution means Acquires completion information of the individual process from the execution information storage unit, starts cancellation execution means for canceling the executed individual process based on the completion information, and uses the cancellation execution means to execute the execution The gist is to execute the rollback cancellation processing of the completed individual processing .

  According to a second aspect of the present invention, in the transaction management system according to the first aspect, when executing the cancellation process of the executed individual processes, the individual processes are performed in the reverse order of the execution order of the executed individual processes. The main point is to execute the cancellation process.

Invention of Claim 3 memorize | stored the information regarding the control part connected to the transaction terminal, the execution apparatus which performs the separate process for a transaction, and the several separate process cooperated for a transaction A cooperation information storage unit, an execution information storage unit that records completion information of an individual process executed in response to a transaction message received from the transaction terminal, and a cooperation application that executes the cooperation process recorded in the cooperation information storage unit And a transaction management system comprising a management unit that monitors the execution status of the application execution means for executing the transaction, wherein the control unit receives the transaction message received from the transaction terminal. the corresponding cooperative application, then start the application execution means for executing the individual process, said application executing means, the cooperative application Ri for individual process specified in the linkage information storage section, to the execution unit sequentially transmits a processing request of the individual processing, if completed the individual processing, the completion information of the individual processing When the application execution unit detects an error in a part of the individual processing of the cooperation process that combines a plurality of individual processes , the completion information is stored in the execution information storage unit by the cooperation application. The recorded individual executed process is identified, a cancellation request message for canceling the executed individual process in the cooperation process is sequentially generated, and a flow cancellation process is transmitted to the execution device . A system error is detected in the cooperative application being executed by the application execution means. In this case, the completion information of the individual process is acquired from the execution information storage unit, and based on the completion information, a cancellation execution unit for canceling the executed individual process is started, and the cancellation execution unit is used. The gist of the present invention is to execute rollback cancellation processing of the executed individual processing .

Invention of Claim 4 memorize | stored the information regarding the control part connected to the transaction terminal, the execution apparatus which performs the separate process for transaction, and the several separate process cooperated for transaction A cooperation information storage unit, an execution information storage unit that records completion information of individual processing executed in response to a transaction message received from the transaction terminal, and a cooperation application that executes the cooperation process recorded in the cooperation information storage unit A program for managing transactions using a transaction management system comprising a management unit that monitors the execution status of the application execution means for executing the control, and the control unit is connected to the transaction message received from the transaction terminal. the corresponding cooperative application, then start the application execution means for executing an individual process, said application executing means, wherein the linkage Apurikeshi The individual process specified in the linkage information storing unit by emissions, to the execution unit sequentially transmits a processing request of the individual processing, if completed the individual processing, the completion information of the individual processing When the application execution means detects an error in a part of the individual processing of the cooperation process that combines a plurality of individual processes , the completion information is recorded in the execution information storage unit by the cooperation application. The execution individual process in which the executed individual process is recorded , the cancellation request message for canceling the executed individual process in the cooperation process is sequentially generated, and the flow cancellation process is transmitted to the execution device, and the management unit A system error in the cooperative application being executed by the application executing means. If known, the completion information of the individual process is acquired from the execution information storage unit, and based on the completion information, a cancellation execution unit for canceling the executed individual process is started, and the cancellation execution unit is used. Thus, the gist is to function as means for executing the rollback cancellation processing of the individual processing that has been executed .

(Function)
According to invention of Claim 1, 3 or 4 , a control part starts the application execution means for performing the separate process corresponding to the transaction message received from the transaction terminal, and an application execution means is cooperation information. For the individual processes specified in the storage unit, processing requests for the individual processes are sequentially transmitted to the execution device. When the individual process is completed, the completion information about the individual process is recorded in the execution information storage unit. When an error is detected in some of the individual processes, the executed individual process in which the completion information is recorded in the execution information storage unit is specified, and the executed individual process is canceled. Thereby, when an error occurs, the executed process can be canceled and the state before the process can be efficiently restored.

  According to the second aspect of the present invention, when executing the cancellation processing of the executed individual processing, the cancellation processing of each individual processing is executed in the reverse order of the execution order of the executed individual processing. Thereby, it is possible to return to the state before the processing in consideration of the order in which the individual processing is executed.

According to the present invention, when executing the cancellation process of the executed individual process, the application execution unit acquires the completion information of the individual process from the execution information storage unit and, based on the completion information, the execution apparatus Send a cancellation request message. As a result, an executed process can be canceled by an application for a previously assumed error such as a business error.

According to the present invention, when a system error is detected in the application execution unit, the management unit that monitors the application execution unit acquires completion information of the individual process from the execution information storage unit. Then, based on the completion information, a cancel execution means for canceling the executed individual process is activated, and the individual process is canceled using the cancel execution means. As a result, even when the application cannot be controlled, such as a system error, the executed process can be canceled.

  According to the present invention, a transaction management system, a transaction management method, and a transaction management program for supporting an efficient response to an error occurring in a part of processing when a plurality of processes are executed in cooperation with each other. Can be provided.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each information storage part of embodiment of this invention, (a) is a cooperation information storage part, (b) is a transaction management information storage part, (c) is an error information storage part. Explanatory drawing of the recorded data. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that each transaction is executed by individual processing combining a plurality of processes in response to a transaction request.

As shown in FIG. 1, here, a transaction terminal 10, a transaction common system 20, and a service management server 30 connected via a network are used.
Transaction terminal 10 includes output means such as a display and input means such as a keyboard and a pointing device.

  The transaction terminal 10 is a computer terminal that transmits a transaction message input by a transaction representative. As the transaction terminal 10, for example, a front terminal installed at a store can be used. The transaction terminal 10 records a transaction type code, a customer code, and transaction contents in a transaction information storage unit (not shown) for the transaction message. And the transaction terminal 10 transfers this transaction message to the transaction common system 20 via a network. Moreover, the transaction terminal 10 outputs the transaction response message received from the transaction common system 20 to the output means.

  The common transaction system 20 is a computer device that specifies necessary individual processing based on the contents of a transaction message and transmits a processing request message to the service management server 30 that executes the individual processing. Here, when it is necessary to execute a subsequent individual process according to the contents of the transaction message, the control unit 21 newly generates a process request message and transmits it to the service management server 30 that executes this individual process. . Then, when all the individual processes corresponding to the transaction message are completed, a transaction response message corresponding to the transaction message is returned to the transaction terminal 10.

The common transaction system 20 includes a control unit 21, a linkage information storage unit 22, a transaction management information storage unit 24, an error information storage unit 26, and a cancellation execution routine storage unit 28.
The control unit 21 includes control means (CPU, RAM, ROM, etc.). And this control part 21 performs the process (each process of a transaction flow management stage, an exception process execution stage, etc.) mentioned later. By executing a transaction management program for this purpose, the control unit 21 functions as each unit such as a transaction flow management unit 211 and an exception process execution unit 212 as shown in FIG.

  The transaction flow management unit 211 functions as an application execution unit, and executes various processes for performing a transaction in response to a transaction message received from the transaction terminal 10 based on the transaction application. Specifically, the transaction flow management unit 211 activates the transaction execution unit A1 and the flow cancellation unit A2 to execute various processes. The transaction execution means A1 specifies a transaction flow necessary for performing the transaction, and executes a process of transmitting a processing request message to the service management server 30 that performs a transaction process (individual processing) included in the transaction flow. On the other hand, when a business error is detected in the individual processing executed in the service management server 30, the flow canceling means A2 performs processing for canceling the executed individual processing.

  The exception process execution unit 212 functions as a management unit that monitors the transaction flow management unit 211. When a system error occurs in the transaction flow management unit 211, the exception process execution unit 212 starts the cancellation execution unit B1 that cancels the executed individual process. To do. Here, rollback cancellation processing is executed in a system environment (execution environment) in which the transaction application is executed.

  As shown in FIG. 2A, a cooperation management record 220 for specifying individual processing to be performed in cooperation with each other in order to realize a transaction message transaction is recorded in the cooperation information storage unit 22. This cooperation management record 220 is recorded when an individual process necessary for the transaction is registered. In the cooperation management record 220, data related to transaction types and processing types is recorded.

In the transaction type data area, data relating to an identifier for specifying the transaction type in the transaction message is recorded.
In the process type data area, data relating to an identifier for specifying the process type of the individual process necessary for completing the transaction of the transaction message is recorded. Here, it records so that the order which performs an individual process can be specified.

  The transaction management information storage unit 24 functions as an execution information storage unit. In the transaction management information storage unit 24, as shown in FIG. 2B, a transaction management record 240 for managing the transaction message received from the transaction terminal 10 is recorded. This transaction management record 240 is registered when a transaction message is received from the transaction terminal 10. In the transaction management record 240, data relating to a transaction message code, message reception date and time, transaction type, transaction content, and transaction result is recorded. Further, in the transaction management record 240, data regarding the processing result is recorded for the processing type.

Data relating to an identifier for identifying each transaction message is recorded in the transaction message code data area.
Data related to the date and time when this transaction message is received is recorded in the message reception date and time data area.

In the transaction type data area, data relating to an identifier for specifying the transaction type in the transaction message is recorded.
In the transaction content data area, data relating to the details of the transaction in the transaction message is recorded. This transaction content includes data relating to the transaction amount.

  In the transaction result data area, data relating to the final result of the transaction in this transaction message is recorded. In the present embodiment, when the transaction is completed, a completion flag is recorded. On the other hand, when an error occurs and the transaction cannot be completed, an error flag is recorded.

In the process type data area, data relating to an identifier for specifying the process type of the individual process performed in cooperation with each other is recorded based on this transaction message.
In the processing result data area, data related to the processing result for the individual processing is recorded. In the present embodiment, when the individual processing of this processing type is completed, a completion flag (individual processing completion information) is recorded. When an individual process is canceled in response to the occurrence of an error, a cancellation flag is recorded.

  In the error information storage unit 26, as shown in FIG. 2 (c), an error management record 260 regarding an error that has occurred in the individual processing performed based on the transaction message is recorded. This error management record 260 is registered when error information is acquired from the service management server 30 that performed the individual processing in which the error occurred. In the error management record 260, data related to a transaction message code, error occurrence date / time, processing type, error code, and error details are recorded.

In the transaction message code data area, data relating to an identifier for identifying a transaction message in which an error has occurred is recorded.
In the error occurrence date and time data area, data related to the date and time when the error occurred is recorded.

In the process type data area, data relating to an identifier for specifying an individual process in which an error has occurred is recorded.
In the error code data area and the error detailed data area, an identifier for specifying the content of the error that has occurred and data relating to the detailed content are recorded.

  The cancellation execution routine storage unit 28 stores a program (cancellation execution routine) used in rollback cancellation. By calling this cancellation execution routine, the cancellation execution means B1 can be activated. In the cancellation execution routine storage unit 28, a cancellation execution routine is recorded for each processing type.

  The service management server 30 functions as an execution device, and is a computer device (for example, a host computer) that executes each individual process necessary for responding to a processing request message. The individual processing in each service management server 30 includes, for example, sales management for each branch, customer information file management (CIF) for each customer, account management, and the like.

  The service management server 30 executes individual processing according to the processing type based on the processing request message received from the transaction common system 20. In this case, there are a case where the processing ends normally and an case where an error occurs. Then, the service management server 30 returns a processing result message including the processing result of the individual processing based on the processing request message. The processing result message includes data related to the transaction message code and the processing type. Furthermore, when the individual processing is normally completed without causing an error, a completion message is included as a processing result in the processing result message. On the other hand, if an error is detected and the individual processing cannot be completed normally, an error message is included as a processing result in the processing result message. This error message includes an error code for specifying the error content and data related to the details.

  In addition, when the service management server 30 receives a cancellation request message from the transaction common system 20, the service management server 30 cancels the individual processing performed in the transaction message code included in the cancellation request message and returns to the state before the transaction ( Execute rollback processing.

  The service management server 30 includes a transaction log storage unit 32. In the transaction log storage unit 32, an execution history (transaction log) for an individual process executed corresponding to the process request message is recorded. In this transaction log, data relating to processing contents and processing results is recorded in association with the transaction message code.

(Overview of flow cancellation)
First, the outline of the flow cancellation will be described with reference to FIG.
The control unit 21 of the transaction common system 20 that has received the transaction message from the transaction terminal 10 activates the transaction execution means A1 with an application corresponding to the transaction message.

  This transaction execution means A1 sequentially specifies the process types recorded in the cooperation information storage unit 22, and requests execution of individual processes of this process type. Here, as shown in FIG. 3, it is assumed that the transaction flow is executed in the order of the transaction processes (S11, S12, S13,...) Included in the transaction flow. Therefore, the transaction execution means A1 sequentially transmits to the service management server 30 processing request messages of processing types corresponding to the transaction processes (S11, S12, S13,...) Included in the transaction flow. In this case, the service management server 30 performs individual processing corresponding to the processing request message. Here, in the service management server 30, individual processes (S31, S32, S33,...) Corresponding to the transaction processes (S11, S12, S13,...) Included in the transaction flow are performed.

And transaction execution means A1 records a processing result in transaction management information storage part 24 based on a processing result message received from service management server 30.
Here, when a business error is detected in the processing result message, the transaction execution unit A1 takes over the processing to the flow cancellation unit A2 in order to execute the cancellation process S1n by the application. In this case, the flow cancellation unit A2 uses the transaction management information storage unit 24 to identify the executed individual process. Then, the flow cancellation unit A2 executes a cancellation request message creation process S41, a message transmission process S42, and a cancellation result confirmation process S43 as a cancellation flow.

  In this cancellation request message creation process S41, a cancellation request message for canceling an executed transaction process is created. This cancellation request message includes data regarding the transaction message code to be canceled and transaction details.

In the message transmission process S42, the created cancellation request message is transmitted to the service management server 30.
The cancellation result confirmation processing S43 confirms that the transaction process to be canceled has been canceled based on the processing result message received from the service management server 30.

(Overview of rollback cancellation)
Next, an outline of rollback cancellation when a system error occurs in an application will be described with reference to FIG.

  Also in the rollback cancellation, similarly to the flow cancellation, the transaction execution means A1 executes the transaction process (S11, S12, S13,...), And sequentially transmits processing request messages to the service management server 30. And in the service management server 30, an individual process (S31, S32, S33, ...) is performed corresponding to a transaction process (S11, S12, S13, ...).

  Here, when a system error occurs in the transaction flow management unit 211, the flow cancellation unit A2 cannot be activated. Therefore, the exception processing execution means 212 that has detected the system error activates the cancellation execution means B1. This cancellation execution means B1 uses the transaction management information storage unit 24 to specify an executed transaction process (S11, S12, S13). Next, the transaction log storage unit 32 of the service management server 30 that has executed the individual processing in the transaction process is accessed to acquire the transaction log. And cancellation execution means B1 performs cancellation processing (S51, S52, S53) for canceling individual processing corresponding to the executed individual processing (S33, S32, S31) based on this transaction log. .

Next, a procedure for performing a transaction in the system configured as described above will be described with reference to FIGS.
(Transaction processing)
First, the transaction management process will be described with reference to FIG.
Here, the control unit 21 of the transaction common system 20 executes transaction flow definition processing (step S1-1). Specifically, when a transaction is performed at a store, the person in charge of transaction inputs transaction information to the transaction terminal 10. When the input is completed, the transaction terminal 10 transmits a transaction message to the transaction common system 20. This transaction message includes data relating to the transaction type, customer code, and amount. The transaction flow management means 211 of the control unit 21 of the transaction common system 20 that has received the transaction message from the transaction terminal 10 gives the transaction message code, obtains the current date and time from the system timer, and obtains the transaction message code and the message reception date and time. A recorded transaction management record 240 is generated. Further, the transaction management record 240 includes data regarding the transaction type and transaction content (transaction amount). Then, the transaction flow management unit 211 records the generated transaction management record 240 in the transaction management information storage unit 24.
Furthermore, the transaction flow management unit 211 specifies the cooperation management record 220 recorded in the cooperation information storage unit 22 based on the transaction type included in the transaction message.

  Next, the control part 21 of the transaction common system 20 performs the specific process of the individual process of execution object (step S1-2). Specifically, the transaction flow management unit 211 of the control unit 21 uses this cooperation management record 220 to specify the processing type of individual processing necessary for realizing the transaction of the transaction message, and this transaction type is changed to the transaction. Record in the management record 240. Then, the transaction flow management means 211 generates a processing request message for individual processing. The processing request message includes a transaction message code and data related to transaction contents.

  Next, the control unit 21 of the transaction common system 20 executes processing request transmission processing (step S1-3). Specifically, the transaction flow management unit 211 of the control unit 21 transmits the generated processing request message to the service management server 30. Here, the process request messages are transmitted in the order of the individual processes recorded in the cooperation management record 220.

  The service management server 30 that has received the processing request message executes individual processing based on the processing request message. Then, the service management server 30 returns a processing result message including the processing result of the individual processing to the transaction common system 20. This processing result message includes data related to a transaction message code, a processing type, and a processing result (completion message or error message).

  Next, the control part 21 of the transaction common system 20 performs the recording process of the execution result of transaction flow (step S1-4). Specifically, the transaction flow management unit 211 of the control unit 21 records the processing result corresponding to the processing type in the transaction management record 240 based on the processing result message received from the service management server 30.

  Next, the control part 21 of the transaction common system 20 performs the determination process about whether the error generate | occur | produced (step S1-5). Specifically, the transaction flow management unit 211 of the control unit 21 determines an error when an error message is included as a processing result in the processing result message.

  Here, when it is determined that the processing result includes a completion message as a processing result and no error has occurred (in the case of “NO” in step S1-5), the control unit 21 of the transaction common system 20 Then, a determination process is executed as to whether all the individual processes have been completed (step S1-6). Specifically, the transaction flow management unit 211 of the control unit 21 determines whether all individual processes have been completed based on the processing results recorded in the transaction management record 240 of the transaction management information storage unit 24. . Here, when processing results are recorded for all processing types, the transaction flow management unit 211 determines that all individual processing has been completed.

  When it is determined that all the individual processes have been completed (in the case of “YES” in step S1-6), the control unit 21 of the transaction common system 20 records a completion flag in the transaction result data area of the transaction management record 240, A transaction response message is transmitted to the transaction terminal 10 to end the transaction process. This transaction response message includes a message indicating that the transaction has been completed.

  On the other hand, if it is determined that there are processing types for which no processing result is recorded and that all individual processing has not been completed (in the case of “NO” in step S1-6), the control unit 21 of the transaction common system 20 Are repeated from the process of step S1-2. In this case, in the process type in which the process result is not recorded in the transaction management record 240, the process request message of the next process type in the order is transmitted to the service management server 30.

  In addition, when it is determined that an error message has been included as a processing result in the processing result message and an error has occurred (in the case of “YES” in step S1-5), the control unit 21 of the transaction common system 20 determines a business error. Execute flow cancellation processing based on. Here, the control part 21 of the transaction common system 20 performs the calling process of the execution result of transaction flow (step S1-7). Specifically, the transaction flow management unit 211 of the control unit 21 takes over the process to the flow cancellation unit A2. This flow canceling means A2 acquires the current date and time from the system timer and generates an error management record 260 set as the error occurrence date and time. The error management record 260 includes a transaction message code, a process type, an error code, and error details based on the error message of the process result message received from the service management server 30. Then, the flow cancellation unit A2 registers the generated error management record 260 in the error information storage unit 26.

  Next, the flow canceling means A2 extracts from the transaction management information storage unit 24 a transaction management record 240 in which an individual processing transaction message code in which an error has occurred is recorded. Then, the flow canceling means A2 records an error flag in association with the processing type in the transaction management record 240.

  Next, the control part 21 of the transaction common system 20 performs the specific process of the individual process of cancellation object (step S1-8). Specifically, the flow canceling means A2 of the control unit 21 specifies the process type in which the completion flag is recorded in the transaction management record 240 as the individual process to be canceled. Here, the individual process to be canceled is specified in the reverse order of the order in which the individual processes were executed in the original transaction.

  Next, the control part 21 of the transaction common system 20 performs the cancellation request transmission process (step S1-9). Specifically, the flow cancellation unit A2 of the control unit 21 generates a cancellation request message for canceling the individual processing of the specified processing type, and transmits it to the service management server 30. This cancellation request message includes information (transaction message code, transaction type, transaction content, etc.) for specifying the individual processing to be canceled.

  Next, the control part 21 of the transaction common system 20 performs cancellation response acquisition processing (step S1-10). Specifically, the service management server 30 that has received the cancellation request executes cancellation processing of individual processing corresponding to the transaction message code. Then, the service management server 30 returns a cancellation response message including the result of the cancellation process to the transaction common system 20. The flow cancellation means A2 of the control unit 21 of the transaction common system 20 receives a cancellation response message for the cancellation request message from the service management server 30. In this case, the flow cancellation means A2 records a cancellation flag in the transaction management record 240 in association with the canceled processing type.

  Next, the control part 21 of the transaction common system 20 performs the determination process about whether it canceled all (step S1-11). Specifically, the flow cancellation means A2 of the control unit 21 determines that all of the transaction management records 240 have been canceled when there is no remaining processing type in which the completion flag is recorded.

  If it is determined that all have been canceled (“YES” in step S1-11), the control unit 21 of the transaction common system 20 records an error flag in the transaction result data area of the transaction management record 240, and the transaction A transaction response message is transmitted to the terminal 10 to end the transaction process. This transaction response message includes a message indicating that the transaction could not be completed due to a business error.

  On the other hand, when it is determined that the processing type in which the completion flag is recorded remains and all cancellations are not completed (in the case of “NO” in step S1-11), the control unit 21 of the transaction common system 20 The process from step S1-8 is repeated.

(Rollback cancellation processing)
Next, rollback cancellation processing will be described with reference to FIG. This process is executed when the exception process execution unit 212 detects a system error in the transaction flow management unit 211.

  First, the control unit 21 of the transaction common system 20 executes execution record acquisition processing (step S2-1). Specifically, the exception process execution unit 212 of the control unit 21 extracts from the transaction management information storage unit 24 a transaction management record 240 in which a transaction message code in which an error has occurred is recorded. Next, the exception process execution unit 212 records an error flag as a process result in the transaction management record 240 in association with the process type. Then, the exception process execution unit 212 identifies the process type in which the completion flag is recorded in the transaction management record 240 as the flow information to be canceled.

  Next, the control part 21 of the transaction common system 20 performs the specific process of the individual process of cancellation object (step S2-2). Specifically, the exception process execution unit 212 of the control unit 21 specifies the process type in which the completion flag is recorded in the transaction management record 240 as the individual process to be canceled. Here, the individual process to be canceled is specified in the reverse order of the order in which the individual processes were executed in the original transaction.

  Next, the control part 21 of the transaction common system 20 performs the calling process of cancellation execution routine (step S2-3). Specifically, the exception process execution unit 212 of the control unit 21 calls a cancellation execution routine corresponding to the specified processing type of the individual process to be canceled from the cancellation execution routine storage unit 28. Then, the exception processing execution unit 212 activates the cancellation execution unit B1 by the called cancellation execution routine.

  In this case, the control unit 21 of the transaction common system 20 executes transaction log acquisition processing (step S3-1). Specifically, the cancellation execution unit B1 of the control unit 21 accesses the service management server 30 that executes the individual processing of the processing type to be canceled, and the transaction log associated with the transaction message code from the transaction log storage unit 32. To get.

  Next, the control part 21 of the transaction common system 20 performs cancellation processing (step S3-2). Specifically, the cancellation execution unit B1 of the control unit 21 generates a cancellation request message for canceling the individual processing based on the acquired transaction log, and transmits the cancellation request message to the service management server 30. This cancellation request message includes information (transaction message code, transaction type, transaction content, etc.) for specifying the individual processing to be canceled.

  Next, the control part 21 of the transaction common system 20 performs the output process of a cancellation result (step S3-3). Specifically, the service management server 30 that has received the cancellation request executes cancellation processing of individual processing corresponding to the transaction message code. Then, the service management server 30 returns a cancellation response message including the result of the cancellation process to the transaction common system 20. The transaction common system 20 receives a cancellation response message for the cancellation request message from the service management server 30 and outputs a cancellation result to the exception processing execution unit 212.

  Next, the control unit 21 of the transaction common system 20 executes a cancellation result acquisition process (step S2-4). Specifically, the exception process execution unit 212 of the control unit 21 records a cancel flag as a process result in the transaction management record 240 in association with the canceled process type.

  Next, the control part 21 of the transaction common system 20 performs the determination process about whether it canceled all (step S2-5). Specifically, the exception process execution unit 212 of the control unit 21 determines that all have been canceled when there is no process type in which the completion flag is recorded in the transaction management record 240.

  Here, when it is determined that all have been canceled (in the case of “YES” in step S2-5), the control unit 21 of the transaction common system 20 executes a system error notification process (step S2-6). Specifically, the exception process execution unit 212 of the control unit 21 records an error flag in the transaction result data area of the transaction management record 240, transmits a transaction response message to the transaction terminal 10, and ends the transaction process. . This transaction response message includes a message indicating that the transaction could not be completed due to a system error.

  On the other hand, when it is determined that the processing type in which the completion flag is recorded remains and all the cancellations are not completed (in the case of “NO” in step S2-5), the control unit 21 of the transaction common system 20 The process from step S2-3 is repeated.

As described above, according to the present embodiment, the following effects can be obtained.
(1) According to the present embodiment, when a processing result message contains an error message as a processing result and it is determined that an error has occurred (in the case of “YES” in step S1-5), the transaction common system 20 The control unit 21 executes a flow cancellation process based on a business error. Here, the control unit 21 of the transaction common system 20 calls the transaction flow execution result calling process (step S1-7), the individual process to be canceled (step S1-8), and the cancellation request transmission process (step S1-7). S1-9) is executed. Thereby, when a business error occurs, the executed individual processing can be canceled and the original state can be efficiently restored.

  (2) According to this embodiment, the control part 21 of the transaction common system 20 performs a rollback cancellation process, when a system error is detected. Thereby, even when the flow cancellation cannot be executed by the application (transaction flow management means 211), the executed individual processing can be canceled and the original state can be efficiently restored.

  (3) According to the present embodiment, in the rollback cancellation process, the control unit 21 of the transaction common system 20 executes a calling process of a cancellation execution routine (step S2-3). And the control part 21 uses the cancellation execution routine of the process type of cancellation object, transaction log acquisition process (step S3-1), cancellation process (step S3-2), and output process (step S3- 3) is executed. Thereby, the executed individual processing can be canceled using the function provided in the execution environment of the application.

(4) According to this embodiment, the control part 21 of the transaction common system 20 performs the flow cancellation process based on a business error. Moreover, the control part 21 performs a rollback cancellation process, when a system error is detected. As a result, the system operator can return to the state before the transaction without performing the subsequent operation.
Moreover, in the transaction common system 20, since it cancels based on the information currently recorded on the transaction management information storage part 24, it can be reused by preparing one general purpose flow cancellation means A2. System development efficiency and maintainability can be improved.
On the other hand, in the service management server 30, there is no difference between flow cancellation and rollback cancellation, and cancellation can be performed without performing customization according to each cancellation.

In addition, you may change the said embodiment as follows.
In the above embodiment, the control unit 21 of the transaction common system 20 executes the individual process specific process (steps S1-8 and S2-2) to be canceled. In this case, the processing type for which the completion flag is recorded in the transaction management record 240 identifies the individual processing to be canceled in the reverse order of the order in which the individual processing was executed in the original transaction. The method for specifying the cancellation order is not limited to the method using the transaction management record 240. For example, it is also possible to specify the transaction type and specify the cancellation order using the cooperation management record 220 recorded in the cooperation information storage unit 22.

  In the above embodiment, the flow cancel process is executed for a business error, and the rollback cancel process is executed for a system error. Here, any cancellation processing may be executed according to the content of the error. In this case, the control unit 21 holds information for determining a cancellation method (flow cancellation or rollback cancellation) according to the error code and the error content.

  -In above-mentioned embodiment, in rollback cancellation, the control part 21 of the transaction common system 20 performs the specific process of the individual process of cancellation object (step S2-2). Here, whether to execute rollback cancellation may be determined according to the processing type. In this case, the control unit 21 holds a rollback cancellation condition for determining whether or not rollback cancellation can be executed. Further, whether or not rollback cancellation can be executed may be determined according to the operating status of the service management server 30. In this case, the operating status of the service management server 30 is set in the rollback cancellation condition. Then, before executing the rollback cancellation process, the operation status information of the service management server 30 is acquired, and whether or not execution is possible is determined based on the rollback cancellation condition.

  In the above embodiment, in rollback cancellation, the control unit 21 of the transaction common system 20 executes transaction log acquisition processing (step S3-1) and cancellation processing (step S3-2). Instead, the service management server 30 may call the transaction log and cancel it. In this case, the control unit 21 of the transaction common system 20 specifies an executed individual process (cancellation target) based on the transaction management record 240 recorded in the transaction management information storage unit 24. And the control part 21 transmits cancellation instruction | indication to the service management server 30 which performed this individual process. Receiving the cancellation instruction, the service management server 30 cancels the transaction for the individual process to be canceled. Thereby, it is possible to cancel the transaction for the individual processing executed in a server different from the transaction common system 20.

  In the above embodiment, the control unit 21 of the transaction common system 20 executes the flow cancellation process and the rollback cancellation process. Here, additional processing may be added after each cancellation processing. For example, as an additional process, a log of automatic cancellation (flow cancellation processing or rollback cancellation processing) may be recorded so that it can be distinguished from other cancellation logs. In addition, additional processing may be executed only when cancellation of specific individual processing is detected. Further, when the exception processing execution unit 212 cancels the rollback, the transaction flow management unit 211 may be restarted as an additional process.

In the above embodiment, the control unit 21 of the transaction common system 20 executes the flow cancellation process and the rollback cancellation process. Here, when the automatic cancellation processing of the flow cancellation processing or rollback cancellation processing fails, manual cancellation is performed. In this case, the control unit 21 of the transaction common system 20 may perform a manual cancellation support process so that the manual cancellation can be efficiently performed. For example, information for this manual cancellation is output on the display. This information includes manual cancellation targets and procedures.
Further, in the transaction common system 20, a table in which processing types that can be manually canceled can be stored, and information indicating whether or not manual cancellation can be included in the processing types in which the automatic cancellation processing has failed may be included.

  DESCRIPTION OF SYMBOLS 10 ... Transaction terminal, 20 ... Transaction common system, 21 ... Control part, 211 ... Transaction flow management means, 212 ... Exception processing execution means, A1 ... Transaction execution means, A2 ... Flow cancellation means, B1 ... Cancel execution means, 22 ... Cooperation information storage unit, 24 ... transaction management information storage unit, 26 ... error information storage unit, 28 ... cancellation execution routine storage unit, 30 ... service management server.

Claims (4)

A control unit connected to a transaction terminal and an execution device that executes individual processing for transaction;
A cooperative information storage unit storing information on a plurality of individual processes performed in cooperation for transactions;
An execution information storage unit that records completion information of individual processing executed in response to the transaction message received from the transaction terminal ;
A transaction management system comprising a management unit that monitors an execution status of an application execution unit that executes a linked application that executes a linked process recorded in the linked information storage unit ;
The control unit is
With the cooperation application corresponding to the transaction message received from the transaction terminal, start the application execution means for executing the individual processing,
When the application execution unit transmits the processing request for the individual processing sequentially to the execution device for the individual processing specified in the cooperation information storage unit by the cooperation application, and completes the individual processing, Recording completion information about the individual processing in the execution information storage unit,
When the application execution unit detects an error in some of the individual processes of the cooperation process that combines a plurality of individual processes , the cooperation application performs an executed individual process in which completion information is recorded in the execution information storage unit. Identify, execute a flow cancellation process that sequentially generates a cancellation request message for canceling the executed individual process in the cooperation process, and transmits it to the execution device ;
When the management unit detects a system error in the cooperative application being executed by the application execution unit, the completion information of the individual processing is acquired from the execution information storage unit,
Based on the completion information, start cancel execution means for canceling the executed individual processing,
The transaction management system, wherein the cancel execution unit is used to execute a rollback cancellation process of the executed individual process .   2. The transaction management system according to claim 1, wherein when executing the cancellation processing of the executed individual processing, the cancellation processing of each individual processing is executed in the reverse order of the execution order of the executed individual processing. . A control unit connected to a transaction terminal and an execution device that executes individual processing for transaction;
A cooperative information storage unit storing information on a plurality of individual processes performed in cooperation for transactions;
An execution information storage unit that records completion information of individual processing executed in response to the transaction message received from the transaction terminal ;
A method for managing a transaction using a transaction management system including a management unit that monitors an execution status of an application execution unit that executes a linked application that executes a linked application recorded in the linked information storage unit. And
The control unit is
With the cooperation application corresponding to the transaction message received from the transaction terminal, start the application execution means for executing the individual processing,
When the application execution unit transmits the processing request for the individual processing sequentially to the execution device for the individual processing specified in the cooperation information storage unit by the cooperation application, and completes the individual processing, Recording completion information about the individual processing in the execution information storage unit,
When the application execution unit detects an error in some of the individual processes of the cooperation process that combines a plurality of individual processes , the cooperation application performs an executed individual process in which completion information is recorded in the execution information storage unit. Identify, execute a flow cancellation process that sequentially generates a cancellation request message for canceling the executed individual process in the cooperation process, and transmits it to the execution device ;
When the management unit detects a system error in the cooperative application being executed by the application execution unit, the completion information of the individual processing is acquired from the execution information storage unit,
Based on the completion information, start cancel execution means for canceling the executed individual processing,
A transaction management method , wherein rollback cancellation processing of the executed individual processing is executed using the cancellation execution means . A control unit connected to a transaction terminal and an execution device that executes individual processing for transaction;
A cooperative information storage unit storing information on a plurality of individual processes performed in cooperation for transactions;
An execution information storage unit that records completion information of individual processing executed in response to the transaction message received from the transaction terminal ;
A program for managing transactions using a transaction management system including a management unit that monitors an execution status of an application execution unit that executes a linked application that executes a linked application recorded in the linked information storage unit. And
The control unit
With the cooperation application corresponding to the transaction message received from the transaction terminal, start the application execution means for executing the individual processing,
When the application execution unit transmits the processing request for the individual processing sequentially to the execution device for the individual processing specified in the cooperation information storage unit by the cooperation application, and completes the individual processing, Recording completion information about the individual processing in the execution information storage unit,
When the application execution unit detects an error in some of the individual processes of the cooperation process that combines a plurality of individual processes , the cooperation application performs an executed individual process in which completion information is recorded in the execution information storage unit. Identify, execute a flow cancellation process that sequentially generates a cancellation request message for canceling the executed individual process in the cooperation process, and transmits it to the execution device ;
When the management unit detects a system error in the cooperative application being executed by the application execution unit, the completion information of the individual processing is acquired from the execution information storage unit,
Based on the completion information, start cancel execution means for canceling the executed individual processing,
A transaction management program that functions as means for executing rollback cancellation processing of the executed individual processing using the cancellation execution means .

Images