JP2008276641A - Business process management method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for preventing deterioration of overall performance of a system, and for reducing costs by reducing frequency of occurrence of such an event that a BP is canceled after a service enters a cancellation-prohibited state. <P>SOLUTION: In a business process management method and system, a period (Tc) when a cancellation request is accepted is calculated on the basis of an expected value of cancellation costs of a service and costs for the service to maintain a cancellation-permitted state, and cancellation processing is provided by the service during that period. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technology for business process management in cooperation between companies such as finance, distribution, and industry or between companies, and more particularly, to service cancellation processing.

  In a method and system for managing a business process (abbreviated as BP) designed by a business designer, when a BP is canceled due to a failure or the like, a compensation transaction is often used. The compensation transaction is to execute a cancel process for canceling the effect of the service (abbreviated as SV) executed by the BP execution. For example, when depositing 10,000 yen by account management, the balance is reduced by 10,000 yen, and the history of deposit is also deleted.

Non-patent documents 1 and 2 describe the above-described technology.
WS-Transaction specification, <URL: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnglobspec/html/ws-transaction.asp>, 2002 SOA Encyclopedia, Dirk Kraftzick, 2005, Nikkei Business Publications

  Conventionally, when canceling a BP using a compensation transaction, if a corresponding update process is canceled after a certain update process transitions from a cancelable state to a cancelable state, there is no choice but to deal with the operation. Could be enormous. A solution to this problem is that the service remains in a cancelable state until the BP management system notifies each service of the completion of BP. However, in this case, until the service obtains the notification of the BP management server, the service will be in a standby state indefinitely, and other BP processes cannot be executed.

  The present invention has been made in view of the above problems, and its purpose is to reduce the number of times that an event of canceling a BP (canceling a service) after the service transitions to a non-cancelable state occurs. An object of the present invention is to provide a technology capable of preventing the performance of the entire system from being lowered and reducing the cost.

  Of the inventions disclosed in the present application, the outline of typical ones will be briefly described as follows. In order to achieve the above object, the present invention is a BP management technique for calling a service that executes a business in accordance with a BP indicating a series of business operations on one or more computers, and has the following configuration. It is characterized by that.

  In the present BP management method and system, based on the expected value of the service cancellation cost (first expected value: E1) and the cost for maintaining the service in a cancelable state (first cost: C1) Then, a first time limit (cancellation time limit: Tc) for receiving a cancel request (service cancel processing) is calculated, and the service provides a cancel processing during the time limit (Tc).

  The system includes, for example, a first means for setting and managing a first time limit (Tc) and a second means for locking the data updated or referred to by the corresponding process until the first time limit (Tc) elapses. When the service and the service cancellation request are received, it is determined whether or not the cancellation process of the service can be executed according to the determination of the elapse of the first time limit (Tc), and the first time limit (Tc) has not elapsed. And a third means for executing the cancellation process of the service. Further, the first means calculates (estimates) the cost for canceling the business process by adding E1 and C1, and sets the first time limit so that the cost is minimized.

  Among the inventions disclosed in the present application, effects obtained by typical ones will be briefly described as follows. According to the present invention, it is possible to reduce the number of times of occurrence of an event that a BP is canceled after the service transitions to a non-cancelable state, to prevent a decrease in performance of the entire system, and to reduce costs.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

<Prerequisite technology>
First, details of the premise technique and problems for the present invention are as follows. In the compensation transaction, there is a problem that inconsistency may occur when there is a reference or update process for the same resource between a method call and cancellation. An example is shown in FIG.

  In FIG. 16, a product order reception BP (first BP) 101 which is a BP for receiving product orders, an order form management service (first SV) 102 which is a service for managing an order form, and the cost for purchasing a product from a customer account. It has an account withdrawal service (second SV) 103 that is a withdrawal service, and a product ordering BP (second BP) 104 that is a BP for ordering products. The product order reception BP (first BP) 101 registers the order form in the order form management service (first SV) 102 (execution of the first SV), and the account withdrawal service (second SV) 103 performs processing (account withdrawal). Is requested (second SV request). On the other hand, the product ordering BP (second BP) 104 operating separately orders the product based on the registered order form. An example of a processing sequence when a problem occurs under such a premise is shown. Hereinafter, S represents a processing step.

  In this example, in S161, the merchandise order reception BP (first BP) 101 registers, for example, an order slip having contents (x = x + 10) for purchasing ten items in the order slip management service (first SV) 102. In S162 and S163, the product order BP (second BP) 104 refers to the data of the order form from the order form management service (first SV) 102 (commodity number reference request and result response (x = 10)). .

  Under this circumstance, in S164 and S165, the processing of the account withdrawal service (second SV) 103 that received the processing request (account withdrawal request) from the product order acceptance BP (first BP) 101 fails (failure response), and in S166. Consider a case where it is desired to cancel the merchandise order acceptance BP (first BP) 101 (that is, cancel the first SV). In S166, a cancel request (service cancellation process) of the content (x = x-10) of canceling the purchase of the ten products from the product order reception BP (first BP) 101 to the order form management service (first SV) 102 Request). However, if the cancel process is executed in the first SV 102, a contradiction occurs in the second BP 104 (in other words, after the second BP 104 is executed). Therefore, the cancel process cannot be executed, and a cancel impossible response is returned in S167. become.

  When the above situation occurs, the current situation (conventional) has to be dealt with by operation, and the cost for canceling the BP becomes enormous. Here, the handling in the operation means the handling including the viewpoint of the business such as the handling that is closed to the system administrator, such as the service manager modifying the database directly, or the orderer of the product order pays the penalty. Etc.

  The above problem occurs when cancel processing is executed in a situation where a plurality of BPs simultaneously execute the same service as shown in FIG. Here, a state in which the service can accept a cancel request is referred to as a “cancelable state”, and a state in which the service cannot accept a cancel request is referred to as a “cancelable state”. For example, in the example of FIG. 16, for the first SV 102 for the first BP 101, the cancelable state corresponds to before the second BP 104 is executed (before S163), and the cancelable state is after the second BP 104 is executed (after S163). ).

  As a solution to the above-described problem, there is a method in which data reference by another BP and processing that cannot be canceled (update processing) are not performed until it is confirmed that a cancel request is not generated. For example, until the BP informs the service that no cancel request is issued, the process that disables the service is not executed. This method has the same idea as the two-phase commit protocol. However, with this method, until the service obtains the notification from the BP, the service will be in a standby state indefinitely, and the processing of other BPs cannot be executed, so that the performance of the entire system may be deteriorated.

