JP2010026695A - Business process execution method, business process execution device and business process execution program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce usage of resources in executing a business process. <P>SOLUTION: A computer system includes: a service execution device; and a business process execution device which executes a business process obtained by combining services. The business process is divided into regions including at least one activity. The business process execution device stores process division information including the association between the regions and activity, and business execution state information including the execution information of the business process.When accepting the execution of the business process, the business process extracts an activity to be executed and the region based on the process execution state information and the process division information, and executes the activity included in the region extracted based on the execution information corresponding to the extracted region. When the execution of all the activity included in the extracted region is completed, the business process stores the execution information corresponding to the region into the process execution state information. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for reducing resources consumed when executing a business process.

  In recent years, there has been a demand for a system that can flexibly respond in a short period of time to drastic changes in the business environment surrounding a company, such as the consolidation of companies and intensifying market competition. Thus, a system based on the concept of SOA (Service Oriented Architecture) has attracted attention. The SOA provides software functions that have independent functions in the business in units called services, and provides service functions by publishing service interface information in which service names and input / output message formats are defined. It is one of the software construction techniques. Here, a system constructed based on the SOA is referred to as an SOA system.

  In the SOA system, we can flexibly respond to business changes by reusing existing services as much as possible, developing new services as needed, and combining these services to provide new functions. can do. A new service provided by combining a plurality of services as described above is called a business process.

  The business process provides a new function by combining a plurality of services using a business process description language such as BPEL (Business Process Execution Language). A business process can itself be a service. Therefore, a new business process can be configured by combining business processes.

  Since business processes provide functions by combining services with independent functions, when changes in functions become necessary, it is possible to respond by simply changing the combination of services. Can respond flexibly. In the business process, it is possible to describe flow control such as branch processing and format editing processing in addition to service call. Elements that constitute such a business process are called activities. In the business process, an area for storing a message instance used in each activity is called a variable. The variable can be used for storing an input / output message of a service call and a branch condition of a branch process.

  As a business process description method, the business process definition language such as BPEL described above is used. Various component models are used as business process and service implementation methods. Various programs for executing the implemented components are used as business process and service execution platform programs. Here, the service execution platform program is referred to as a service execution platform program.

  When a business process in which a business flow is described is executed, it may take a very long time. For example, when work involving human intervention is involved, it may take several days to several weeks. Business process execution is generally executed by deploying an instance in memory, but it is not possible to deploy it in memory while it is in a wait state, such as waiting for completion of a manual operation in a business process. Inefficient. Therefore, the execution time information of the waiting business process is made permanent in a database (DB) and the execution is temporarily interrupted, and when the manual work is completed, the business process is activated and processing is continued. Therefore, a technique for improving the memory utilization efficiency is generally used. Here, the persistence means storing business process runtime information such as a business process flow definition, an execution state of each activity included in the flow, variable definition information, and variable values in a DB or the like. In addition, activation refers to acquiring information that is made permanent in the DB and deploying it on the memory.