<Embodiment>
Based on the above, a BP management system according to an embodiment of the present invention will be described with reference to FIGS. In this embodiment, the service provides cancellation processing with a time limit, thereby reducing the number of occurrences of the event that the BP is canceled after the service transitions to the cancel disabled state while preventing the performance of the entire system from being deteriorated. . The time limit (Tc) of the cancellation process is calculated based on the expected value (E1) of the service cancellation cost and the cost (C1) for maintaining the service in a cancelable state.

<System>
FIG. 1 shows the overall configuration of the BP management system in the present embodiment. This BP management system includes a first computer (BP management server) 1 that manages and controls BP, and a second computer (service provision server) 2 that provides services, which are communication means such as a network. Connected through. This is the case of the minimum configuration, and there may be a plurality of first computers 1 and second computers 2. Although not shown in the figure, the BP management server 1 can be connected to or built in a higher-level client (client computer) that requests BP processing.

  The BP management server 1 includes a CPU 10, a main memory 11, a storage device 12, an input device 13, an output device 14, a communication I / F (interface) 15, and the like, which are connected by an internal bus or the like. The CPU 10 performs various processes by reading the program stored in the storage device 12 into the main memory 11 and executing it. Hereinafter, for the sake of simplicity, the program will be described as if it were the subject of action.

  The storage device 12 includes, as a program (processing unit), a BP control unit 201, a service cancellation cost expected value (E1) calculation unit 202, a cancellation deadline (Tc) calculation unit 203, a cancellation deadline (Tc) change unit 204, and a table. BP status management table 205 (T11), cancellation deadline (Tc) management table 206 (T12), activity (AC) transition probability management table 207 (T13), service information management table 208 (T14), information management table by BP processing flow 209 (T15) and service cancellation cost expected value (E1) management table 210 (T16) are stored.

  The BP control unit 201 controls execution of BP. The service cancellation cost expected value (E1) calculation unit 202 calculates the expected value (E1) of the cancellation cost per service normal process for each cancellation deadline (Tc). The cancellation time limit (Tc) calculation unit 203 is expected to minimize the cost generated based on the expected value (E1) of the service cancellation cost and the cost (C1) for maintaining the service in a cancelable state. An appropriate cancellation deadline (Tc) is calculated. The cancellation deadline (Tc) changing unit 204 changes (resets) the cancellation deadline (Tc) with the delay of the BP being processed as a trigger.

  The BP status management table 205 (T11) manages the progress status of BP, messages exchanged with services, and the like, and is an essential table for a general BP management system. The cancellation deadline (Tc) management table 206 (T12) manages the service deadline (Tc). The activity (AC) transition probability management table 207 (T13) manages the probability (AC transition probability) to which AC the activity being executed in the BP (abbreviated as AC) proceeds after the processing is completed. The service information management table 208 (T14) manages information related to services. The BP processing flow-specific information management table 209 (T15) manages information related to processing flows that may be executed after successful processing of the AC currently being processed. The service cancellation cost expected value (E1) management table 210 (T16) manages the service cancellation cost expected value (E1) for each cancellation deadline (Tc).

  The service providing server 2 includes a CPU 20, a main memory 21, a storage device 22, an input device 23, an output device 24, a communication I / F 25, and the like, which are connected by an internal bus or the like. The CPU 20 performs various processes by reading the program stored in the storage device 22 into the main memory 21 and executing it.

  The storage device 22 includes a service normal processing unit 211, a cancellation processing unit 212, a cancelable state maintenance cost (C1) calculation unit 213, a cancellation deadline (Tc) resetting reception unit 214, and a business as a table (processing unit). Management table 215 (T21) and lock management table 216 (T22).

  The service normal processing unit 211 executes normal processing of services provided to the BP management server 1. The cancel processing unit 212 executes a service cancel process. Cancelable state maintenance cost (C1) calculation unit 213 cancelable state maintenance cost that occurs when data is not referred to by another BP or non-cancellable processing (update processing) is not performed (maintaining the cancelable state). (C1) is calculated. The cancellation deadline (Tc) reset acceptance unit 214 accepts an extension (resetting request) of the cancellation deadline (Tc) from the BP management server 1 and resets the cancellation deadline (Tc).

  The business management table 215 (T21) manages data that the service refers to and updates as normal processing. The lock management table 216 (T22) is information for determining whether the data stored in the business management table 215 (T21) may be referred to or updated, and a message at the time of calling from the BP management server 1 Etc.

  FIG. 2 shows the mutual relationship between the respective processing units (functions) and tables in the BP management server 1 and the service providing server 2. The BP control unit 201 sends a request for calculating a cancellation deadline (Tc) to the Tc calculation unit 203, sends a request for normal service processing to the service normal processing unit 211, and sends a service cancellation request to the cancel processing unit 212. Do. The Tc calculation unit 203 requests the E1 calculation unit 202 to calculate the service cancellation cost expected value (E1), and requests the C1 calculation unit 213 to calculate the cancelable state maintenance cost (C1). The Tc changing unit 204 makes a request for E1 calculation to the E1 calculating unit 202, makes a request for calculating C1 to the C1 calculating unit 213, and makes a request for resetting the service cancellation deadline (Tc) to Tc resetting. This is performed in the reception unit 214.

  Further, the BP control unit 201 and the Tc change unit 204 use the BP status management table 205 (T11) and the Tc management table 206 (T12), respectively. The E1 calculation unit 202 uses the AC transition probability management table 207 (T13), the service information management table 208 (T14), the BP processing flow-specific information management table 209 (T15), and the E1 management table 210 (T16). Further, the service normal processing unit 211, the cancellation processing unit 212, and the Tc resetting reception unit 214 use the business management table 215 (T21) and the lock management table 216 (T22), respectively.

  In the present embodiment, the E1 calculation unit 202, the Tc calculation unit 203, the C1 calculation unit 213, and the like correspond to the first processing step and the first means in the configuration of the means for solving the problem. is there. Further, the service normal processing unit 211, the cancel processing unit 212, and the like correspond to the second and third processing steps and the second and third means.

<Example of BP processing sequence>
Next, FIG. 3 shows a processing sequence example of BP and service in this system. As in FIG. 16, a product order reception BP (first BP) 101, an order form management service (first SV) 102, an account withdrawal service (second SV) 103, and a product order BP (second BP) 104 are provided. The first BP 101 calls and executes the first SV 102 and the second SV 103 (SV request and response), while the second BP 104 operating separately calls and executes the first SV 102.

  In S101, the first BP 101 executes processing for the first SV 102 (first SV execution). At this time, a cancellation deadline (Tc) is provided and set. In S102, the second BP 104, which is another BP, tries to refer to the data of the order form from the first SV 102 (first SV request). At this time, since it is in a cancelable state where the cancellation time limit (Tc) has not elapsed, the processing of another BP is not accepted, and the content of the response fails in S103.

  In S104 and S105, the processing of the second SV 103 that has received the processing request (second SV request) from the first BP 101 has failed. In this case, it is desired to cancel the first BP 101 (cancel the first SV 102).

  As a first case of BP cancellation, a cancel request is issued from the first BP 101 to the first SV 102 in S106. At this time, the cancellation deadline (Tc) has not yet elapsed and is in a cancelable state. Therefore, the cancel process of the first SV 102 is executed, and the content of the response can be canceled in S107.

  When the cancellation time limit (Tc) has elapsed, the state changes from a cancelable state to a cancelable state. If a processing request is made from the second BP 104 to the first SV 102 in S108, since the cancellation deadline (Tc) has passed, the processing of another BP is accepted, and the content of the response is successful in S109.

  As a second case of BP cancellation, a cancel request is issued from the first BP 101 to the first SV 102 in S110. At this time, it is after the cancellation time limit (Tc) has elapsed and is in a state where cancellation is not possible. Therefore, the cancel process of the first SV 102 is not executed, and the content of the response cannot be canceled in S111.