In Patent Document 1, in order to reduce the amount of memory required when executing a business process, a variable is created on the memory as needed when executing the business process, and the variable is deleted from the memory when it is no longer needed. Thus, a technique for preventing the load of more variables than necessary on the memory is disclosed.
JP 2006-31500 A

  When a business process becomes longer, the execution time of the business process tends to be longer, and the frequency with which the business process is made permanent and activated increases. Further, since the number of business steps constituting the business process and the number of variables used by the business process increase, the amount of information manipulated when the business process is made permanent or activated also increases.

  In the conventional technology, since the entire business process is activated or made permanent, the definition information and execution state of business steps that are not executed when the business process is activated, variable definitions and values that are not used at the time of activation, etc. It was always activated or permanent. As described above, activating an activity that is not executed and variable information that is not used consumes resources such as a memory unnecessarily, which hinders efficient use of the memory.

  Further, the technique disclosed in Patent Document 1 creates a variable on a memory when a variable defined in a business process becomes necessary, and discards the variable from the memory when the variable becomes unnecessary. Improve usage efficiency. However, since the variables are generated as needed, it is necessary to read the information from the DB and allocate a memory area every time a new variable is needed, which may deteriorate the execution performance. In addition, since the flow definition of the business process is not analyzed, the efficient use of resources based on the flow definition is not realized.

  An object of the present invention is to improve the execution performance of a business process and reduce the amount of resources necessary for executing the business process.

  In a typical embodiment of the present invention, a business process execution method in a computer system comprising: a service execution device that provides a service; and a business process execution device that executes a business process in which business processing is defined by combining the services. The business process execution device includes an interface connected to the service execution device, a processor connected to the interface, and a memory connected to the processor, and the business process is the business process Is divided into areas including at least one activity, and the memory stores process execution state information for storing execution information including execution progress of the business process, and correspondence between the area and the activity The Process division information, and when the method accepts execution of the business process, the method identifies an activity to be executed based on the process execution state information and the process division information, and the identified An area including an activity is extracted, execution information corresponding to the extracted area is acquired from the process execution state information, and an activity included in the extracted area is executed based on the acquired execution information. When execution of all activities included in the extracted area is completed, execution information corresponding to the extracted area is stored in the process execution state information.

  According to an aspect of the present invention, by dividing and executing a business process, the execution unit of the business process can be reduced, and the amount of resources required when executing the business process can be reduced.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an example of the configuration of the SOA system according to the embodiment of this invention.

  The SOA system according to the embodiment of this invention includes a business process execution computer 201, a business process development computer 300, service execution computers (501, 502), and a client computer 701. The business process execution computer 201, the business process development computer 300, the service execution computers (501, 502), and the client computer 701 are connected to each other via a network.

  The business process execution computer 201 executes a business process. The business process execution computer 201 is a general-purpose computer such as a personal computer (hereinafter referred to as a personal computer). Details of the configuration of the business process execution computer 201 will be described later with reference to FIG.

  The business process execution computer 201 includes a business process execution unit 221, a load area determination unit 222, a process division result storage table 230, a variable reference relationship storage table 240, a process execution state storage table 250, and a variable state storage table 260. In the embodiment of the present invention, the business process execution unit 221 and the load region determination unit 222 are realized as software, but are not limited thereto, and may be realized by a dedicated semiconductor circuit or the like.

  The business process execution unit 221 controls the execution of the business process using the process execution state storage table 250, the variable state storage table 260, and the like. Since the business process execution unit 221 can be realized by using a general-purpose business process execution program, a detailed description thereof is omitted. Note that the business process execution unit 221 according to the embodiment of the present invention has a function of requesting processing to the load region determination unit 222 at the timing of activating a business process, in addition to the function of a general-purpose business process execution program.

  The process execution state storage table 250 stores the execution status of business processes. Details of the process execution state storage table 250 will be described later with reference to FIG. The variable state storage table 260 stores variables that are set when the business process is executed. Details of the variable state storage table 260 will be described later with reference to FIG.

  Based on the request from the business process execution unit 221, the load area determination unit 222 acquires information necessary for executing the business process from the process division result storage table 230 and the variable reference relation storage table 240, and executes the business process execution result. Responds to unit 221.

  The process division result storage table 230 stores the divided business processes for each area. Details of the process division result storage table 230 will be described later with reference to FIG. The variable reference relationship storage table 240 stores variables used for each divided business process area. Details of the variable reference relationship storage table 240 will be described later with reference to FIG.

  The business process development computer 300 is a computer for the business process developer 800 to define a business process. Similar to the business process execution computer 201, the business process development computer 300 is a general-purpose computer such as a personal computer. Details of the configuration of the business process development computer 300 will be described later with reference to FIG.

  The business process development computer 300 includes a business process development unit 310, a flow definition analysis unit 320, and a variable reference relationship analysis unit 330. In the embodiment of the present invention, the business process development unit 310, the flow definition analysis unit 320, and the variable reference relationship analysis unit 330 are realized as software, but may be realized by a dedicated semiconductor circuit or the like.

  The business process development unit 310 is an application for the business process developer 800 to define a business process. The business process development unit 310 is often a GUI (Graphical User Interface) tool, but is not limited thereto. Since the business process development unit 310 can be realized by a general-purpose business process development program or the like, detailed description thereof is omitted.

  The business process defined by the business process developer 800 is described in a process definition description language such as BPEL. The business process definition information is described in a format such as XML (extensible Markup Language), but is not limited thereto. A definition example of the business process will be described later with reference to FIG.

  In the embodiment of the present invention, the business process development unit 310 includes a business process persistence point presentation unit 311 and a business process persistence point designation unit 312 in addition to a general-purpose business process development program.

  The business process persistence point presentation unit 311 presents to the business process developer 800 the business process persistence points extracted based on the analysis result of the business process by the flow definition analysis unit 320 described later. Further, the business process persistence point designating unit 312 receives an input of a point for perpetuating the business process from the business process developer 800.

  The flow definition analysis unit 320 analyzes the flow of the business process developed by the business process developer 800 in accordance with an algorithm described later, and extracts business process persistence points. Furthermore, the flow definition analysis unit 320 divides the business process based on the extracted permanent points, and stores the result in the process division result storage table 230.

  The flow definition analysis unit 320 may present the extracted business process persistence points to the business process developer 800 using the business process persistence point presentation unit 311. The business process developer 800 can perform an editing process such as deleting a persistence point of the presented business process or designating a new persistence point using the business process persistence point designating unit 312. . When the analysis result is presented to the business process developer 800, the flow definition analysis unit 320 divides the business process based on the persistence point specified by the business process developer 800 and stores the result as a process division result. Store in table 230.

  The variable reference relationship analysis unit 330 extracts a variable referred to from each divided area by applying an algorithm described later to the division result by the flow definition analysis unit 320, and the result is stored in the variable reference relationship storage table 240. To store.

  In the embodiment of the present invention, only the business process execution computer 201 holds the process division result storage table 230 and the variable reference relation storage table 240, but the business process development computer 300 holds equivalent information. It may be. Alternatively, the business process execution computer 201 may refer to a table held in the business process development computer 300. Furthermore, in the embodiment of the present invention, the business process execution computer 201 and the business process development computer 300 are different computers, but the present invention is not limited to this, and can be realized by a single computer.

  The client computer 701 is a computer for requesting the business process execution computer 201 to execute a business process. The client computer 701 is a general-purpose computer such as a personal computer. The client computer 701 includes a service call program 710.

  The client computer 701 uses a service by receiving a request from the client 820, executing the service call program 710, and transmitting a service execution request to the business process execution unit 221 of the business process execution computer 201. The service call program 710 can be realized by various program languages, and detailed description thereof is omitted. In the embodiment of the present invention, the service call program 710 is realized as software, but may be implemented as dedicated hardware such as a semiconductor circuit.

  Service execution computers 501 and 502 are computers on which a service called by a business process is executed. The service execution computers 501 and 502 are general-purpose computers such as personal computers. The service execution computers 501 and 502 include a service execution base program 510 that is a server program for executing a service.

  Services can be implemented by various component models. Further, since the service execution platform program 510 can be realized by various programs that execute the mounted components, a detailed description of the implementation method is omitted. In the embodiment of the present invention, the service and service execution platform program 510 is realized as software, but may be realized as dedicated hardware such as a semiconductor circuit.

  FIG. 2 is a diagram illustrating an example of the configuration of the business process development computer 300 according to the embodiment of this invention.

  The business process development computer 300 includes a CPU 900, a network interface 910, a graphic interface 920, a user input interface 930, a main storage device 940, and a secondary storage device 950. The CPU 900, network interface 910, graphic interface 920, user input interface 930, main storage device 940, and secondary storage device 950 are connected by a system bus 960.

  The CPU 900 executes various business processes by processing a program stored in the main storage device 940. The network interface 910 communicates with other computers connected via the network 1000 in accordance with instructions from the CPU 900.

  The user input interface 930 receives user input from an input device such as a mouse or a keyboard. The graphic interface 920 performs processing of an image displayed on the image display device 921 such as a display.

  The main storage device 940 stores a program processed by the CPU 900 and data necessary for the processing of the program. The programs stored in the main storage device 940 are a business process development unit 310, a flow definition analysis unit 320, a variable reference relationship analysis unit 330, and an OS (Operating System) 970. The main storage device 940 is a volatile storage medium.

  The secondary storage device 950 inputs and outputs data based on instructions from the CPU 900. The secondary storage device 950 is a non-volatile storage medium such as a magnetic storage device such as a hard disk or an optical storage device such as a CD or a DVD drive, but is not limited thereto.

  The hardware configurations of the business process execution computer 201, the service execution computers (501, 502), and the client computer 701 are the same as those of the business process development computer 300 shown in FIG. The difference from the business process development computer 300 is the contents of programs and data stored in the main storage device 940.

  FIG. 3 is a diagram illustrating an example of the configuration of the business process execution computer 201 according to the embodiment of this invention.

  The hardware configuration of the business process execution computer 201 is the same as that of the business process development computer 300 as described above.

  The main memory 940 of the business process execution computer 201 stores an OS 970, a business process execution unit 221, a load area determination unit 222, a process division result storage table 230, and a variable reference relationship storage table 240. The process division result storage table 230 and the variable reference relationship storage table 240 may be included in the business process execution unit 221 or the load region determination unit 222. Further, it may be stored in the secondary storage device 950.

  The main storage 940 of the service execution computer (501, 502) stores the OS 970, the service execution infrastructure program 510, and the services deployed in the service execution infrastructure program. The main storage 940 of the client computer 701 stores an OS 970 and a service call program 710.

  FIG. 4 is a diagram illustrating an example of a configuration of the process execution state storage table 250 according to the embodiment of this invention.

  The process execution state storage table 250 includes a business process (BP) name 251, an activity name 252, a state 253, a start time 254, and an end time 255. Records are stored and updated in the process execution state storage table 250 by the business process execution unit 221. Each record of the process execution state storage table 250 is stored for each activity for the executed business process.

  The business process name 251 is the name of the business process. The activity name 252 is the name of an activity belonging to the business process. The business process name 251 and the activity name 252 may be information that can uniquely identify each, and are not limited to names, and may be identification codes.

  In addition, when a plurality of business processes are executed by the same business process definition, information for identifying the executed business process is further added.

  The state 253 is an activity execution state. In the state 253, for example, “completed” is recorded when the execution is completed, and “unexecuted” is recorded when the execution is not performed. The start time 254 is the time when the activity is started when the business process is executed. The end time 255 is an activity execution end time.

  FIG. 5 is a diagram illustrating an example of a configuration of the variable state storage table 260 according to the embodiment of this invention.

  The variable state storage table 260 includes a business process (BP) name 261, a variable name 262, and a variable value 263. The variable state storage table 260 is stored and updated by the business process execution unit 221. The variable state storage table 260 stores a record for each variable used in the business process for the executed business process.

  The business process name 261 is the name of the business process. The variable name 262 is a name of a variable used in the business process. The variable value 263 is a value stored in the variable specified by the variable name 262. The business process name 261 and the variable name 262 may be information that can uniquely identify each, and are not limited to names.

  Further, when a plurality of business processes are executed with the same business process definition, information for identifying the executed business process is further added as in the process execution state storage table 250.

  FIG. 6 is a diagram illustrating an example of the configuration of the process division result storage table 230 according to the embodiment of this invention.

  The process division result storage table 230 includes a business process (BP) name 231, an area name 232, and an activity name 233. The process division result storage table 230 is stored by the flow definition analysis unit 320. In the process division result storage table 230, a record is stored for each activity constituting the business process, and an area is set based on an analysis result by the flow definition analysis unit 320.

  The business process name 231 is the name of the business process. The area name 232 is the name of an area constituting the business process. The activity name 233 is an activity that constitutes a business process. The business process name, the area name, and the activity name may be information that can uniquely identify each, and are not limited to names.

  FIG. 7 is a diagram illustrating an example of the configuration of the variable reference relationship storage table 240 according to the embodiment of this invention.

  The variable reference relationship storage table 240 includes an area name 241 and a variable name 242. The variable reference relationship storage table 240 is stored by the variable reference relationship analysis unit 330. Each record of the variable reference relationship storage table 240 is stored for each variable used in each area.

  The area name 241 is the name of an area constituting the business process. The variable name 242 is a name of a variable belonging to the business process. Note that the area name 241 and the variable name 242 may be information that can uniquely identify each, and are not limited to names.

  FIG. 8 is a diagram illustrating an example of a business process definition (XML format) according to the embodiment of this invention.

  A business process BP-A 1700 shown in FIG. 8 is described in XML format BPEL. In the business process shown in FIG. 8, the <variable> tag describes the declaration of the variable that stores the message that is sent and received when calling the service, and the <sequence> tag describes the activity that calls the service and the service. Describes the activities that make up the business process and related information such as variables used in the activity, such as the specification of the variable that stores the message sent to the service and the specification of the variable that stores the message received by executing the service. Yes.

  The business process can be described in an XML format as shown in FIG. 8, but can also be expressed in a flowchart format as shown in FIG.

  FIG. 15 is a diagram illustrating an example of a business process definition (flow chart format) according to the embodiment of this invention.

  In the embodiment of the present invention, a business process developer 800 uses a business process development computer 300 to define a business process.

  The business process definition in the flowchart format shown in FIG. 15 corresponds to the business process definition in the XML format shown in FIG. Therefore, it is possible to mutually convert the business process definition in the XML format shown in FIG. 8 and the business process definition shown in FIG. 15 using a general-purpose business process development program or the like.

  Here, the behavior of the business process shown in FIGS. 8 and 15 will be described with reference to FIGS.

  In the business process BP-A 1700, first, a receive-A1 activity that is an activity (acceptance activity) for receiving a request from the outside is defined. In the receive-A1 activity, the received request is stored in the variable in-A1.

  Subsequently, in the invoke-A1 activity, an external service is called with the variable in-A1 as an input, and the result is stored in the variable var-A1. The invoke activity is an activity for calling a service provided externally (for example, the service execution computer 501).

  Next, in the dt-A1 activity (assign activity), the value of the variable var-A1 is converted and set to the variable out-A1, and the conversion result is output to the outside in the reply-A1 activity (reply activity).

  Further, the business process BP-A1700 defines an activity receive-A2 that receives an external request again and stores the received content in a variable in-A2. Thereafter, a dt-A2 activity for generating the variable var-A2 based on the variable var-A1 and the variable in-A2 is defined.

  Subsequently, in the business process BP-A1700, an invoke-A2 activity that calls an external service with the value of the generated variable var-A2 as an input is defined. In the invoke-A2 activity, the response from the called external service is stored in the variable out-A2, and the result is output to the outside by the reply-A2 activity.

  The details of the business process development and execution procedure according to the embodiment of the present invention will be described below. First, a procedure for analyzing a business process when a business process is developed (defined) by the business process developer 800 will be described, and then a procedure for executing the business process based on the analysis result will be described. Note that each procedure will be described assuming that the business process defined by the business process developer 800 is BP-A 1700 shown in FIGS. 8 and 15.

  Hereinafter, the procedure for analyzing the business process in the embodiment of the present invention will be described. FIG. 16 shows the result of analyzing the business process definition shown in FIGS. 8 and 15 according to the procedure shown in FIG. 9, and the procedure for analyzing the business process will be described with reference to it as appropriate.

  FIG. 9 is a flowchart showing a procedure for analyzing a business process in the embodiment of the present invention.

  When the business process developer 800 defines a business process by the business process development unit 310 executed by the business process development computer 300, the business process developer 800 executes the flow definition analysis unit 320 using the developed business process definition information as input information.

  The CPU 900 of the business process development computer 300 uses the flow definition analysis unit 320 to analyze the input business process and extract all points at which the business process is made permanent (hereinafter referred to as “permanent points”). Then, the business process persistence point presentation unit 311 presents the extracted persistence points to the business process developer 800 (step 1103). Details of the flow definition analysis process (step 1103) will be described later with reference to FIG.

  Here, the persistence is to store business process execution information in a DB or the like when the business process is in a waiting state for a long time, as described above. The persistence point is a point (timing) that is likely to be persisted.

  The case where the business process is in a waiting state for a long time is, for example, a case where the business process accepts an input from the outside, that is, a case where the business process waits for an input from outside. Therefore, it is possible to determine that the business process is likely to be persisted immediately before the reception activity as a persistence point.

  Here, a persistence point extraction process for analyzing an input business process and extracting a persistence point will be described. In the embodiment of the present invention, the immediately preceding reception activity included in the business process is determined as the persistence point. However, the present invention is not limited to this, and other points are determined as the persistence points. Also good.

  FIG. 10 is a flowchart showing the procedure of the persistence point extraction process for extracting the persistence points for dividing the business process according to the embodiment of this invention.

  The permanent point extraction processing is executed by the flow definition analysis unit 320 as described above.

  The CPU 900 of the business process development computer 300 first sets the activity defined at the beginning of the business process defined by the business process developer 800 to S (step 11031). The activity S is a target activity for determining whether or not the immediately preceding point is set as a permanent point.

  Next, the CPU 900 of the business process development computer 300 determines whether or not the activity S is a reception activity (step 11032). If the activity S is not a reception activity (the result of step 11032 is “No”), the activity S is not a candidate for a permanent point, so the permanent point determination process is terminated and the process of step 11035 is executed.

  If the activity S is a received activity (the result of step 11032 is “Yes”), the CPU 900 of the business process development computer 300 can further be a candidate for a persistence point. It is determined whether it is the first activity of the process (step 11033). If the activity S is the first activity of the business process (the result of step 11033 is “Yes”), the persistence point is never set at the beginning of the business process, so the activity S becomes the persistence point. There is nothing. In this case, the permanent point determination process is terminated, and the process of step 11035 is executed.

  If the activity S is not the first activity of the business process (the result of step 11033 is “No”), the CPU 900 of the business process development computer 300 sets the point immediately before the activity S as the persistence point (step 11034).

  Subsequently, the CPU 900 of the business process development computer 300 determines whether or not the activity S is the last activity of the business process (step 11035). If the activity S is the last activity (the result of step 11035 is “Yes”), this processing is terminated.

  If the activity S is not the last activity (the result of step 11035 is “No”), the CPU 900 of the business process development computer 300 sets the activity to be processed next to the activity S as the activity S (step 11036), and returns to the processing of step 11032.

  With the above procedure, all the received activities other than the activity defined at the head of the business process can be extracted from the received activities included in the business process definition, and the point immediately before the extracted received activity can be set as the persistence point. It becomes possible. When the procedure shown in FIG. 10 is applied to the business process definition example BP-A1700 shown in FIG. 15, two reception activities of receive-A1 and receive-A2 are defined in BP-A1700, but receive-A1. Since the activity is the first activity of BP-A 1700, one persistence point 1720 is extracted only immediately before receive-A2 (see FIG. 16).

  Now, the description returns to the flowchart of FIG.

  Subsequently, the CPU 900 of the business process development computer 300 accepts correction or confirmation of the analysis result by the flow definition analysis unit 320 (step 1104). Specifically, deletion of unnecessary points or addition of arbitrary permanent points is accepted from the permanent points extracted in the processing of step 1103.

  It should be noted that the analysis result by the flow definition analysis unit 320 does not necessarily have to be presented to the business process developer 800, and the processing after step 1105 may be executed without executing the processing at step 1104.

  Presentation of the business process to the business process developer 800 is executed by the business process persistence point presentation unit 311. As a format of the business process presented by the business process persistence point designating unit 312, for example, there is an XML format shown in FIG. 8 or a flowchart format shown in FIG. 15, but it is not limited to this.

  In addition, as a format of the persistence point to be presented to the business process developer 800, for example, a format in which a special tag is inserted in the XML format, or a special symbol is inserted in the flowchart like the persistence point 1720 shown in FIG. However, the present invention is not limited to this.

  In the embodiment of the present invention, the business process persistence point designating unit 312 can accept from the business process developer 800 the addition of the persistence point to the business process or the deletion of the persistence point. FIG. 17 shows an example of a screen for adding or deleting a permanent point.

  The CPU 900 of the business process development computer 300 reflects the information of the persistence points added or deleted by the business process persistence point designating unit 312 in the business process definition. For example, a tag indicating a persistence point is inserted or deleted in the business process definition information in the XML format shown in FIG.

  FIG. 17 is a diagram showing an example of a permanent point edit screen presented to the business process developer 800 according to the embodiment of this invention.

  FIG. 17 shows an example in which a new persistence point 1730 is added by the business process developer 800 in addition to the persistence points 1720 extracted by the flow definition analysis unit 320 in the processing of step 1103. .

  The procedure for adding or deleting a persistence point will be described in detail. To add a persistence point, select a line connecting the two activities that make up the flowchart, and add a persistence point on the selected line. Can be specified. The instruction to add a permanent point may be, for example, a method of double-clicking a line or a method of selecting an instruction from a menu, and is not limited thereto.

  The deletion of the permanent points may be performed by specifying the permanent points displayed on the flowchart and instructing the deletion. The instruction to delete the persistence point may be, for example, a method of double-clicking the persistence point or a method of selecting an instruction from a menu, and is not limited thereto.

  Further, as shown in FIG. 17, the business process persistence point presentation unit 311 distinguishes and displays the persistence points extracted by the flow definition analysis unit 320 and the persistence points added by the business process developer 800. It may be. Of the persistence points extracted by the flow definition analysis unit 320, the persistence points deleted by the business process developer 800 are separated from other persistence points using, for example, a black diamond. You may display separately.

  The business process edited by the business process developer 800 is input to the flow definition analysis unit 320 again. The designation (addition) of the persistence point by the business process developer 800 may be performed before the flow definition analysis unit 320 is executed.

  Now, the description returns to the flowchart of FIG. In the embodiment of the present invention, the following description will be made assuming that the persistence point has not been added or deleted by the business process developer 800.

  The CPU 900 of the business process development computer 300 further analyzes the business process edited in the process of step 1104 by the flow definition analysis unit 320 (step 1105). Specifically, the business process is divided into areas, and activities included in each area are extracted. Further, the analysis result is stored in the process division result storage table 230.

  The area division of the business process is performed by cutting out each of the base points as one area with the perpetuation points designated by the processing of step 1103 and step 1104 and the start and end of the business process as base points.

  The details of the business process area dividing process executed by the flow definition analyzing unit 320 in the process of step 1105 will be described below with reference to FIG.

  FIG. 11 is a flowchart showing a procedure of business process area division processing by the flow definition analysis unit 320 according to the embodiment of this invention.

  The business process area dividing process is executed by the flow definition analyzing unit 320 as described above.

  The CPU 900 of the business process development computer 300 first sets the activity defined at the beginning of the business process to S and L (step 11051). The activity S is an activity corresponding to the head of the area to be divided. On the other hand, the activity L is an activity corresponding to the tail end of the area to be divided.

  The CPU 900 of the business process development computer 300 next determines whether or not the activity L is set as a permanent point (step 11052). If the point immediately after activity L is not set as a permanent point (the result of step 11052 is “No”), the next activity of activity L is set as a new L (step 11053), and the processing of step 11052 is performed. Return.

  When the CPU 900 of the business process development computer 300 is set as a persistence point immediately after the activity L (the result of step 11052 is “Yes”), the activities S to L are extracted as new areas. A unique name is assigned to the area (step 11054).

  Next, the CPU 900 of the business process development computer 300 extracts information on all the activities included in the activities S to L and associates them with the business process name and the area name given in the processing of step 11054. The result is stored in the division result storage table 230 (step 11055).

  Referring to the process division result storage table 230 illustrated in FIG. 6, for example, a “receive-A1” activity is associated with the business process BP-A and the area realm-A1. This indicates that the area realm-A1 is included in the business process BP-A, and the receive-A1 activity is included in the area realm-A1.

  Subsequently, the CPU 900 of the business process development computer 300 determines whether or not the activity L is the last activity of the business process (step 11056). If the activity L is the last activity of the business process (the result of step 11056 is “Yes”), this process is terminated. If the activity L is not the last activity (the result of step 11056 is “No”), the activity next to the activity L is newly set to S and L (step 11057), and the processing returns to step 11052.

  According to the above procedure, the business process can be divided into regions based on the persistence points designated in the processing of step 1103 and step 1104, and the result can be stored in the process division result storage table 230.

  In the embodiment of the present invention, as a result of the processing up to step 1105, the area realm-A1 (1710) and the area realm-A2 (1711) are extracted as shown in FIG. The area realm-A1 (1710) includes activities receive-A1, invoke-A1, dt-A1, and reply-A1. Also, the area realm-A2 (1711) includes activities receive-A2, dt-A2, invoke-A2, and reply-A2.

  Further, the processing results up to step 1105 are stored in the process division result storage table 230 as shown in FIG. Referring to the process division result storage table 230 shown in FIG. 6, as described above, the business process BP-A includes the area realm-A1, and the area realm-A1 includes the receive-A1 activity. This is shown in the record on the first line. The same applies to subsequent records.

  Now, the description returns to the flowchart of FIG.

  Next, the CPU 900 of the business process development computer 300 uses the variable reference relationship analysis unit 330 to analyze the variables referenced in each area extracted in the processing of step 1105 and stores the results in the variable reference relationship storage table 240. (Step 1106).

  Details of the variable reference relationship analysis processing executed by the variable reference relationship analysis unit 330 in the processing of step 1106 will be described below with reference to FIG.

  FIG. 12 is a flowchart illustrating a procedure of variable reference relationship analysis processing by the variable reference relationship analysis unit 330 according to the embodiment of this invention.

  The variable reference relationship analysis process is executed by the variable reference relationship analysis unit 330 as described above. Also, the variable reference relationship analysis process is executed for each divided area.

  The CPU 900 of the business process development computer 300 first sets the activity defined at the beginning of the area to S (step 11061).

  Next, the CPU 900 of the business process development computer 300 refers to the business process definition and extracts all variable names referred to by the activity S (step 11062). For example, in the receive-A1 in the BP-A shown in FIG. 15, the received request is assigned to the variable in-A1. Therefore, the receive-A1 assigns the variable in-A1 to the variable in-A1. It can be determined to refer to it. Similarly for other activities, it is possible to specify a variable referred to from each activity from the definition of the business process.

  Next, the CPU 900 of the business process development computer 300 executes the processing of steps 11064, 11065 and 11066 for each variable extracted from the business process (steps 11063 and 11067).

  The CPU 900 of the business process development computer 300 first searches the variable reference relation storage table 240 for the extracted variables based on the area name and the variable name, and the area name 241 and the variable name 242 match. Records are extracted (step 11064). If a variable to be processed is already referenced in an activity defined before the activity S in the area, it is not necessary to register the same variable in the variable reference relationship storage table 240 in advance, Search for registered variables.

  The CPU 900 of the business process development computer 300 determines whether or not a corresponding record exists in the processing of step 11064 (step 11065). If the corresponding record exists (the result of step 11065 is “Yes”), the variable to be processed has already been registered in the variable reference relation storage table 240, so that the variable is not registered and another variable is registered. Continue processing for.

  If the corresponding record does not exist (the result of step 11065 is “No”), that is, if the use of the variable to be processed in the area is not registered, the CPU 900 of the business process development computer 300 A record corresponding to the variable is added to the variable reference relation storage table 240 (step 11066). By adding a record to the variable reference relationship storage table 240, the use of the variable in the area is registered. Referring to the variable reference relation storage table 240 shown in FIG. 7, the record in the first line indicates that the variable in-A1 is referred to in the area realm-A1 (1701). The same applies to subsequent records.

  The CPU 900 of the business process development computer 300 executes the processing of steps 11064, 11065, and 11066 for all the variables extracted in the processing of step 11062, and then determines whether or not the activity S is the last activity in the area. Determination is made (step 11068). If the activity S is the last activity in the area (the result of step 11068 is “Yes”), this process ends. If the activity S is not the last activity (the result of step 11068 is “No”), the activity next to the activity S is set to a new S (step 11069), and the processing returns to step 11062.

  Through the above procedure, all variables referred to by activities included in each area can be extracted, and the result of associating the extracted variable names with the area names can be stored in the variable reference relation storage table 240.

  When the processing of step 1106 ends, the CPU 900 of the business process development computer 300 ends the business process analysis processing.

  In the embodiment of the present invention, as a result of the processing in step 1106, as shown in FIG. 16, in the area realm-A1 (1710), the variables in-A1, var-A1, and out-A1 are referred. In the area realm-A2 (1711), the variables in-A2, var-A1, var-A2, and out-A2 are referred to.

  Further, as shown in FIG. 7, variables in-A1, var-A1, and out-A1 are referred to in the area realm-A1, and variables in-A2, var-A1, var-A2, and out-- are referred to in the area realm-A2. Reference to A2 is stored in the variable reference relation storage table 240.

  FIG. 13 is a flowchart illustrating a procedure when executing a business process according to the embodiment of this invention.

  The client computer 701 receives the service execution request transmitted by the client 820, and requests the business process execution computer 201 to execute the service (business process) by the service call program 710 (step 1201). The process of step 1201 can also be regarded as a process of waiting until a service execution request is received from the client 820. The business process execution request may be requested from an external system. Further, it may be requested by executing software such as a program, or may be requested by hardware having the function.

  The CPU 900 of the business process execution computer 201 receives the service execution request transmitted by the client computer 701 and starts the execution of the specified business process by the business process execution unit 221. If the business process has been made permanent, the business process is activated.

  Note that when a persistence point is specified before an activity other than the reception activity, the timing for activating the business process is included in cases other than the reception of the request. However, in the embodiment of the present invention, The case where the persistence point is specified only before will be described.

  When the business process execution unit 221 receives a business process execution request from the client 820, the CPU 900 of the business process execution computer 201 first identifies an activity to be executed. The identified business process name and activity name are notified to the load area determination unit 222 (step 1202). The technology for identifying the business process and activity to be executed next based on the received business process execution request is a function realized by a general-purpose business process execution program that is a conventional technology. Is omitted.

  The CPU 900 of the business process execution computer 201 specifies the area to be executed next based on the business process name and activity name notified in the process of step 1202 by the load area determination unit 222. Furthermore, the activity and variable included in the specified area are returned to the business process execution unit 221 (step 1203).

  Details of the load area specifying process executed by the load area determining unit 222 in the process of step 1203 will be described below with reference to FIG.

  FIG. 14 is a flowchart showing a procedure for acquiring an activity included in an area to be loaded and a variable used in the area according to the embodiment of this invention.

  First, the CPU 900 of the business process execution computer 201 specifies an area including the activity name notified from the business process execution unit 221 (step 1401). More specifically, the process division result storage table 230 is searched based on the notified business process name and activity name, and records in which the business process name 231 matches and the activity name 233 matches are extracted.

  Next, the CPU 900 of the business process execution computer 201 extracts activities included in the area specified in the process of step 1401 (step 1402). Specifically, the process division result storage table 230 is searched based on the business process name and the name of the area specified in step 1401, the business process name 231 matches, and the area name 232 matches. Get all activity names.

  Further, the CPU 900 of the business process execution computer 201 extracts variables used in the area specified in the process of step 1401 (step 1403). More specifically, the variable reference relationship storage table 240 is searched based on the area name specified in the process of step 1401, and all variable names that match the area name 241 are acquired.

  Finally, the CPU 900 of the business process execution computer 201 notifies the business process execution unit 221 of all activity names extracted in the process of step 1402 and all variable names extracted in the process of step 1403 (step 1404). ).

  Now, the description returns to the flowchart of FIG.

  The CPU 900 of the business process execution computer 201 loads the flow definition including the activity responded in the process of step 1203 and the variable definition information and the value thereof onto the memory by the business process execution unit 221, and is defined in the area. Execute business process (activity). Further, the business process is made permanent by storing the execution results in the process execution state storage table 250 and the variable state storage table 260 (step 1204).

  The CPU 900 of the business process execution computer 201 determines whether or not the area executed in the process of step 1204 is the last area included in the business process by the business process execution unit 221 (step 1205). If it is the last area (the result of step 1205 is “Yes”), the execution of the business process is terminated. If it is not the last region (the result of step 1205 is “No”), the process returns to step 1201 to wait until the business process is activated.

  As described above, the divided business processes can be executed for each region by the procedure shown in FIG.

  Next, an analysis procedure when the business process includes a control structure will be described with reference to FIG. The control structure is a structure that performs flow control such as branch processing or parallel processing in a business process. Specifically, an activity corresponding to the control structure is included in the business process.

  The branch process is a control structure for selecting (controlling) a flow at the time of executing a business process based on a value of a variable defined in the business process. Parallel processing is a control structure for processing a plurality of processing flows in parallel.

  FIG. 18 is a diagram illustrating an example of a business process including the control structure according to the embodiment of this invention.

  In the example of the business process BP-B1800 shown in FIG. 18, a control structure 1850 is included after “invoke-A1”.

  First, a case where the control structure 1850 is a branch process will be described. The control structure 1850 executes four activities from invoke-A2 to reply-A3 when a predetermined condition is satisfied. When the condition is not satisfied, four activities from invoke-A4 to reply-A5 are executed.

  On the other hand, when the control structure 1850 is parallel processing, after the reply-A1 activity is executed, there are four activities from invoke-A2 to reply-A3 and four activities from invoke-A4 to reply-A5. Run in parallel. Then, after both the reply-A3 and reply-A5 processes are completed, the processes after invoke-A7 are executed.

  Here, the analysis process of a business process including a control structure will be explained. When a business process includes a control structure, the business process is divided in advance before and after the control structure, and is divided into business processes not including the control structure. . Then, the region is further divided by applying the processing procedure shown in FIG. 9 to each divided flow. In other words, before the business process analysis process is executed by the flow definition analysis unit 320 shown in FIG. 9, a preprocess for adding a permanent point before and after the control structure may be executed.

  The business process BP-B1800 shown in FIG. 18 has a flow 1801 from the start of the business process to the start of the control structure, flows 1810 and 1811 for each flow included in the control structure, and flows from the end of the control structure to the end of the business process. It is divided as 1802.

  Further, another analysis procedure when the business process includes a control structure will be described with reference to FIG.

  FIG. 19 is a diagram illustrating an example of a business process including the control structure according to the embodiment of this invention. The structure of the business process itself is the same as that shown in FIG.

  The analysis result shown in FIG. 19 is a result of dividing the region without specially distinguishing the control structure. For this reason, the area 1901 before the start of the control structure includes activities invoke-A2 and invoke-A5 defined before 1910 and 1911 which are the first persistence points extracted in the flow in the control structure. ing.

  In addition, the areas 1902 and 1903 including the flow in the control structure indicate that the activity invoke-A7 defined up to the first persistence point 1912 after the end of the control structure is included. That is, in the example of FIG. 19, for each flow included in the control structure, the area up to the first persistence point is included in the area before the start of the control structure, and the last area of each flow is the control structure. Indicates that the activity defined by the first persistence point after the end is included.

  Note that when the control structures are parallel, the invoke-A7 is included in the areas 1902 and 1903, so that if the activity is executed for each area, the invoke-A7 may be executed without being synchronized. . Therefore, when the control structures are parallel, there is a possibility that a problem occurs if the areas are divided without distinguishing the control structures.

  As described above, the business process including the control structure can be divided for each region by the method shown in FIGS.

  Next, a method for reconfiguring each area of the business process based on the operation statistics of the business process after the business process is analyzed by the procedure described above with reference to FIG. 9 and the business process is executed will be described. In the embodiment of the present invention, an average value is used as the operation statistics, but other values may be used.

  The procedure for reconfiguring each area of the business process is substantially the same as the procedure shown in FIG. 9 and is executed by the flow definition analysis unit 320.

  The procedure added when reconfiguring the business process sets a persistence point based on the operating status of the business process in an algorithm (see FIG. 10) for extracting the persistence point.

  Specifically, first, an average value of the difference between the start time of the activity S in FIG. 10 and the end time of the activity executed before the activity S is calculated. If the calculated value is larger than a reference value (predetermined threshold), it is determined that the time from the end of the activity executed before the activity S to the start of the execution of S is long, and the activity The point before S is designated as the persistence point.

  On the other hand, when the calculated value is smaller than the reference value, it is determined that the time from the end of the activity executed before the activity S to the start of the execution of the activity S is short, and the activity S is a reception activity. Even in such a case, the point immediately before the activity S is not set as a permanent point.

  The start time of the activity S and the end time of the activity executed before the activity S can be acquired from the process execution state storage table 250. Specifically, the process execution state storage table 250 is searched based on the business process name and the activity S and the activity name executed before the activity S. Then, a record in which the business process name 251 matches and the activity name 252 matches is extracted, and the start time 254 or the end time 255 is acquired.

  Further, the reference value may be fixed numerical information (for example, 30 seconds) or may be specific numerical data designated by the business process developer 800. Further, it may be a numerical value calculated from the execution time of the entire business process, or may be a value depending on a service provided by the business process.

  By the above procedure, it becomes possible to dynamically divide the area based on the operation statistics at the time of executing the business process, and more efficient execution of the business process can be realized. Note that the reconfiguration at the time of executing the business process is not necessarily performed, and the area may be divided only when the business process is defined.

  Finally, the effect when the business process analysis and execution method according to the embodiment of the present invention is applied to the business process BP-A 1700 shown in FIG. 15 will be described with reference to FIGS. 20 and 21. FIG.

  As described above, when the business process BP-A 1700 is analyzed by the flow definition analysis unit 320, the business process BP-A 1700 is divided into two regions (regions 1710 and 1720 in FIG. 16).

  20 and 21 are diagrams for explaining the effects of the division and execution of business processes according to the embodiment of this invention.

  FIG. 20 is a diagram for explaining information developed on the memory at the timing when receive-A1 which is the first activity of the business process BP-A1700 is executed. In the table of FIG. 20, each record surrounded by a thick frame is read at the timing when the receive-A1 activity is executed.

  In the business process BP-A 1700, as shown in the area realm-A1 (1710) shown in FIG. 16, the area from the receive-A1 activity to the reply-A1 activity is divided as one area. Therefore, in the memory, the flow definition from the receive-A1 activity to the reply-A1 activity and the variables referred to during execution of the reply-A1 activity to the reply-A1 activity are in-A1, var-A1, and out- A1 is expanded.

  Conventionally, flow definition information (from receive-A2 activity to reply-A2 activity) and variables (in-A2, var-A2, and out-A2) that are not necessary for executing the activity included in the area realm-A1 That is, all the records stored in the table of FIG. 20 have been read into the memory.

  In the embodiment of the present invention, only records surrounded by a thick frame in the table in FIG. 20 are read into the memory, so that the amount of data read and the amount of information developed on the memory are compared with the conventional case. Can be reduced.

  FIG. 21 shows information written in each table at the timing when the execution of the receive-A1 activity is completed.

  When the execution of the receive-A1 activity is completed, the business process BP-A1700 is made permanent, and the execution state of the business process and the state of each variable are stored in each table. In the table in FIG. 21, records surrounded by a thick frame are records that are written when the execution of the receive-A1 activity is completed.

  Conventionally, when the business process BP-A 1700 is made permanent, all the records stored in the table in FIG. 21 are written. However, in the embodiment of the present invention, only the information in the bold frame is written. Therefore, the amount of data to be written can be reduced.

  According to the embodiment of the present invention, by dividing and executing a business process for each region, it is possible to reduce the amount of resources necessary for executing the business process, particularly the amount of memory used.

  Further, according to the embodiment of the present invention, the business process is divided into regions, thereby reducing the amount of data written when the business process is made permanent and the amount of data read when the business process is activated. Execution performance can be improved.