<BP processing flow>
Next, the BP processing flow and management table in this system will be described with reference to FIG. This is a case where a service (service providing server 2) participating in BP (BP management server 1) provides a cancellation process with a cancellation deadline (Tc).

  FIG. 4 shows a processing flow when the BP management server 1 calls the service providing server 2 (requests processing) and executes the service.

  In S501, the BP management server 1 executes an inquiry about the service cancellation deadline (Tc). The BP control unit 201 selects which BP to call and generates a BP ID (BP_ID). In this example, it is assumed that the BP name BP_T is selected and “31” is generated as the BP_ID. Next, the BP control unit 201 selects a service to be called based on the defined BP, and inquires the cancellation time limit (Tc) of the corresponding service to the Tc calculation unit 203.

  Next, in S502, the BP management server 1 calculates E1 for each cancellation deadline (Tc). The Tc calculation unit 203 inquires of the E1 calculation unit 202 about the service cancellation cost for each cancellation deadline (Tc). Here, the service cancellation cost (and its expected value) is a cost (and its expected value) generated for canceling the service after normal processing of the called service is completed. The E1 calculation unit 202 calculates E1 for each cancellation deadline (Tc) and returns the result.

  FIG. 5 shows a processing flow when the E1 calculation unit 202 of the BP management server 1 calculates E1 for each cancellation deadline (Tc) in S502 of FIG. In step S601, the E1 calculation unit 202 refers to the BP status management table 205 (T11) and acquires the progress status of the BP.

  In the present embodiment, the timing for executing the activity P2 for calling the service A in the BP shown in FIG. 6 will be described as an example. In FIG. 6, P1 to P6 represent activity (AC) names, and services A to D represent service normal processing names (service names) provided by the service providing server 2, respectively. In FIG. 6, it is assumed that after the service B calling process described in activity P3, the process branches to activity P4 or activity P5.

  Next, in S602, the E1 calculation unit 202 refers to the AC transition probability management table 207 (T13) and acquires the AC transition probability.

  FIG. 7 shows the AC transition probability management table 207 (T13). Hereinafter, the AC being executed is called a caller AC, and the next selected AC is called a callee AC. T13 manages the BP name 801 that is the name of the defined BP, the caller AC name 802, the callee AC name 803, the AC transition probability 804 that is the probability of transition from the caller AC to the callee AC, and the like. To do.

  The AC transition probability 804 is statistically calculated based on the BP results executed so far, or set by the administrator of the BP management server 1. For example, in the case of the BP in FIG. 6, the probability of transition from the activity P3 that calls the service B to the activity P4 that calls the service C is 60%, and the probability that the activity P3 that calls the service B transitions to the activity P5 that calls the service D. Is 40%, the AC transition probability of the line of the caller activity P3 and the callee activity P4 is 60%, and the AC transition probability of the line of the caller activity P3 and the callee activity P5 is 40%.

  Next, in S603, the E1 calculation unit 202 refers to the service information management table 208 (T14) and acquires information about the service.

  FIG. 8 shows the service information management table 208 (T14). T14 is a service name (service name) 901, an average service processing time 902, a service processing success probability 903, a cancel execution cost 904 executed when a BP is canceled, an operation handling cost 905 executed when a BP is canceled, etc. Manage. Here, the cancel execution cost 904 is a cost converted into an amount when the cancel process is executed in a cancelable state of the service. The operation coping cost 905 is a cost converted to an amount when the service coping with the operation in order to cancel the effect of the service when the service cannot be canceled. These costs are set by the administrator of the service providing server 2. The average service processing time 902 and the processing success probability 903 are statistically calculated based on the service operation information collected so far, or set by the administrator of the BP management server 1.

  Next, in S604, the E1 calculation unit 202 calculates a BP cancellation probability for each BP processing flow. The E1 calculation unit 202 calculates the probability of occurrence of a BP process flow that may be executed after the AC process currently being processed is successful. The BP processing flow to be executed includes a BP processing flow in the case where AC processing fails and BP is canceled. In the example of BP in FIG. 6, there are five BP processing flows after calling service A, namely, BP processing flows 1001 to 1005 shown in FIG. This BP processing flow is defined in advance by the administrator of the BP management server 1.

  FIG. 9 shows the BP processing flow, the outline of the BP processing flow, and the occurrence probability of the BP processing flow corresponding to the BP in FIG. For example, the BP processing flow 1001 is in the order of P1, P2, and cancellation (P3), and the outline is that the service B call processing of the activity P3 has failed and the BP is canceled.

  The occurrence probability of the BP process flow can be calculated by (probability of success of AC before process failure AC) × (probability of transition of BP process flow to process failure AC) × (probability of failure of process failure AC). For example, the occurrence probability of the BP processing flow 1001 is 1 × 1 × (1−0.9) × 100 = 10%. Further, the probability of occurrence of the BP process flow 1002 is (probability that the process flow before P4 succeeds: 0.9) × (probability of transition to P4: 0.6) × (probability that the process of P4 fails: (1 −0.8)) × 100 = 10.8%. Similarly, the occurrence probability of the BP process flow 1003 is 0%, the occurrence probability of the BP process flow 1004 is 43.2%, and the occurrence probability of the BP process flow 1005 is 36%.

  In step S <b> 605, the E1 calculation unit 202 calculates a time zone in which a BP process flow is highly likely to occur for each BP process flow. The time zone is from the scheduled time (process scheduled start time) at which the last AC process of the BP process flow is started to the scheduled time (process scheduled scheduled time) to be completed. Here, the scheduled processing start time is calculated by the sum of the average processing time (902) of the service. For example, in the case of the BP process flow 1001, the scheduled process start time is the time when the process of the service A is completed. Here, since it is assumed that E1 is calculated in the situation where the processing of service A is completed, the scheduled processing start time is 0 minute. On the other hand, since the processing completion scheduled time is the scheduled time for completing service B, (BP processing flow scheduled starting time: 0 minutes) + (service B average processing time: 5 minutes) = 5 minutes. In the case of the BP process flow 1002, the scheduled process start time is 5 minutes because the process B is completed. The scheduled processing completion time is (BP processing flow start scheduled time: 0 minutes) + (Service C average processing time: 10 minutes) = 15 minutes. Similarly, in the case of the BP process flow 1003, the scheduled process start time is 5 minutes and the scheduled process completion time is 25 minutes. In the case of the BP processing flow 1004, the scheduled process start time is 15 minutes and the scheduled process completion time is 15 minutes. In the case of the BP process flow 1005, the scheduled process start time is 25 minutes and the scheduled process completion time is 25 minutes.

  Next, in S606, the E1 calculation unit 202 collects the results of S604 and S605, and generates a BP processing flow-specific information management table 209 (T15).

  FIG. 10 shows the BP processing flow-specific information management table 209 (T15). T15 includes BP name 1101, BP_ID 1102, processing AC name 1103, BP processing flow 1104, (BP processing flow) occurrence probability 1105, (BP processing flow) scheduled processing start time 1106, (BP processing flow) scheduled processing completion time 1107. Manage, etc. The BP name 1101, the BP_ID 1102, and the processing AC name 1103 are acquired at the time of inquiry from the BP control unit 201. The BP processing flow 1104 and the occurrence probability 1105 are acquired and calculated when S604 is executed. The scheduled process start time 1106 and the scheduled process completion time 1107 are calculated when S605 is executed.

  In step S <b> 607, the E1 calculation unit 202 cancels the cancellation deadline (Tc) based on the occurrence probability 1105 of the BP processing flow, the scheduled processing start time 1106, the scheduled processing completion time 1107, the cancel execution cost 904, and the operation handling cost 905. Calculate another E1. E1 is an expected value of the cancellation cost per normal process of the corresponding service. This varies depending on the cancellation deadline (Tc) provided by the service. The longer Tc is, the lower the probability of canceling BP after Tc elapses, so that the expected cancellation cost is reduced.

  The cancellation deadline (Tc) candidate for calculating E1 is the time stored in the scheduled processing start time 1106 and the scheduled processing completion time 1107. Hereinafter, a candidate for the cancellation deadline (Tc) is referred to as a cancellation deadline (Tc) candidate value. In the example of BP in FIG. 6, there are four types of Tc candidate values: 0 minutes, 5 minutes, 15 minutes, and 25 minutes.

  First, for each Tc candidate value, the probability of canceling BP before the lapse of Tc (pre-Tc BP cancellation probability) and the probability of canceling the BP after the lapse of Tc (post-Tc BP cancellation probability) are calculated. This is the sum of the AC BP cancellation probabilities for executing the process before and after Tc. In the case of the BP in FIG. 6, when the Tc candidate value is 0 minute, all BP cancellations occur after Tc elapses. Therefore, the occurrence probability 1105 of the BP processing flow 1001 and the BP processing flow 1002 in which BP cancellation occurs. 20.8% which is the sum of BP is the BP cancellation probability after Tc. If the Tc candidate value is 5 minutes, BP cancellation occurs before Tc only because the BP processing flow 1001 in which the BP processing flow occurs is from 0 minutes to 5 minutes. The occurrence probability 1105 of 10% is the BP cancellation probability before Tc. On the other hand, the cancellation of BP after Tc occurs only in the BP processing flow 1002 where the time zone in which the BP processing flow occurs is from 5 minutes to 15 minutes, and therefore the BP cancellation probability after Tc is 10.8%.

  Next, E1 is calculated for each Tc candidate value. E1 can be calculated by ((pre-Tc BP cancellation probability)) × (cancellation execution cost) + (post-Tc BP cancellation probability) × (operation handling cost). In the example of BP in FIG. 6, when the Tc candidate value is 0 minute, 0% × 100 yen + 20.8% × 10000 yen = 2080 yen. When the Tc candidate value is 5 minutes, 10% × 100 yen + 10.8% × 10000 yen = 1090 yen.

  The E1 calculating unit 202 calculates the pre-Tc BP cancellation probability, the post-Tc BP cancellation probability, and the E1 for all Tc candidate values, and then generates the E1 management table 210 (T16).

  FIG. 11 shows the E1 management table 210 (T16). T16 includes a BP name 1201, a BP_ID 1202, and a service name 1203 for calculating E1, a Tc candidate value 1204, a pre-Tc BP cancellation probability 1205, a post-Tc BP cancellation probability 1206, and an expected service cancellation cost value (E1) for each cancellation deadline (Tc). 1207, etc. are managed.

  Next, in S608, the E1 calculation unit 202 returns the information of the E1 management table 210 (T16) generated in S607 to the Tc calculation unit 203.

  In the present embodiment, the processing flow is such that the processing from S601 to S608 is executed each time the BP control unit 201 calls the service normal processing unit 211. However, the present invention is not limited to this, and all or part of the processing from S601 to S608 may be executed in advance (for example, the calculation is performed once when the server is started and then reused). In this case, since the information cannot be used in real time, the accuracy of E1 is reduced, but the processing performance is improved. Therefore, the information may be properly used based on the characteristics of the BP.

  Next, in S503 of FIG. 4, the BP management server 1 calculates C1 for each designated time limit (Tc). The Tc calculation unit 203 inquires of the C1 calculation unit 213 about the cancelable state maintenance cost (C1) of the Tc candidate value returned from the E1 value calculation unit 202. The C1 calculation unit 213 returns the calculated result (C1) to the Tc calculation unit 203.

  The cancelable state maintenance cost (C1) is a cost that is incurred by not performing data reference by another BP or non-cancellable processing (update processing) (maintaining a cancelable state). For example, by maintaining the cancelable state, the performance of the entire system is reduced, and an opportunity loss occurs (the number of BPs that can be processed decreases). The calculation method of C1 varies depending on the service.

  As C1, for example, in the case of the order form management service (first SV) 102 as shown in FIG. 3, the time for which the product order BP (second BP) 104 refers to the order form is delayed, so the product order is out of time. In the case of the above procedure, the cost newly generated by the overtime procedure is applicable. For example, in the case of a seat reservation service, there is an opportunity loss due to the failure to provide a service to another BP between a seat reservation request and a cancellation request.

  Next, in S504, the Tc calculation unit 203 sets a cancellation deadline (Tc) that minimizes the cost for each cancellation deadline (Tc). Specifically, an example of a cost calculation (estimation) method is to add E1 and C1. The Tc calculation unit 203 returns the calculated and set result (Tc) to the BP control unit 201.

  Next, in S505, the BP control server 1 executes a normal service process. The BP control unit 201 that has acquired the cancellation time limit (Tc) calls the service normal processing unit 211 and requests service processing. The message requesting the processing includes the name of the BP control server 1, the message ID, BP_ID, and the cancellation deadline (Tc).

  Next, in S506, the service normal processing unit 211 refers to the lock management table 216 (T22) and determines whether the service normal processing may be executed. If it can be executed, the lock information is registered in the lock management table 216 (T22), and the data stored in the business management table 215 (T21) is referred to or updated.

  FIG. 12 shows the lock management table 216 (T22). T22 is BP_ID 1301 of the BP that has transmitted the message, message ID 1302 that is an ID assigned to each message to the service normal processing unit 211, and updated by the service normal processing unit 211 as lock information registered by the service normal processing unit 211 The business data name 1303 to be executed, the cancellation time limit (Tc) 1304 assigned (given) to the message, and the like are managed.

  As for the information of T22, the service normal processing unit 211 acquires from the message exchanged with the BP control unit 201, and writes the corresponding information. Thereafter, the service normal processing unit 211 refers to or updates the data stored in the business management table 215 (T21), and returns the processing result to the BP control unit 201.

  In the present embodiment, a configuration in which a client for the BP management server 1 is not considered is shown. In addition to this configuration, a mode in which Tc is set or changed for each client that has requested processing of a business process is also possible. In this case, for example, in the lock management table 216 (T22) in FIG. 12, the ID of the client and the ID of the BP management server 1 (name of the BP management server 1 that called the service) are stored in association with each other.

  In FIG. 13, corresponding to S505 and S506, a processing flow such as service normal processing and information registration processing in the lock management table 216 (T22) is shown. The service normal processing unit 211 refers to whether the business data name to be updated is stored in the corresponding record (1303) of the lock management table 216 (T22). That is, in S1401, the lock management table 216 (T22) is searched using the business data name as a key. If the corresponding business data is not stored (S1402-N), in S1403, the service normal processing unit 211 newly registers lock information in the lock management table 216 (T22) (adding a new record) and continues the processing. . That is, in S1404, service normal processing is executed, and the processing result is returned to the BP control unit 201.

  If the corresponding business data is stored (S1402-Y), the service normal processing unit 211 refers to the BP_ID of the corresponding record in S1405. If the BP_ID is the same (S1406-Y), the service normal process is executed in S1407, and the process result is returned to the BP control unit 201. When the BP_IDs are different (S1406-N), the service normal processing unit 211 refers to the cancellation time limit (Tc) 1304 of the corresponding record in S1408. In S1409, it is determined whether or not the cancellation time limit (Tc) has elapsed at that time. If the cancellation time limit (Tc) has not elapsed (S1409-N), the service normal processing unit 211 returns an error to the BP control unit 201 or waits until the lock state is changed. On the other hand, when the cancellation time limit (Tc) has elapsed (S1409-Y), the service normal processing unit 211 deletes the corresponding record and newly registers lock information (add new record). In step S1411, normal service processing is executed, and the processing result is returned to the BP control unit 201.

  Next, in S507 of FIG. 4, the BP control unit 201 obtains a response result from the service normal processing unit 211, and then writes the progress status of the BP and the message content in the BP status management table 205 (T11). Further, the set cancellation deadline (Tc) is written in the Tc management table 206 (T12). The Tc management table 206 (T12) manages the BP name, BP_ID, message ID, cancellation deadline (Tc), and the like.

<Cancel processing>
Next, FIG. 14 shows a processing flow when the BP management server 1 requests the service providing server 2 to cancel the BP in order to cancel the BP.

  In step S1501, the BP control unit 201 calls the cancel processing unit 212 in order to cancel the BP. Here, the message content of the BP control unit 201 includes the name, BP_ID, and message ID of the BP management server 1.

  In S1502, the cancel processing unit 212 refers to the lock management table 216 (T22), and refers to a record having the same name, BP_ID, and message ID of the BP management server 1. If there is a corresponding record (S1503-Y), the process proceeds to S1504. If there is no corresponding record (S1503-N), the process proceeds to S1505.

  In S1504, if there is a corresponding record, the service state is a cancelable state, and therefore cancellation can be executed. Therefore, the cancel processing unit 212 executes a cancel process and deletes the corresponding record stored in the lock management table 216 (T22).

  If there is no corresponding record in S1505, the service state is in a cancelable state, so that the cancel cannot be executed. Therefore, the cancel processing unit 212 returns an error indicating that cancellation cannot be executed to the BP control unit 201. In step S1506, the BP control unit 201 writes a cancellation process failure in the BP status management table 205 (T11), and ends the process. In this case, cancellation of BP will be dealt with by operation.

<Reset cancellation deadline>
Next, in the configuration of the present embodiment, it is also possible to reset the cancellation deadline (Tc) once set when the BP processing is delayed due to the processing delay of the other called service. FIG. 15 shows a processing flow in that case.

  In FIG. 15, in S1601, the Tc changing unit 204 periodically checks the progress of the BP process. The Tc changing unit 204 refers to the BP status management table 205 (T11), the Tc management table 206 (T12), and the BP processing flow-specific information management table 209 (T15), and assumes (predicts) the processing time when a service normal processing request is made. To check whether the BP process (BP process flow) is proceeding. The Tc changing unit 204 determines that it is necessary to reset the cancellation deadline (Tc) when the BP process has not progressed in the processing time (in other words, when it is behind the threshold value), and the Tc resetting process is performed. Migrate to The threshold is set by the administrator of the BP management server 1.

  Next, in S1602, the Tc changing unit 204 inquires of the E1 calculating unit 202 about E1 for each cancellation deadline (Tc). The E1 calculating unit 202 calculates E1 for each cancellation deadline (Tc) and returns the result to the Tc changing unit 204. The calculation method of E1 is the same as that of FIG.

  In step S <b> 1603, the Tc changing unit 204 inquires the C1 calculating unit 213 about C1 of the candidate value for the cancellation deadline (Tc) returned from the E1 calculating unit 202. The C1 calculation unit 213 calculates C1 for each designated time limit (Tc) and returns the result. The calculation method of C1 is the same as S503 in FIG.

  In step S <b> 1604, the Tc changing unit 204 calculates a cost for each cancellation deadline (Tc), and sets a Tc that minimizes the cost. An example of the cost calculation method is the same as described above. In step S <b> 1605, the Tc changing unit 204 requests the Tc resetting reception unit 214 to reset the Tc. The message includes the name of the BP management server 1, the BP_ID, and the message ID, which are information related to the message for which Tc is reset. In step S <b> 1606, the Tc resetting reception unit 214 refers to the lock management table 216 (T <b> 22), and refers to records having the same name, BP_ID, and message ID of the BP management server 1. If there is a corresponding record (S1607-Y), the process proceeds to S1608. If there is no corresponding record (S1607-N), the process proceeds to S1610.

  If there is a corresponding record in S1608, the Tc resetting accepting unit 214 changes the cancellation time limit (Tc) stored in the lock management table 216 (T22), and returns a success of processing. In step S1609, the Tc changing unit 204 changes the cancellation deadline (Tc) stored in the Tc management table 206 (T12), and the processing is completed. On the other hand, if there is no corresponding record in S1610, the Tc resetting reception unit 214 returns an error. In step S <b> 1611, the Tc changing unit 204 notifies the administrator of the BP management server 1 of a warning.

  As described above, the present embodiment has the following effects. In this system, the service provides a cancellation process during the cancellation deadline (Tc) calculated based on the expected service cancellation cost value (E1) and the cancelable state maintenance cost (C1). As a result, it is possible to reduce the number of times that an event of canceling a BP after the service has transitioned to a non-cancelable state while preventing performance degradation of the entire system (improvement in the success rate of the BP process). In addition, when the precondition of the set cancellation deadline (Tc) changes, such as when the BP processing is delayed due to the processing delay of the other called service, the cancellation deadline (Tc) may be reset. It becomes possible.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiment. However, the present invention is not limited to the embodiment, and various modifications can be made without departing from the scope of the invention. Needless to say.

  The present invention can be used in an information processing system such as a business process management system.