It is a figure which shows an example of a structure of the SOA system of embodiment of this invention. It is a figure which shows an example of a structure of the computer for business process development of embodiment of this invention. It is a figure which shows an example of a structure of the business process execution computer of embodiment of this invention. It is a figure which shows an example of a structure of the process execution state storage table of embodiment of this invention. It is a figure which shows an example of a structure of the variable state storage table of embodiment of this invention. It is a figure which shows an example of a structure of the process division | segmentation result storage table of embodiment of this invention. It is a figure which shows an example of a structure of the variable reference relationship storage table of embodiment of this invention. It is a figure which shows an example of the definition (XML format) of the business process of embodiment of this invention. It is a flowchart which shows the procedure which analyzes the business process in embodiment of this invention. It is a flowchart which shows the procedure of the permanent point extraction process which extracts the permanent point which divides | segments the business process of embodiment of this invention. It is a flowchart which shows the procedure of the business process area | region division | segmentation process by the flow definition analysis part of embodiment of this invention. It is a flowchart which shows the procedure of the variable reference relationship analysis process by the variable reference relationship analysis part of embodiment of this invention. It is a flowchart which shows the procedure at the time of business process execution of embodiment of this invention. It is a flowchart which shows the procedure which specifies the area | region loaded and identifies the activity contained in the specified area | region, and the variable used by the specified area | region of embodiment of this invention. It is a figure which shows an example of the definition (flowchart format) of the business process of embodiment of this invention. It is a figure which shows an example of the state after the business process of embodiment of this invention was analyzed. It is a figure which shows an example of the permanent point edit screen shown to the business process developer of embodiment of this invention. It is a figure which shows an example of the business process containing the control structure of embodiment of this invention. It is a figure which shows an example of the business process containing the control structure of embodiment of this invention. It is a figure explaining the effect by division and execution of a business process of an embodiment of the invention. It is a figure explaining the effect by division and execution of a business process of an embodiment of the invention.