It is a figure which shows the whole structure (functional block structure) of the BP management system which is one embodiment of this invention. It is a figure which shows the mutual relationship of each program (processing part) and a table in the BP management system of one embodiment of this invention. It is a figure which shows the example of a processing sequence of BP and a service in the BP management system of one embodiment of this invention. In the BP management system of one embodiment of this invention, it is a processing flowchart in case a BP management server calls a service provision server and performs a service. In the BP management system of one embodiment of this invention, it is a processing flowchart in case a BP management server calculates the service cancellation cost expectation value (E1) according to cancellation time limit. It is a figure which shows the example of BP which a BP management server performs in the BP management system of one embodiment of this invention. It is a figure which shows the structural example of an activity transition probability management table in the BP management system of one embodiment of this invention. It is a figure which shows the structural example of a service information management table in BP management system of one embodiment of this invention. It is a figure which shows the example of BP processing flow in the BP management system of one embodiment of this invention. It is a figure which shows the structural example of the information management table classified by BP process flow in the BP management system of one embodiment of this invention. It is a figure which shows the structural example of a service cancellation cost expected value (E1) management table in BP management system of one embodiment of this invention. It is a figure which shows the structural example of a lock management table in the BP management system of one embodiment of this invention. In the BP management system of one embodiment of this invention, it is a processing flowchart, such as service normal processing and lock information update. In the BP management system of one embodiment of this invention, in order to cancel BP, it is a processing flowchart in case a BP management server requests | requires cancellation processing from the service provision server. It is a processing flowchart in the case of resetting a cancellation time limit in the BP management system of one embodiment of this invention. It is a figure which shows the example of a processing sequence regarding a base technology and a problem.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... 1st computer (BP management server), 2 ... 2nd computer (service provision server) 10, 20 ... CPU, 11, 21 ... Main memory, 12, 22 ... Storage device, 13, 23 ... Input device , 14, 24 ... output device, 15, 25 ... communication interface, 101 ... merchandise order acceptance BP (first BP), 102 ... order form management service (first SV), 103 ... account withdrawal service (second SV), 104 ... merchandise Order BP (second BP), 201 ... BP control unit, 202 ... Service cancellation cost expected value (E1) calculation unit, 203 ... Cancellation deadline (Tc) calculation unit, 204 ... Cancellation deadline (Tc) change unit, 205 ... BP status Management table, 206 ... Cancel time limit (Tc) management table, 207 ... Activity (AC) transition probability management table, 208 ... Service Information management table, 209... BP processing flow-specific information management table, 210... Service cancellation cost expected value (E1) management table, 211... Service normal processing unit, 212 ... Cancel processing unit, 213 ... Cancelable state maintenance cost (C 1) Calculation unit, 214... Cancellation deadline (Tc) resetting reception unit, 215... Business management table, 216.

Claims (10)

A business process management method for calling a service for executing a business in accordance with a business process indicating a series of business flows on one or more computers,
In the processing performed by the computer,
A first processing step of setting a first time limit for enabling cancellation of the service;
A second processing step of locking data updated or referred to by the processing of the corresponding service called by the corresponding business process until the first time limit has passed;
When the cancellation request for the service is received, it is determined whether or not the cancellation process of the service can be executed according to the determination of the elapse of the first time limit, and the cancellation process of the service is performed when the first time limit has not elapsed And a third processing step for executing the business process management method. The business process management method according to claim 1,
In the first processing step, the cost for canceling the business process is minimized based on the expected value of the cancellation cost of the service and the cost for maintaining the service in a cancelable state. A business process management method comprising: setting a first deadline. A business process management system for calling a service for executing a business according to a business process indicating a series of business flows on one or more computers,
A first means for setting and managing a first time limit for enabling cancellation of the service;
Second means for locking the data updated or referred to by the processing of the corresponding service called by the corresponding business process until the first time limit has passed;
When the cancellation request for the service is received, it is determined whether or not the cancellation process of the service can be executed according to the determination of the elapse of the first time limit, and the cancellation process of the service is performed when the first time limit has not elapsed And a third means for executing the business process management system. The business process management system according to claim 3.
The first means is configured to reduce the cost related to the cancellation of the business process based on an expected value of the cancellation cost of the service and a cost for maintaining the cancelable state of the service. A business process management system characterized by setting a time limit of 1. The business process management system according to claim 4, wherein
The first means estimates the cost related to the cancellation of the business process by an addition value of an expected value of the cancellation cost of the service and a cost for maintaining the service in a cancelable state. Business process management system. The business process management system according to claim 4, wherein
The first means includes
Based on the progress status of the business process, the activity transition probability of the processing flow of the business process, and the probability of successful processing of the service, the probability of cancellation of the business process for each processing flow of the business process is calculated. And
Based on the progress of the business process and the average processing time of the service, calculate the scheduled start and completion times of processing of the last activity described in the processing flow of the business process,
Using the cancellation execution cost required for the server providing the service or its computer to execute the cancellation process, and the operation handling cost required to cancel the effect of the service when the cancellation process cannot be executed, A business process management system characterized by calculating an expected value of a cancellation cost of the service. The business process management system according to claim 3.
The business process management system, wherein the first means sets or changes the first time limit for each client or its computer that has requested processing of the business process. The business process management system according to claim 3.
The business process management system according to claim 1, wherein the first means includes means for resetting the first time limit during the processing of the business process. The business process management system according to claim 8.
Based on the progress status of the business process and the average processing time of the service, means for calculating scheduled start and completion times of processing of the last activity described in the processing flow of the business process ,
The means for resetting the first deadline is such that the cost of canceling the business process is minimized when the progress of the business process is different compared to the scheduled start and completion times. A business process management system, wherein the first deadline is reset. A business process management system for calling a service for executing a business according to a business process indicating a series of business flows on one or more computers,
One or more first servers that manage the business process and one or more second servers that provide the service are communicatively connected,
The first server sets, based on communication with the second server, a first deadline in which a cancellation process for the service can be accepted, an expected value of the cancellation cost of the service, and the service Based on the calculation of the cost for maintaining the cancelable state, and performing the process of setting and managing so that the cost for canceling the business process is minimized,
The second server locks data updated or referred to by the process of the corresponding service called by the corresponding business process until the first time limit elapses, and the service cancel request from the first server. A process for determining whether or not to execute the cancellation process of the service according to the determination of the elapse of the first time limit when receiving the service, and executing the cancel process of the service when the first time limit has not elapsed Business process management system, characterized by doing.

Images