Explanation of symbols

201 business process execution computer 221 business process execution unit 222 load area determination unit 230 process division result storage table 240 variable reference relation storage table 250 process execution state storage table 260 variable state storage table 300 business process development computer 310 business process development unit 311 Business process persistence point presentation unit 312 Business process persistence point specification unit 320 Flow definition analysis unit 330 Variable reference relation analysis unit 501 Service execution computer 510 Service execution platform program 701 Client computer 710 Service call program 800 Business process developer 820 Client 900 CPU
910 Network interface 920 Graphic interface 921 Image display device 930 User input interface 940 Main storage device 950 Secondary storage device 960 System bus 1000 Network

Claims (20)

A business process execution method in a computer system comprising: a service execution device that provides a service; and a business process execution device that executes a business process that defines a business process by combining the services,
The business process execution device includes an interface connected to the service execution device, a processor connected to the interface, and a memory connected to the processor,
The business process is divided into regions including at least one activity based on the activities constituting the business process,
The memory stores process execution state information for storing execution information including execution progress of the business process, and process division information including correspondence between the area and the activity,
The method
When the execution of the business process is accepted, the activity to be executed is identified based on the process execution state information and the process division information,
Extracting an area containing the identified activity;
Obtaining execution information corresponding to the extracted area from the process execution state information;
Based on the acquired execution information, the activity included in the extracted area is executed,
When the execution of all activities included in the extracted area is completed, the execution information corresponding to the extracted area is stored in the process execution state information. The method
If the business process is defined, identify activities that are likely to interrupt the execution of the business process,
The business process execution method according to claim 1, wherein the business process is divided based on the identified activity.   The business process execution method according to claim 2, wherein the activity that is likely to be interrupted in the execution of the business process is a reception activity that accepts an input from the outside.   3. The business process execution method according to claim 2, wherein when the business process is newly defined, the method presents a division result of the business process.   5. The business process execution method according to claim 4, wherein after the division result of the business process is presented, division or integration of the area is accepted.   The business process execution method according to claim 1, wherein the execution information corresponding to the extracted area includes a variable used when the business process is executed. The method
Measuring time information including an execution start time and an execution end time of an activity included in the business process;
The business process execution method according to claim 1, wherein the business process is divided based on the measured time information. The method
Based on the time information, calculate the execution interval of the activity,
The business process execution method according to claim 7, wherein the business process is divided between activities in which the calculated execution interval is longer than a predetermined threshold.   The business process execution method according to claim 1, wherein the business process is divided based on an activity that controls parallel processing.   The business process execution method according to claim 1, wherein the business process is divided based on an activity that controls conditional branch processing. A business process execution device that connects to a service execution device that provides a service and executes a business process that defines business processing by combining the services,
An interface connected to the service execution device, a processor connected to the interface, and a memory connected to the processor,
The business process is divided into regions including at least one activity based on the activities constituting the business process,
The memory stores process execution state information for storing execution information including execution progress of the business process, and process division information including correspondence between the area and the activity,
The processor is
When the execution of the business process is accepted, the activity to be executed is identified based on the process execution state information and the process division information,
Extracting an area containing the identified activity;
Obtaining execution information corresponding to the extracted area from the process execution state information;
Based on the acquired execution information, the activity included in the extracted area is executed,
A business process execution apparatus characterized in that, when execution of all activities included in the extracted area is completed, execution information corresponding to the extracted area is stored in the process execution state information. The processor is
If the business process is newly defined, identify activities that are likely to interrupt the execution of the business process,
The business process execution device according to claim 11, wherein the business process is divided based on the identified activity.   13. The business process execution apparatus according to claim 12, wherein the activity that is highly likely to be interrupted in execution of the business process is a reception activity that accepts an input from the outside.   12. The business process execution device according to claim 11, wherein the execution information corresponding to the extracted area includes a variable used when the business process is executed. The processor is
Measuring time information including an execution start time and an execution end time of an activity included in the business process;
The business process execution device according to claim 11, wherein the business process is divided based on the measured time information. The processor is
Based on the measured time information, the execution interval of the activity is calculated,
The business process execution device according to claim 15, wherein the business process is divided between activities in which the calculated execution interval is longer than a predetermined threshold. A program executed by a business process execution device that connects to a service execution device that provides a service and executes a business process that defines a business process by combining the services,
The business process is divided into regions including at least one activity based on the activities constituting the business process,
The business process execution device stores process execution state information for storing execution information including execution progress of the business process, and process division information including correspondence between the area and the activity,
The program is
When the execution of the business process is accepted, a procedure for identifying an activity to be executed based on the process execution state information and the process division information;
Extracting an area containing the identified activity;
A procedure for acquiring execution information corresponding to the extracted area from the process execution state information;
A procedure for executing an activity included in the extracted area based on the acquired execution information;
A procedure for storing execution information corresponding to the extracted area in the process execution state information when execution of all activities included in the extracted area is completed. Process execution program. The program is
If the business process is newly defined, an activity procedure that is likely to interrupt the execution of the business process; and
The business process execution program according to claim 17, further comprising a step of dividing the business process based on the identified activity. The program is
A procedure for measuring time information including an execution start time and an execution end time of an activity included in the business process;
The business process execution program according to claim 17, further comprising a step of dividing the business process based on the measured time information. The program is
A procedure for calculating an execution interval of the activity based on the measured time information;
The business process execution program according to claim 19, further comprising a step of dividing the business process among activities whose calculated execution interval is longer than a predetermined threshold.

Images