JP2007257513A - Workflow tracking system, integrated management device, method, program and information recording medium which records the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that operation process monitor tracking is constrained in workflow management not under distributed environment and the business process monitor tracking is inefficient in an operation by an opposed type even under distributed environment. <P>SOLUTION: A DsWfMS4 which acquires information regarding the workflows (WF) from workflow systems (WFS) 1-3 to generate an integrated WF has: a Wf definition/service definition acquisition part 55 which acquires workflow description for representing the contents of the WFs in a standardized data form from the WFS 1-3; an event data receiving part 49 which acquires event information representing the contents of events generated when the WF is executed by the WFS 1-3; an event data association part 51 which detects association with other events regarding each event to be specified by the acquired event information; a Wf compositing part 48 which generates the integrated WF; an event storage DB 52 which records all pieces of acquired event information and a tracking display creation part 54 which refers the recorded event information according to request from other devices. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  In general, the present invention belongs to a workflow management system for performing business cooperation by linking a plurality of business application systems regardless of whether or not the Internet is used. Related to progress tracking and status assessment of work conducted in Japan.

  Two examples of methods related to a conventional business process tracking device are described below. The method shown in FIG. 18 is a method that does not have a distributed management concept for workflow management (hereinafter referred to as the first conventional method). The method shown in FIG. 19 is a method that has a distributed management concept in the conventional business process tracking apparatus, but is a method that is considered to have problems in terms of efficiency and the like (hereinafter referred to as the conventional second method).

  FIG. 18 shows a configuration example of a first conventional system disclosed in Patent Document 1. As shown in FIG.

  In the system shown in FIG. 18, B1 is an event management apparatus that collects and manages event data, B3, B4, and B5 are business systems, and B6 is a user terminal.

  In the event management device B1, the input unit B11 inputs search conditions for event data. The event queue B12 queues event data transmitted from the business systems B3 to B5. The event association unit B13 collects event data in the event queue B12 in units of business data and associates the business data. The event management DBB 14 stores associated business data. The business process DBB 15 stores business process definition information and business data definition information. The output unit B16 outputs the search result of the event management DB B14 based on the search condition input from the user terminal B6.

  A business process means the flow of the entire business across business systems. In the following description, it is assumed that the business process is composed of business such as order receipt, inventory inquiry, order placement, acceptance, shipment, and delivery. Further, the business data means event data shared among a certain unit of business as described above. The business data is stored in the event management DBB 14 in the form of a slip for each business.

  In the business system B3, the applications B30 and B30 'execute business in the business system B3. The state DBB31 stores the state of the application B30, and the state DBB31 'stores the state of the application B30'. The event extraction unit B32 extracts event data from the state DBB31 and the state DBB31 '. The event data conversion unit B33 converts the extracted event data into, for example, an XML (Extensible Markup Language) format. The event data transmission unit B34 transmits the converted event data to the event management device B1. Event extraction definition data (hereinafter simply referred to as event extraction definition) B320 defines which data items in the business system B3 are to be extracted.

  In the business system B4, the applications B40 and B40 'execute a business in the business system B4. The state DBB 41 stores the state of the application B40. The state DBB 41 'stores the state of the application B40'. The event extraction unit B42 extracts event data from the state DBB41 or the state DBB41 '. The event data conversion unit B43 converts the extracted event data into, for example, an XML format. The event data transmission unit B44 transmits the converted event data to the event management device B1. The event extraction definition B420 defines which data items in the business system B4 are to be extracted.

  In the business system B5, the applications B50 and B50 'execute a business in the business system B5. The state DBB51 stores the state of the application B50. The state DBB 51 'stores the state of the application B50'. The event extraction unit B52 extracts event data from the state DBB51 or the state DBB51 '. The event data conversion unit B53 converts the extracted event data into, for example, an XML format. The event data transmission unit B54 transmits the converted event data to the event management device B1. The event extraction definition B520 defines which data items in the business system B5 are to be extracted.

  The event data queued in the event queue B12 of the event management device B1 includes, for example, the event type indicating the event type, the primary key that is the identifier of the data to which the event belongs, and the business related to the business corresponding to the primary key It consists of attribute data such as related keys, serial numbers, quantity, unit price, etc., which are identifiers of data to which the event belongs.

  The business systems B3 to B5 are arranged as follows. The business system B3 executes, for example, business operations such as order receipt and inventory inquiry, and handles order receipts. The business system B4 executes, for example, business of ordering and receiving and handles an order slip. The business system B5 executes, for example, business of shipping and delivery and handles delivery slips.

  In the first conventional method, as preparation for tracking of business processes, the input of business process and business data definition information stored in the business process DBB15, and the events set in the event extraction units B32 to B52 of the business systems B3 to B5 Input of extraction definitions B320 to B520 is required.

  FIG. 19 shows a system configuration example of a method (hereinafter referred to as a conventional second method) using a technique related to conventional business process tracking having a distributed management concept described in Patent Document 2.

  FIG. 19 shows an overall view of two organizations (symbol: ORG1) A1 and (symbol: ORG2) A2 involved in the execution of the common business process. These two organizations are, for example, partner organizations of the same company or company, and each organization implements a respective part of the common business process. Alternatively, a case where one of the organizations, for example, the organization A1 is a customer organization and the execution of at least a part of the business process is entrusted to the organization A2, which is a supplier, is also applicable. The conventional technology of this method can be applied even when there are three or more organizations involved in the execution of the common business process.

Organizations A1 and A2 involved in the execution of this business process (hereinafter referred to simply as “participating organizations”) have their workflow management system (symbol: WfMS1) A3, (symbol: WfMS2) has A4. Specifically, each workflow management system A3, A4 in each participating organization A1, A2 corresponds to a computer-based management system operating on each data processing system of that organization.
The data processing system of each participating organization A1, A2 includes one or more generally several personal computers or workstations. In the case of several, LAN (Local Area Network), WAN (Wide Area) Are interconnected via a data communication network such as Network) and are interconnected via the Internet if the organization is distributed in different geographical locations.

  The workflow management systems A3 and A4 of each participating organization A1 and A2 include a workflow management system server (symbol: WfMS1_S) A5 and (symbol: WfMS2_S) A6 (these are hereinafter simply referred to as workflow servers). The workflow servers A5 and A6 are server computer applications that operate and operate as servers of the workflow management systems A3 and A4. The workflow servers A5 and A6 maintain and update information related to the execution state of each part of the business process. The information maintained and managed by the workflow server is changed in state by an event operation on the workflow, and information on the execution state is updated.

  With the introduction of these workflow management systems A3 and A4, it becomes possible to digitize general business processes, and modeling and electronic business processes are defined based on syntactical units. After the model of the electronic business process is created, a template of a class of similar processes performed in the company or in the company is configured. The process template can generally be instantiated and interpreted by a data processing system to determine the individual sequence of work steps required to perform a business process. The sequence of work steps will depend on the context of the process template instantiation. Process template instances and their interpretation represent individual processes. The basic elements of a process template are called activities. An activity represents a business action that can also be regarded as a semantic entity. A process template describes a workflow activity, its execution order and assigned resources.

  As shown in FIG. 19, the workflow server A5 includes a plurality of process templates (symbol: PT1) A13, (symbol: PT2) A11,. . To manage. Similarly, the workflow server A6 includes a plurality of process templates (symbol: PT1 ′) A14, (symbol: PT2 ′) A12,. . To manage.

  The process instance (symbol: PI1 (PT1)) A9 of the process template A11 is also shown schematically in the workflow server A5, and the corresponding process instance PI of the same process template A11 is shown. (PT1) is running on workflow server A6.

  In each participating organization A1, A2, the workflow server A5, A6 has its own state shadowing engine (symbol) running on the same server computer or workstation where the respective workflow server is running. : SSE1) A15, (Symbol: SSE2) A16.

In each participating organization A1, A2, multiple workflow management system clients (symbol: WfMS1_C) A17, (symbol: WfMS2_C) A18 (hereinafter simply referred to as workflow clients) have their state shadowing engines. It interacts with the workflow servers A5 and A6 via the interfaces provided in A15 and A16.
The workflow clients A17 and A18 are client applications that run on a personal computer or workstation. The users (symbol: Ua) A27, (symbol: Ub) A29, (symbol: Uc) A28, (symbol: Ud) A30 of the workflow management systems A3 and A4 in the participating organizations A1 and A2 are the workflow client A17, Using A18, you can interact with the workflow management systems A3 and A4 of your organization.

  Workflow servers A5 and A6 have interfaces (symbol: WfMS1_ST) and (symbol: WfMS2_ST), respectively, so that users A27, A29, A28, and A30 in organizations A1 and A2 pass through workflow clients A17 and A18. To log on to the relevant workflow server A5, A6, see the status of the activity being executed in that organization (for example, start, end, complete), and update the status of that activity as needed Can be added. Different users have different user identifiers, for example, user A27 has UIda, A29 has UIDb, A28 has UIDc, and A30 has UIDd, which allows workflow clients A17 and A18 to interact with workflow servers A5 and A6. It is possible to refer to and update the status of the workflow management system. Different privilege levels can be assigned to these different user identifiers, so that different users can operate the workflow management systems A3, A4 with different privilege levels. For example, a user A27 having a user identifier UIDa can be assigned privileges to refer to and update the state of the workflow management system A3, and a user A29 having an identifier UIDb can be assigned a lower privilege. Only the status of the workflow management system A3 can be referred to.

  The state shadowing engines A15, A16 of the two organizations A1, A2 can communicate with each other. This interaction is made possible by connecting any suitable data communication infrastructure DCI to the data processing systems of the two organizations A1, A2, such as LAN, WAN, Internet, etc.

  Each state shadowing engine A15, A16 implements a state shadowing function that allows users of one of the organizations involved in the execution of a common business process to monitor the progress of workflows in other participating organizations. Can be tracked. For example, the state shadowing function allows the users A27 and A29 of the workflow management system A3 in the organization A1 to track the progress of the workflow in the organization A2, and vice versa.

  Specifically, the state shadowing function realized by the state shadowing engines A15 and A16 enables execution by other organizations in the common business process within the workflow management systems A3 and A4 of each participating organization A1 and A2. It is possible to create a shadow that is an internal copy of the portion that is being processed.

  When an operation is performed by one of the participating organizations, for example, organization A2, during the execution of each part of the common business process, the local workflow management system A4 changes the state, via the state shadowing engine A16, A message notifying the status change is sent to another participating organization, for example, the workflow management system A3 of the organization A1. Participating organization A1's state shadowing engine A15 receives the message, converts it as necessary, and causes a corresponding state change. Thereby, the state of the workflow management system A4 of the organization A2 can be duplicated.

  The state shadowing engines A15 and A16 communicate with each other by using the existing interfaces (symbol: WfMS1_SI) A7 and (symbol: WfMS2_SI) A8 of the accompanying workflow servers A5 and A6.

For this purpose, the state shadowing engines A15, A16 are defined with respective user identifiers UIDx, UIDy with appropriate high level privileges. The state shadowing engines A15 and A16 use the user identifiers UIDx and UIDy when logging into the respective workflow servers A5 and A6. From the above, the state shadowing engines A15 and A16 are regarded as one workflow client when viewed from the respective workflow partners A5 and A6.
JP 2005-115494 A JP 2004-5550 A

Issues related to the conventional business process tracking device will be described.
The conventional second method has solved some problems in the conventional first method, but the conventional second method has its own problems. First, problems in the first conventional method will be described.

The problems in the first conventional method are complex and hierarchical, and are divided into basic problems and related problems.
There are two basic issues.

  The first basic problem is that the first conventional method is a method found in products related to EAI (Enterprise Application Integration) and cannot be handled in a distributed environment. Inter-organizational collaboration and business collaboration between different companies based on the Internet are extremely widespread matters, and cannot be handled by a single industry alone. For this reason, the role of standards including interdisciplinary matters (items related to one industry and items related to other industries, and items that cross between these industries) becomes very large. Therefore, in reality, it can be realized for the first time in a multi-vendor distributed environment. However, the first conventional method as shown in FIG. 18 is not intended for a distributed environment at the workflow level.

  The second basic problem is that the role of the workflow engine is not clearly defined in the first conventional method. When an environment as shown in FIG. 18 is constructed, the role of the workflow engine is decisive, and system cooperation ignoring this existence cannot be assumed. For this reason, in the case of service-oriented cooperation, there arises a problem that it is impossible to cooperate with other workflow systems at all.

Three more related issues occur due to the above two basic issues.
The first related issue is that the business flow must be defined by itself. In normal workflow and business tracking products, the flow of business processes is controlled by an internal workflow engine. However, since the first conventional method is independent of the workflow engine, the business flow must be defined and input by itself. This causes a problem that if the business flow changes dynamically, all of the business must be re-registered or definition information must be input twice with the workflow engine.

  The second related problem is that the system of the conventional first method cannot track the flow of the entire business even when combined with the business flow engine. In other words, the first conventional system tracks events in a business flow as a unit, so what is not defined in the business flow or how the application is executed to execute the business flow. It is not always possible to track how much processing is performed. In other words, in the first conventional method, when strict tracking is performed, the detailed data cannot be tracked unless business data up to all the branches and leaves are registered. Normally, in the current situation where the workflow is controlled by the workflow engine, it is impractical to track the entire workflow in this way.

  As a third related problem, it is claimed that events can be collected without placing the state management DB on the business system (without adding functions to the business system). There are other platforms and may not be disclosed. When an actual operating environment is considered, it is not realistic to arrange a state management DB as shown in FIG.

  In contrast to the above five problems in the first conventional method, the second conventional method solves several problems. The second basic problem can be solved by the second conventional method. The first related problem can also be solved by applying the template concept to the development environment.

  For the second related issue, expand the template creation range in Fig. 19 or create a new template, start up multiple workflow servers (symbols: WfMS2_S, WfMS1_S), and implement shadowing So you can extend the tracking range. However, regarding the second related problem and the first basic problem, there are preconditions for completely solving by the second conventional method. In the second conventional method, the separation between the part to be defined as the standard and the other part is ambiguous. Therefore, in principle, even if the solution to the first basic problem and the second related problem can be realized, it cannot be solved by the conventional second method alone in the actual implementation. Is also present.

  Further, the third related problem is not particularly mentioned, and the conventional second method is independent of the solution (in other words, the conventional second method cannot solve the third related problem. ). Here, it is referred to as “a problem relating to the independence of the observation means for business process tracking with respect to the business application system”.

  Conventionally, the second method itself has a problem. With this method, it is possible to manage the progress of distributed workflows. However, this method is not primarily oriented to business tracking. In principle, all of the plurality of workflow servers share the progress management of the distributed workflow, so that the task tracking can be realized by looking at the workflow client for an arbitrary workflow server.

  However, according to the second conventional method, this cannot be realized unless all the plurality of workflow servers communicate the progress with each other. In this case, if there are N participating workflow servers, N-squared communication will occur in principle for one communication, and there is a concern that the network usage efficiency will drop decisively. . Hereinafter, this problem is referred to as “a problem related to management inefficiency of a method having a distributed management concept in business process tracking processing”.

  An object of the present invention is to solve the following problems.

  To solve all the above five problems of the first conventional method.

  To solve the above-mentioned “problem regarding management inefficiency of a method having a distributed management concept in business process tracking processing” newly generated in the second method.

  To solve the above-mentioned “problem relating to independence of the observation means for business process tracking with respect to the business application system” that occurs in the conventional first method and cannot be completely solved by the conventional second method.

  In other words, the present invention can deal with a distributed environment, can be easily linked with other workflow systems, does not need to define a business flow, does not require a state management DB, and does not reduce the efficiency of network use. The present invention is directed to a workflow tracking system, a workflow integrated management device, a workflow integrated management method, a workflow integrated management program, and a recording medium recording the same.

  In order to achieve the above object, the present invention provides, as a first aspect, a plurality of workflow execution devices that manage and execute workflows, and an integrated workflow that acquires information about workflows from each of the workflow execution devices and integrates them. Each workflow execution device represents the content of an event that occurs in the own device when executing an arbitrary workflow managed by the own device. A means for recording unique event information, and means for sending recorded event information and a workflow description representing the contents of the workflow in a standardized data format to the workflow integrated management apparatus. Each workflow execution device A means for acquiring a workflow description, an event relation detecting means for detecting a relation with another event for each event specified by event information acquired from each workflow execution apparatus, and a workflow acquired from each workflow execution apparatus. A means for integrating a plurality of workflows based on the description and event information and the detection result of the event-related detection means to generate an integrated workflow; and an event information recording means for recording all event information acquired from each workflow execution device; And a means for referencing the event information recorded in the event information recording means in response to a request from another device.

  In the first aspect of the present invention, the workflow execution device in which the workflow description is defined in a format different from the standardized data format has a built-in or connected standardization device for converting the workflow description into the standardized data format. It is preferable that

  In any of the above configurations of the first aspect of the present invention, it is preferable that the workflow integrated management device further includes means for adding arbitrary information in a form that can be recognized by humans to the event information. The workflow integrated management apparatus preferably includes a patch processing unit that performs statistical processing based on event information recorded in the event information recording unit and generates statistical data. The workflow execution apparatus preferably includes a plurality of adapters for converting a communication procedure unique to a business application system that is a communication partner when executing the workflow into a standardized communication procedure.

  In order to achieve the above object, according to the second aspect of the present invention, as a second aspect, the workflow is obtained by acquiring information related to the workflow from each of a plurality of workflow execution devices that manage and execute the workflow, and generates an integrated workflow that integrates the information. Means for acquiring a workflow description representing the contents of a workflow in a standardized data format from each workflow execution device, and an event generated in the device when each workflow execution device executes the workflow; Means for acquiring event information specific to each event from each workflow execution device, and event-related detection means for detecting an association with other events for each event specified by the acquired event information; From each workflow execution device Based on the obtained workflow description and event information and the detection result of the event related detection means, a means for integrating a plurality of workflows to generate an integrated workflow, and event information for recording all event information acquired from each workflow execution device The present invention provides a workflow integrated management apparatus comprising recording means and means for referring to event information recorded in the event information recording means in response to a request from another apparatus.

  In the second aspect of the present invention, it is preferable to further include means for adding arbitrary information in a form that can be recognized by a human to the event information.

  In any of the above configurations of the second aspect of the present invention, it is preferable to have a patch processing unit that performs statistical processing based on event information recorded in the event information recording unit and generates statistical data.

  In order to achieve the above object, according to the third aspect of the present invention, as a third aspect, a plurality of workflow execution devices that manage and execute workflows, and information related to workflows are acquired from each of the workflow execution devices, and these are integrated. A workflow integrated management method using a workflow integrated management device that generates an integrated workflow, and represents the content of an event that occurs in the own device when each workflow execution device executes an arbitrary workflow managed by the own device , A process of recording unique event information for each event, and each workflow execution apparatus transmits the recorded event information and a workflow description representing the contents of the workflow in a standardized data format to the workflow integrated management apparatus. Each process and workflow integrated management device For each event specified by the event information acquired from the workflow execution device, an event related detection step for detecting a relationship with another event, the workflow description and event information acquired from each workflow execution device by the workflow integrated management device, and A step of integrating a plurality of workflows based on the detection result of the event-related detection unit and generating an integrated workflow, and an event information recording unit that records all event information acquired from each workflow execution device by the workflow integrated management device And a workflow integrated management device comprising: a step of referring to event information recorded in the event information recording means in response to a request from another device. is there.

  In the third aspect of the present invention, the workflow execution device in which the workflow description is defined in a format different from the standardized data format converts the workflow description into a standardized data format and transmits it to the workflow integrated management device. It is preferable to do.

  In any of the above configurations of the third aspect of the present invention, it is preferable that the workflow integrated management device further includes a step of adding arbitrary information in a format that can be recognized by humans to the event information. Moreover, it is preferable that the workflow integrated management apparatus has a patch processing step of performing statistical processing based on the event information recorded in the event information recording step and generating statistical data.

  In order to achieve the above object, the present invention provides, as a fourth aspect, a workflow integrated management program for causing a computer to execute the workflow integrated management method according to any one of the configurations of the third aspect of the present invention. It is to provide.

  In order to achieve the above object, the present invention provides, as a fifth aspect, a computer-readable information recording medium in which a workflow integrated management program is recorded.

  According to the present invention, it is possible to cope with a distributed environment, easy cooperation with other workflow systems, no need to define a business flow, no need to install a state management DB, and no reduction in network utilization efficiency. A workflow tracking system, a workflow integrated management device, a workflow integrated management method, a workflow integrated management program, and a recording medium recording the same can be provided.

[Principle of the Invention]
The present invention maintains a plurality of business application system group activation states and operation order definitions, controls each element workflow part of a whole workflow that means a certain business range, and implements a workflow engine. This is a device that embodies a method for integrating and managing the execution of distributed element workflow parts in an environment where the workflow management system of FIG. The conventional problem is solved by the following means.
[Means 1]
A combination of the following six element means.
A means for collecting descriptions of elementary workflows distributed across multiple workflow management systems.
A means for describing and managing a description of distributed element workflows in a standard format designated in advance.
A means for converting a description of a distributed element workflow that is not described in a standard format into the standard format.
A workflow synthesis means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description.
Event storage element means for positioning an event group that occurs as an event when executing the element workflow part in the description of the entire workflow and recording it in association with an event group other than the event group.
Element means for causing other devices to refer to arbitrary information recorded in the event storage means upon request.
[Means 2]
The event group that occurs as an event when the element workflow part is executed is described as the standard format in order to capture the event group that occurs as an event in the area outside the element workflow described as the standard format. -A proxy communication means that takes care of intermediation when the management method is different.
[Means 3]
Application label input means for giving arbitrary information to the descriptor in the description of the element workflow since the description of the distributed element workflow is in a machine-readable format.
[Means 4]
Apply the event group that occurs as an event when implementing the element workflow part to the description of the entire workflow, access the event storage means to record in relation to the event group other than the event group, and access the statistics related to the event group A processing means for generating data.
[Means 5]
Communication specific to a business application system group when a workflow management system that implements the workflow engine calls a plurality of business application system groups that are maintained and controlled by the definition of the overall workflow according to the description of the overall workflow. Adapter processing means for converting the procedure as a standard communication procedure.
[Work of means to bring effects]
Conventionally, the first basic problem generated by the first method is to clearly define the role of the standard and to promote multi-vendorization. Element means function effectively.
(1) Means for describing and managing the description of distributed element workflows in a standard format designated in advance.
(2) A means for converting a description of a distributed element workflow that is not described in a standard format into the standard format.
(3) Workflow composition means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description.

Conventionally, the second basic problem generated by the first method is that although the role of the workflow engine is decisively important, no specific definition has been made. The problem is that it cannot be linked to the workflow system at all. Also for this, the following three element means combined in particular by means 1 function effectively.
(1) Element means for describing and managing a description of distributed element workflows in a standard format designated in advance.
(2) A means for converting a description of a distributed element workflow that is not described in a standard format into the standard format.
(3) Workflow composition means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description.

  In this method, unlike the method of FIG. 19, the object to be standardized is clearly linked with the existing standardized function range, so the first basic problem that occurs in the conventional first method, the second basic Specific issues can be clearly resolved.

The first related problem that occurs in the conventional first method is that the method is independent of the workflow engine, so that the business flow must be defined and input by itself.
This causes a problem that if the business flow changes dynamically, all of the business must be re-registered or definition information must be input twice with the workflow engine.

In particular, the following four element means combined by means 1 function effectively for the above problems.
(1) Means for collecting descriptions of elementary workflows distributed in a plurality of workflow management systems.
(2) Element means for describing and managing a description of distributed element workflows in a standard format designated in advance.
(3) A means for converting a description of a distributed element workflow that is not described in a standard format into the standard format.
(4) Workflow composition means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description.

  Conventionally, the second related problem that occurs with the first method is that it is not possible to track the flow outside the business flow definition and the flow inside the application. When strict tracking is performed, business data up to all branches and branches are stored. If you don't register, it means you can't track.

The second related problem can be solved by the following functions.
(1) The business process tracking device uses a method with a decentralized management concept.
(2) Provide a proxy communication means that has the mediation as means 2 above.
(3) Provide adapter processing means for converting the communication procedure unique to the business application system group into a standard communication procedure.
(4) A workflow synthesis means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description is provided.
As described above, it is possible to synthesize the business data up to all the branches and leaves and nodes by combining them, which can be solved.

  As a solution to the above “problem related to management inefficiency of a method having a distributed management concept in business process tracking processing”, the distributed management concept in the conventional business process tracking device shown in FIG. 19 is completely contrasted and distributed. In contrast to processing, the present invention provides a centralized system in which a business process monitor / tracking device is arranged.

The premise is that
(1) Workflow composition means for synthesizing a plurality of distributed element workflow descriptions and reproducing the entire workflow description.
(2) Event storage means for applying an event group generated as an event when the element workflow part is executed to the description of the entire workflow and recording it in association with an event group other than the event group.
(3) Element means for causing other devices to refer to arbitrary information recorded in the event storage means upon request.
(4) Application label input means for giving semantic information in the business to the descriptor in the description of the element workflow.
(5) Processing means for generating statistical data that performs statistical processing intensively.
The above five elements exist.

  As a solution to the above “problem regarding the independence of the observation means for business process tracking to the business application system”, when a workflow management system that implements a workflow engine calls a plurality of business application systems, the business application system This is adapter processing means for converting a group-specific communication procedure as a standard communication procedure.

The present invention based on the above principle is effective because the element means included therein can solve all the above five problems occurring in the business process tracking apparatus of the first conventional method shown in FIG.
Furthermore, the conventional solution to the five problems is more effective because it can be expected to be more efficient than the second conventional method.

  Hereinafter, a preferred embodiment of the present invention based on the above principle will be described.

[First Embodiment]
FIG. 1 shows a configuration of a business process tracking apparatus based on a distributed workflow management method according to a first embodiment in which the present invention is preferably implemented. This business process tracking device is composed of a plurality of workflow systems (symbol: WfMS_1) 1 and (symbol: WfMS_2) 2 based on a distributed workflow management system, as well as other company / existing workflow systems (symbol: WfMS_3) that are uniquely implemented. 3 and multiple other companies / existing workflow systems 3 were collected, and various event information was collected from the Proxy system (symbol: PrxS) 4, workflow systems 1, 2, and Proxy system 4 that mediates this distributed workflow management method. Later, a distributed workflow monitor system (symbol: DsWfMS) 5 for organizing, integrating, and storing, and a client system for accessing the distributed workflow monitor system 5 are configured to include client sites 6 and 60 using a Web browser. .

  The workflow system 1 communicates with a plurality of business application systems (symbol: AP_A) 7 and (symbol: AP_B) 8. The workflow system 2 communicates with a plurality of business application systems (symbol: AP_C) 9 and (symbol: AP_D) 10. The workflow system 3 communicates with a plurality of business application systems (symbol: AP_E) 11 and (symbol: AP_F) 12 via the proxy system 4.

  In order to realize the above communication, the business application system 7 includes a data communication unit (symbol: COM_A) 13. The business application system 8 includes a data communication unit (symbol: COM_B) 14.

  Similarly, the business application system 9 includes a data communication unit (symbol: COM_C) 15. The business application system 10 also includes a data communication unit (symbol: COM_D) 16.

  Similarly, the business application system 11 includes a data communication unit (symbol: COM_E) 17. The business application system 12 includes a data communication unit (symbol: COM_F) 18.

  On the other hand, the workflow system 1 includes an adapter (symbol: AD1_A) 19 for communicating with the data communication unit 13 and an adapter (symbol: AD1_B) 20 for communicating with the data communication unit 14. These adapters are different from each other in communication protocol and operation in performing necessary communication with the business application system 7 and the business application system 8 as a result of the operation of the workflow engine (symbol: WfE_1) 29 included in the workflow system 1. Convert differences.

  Similarly, the workflow system 2 includes an adapter (symbol: AD2_C) 21 for communicating with the data communication unit 15 and an adapter (symbol: AD2_D) 22 for communicating with the data communication unit 16. As a result of the operation of the workflow engine (symbol: WfE_2) 32 included in the workflow system 2, these adapters differ in communication protocol and operation when necessary communication is performed with the business application system 9 and the business application system 10. Convert differences.

  Similarly, the workflow system 3 includes an adapter (symbol: AD3_E) 23 for communicating with the data communication unit 17 and an adapter (symbol: AD3_F) 24 for communicating with the data communication unit 18. As a result of the operation of the workflow engine (symbol: WfE — 3) 37 included in the workflow system 3, these adapters differ in communication protocol and operation when necessary communication is performed with the business application system 11 and the business application system 12. Convert differences.

  Since the workflow system 3 is assumed to be an original implementation of another company / existing workflow engine, communication between the data communication unit 17 and the adapter 23 and communication between the data communication unit 18 and the adapter 24 are not performed. This is realized through a proxy unit (symbol: Prx_3) 35 in the Proxy system 4.

The behavior of the workflow engine 29 is defined by a workflow definition (symbol: Wf definition_1) 31 included in the workflow system 1. Usually, one workflow definition 31 is composed of two parts. One part represents only the behavior of the workflow engine 29, and the other part represents the other party's interface with which the workflow engine 29 communicates. Of these, the former is typically described using WS-BPEL (Web Service Business Process Execution Language), and the latter is standard using WSDL (Web Service Definition Language). is there.
The workflow definition 31 includes events related to processing request / processing response messages exchanged with other workflow systems 2 and the workflow system 3 communicated via the proxy system 4 and a plurality of business application systems 7. , 8 defines the state of the workflow engine 29 and what processing request and processing response message are issued when an event related to the processing request / processing response message generated as a result of communication with. Yes.

  The behavior of the workflow engine 32 is defined by a workflow definition (symbol: Wf definition_2) 34 included in the workflow system 2. The workflow definition 34 includes a process request from the other workflow system 1 and the workflow system 3 communicated via the proxy system 4, an event related to a process response message, and a plurality of business application systems 9 and 10. When an event related to a processing request or a processing response message that occurs as a result of communication occurs, the workflow engine 32 is in what state and what processing request or processing response message is issued.

  The behavior of the workflow engine 37 is defined by a workflow definition (symbol: Wf definition — 3) 39 included in the workflow system 3. The workflow definition 39 is communicated from the workflow system 1 and the workflow system 2 via the proxy system 4 via the proxy system 4 and the processing request, the event related to the processing response message, and the business application systems 11 and 12. When an event related to a processing request or a processing response message occurs, it defines what state the workflow engine 37 is in and what processing request or processing response message is issued. Note that the workflow system 3 is assumed to be a third-party / existing workflow engine of its own implementation, so the workflow definition 39 is not always described in a standardized format (for example, WS-BPEL and WSDL). Absent. In that case, the Wf definition / service definition acquisition unit 55 described later converts them into a standardized format.

  Events related to processing requests and processing response messages generated in the workflow system 1 are detected by a plurality of event extraction units scattered in the workflow system 1. All communication between the data communication unit 13 and the adapter 19 is detected by the Msg event extraction unit 25 incorporated in the adapter 19. Similarly, all communication between the data communication unit 14 and the adapter 20 is detected by the Msg event extraction unit 26 incorporated in the adapter 20. The behavior of the workflow engine 29 is detected by the Eng event extraction unit 30.

  The event information extracted by the Msg event extraction unit 25, the Msg event extraction unit 26, and the Eng event extraction unit 30 is temporarily stored in the event data holding unit 40 in the workflow system 1, and is appropriately stored by the common data transmission unit 41. And transferred to the distributed workflow monitor system 5.

  Events relating to processing requests and processing response messages generated in the workflow system 2 are detected by a plurality of event extraction units scattered in the workflow system 2. All communication between the data communication unit 15 and the adapter 21 is detected by the Msg event extraction unit 27 incorporated in the adapter 21. Similarly, all communication between the data communication unit 16 and the adapter 22 is detected by the Msg event extraction unit 28 incorporated in the adapter 22. The behavior of the workflow engine 32 is detected by the Eng event extraction unit 33.

  The event information extracted by the Msg event extraction unit 27, the Msg event extraction unit 28, and the Eng event extraction unit 33 is temporarily stored in the event data holding unit 42 in the workflow system 2, and is appropriately stored by the common data transmission unit 43. And transferred to the distributed workflow monitor system 5.

  The collection of events related to processing requests and processing response messages generated in the workflow system 3 is a proprietary third-party / existing workflow engine, and therefore has a different processing method from the workflow systems 1 and 2. Communication between the data communication unit 17 and the adapter 23 is performed via the proxy unit 35. Therefore, an event related to the generated processing request and processing response message is detected by the Prx event extracting unit 36 connected to the proxy unit 35 in the Proxy system 4. Events relating to processing requests and processing response messages that occur in communication between the data communication unit 18 and the adapter 24 are also detected by the Prx event extraction unit 36.

  The event information extracted by the Prx event extraction unit 36 is temporarily stored in the event data holding unit 45 in the Proxy system 4.

  On the other hand, the behavior of the workflow engine 37 is detected by the Eng event extraction unit 38 arranged in the workflow system 3 and temporarily stored in the common data transmission unit 47. Thereafter, the data related to the event temporarily stored in the workflow system 3 is appropriately transmitted to the Proxy system 4 by the common data transmission unit 47.

  Thereafter, the Proxy system 4 uses the common data receiving unit 46 of itself to collect the data related to the event, and temporarily stores it in the event data holding unit 45 in the Proxy system 4.

  All data related to the event temporarily stored in the event data holding unit 45 is appropriately transferred to the distributed workflow monitor system 5 by the common data transmission unit 44.

  The distributed workflow monitor system 5 receives the workflow definition 31, the workflow definition 34, and the workflow definition 39, and performs a partial conversion on the Wf definition / service definition acquisition unit 55 and all of the Wf definition / service definition acquisition unit 55 obtained. A Wf synthesis unit 48 that synthesizes an integrated workflow definition from the workflow definition, and a synthesis Wf definition 50 that stores and manages the synthesized workflow definition.

  In particular, the Wf definition / service definition acquisition unit 55 can access the repository 56 placed outside.

  Further, the distributed workflow monitor system 5 includes an event data receiving unit 49 that receives all data related to events from the workflow system 1, the workflow system 2, and the proxy system 4, and a composite Wf definition 50 that stores and manages the integrated and combined workflow definitions. The event data correlating unit 51 performs processing for organizing and relating all event data received by the event data receiving unit 49 (defining the causal relationship between birth and death of the event), and holds the associated event data The event storage DB 52 is included. The process of relating event data will be described in detail later.

  Furthermore, the distributed workflow monitor system 5 defines an AP label input unit 58, which is an application for defining and naming business-related labels for the data in the composite Wf definition 50 for storing and managing the integrated and composite workflow definitions, and the composite Wf. Based on the definition 50, the search function unit 53, which is an application for searching event data of a certain condition, associates with the data in the composite Wf definition 50 based on the result returned by the search function unit 53, and arranges the event data in time series A tracking display creation unit 54 for displaying and a batch processing unit 59 for performing statistical processing and evaluation processing based on data stored and managed in the event storage DB 52 are also included. Note that the operation of the batch processing unit 59 (the operation of performing statistical / evaluation processing based on the data accumulated in the database) is the same as the conventionally known operation, and thus detailed description thereof will be omitted.

  The operation of the AP label input unit 58 is performed through one or more client sites 60, and is performed using a screen (a screen for defining meanings for various events) displayed on the client site 60 by a web browser. .

  The search function unit 53 and the tracking display creation unit 54 are operated through one or more client sites 6 and are performed using a screen displayed on the client site 6 by a web browser.

[Description of operation]
FIG. 2 shows an outline of a procedure when collecting event information from a distributed workflow engine.

  When the workflow engine 29 communicates with the business application system 7, the processing request message C 1 is sent to the adapter 19 based on the workflow definition 31. The processing request message C1 may be formed by a Web service or the like and is defined using XML or the like.

  The adapter 19 converts the processing request message C1 into a communication protocol and procedure that can be accepted by the business application system 7, and sends it as a new processing request message C2 to the data communication unit 13 in the business application system 7. .

  The data communication unit 13 receives the processing request message C2 and delivers it to the business application system 7. As a result, if necessary, a new processing response message C3 is generated and transmitted from the data communication unit 13 to the adapter 19.

  The adapter 19 converts the received processing response message C3 into a predetermined communication protocol and procedure, and transmits the converted processing response message C3 to the workflow engine 29 as a processing response message C4.

  The workflow engine 29 determines the next behavior based on the workflow definition 31. As a result, when communicating with the business application system 8, the processing request message C5 is sent to the adapter 20 this time based on the workflow definition 31. The processing request message C5 may also be formed by a Web service or the like and is defined using XML or the like.

  The adapter 20 converts the processing request message C5 into a communication protocol and procedure that can be accepted by the business application system 8, and sends it to the data communication unit 14 in the business application system 8 as a new processing request message C6.

  The data communication unit 14 receives the processing request message C6 and delivers it to the business application system 8. As a result, if necessary, a new processing response message C7 is generated and transmitted from the data communication unit 14 to the adapter 20.

  The adapter 20 converts the processing response message C7 into a predefined communication protocol and procedure, and transmits the processing response message C7 to the workflow engine 29 as a processing response message C8.

  The workflow engine 29 determines the next behavior based on the workflow definition 31, and may communicate with the workflow system 2 as one of the behaviors. In this case, a processing request message C21 is sent to the workflow system 2 this time based on the workflow definition 31. The processing request message C21 may also be formed by a Web service or the like, and is defined using XML or the like.

  When the process response message C22 is transmitted in response to the process request message C21, the workflow engine 29 receives it.

  Events related to processing requests and processing response messages generated in the workflow system 1 are extracted by a plurality of event extraction units scattered in the workflow system 1. Specifically, the adapter 19 incorporates an Msg event extraction unit 25.

  The Msg event extraction unit 25 detects this when the adapter 19 receives the processing request message C1, and records it in the event data holding unit 40 as an event C17 related to the message. In addition, the Msg event extraction unit 25 detects this when the adapter 19 converts the processing request message C1 into a communication protocol and procedure that can be accepted by the business application system 7, and transmits it as the processing request message C2. And recorded in the event data holding unit 40 as an event C18 related to the message.

  Similarly, when the adapter 19 receives the processing response message C3 from the data communication unit 13, the Msg event extraction unit 25 detects this and records it in the event data holding unit 40 as an event C19 related to the message. In addition, the Msg event extraction unit 25 detects this when the adapter 19 converts the processing response message C3 into a processing response message C4 and sends it to the workflow engine 29, and holds event data as an event C20 related to the message. Record in section 40.

  Similarly, an Msg event extraction unit 26 is incorporated in the adapter 20.

  The Msg event extraction unit 26 detects the processing request message C5 in the same manner as the Msg event extraction unit 25, and records it in the event data holding unit 40 as an event C13 related to the message. In addition, the processing request message C6 is detected and recorded in the event data holding unit 40 as an event C14 related to the message. Furthermore, the processing response message C7 is detected and recorded in the event data holding unit 40 as an event C15 related to the message. Finally, the processing response message C8 is detected and recorded in the event data holding unit 40 as an event C16 related to the message.

  The behavior of the workflow engine 29 is detected by the Eng event extraction unit 30. The Eng event extraction unit 30 handles all of the series of events related to messages generated from the workflow engine 29 and received messages.

  For example, the processing request message C1 delivered to the adapter 19 is detected by the Eng event extraction unit 30 and recorded in the event data holding unit 40 as an event C9 related to the message in the engine. Similarly, the processing response message C4 delivered from the adapter 19 is detected by the Eng event extraction unit 30 and recorded in the event data holding unit 40 as an event C10 related to the message in the engine.

  Further, the processing request message C5 delivered to the adapter 20 is detected by the Eng event extracting unit 30 and recorded in the event data holding unit 40 as an event C11 related to the message in the engine. Similarly, the processing response message C8 delivered from the adapter 20 is detected by the Eng event extraction unit 30 and recorded in the event data holding unit 40 as an event C12 related to the message in the engine.

  Furthermore, the same applies when communicating with another workflow system 2. The processing request message C21 sent to the workflow system 2 is detected by the Eng event extraction unit 30 and recorded in the event data holding unit 40 as an event C23 related to the message in the engine. Further, the processing response message C22 returned as a result of the processing request message C21 is also detected by the Eng event extracting unit 30, and recorded in the event data holding unit 40 as an event C24 related to the message in the engine.

  Event data recorded in the event data holding unit 40 in the workflow system 1 (messages recorded by the C17, C18, C19, C20, and Msg event extracting unit 26, which are events related to messages recorded by the Msg event extracting unit 25) C13, C14, C15, C16 that are events related to the event, and C9, C10, C11, C12, C23, C24) that are events related to messages in the engine detected by the Eng event extraction unit 30 are temporarily stored. Thereafter, an event data transfer message C25 in a predetermined format based on this is created by the common data transmission unit 41 and transferred to the distributed workflow monitor system 5 as appropriate.

  The distributed workflow monitor system 5 includes an event data receiving unit 49 that receives all data related to events, and receives an event data transfer message C25.

  Next, using FIG. 3, an outline of a procedure for collecting event information from another company / existing workflow engine that is uniquely implemented via a proxy system will be described.

  When the workflow engine 37 communicates with the business application system 11, the processing request message C30 is sent to the adapter (symbol: AD1_E) 23 based on the workflow definition 39. The processing request message C30 may be formed by a web service or the like and is defined using XML or the like. Here, it is assumed that the workflow system 3 is a third-party / existing workflow engine of its own implementation. Therefore, the communication between the data communication unit 17 and the adapter 23 and the communication between the data communication unit 18 and the adapter 24 are realized via the proxy unit 35 in the Proxy system 4 and are not necessarily performed by a web service or the like. It is not always done.

  The adapter 23 converts the processing request message C30 into a communication protocol and procedure that can be accepted by the business application system 11, and sends it to the data communication unit 17 in the business application system 11 as a new processing request message C31. Send.

  Since sending of the message to the business application system 11 is realized via the proxy unit 35 in the Proxy system 4, the proxy unit 35 receives the processing request message C 31 once and further processes it toward the data communication unit 17. Send as request message C32.

  The data communication unit 17 receives the processing request message C32 and passes it to the business application system 11. As a result, if necessary, a new processing response message C33 is generated and transmitted from the data communication unit 17 to the adapter 23.

  Also in the case of sending a message from the business application system 11 to the workflow system 3, since it is realized through the proxy unit 35 in the Proxy system 4, the proxy unit 35 receives the processing response message C 33 once and further receives it to the adapter 23. Is sent as a process response message C34.

  The adapter 23 converts the processing response message C34 into a predefined communication protocol and procedure, and sends it to the workflow engine 37 as a processing response message C35.

  The workflow engine 37 determines the next behavior based on the workflow definition 39. As a result, when communicating with the business application system 12, the workflow engine 37 now sends a processing request message C 36 to the adapter 24 based on the workflow definition 39.

  The adapter 24 converts the processing request message C36 into a communication protocol and procedure that can be accepted by the business application system 12, and sends it to the data communication unit 18 in the business application system 12 as a new processing request message C37. Send.

  Since the sending of the message to the business application system 12 is realized through the proxy unit 35 in the Proxy system 4, the proxy unit 35 receives the processing request message C 37 once and further sends it to the data communication unit 18. It is transmitted as a processing request message C38.

  The data communication unit 18 receives the processing request message C38 and delivers it to the business application system 12. As a result, if necessary, a new processing response message C39 is generated, and a response is sent from the data communication unit 18 to the adapter 24.

  Also in this case, since the sending is realized via the proxy unit 35 in the Proxy system 4, the proxy unit 35 receives the processing response message C39 once, and further to the adapter 24, the new processing response message C40. Re-send as

  The adapter 24 converts the new process response message C40 into a predefined communication protocol and procedure, and returns it to the workflow engine 37 as a process response message C41.

  The workflow engine 37 determines the next behavior based on the workflow definition 39, and may communicate with the workflow system 2 as one of the behaviors. In this case, a processing request message C48 is sent to the workflow system 2 this time based on the workflow definition 39. The processing request message C48 is not necessarily made by a Web service or the like, but is defined by an arbitrary expression.

  The result of the processing request message C48 is returned to the workflow engine 37 as a processing response message C49.

  The detection of the event group related to the processing request and processing response message generated in the workflow system 3 is a third-party / existing workflow engine that is uniquely implemented, and therefore a method different from the normal processing method is adopted.

  Communication between the data communication unit 17 and the adapter 23 is performed via the proxy unit 35. Therefore, an event related to the generated processing request and processing response message is detected by the Prx event extracting unit 36 connected to the proxy unit 35 in the Proxy system 4. Events relating to processing requests and processing response messages that occur in communication between the data communication unit 18 and the adapter 24 are also detected by the Prx event extraction unit 36.

  The Prx event extraction unit 36 detects the event when the adapter 23 transmits the processing request message C31, the proxy unit 35 receives it, and transmits it to the data communication unit 17 as C32. It is recorded in the event data holding unit 45 as C50. In addition, the Prx event extraction unit 36 detects this when the data communication unit 17 transmits the processing response message C33, the proxy unit 35 receives it, and transmits it to the adapter 23 as C34. Recorded in the event data holding unit 45 as an event C51.

  Similarly, the Prx event extraction unit 36 detects this when the adapter 24 transmits the processing request message C37, the proxy unit 35 receives it, and transmits it to the data communication unit 18 as C38. The event C52 related to the message is recorded in the event data holding unit 45. In addition, the Prx event extraction unit 36 detects this when the data communication unit 18 transmits the processing response message C39, the proxy unit 35 receives it, and transmits it to the adapter 24 as C40. Recorded in the event data holding unit 45 as an event C53.

  The event information extracted by the Prx event extraction unit 36 is temporarily stored in the event data holding unit 45 in the Proxy system 4.

  On the other hand, the behavior of the workflow engine 37 is detected by the Eng event extraction unit 38 arranged in the workflow system 3.

  For example, the processing request message C30 delivered to the adapter 23 is detected by the Eng event extraction unit 38 and temporarily recorded in the common data transmission unit 47 as an event C42 related to the message in the engine. Similarly, the processing response message C35 delivered from the adapter 23 is detected by the Eng event extraction unit 38 and temporarily recorded in the common data transmission unit 47 as an event C43 related to the message in the engine.

  Further, the processing request message C36 delivered to the adapter 24 is detected by the Eng event extraction unit 38 and temporarily recorded in the common data transmission unit 47 as an event C44 related to the message in the engine. Similarly, the processing response message C41 delivered from the adapter 24 is detected by the Eng event extraction unit 38 and temporarily recorded in the common data transmission unit 47 as an event C45 related to the message in the engine.

  Further, the case of communicating with the workflow system 2 is handled in the same manner. The processing request message C48 sent to the workflow system 2 is detected by the Eng event extraction unit 38 and temporarily recorded in the common data transmission unit 47 as an event C46 related to the message in the engine. Further, the processing response message C49 returned as a result of the processing request message C48 is also detected by the Eng event extracting unit 38 and temporarily recorded in the common data transmitting unit 47 as an event C47 related to the message in the engine.

  Thereafter, an event data transfer message C54 is created and transferred to the Proxy system 4 in an appropriately determined format using the common data transmission unit 47 arranged in the workflow system 3.

  Thereafter, the Proxy system 4 receives the event data transfer message C54 regarding the event using its own common data receiving unit 46, and temporarily stores it in the event data holding unit 45 in the Proxy system 4.

  Thereafter, the event data transfer message C26 is created and transferred to the distributed workflow monitor system 5 in a predetermined format by the common data transmission unit 44 as appropriate.

  The distributed workflow monitor system 5 includes an event data receiving unit 49 that receives all data related to events, and accepts an event data transfer message C26.

  In FIG. 4, a workflow definition group (hereinafter referred to as Wf definition) uniquely held in a distributed workflow engine is collected, and a procedure for generating an integrated / synthesized Wf definition, and the integrated Wf. Describes the outline of the procedure for maintaining definitions.

  The behavior of the workflow engine 29 included in the workflow system 1 is defined by a workflow definition 31. Normally, the workflow definition 31 describes only the behavior of the workflow engine 29, and is described in a process description including WS-BPEL and WSDL which are standardized formats.

  The behavior of the workflow engine 32 included in the workflow system 2 is defined by a workflow definition 34. Normally, the workflow definition 34 describes only the behavior of the workflow engine 32, and is described in a process description including WS-BPEL and WSDL which are standardized formats.

  The behavior of the workflow engine 37 included in the workflow system 3 is defined by a workflow definition 39. Here, since the workflow system 3 is assumed to be a third-party / existing workflow engine of its own implementation, the workflow definition 39 is not always described in the standardized format WS-BPEL and WSDL. Absent.

  The workflow definition 31 is a definition transfer message C60, the workflow definition 34 is a definition transfer message C61, and the workflow definition 39 is a definition transfer message C62. 55 is appropriately transferred.

  When the Wf definition / service definition acquisition unit 55 receives the definition transfer messages C60, C61, and C62, it determines the format. If a definition transfer message (here, C62) that is not defined in a standardized format (for example, WS-BPEL and WSDL) is received, the Wf definition / service definition acquisition unit 55 receives a standardized format (for example, WS-BP BPEL and WSDL) and retain.

  FIG. 5 is a diagram showing one expression format of the Wf definition, and shows a description example of WS-BPEL and WSD. Even a non-standardized workflow definition 39 usually has information items that are almost equivalent.

  In FIG. 5, the process definition D1 is described as one WS-BPEL instance. The process definition D1 includes a definition part D3 and activity parts D4, D5, and D6.

  Activity part D4, D5, D6, activity part D4 that defines the behavior when the corresponding message is received, activity part D5 that defines the behavior corresponding to the actual business logic, behavior when sending the corresponding message It is classified into the activity part D6 to be defined.

  In contrast, a specific service definition D2 is described as one WSDL instance. There are two types of service definitions D2: those directly related to the process definition D1 and those that are described independently.

  The service definition D2 is a message definition part D7 that defines the message format when calling the service, the format of the outgoing message generated by calling the service, and the port definition part D8 that defines the actual interface using the message definition part D7. , Including a binding unit D9 that associates the port definition unit D8 with an actual transport, a service definition unit D10 that defines a service using the binding unit D9, and the like.

  When an arbitrary service is specified in the activity part D4 that defines the behavior when a message is received, the port definition part D8 of the service definition D2 corresponding to the service is referred to. Similarly, when an arbitrary service is specified in the activity part D6 that defines the behavior when sending and receiving messages and the activity part D5 that defines the behavior corresponding to the actual business logic, the service corresponding to the service indirectly The port definition unit D8 of the definition D2 is referred to.

  The service definition D2 and the process definition D1 in FIG. 5 are usually described in a computer-readable expression and rarely include semantic information directly.

  Thereafter, the Wf definition / service definition acquisition unit 55 holds all of the workflow definitions 31, 34, and 39 in a standardized format (for example, WS-BPEL and WSDL) obtained by acquisition or conversion. In that case, it may be stored in the repository 56 placed outside.

  In the distributed workflow monitor system 5, a Wf synthesis unit 48 that synthesizes an integrated workflow definition from all the workflow definitions 31, 34, 39, etc. obtained by the Wf definition / service definition acquisition unit 55, and the synthesized workflow. There is a composite Wf definition 50 that stores and manages definitions.

  The Wf synthesis unit 48 activates the Wf definition / service definition acquisition unit 55 as needed to obtain all the workflow definitions that are elements. The Wf definition / service definition acquisition unit 55 obtains all the workflow definition information that is already held in the element, and executes an inquiry C74 to the repository 56, and all the remaining workflows that are the elements. Also obtain definition information.

  Thereafter, the Wf definition / service definition acquisition unit 55 hands over all the workflow definition information C75 to the Wf composition unit 48. The Wf synthesizing unit 48 generates an integrated / synthesized workflow definition C63 according to the procedure shown in FIGS. 6 to 11 and passes it to the synthesized Wf definition 50.

  The event information extracted by the various event extraction units of the workflow system 1 is temporarily stored in the event data holding unit 40 in the workflow system 1, and is appropriately distributed as an event data transfer message C25 by the common data transmission unit 41. It is transferred to the monitor system 5. In the distributed workflow monitor system 5, an event data receiving unit 49 that receives all data related to an event is received in the event data transfer message C25.

  The event information extracted by the various event extraction units of the workflow system 2 is temporarily stored in the event data holding unit 42 in the workflow system 2 and appropriately distributed as an event data transfer message C25 ′ by the common data transmission unit 42. It is transferred to the workflow monitor system 5. In the distributed workflow monitor system 5, the event data receiving unit 49 receives the event data transfer message C25 '.

  On the other hand, event information extracted by various event extraction units of the Proxy system 4 is temporarily stored in the event data holding unit 45 in the Proxy system 4.

  Further, event information extracted by various event extraction units in the workflow system 3 linked with the Proxy system 4 is sent to the Proxy system 4 from the common data transmission unit 47 in the workflow system 3 as an event data transfer message C54.

  The proxy system 4 is provided with an event data receiving unit 46, which receives the event data transfer message C54. Thereafter, all event information described in the event data transfer message C54 is temporarily stored in the event data holding unit 45.

  All data related to the event temporarily stored in the event data holding unit 45 is appropriately transferred to the distributed workflow monitor system 5 as an event data transfer message C26 by the common data transmission unit 44. In the distributed workflow monitor system 5, an event data receiving unit 49 that receives all data related to an event is received in the distributed workflow monitor system 5.

  The event data receiving unit 49 passes all data C64 related to the event to the event data associating unit 51. The event data associating unit 51 refers to the composite Wf definition 50 that stores and manages the integrated / synthesized workflow definition, and searches and references the service definition / process definition information C67 that is managed in the composite Wf definition 50. Each service data C64 is organized and related to which service process message instance corresponds, and the message instance group C66 currently managed in the event storage DB 52 is searched and related. Thereafter, it is stored in the event storage DB 52 as a record of a new message instance C65. This process will be described in detail later with reference to FIG.

  The service definition / process definition information managed by the composite Wf definition 50 includes a process definition D1, a definition unit D3, an activity unit D4, D5, D6, a service definition D2, a message definition unit D7, and a port as shown in FIG. It includes a definition part D8, a binding part D9, a service definition part D10, and the like. These are described in a computer-readable expression as described above, and rarely include semantic information (information in a form understandable by humans) directly.

  For this reason, in the distributed workflow monitor system 5, an AP label input unit 58 is added in order to add an expression on the application (information in a form understandable to humans) to the service definition / process definition information managed by the composite Wf definition 50. Exists.

  A user who is mainly a system administrator operates the AP label input unit 58 by activating one or more client sites 60.

  FIG. 13 is a schematic diagram of a screen (a screen for defining meanings for various events) displayed on the client site 60 by the process of the AP label input unit 58. Shown is a screen that is displayed on the client site 60, belongs to the AP label input unit 58, and defines meanings for various events. A screen frame 62 for displaying the entire workflow definition integrated and synthesized on the Web browser 61 and a screen frame 64 for input are displayed.

  In the screen frame 62, all of the process definitions D1 constituting the entire integrated and synthesized workflow definition, all of the activity parts belonging to the process definition, and all of the service definitions that define the relationship between the activity parts are displayed. A diagram representing the original graph structure is displayed.

  The input screen frame 64 displays a tabular input field, a display name input field 65 corresponding to the activity part instance, a meaning input field 66 corresponding to the activity part instance, and an OK button 67. A cancel button 68 is included.

  When the user operates on the web browser 61 on the client site 60, the service definition / process definition information managed by the composite Wf definition 50 is displayed on the screen frame 62 via the AP label input unit 58. The One node corresponding to an instance of an activity part is selected from the graph structure on the screen frame 62. Then, an input screen frame 64 is displayed. In the input field here, the definition name and meaning are input in the natural language expression for the instance of the activity part corresponding to the previously selected node, and the OK button 67 is pressed.

  When such an operation is performed, the definition name / semantic information C77 is sent to the AP label input unit 58. Once the AP label input unit 58 obtains the definition name / semantic information C77, the service label / process definition information managed by the composite Wf definition 50 is selected and associated with the instance of the activity unit. In this way, the definition name / semantic information C78 is stored in the composite Wf definition 50.

  The batch processing unit 59 is activated at each designated time, and appropriately searches the message instance records stored and managed in the event storage DB 52. In particular, a record group C80 of message instances necessary for specified statistical processing is taken out and used as an input value in internal calculation.

  The batch processing unit 59 stores the result value C79 in the event storage DB 52 when the designated statistical processing calculation is completed. By doing so, it becomes possible to use those statistical data for tracking and the like.

  A user who is a system administrator can display one or more client sites 6 to display an integrated Wf definition or a group of events distributed on the integrated Wf definition. is there. 14 to 17 show screen configurations displayed on the client site 6, which belong to the search function unit 53 and the tracking display creation unit 54, and display an integrated Wf definition or an integrated Wf definition. It is a screen outline figure for displaying the event group distributed above.

  FIG. 14 is a schematic screen view for searching for an integrated Wf definition displayed on the client site 6 and belonging to the search function unit 53. On the Web browser 76, a designation input field 71 for searching for an integrated process definition name, a search button 69, a list display button 70, an OK button 74, a cancel button 75, a list of integrated process definition names consisting of a plurality of entries, In order to select one integrated process definition name from the list of integrated process definition names, a check box group 73 assigned to each entry and a mouse pointer 72 are included.

  When a search character string is entered in the designation input field 71 for searching for an integrated process definition name on the screen of FIG. 14 and the search button 69 is pressed or the list display button 70 is pressed, as shown in FIG. The Wf definition search message C68 is transferred from the client site 6 to the distributed workflow monitor system 5. Thereafter, after the search function unit 53 receives the Wf definition search message C68, the search function unit 53 makes a search inquiry to the composite Wf definition 50 to obtain a search result C70. Thereafter, the search function unit 53 returns the search result C90 to the client site 6 and displays it on the Web browser 76.

  Further, one is selected from the list of integrated process definition names on the screen of FIG. 14, and after checking the check box 73 given to the entry, the OK button 74 is pressed. Then, the Wf definition request message C91 is transferred from the client site 6 to the distributed workflow monitor system 5 as shown in FIG. Thereafter, after the search function unit 53 receives the Wf definition request message C91, a search query is performed on the composite Wf definition 50 to obtain a query result C92.

  Thereafter, the search function unit 53 makes a status state confirmation inquiry C69 to the event storage DB 52, and then passes the necessary activation information argument C71 to the tracking display creation unit 54 to activate it. After startup, the tracking display creation unit 54 receives process definition information and other information C81 necessary for drawing from the composite Wf definition 50. Thereafter, the tracking display creation unit 54 returns the display data C73 to the client site 6 and displays the screen of FIG.

  FIG. 15 is a schematic screen view for visually displaying the integrated Wf definition displayed on the client site 6 and belonging to the tracking display creation unit 54.

  In the screen of FIG. 15, the business application systems 7, 8, etc. are displayed on the Web browser 77, the label group 80 displayed together with the location information on the network, and the process definition on the Wf definition exists. Assigned to each symbol 82 so that the symbol group displayed in time series, the relationship between the activity parts belonging to the process definition, communication by message, the symbol group 82 regarding the service definition expressed as an arrow, and the service definition can be zoomed up. A check box group 81, a detailed display button 79 for specifying zoom-in, a focus button 78 for searching the event storage DB 52 for a record group of message instances related to the process corresponding to the designated position of the Wf definition, and a subordinate of the Wf definition. Process-related message in It includes a screen frame for listing and displaying a list of stance records. Note that a screen frame for list-up display may not be displayed.

  In the screen of FIG. 15, in order to perform zoom-up processing, a check box 81 given to a certain symbol 82 is checked, and a detail display button 79 for designating zoom-up is pressed. Then, the Wf definition request message C91 is transferred from the client site 6 to the distributed workflow monitor system 5 as shown in FIG. Thereafter, after the search function unit 53 receives the Wf definition request message C91, a search query is performed on the composite Wf definition 50 to obtain a query result C92.

  Thereafter, the search function unit 53 makes a status state confirmation inquiry C69 to the event storage DB 52, and then passes the necessary activation information argument C71 to the tracking display creation unit 54 to activate it. After startup, the tracking display creation unit 54 receives process definition information and other information C81 necessary for drawing from the composite Wf definition 50. Thereafter, the tracking display creation unit 54 returns the display data C73 to the client site 6 and displays the screen of FIG.

FIG. 16 is displayed on the client site 6, belongs to the tracking display creation unit 54, displays the details of the integrated Wf definition visually, and lists up a list of process instances under the Wf definition. It is a screen schematic diagram.
Means business application systems 7 and 8 on the web browser 83, a group of labels 84 displayed together with location information on the network, a group of symbols in which the process definition on the Wf definition is displayed in chronological order with birth and death, It is configured to include a symbol group 88 relating to a service definition that expresses a relationship between activity parts belonging to the process definition as a message and an arrow, and is expressed more finely than that of FIG.

  Further, in the screen of FIG. 16, a check box group 89 assigned to each symbol 88 and a definition name / meaning corresponding to the instance of the activity part that is input in the screen frame 64 of FIG. A label group 87 by information, a cancel button 86, a focus button 85 for searching the event storage DB 52 for a record group of a message instance related to a process corresponding to a designated portion of the Wf definition, a message instance related to a process under the Wf definition A screen frame for displaying a list of record groups in a list and a mouse pointer 93 are included.

  The screen frame for list display includes a list display 94 of record groups of message instances related to processes under the designated Wf definition, a check box group 92 assigned to each, and OK indicating the selection result. A button 90 and a cancel button 91 are included.

  When the mouse pointer 93 is brought to the check box group 92 on the screen frame for displaying the list in FIG. 16 and the OK button 90 indicating the selection result is pressed after the check, the screen transitions to the screen in FIG. become.

  The mouse pointer 93 is brought to one of the check boxes 92 on the screen frame for displaying the list in FIG. 16, and after the check, an OK button 90 indicating the selection result is pressed. Then, as shown in FIG. 4, the Wf definition detailed information request message C93 is transferred from the client site 6 to the distributed workflow monitor system 5.

  After that, after the tracking display creation unit 54 receives the Wf definition detailed information request message C93, it makes a detailed inquiry to the event storage DB 52 to obtain a detailed inquiry result C72. Thereafter, the tracking display creation unit 54 returns the detailed inquiry result data C94 to the client site 6 and displays the screen of FIG.

  FIG. 17 is displayed on the client site 6, belongs to the search function unit 53, and selects one record group list of message instances related to processes under the Wf definition in FIG. It is a screen outline figure for displaying the statistical data details given there.

  In the screen of FIG. 17, a frame for displaying information 96 on the record of the message instance related to the process selected in FIG. 16 on the Web browser 95 and displaying all the statistical data details related to the record. 97, an OK button 98, and a cancel button 99.

  FIG. 6 is a diagram showing a relationship with the integrated Wf definition after collecting a workflow definition (hereinafter referred to as Wf definition) group uniquely held in a distributed workflow engine. FIGS. 7 to 11 show procedures and principles for collecting workflow definition groups (hereinafter referred to as Wf definitions) that are uniquely held in a distributed workflow engine and generating an integrated Wf definition. FIG.

  In FIG. 6, when the Wf definition / service definition acquisition unit 55 is started as needed, in addition to the workflow definition 31 and the workflow definition 34 that are already held inside, the workflow definition converted from other formats such as the workflow definition 39, Further, another workflow definition (symbol: Wf definition_N) is obtained from another workflow system (not shown). In addition, a query C74 is performed on the repository 56, and all remaining workflow definition information that can be an element of the integrated workflow is obtained. The inquiries C74 to the repository 56 may all be executed in advance before starting the processing, or may be executed during the processing whenever necessary.

  Of the workflow definition 31, only the behavior of the workflow engine is described, and the standardized form of WS-BPEL is denoted as D20 in FIGS. On the other hand, the part including the WSDL is denoted as D21 in FIGS.

  Of the workflow definition 34, only the behavior of the workflow engine is described, and the standardized form of WS-BPEL is denoted as D22 in FIGS. On the other hand, the part including the WSDL is denoted as D23 in FIGS.

  Similarly, only the behaviors of other workflow engines are described, and the standardized form of WS-BPEL is denoted as D24 in FIGS. On the other hand, the parts including other WSDL are denoted as D25, D26, D27, and D28 in FIGS.

  6 to 12, the activity part D4 that defines the behavior when the corresponding message is received among the activity parts defined in FIG. 5 is the behavior corresponding to the qualifier of the symbol “Rv” and the actual business logic. The activity part D5 that defines (including operations that call other services) is given the symbol “l” qualifier, and the activity part D6 that defines the behavior when sending the relevant message is given the symbol “Rp” qualifier. To express.

  For example, the activity part that defines the behavior when received in the workflow definition 31 is represented by the symbol “1Rv”. The activity part that defines the behavior corresponding to the actual business logic is represented by the symbol “1l1”. Here, since a plurality of activity parts that define the behavior corresponding to the business logic can be defined, a plurality of symbols “1l1” and “1l2” can appear. In addition, the activity part that defines the behavior when the corresponding message is transmitted and received is represented by the symbol “1Rp”.

  After that, the Wf definition / service definition acquisition unit 55 is a WS-BPEL part describing only the behavior of the workflow engine and another WSDL part, and D20, D21, D22, D23, D24, D25, D26, D27, D28. All the workflow definition information C75-1, C75-2, C75-3, C75-4, C75-5, C75-6, C75-7, and C75-8 corresponding to the above are delivered to the Wf composition unit 48.

  The Wf synthesizing unit 48 refers to them in turn, generates an integrated / synthesized workflow definition C63, and passes it to the synthesized Wf definition 50.

7 to 11, a procedure in which the Wf synthesis unit 48 generates the integrated and synthesized workflow definition C63 will be described.
Here, it is assumed that the activity unit 1l1 that defines the behavior corresponding to the actual business logic of the WS-BPEL unit D20 is defined to call another service (the service specified by D23). In addition, it is assumed that the activity unit 2l1 that defines the behavior corresponding to the actual business logic of the WS-BPEL unit D22 is defined to call another service (the service specified by D25). Furthermore, it is assumed that the activity part 3l1 that defines the behavior corresponding to the actual business logic of the WS-BPEL part D24 is defined to call other services (services specified by D26 and D28, respectively). .
In addition, workflow synthesis is performed in a predetermined order. Here, the workflow definition 31, the workflow definition 34, and the workflow definition 39 are combined in this order.

  First, as shown in FIG. 7, the Wf synthesizing unit 48 reads workflow definition information C75-1 and C75-5 corresponding to the workflow definition 31, and expands it in its memory unit.

  At this time, the first reading of the workflow definition information C75-1 and C75-5 is specified by a rule defined in advance by the operator. As a specific example, there is a method of designating which workflow definition information is to be read by pre-evaluating the inside of all workflow definitions before being delivered to the Wf synthesis unit 48. In this pre-evaluation, the number of activity definitions that actively issue messages in each workflow definition is counted and added as a score. Workflow definitions that have a large score have a high probability of actively issuing messages related to messages. Therefore, the workflow definition is handled with priority.

  As a result of the above, the three activity parts (the activity part “1Rv” that defines the behavior when received, the activity part “1l1” that defines the behavior corresponding to the actual business logic, and the behavior when sending the relevant message are shown. The activity part “1Rp” to be defined is expanded on the memory.

  Subsequently, the Wf synthesis unit 48 sequentially checks and activates the activity units developed on the memory. Following the activity part “1Rv” that defines the behavior when received, the activity part “1l1” that defines the behavior corresponding to the actual business logic is activated. The activity part “1l1” corresponds to an activity part that defines a behavior corresponding to the actual business logic, which is D5 in FIG. In this part, if INVOKE is described and the name corresponding to the other service is specified in the name part, it will call another service. In this example, as described above, the service defined in D23 is designated in the activity part “1l1”. Therefore, the Wf synthesis unit 48 reads the workflow definition information C75-2 and C75-6 corresponding to the workflow definition 34 after C75-1 and C75-5 in order to refer to the WSDL of D23, and stores it in its memory unit. Continue to deploy.

  As a result, as shown in FIG. 8, three new activity parts (activity part “2Rv” that defines the behavior when received, activity part “2l1” that defines the behavior corresponding to the actual business logic, are applicable. The activity part “2Rp”) that defines the behavior when sending and receiving a message is additionally developed on the memory of the Wf synthesis part 48.

  In this case, the activity part “2Rv” has a calling relationship with the activity part “1l1” via the WSDL of D23. Therefore, a call relationship is established between the activity part “1l1”, the activity part “2Rv” that defines the behavior when received, and the activity part “2Rp” that defines the behavior when sending the corresponding message. Become. Therefore, the Wf composition unit 48 creates a link relationship on the memory.

  The Wf composition unit 48 sequentially checks and activates the activity units in the same manner. Following the activity part “1l1”, the activity part “1Rp” that defines the behavior when the corresponding message is transmitted is activated. The activity part “1l1” has a link relationship, and the activity part “2Rv” that defines the behavior when received in the workflow definition 34 is followed by the activity part that defines the behavior corresponding to the actual business logic. “2l1” is activated.

  The activity part “2l1” also corresponds to the activity part that defines the behavior corresponding to the actual business logic, which is D5 in FIG. In this part, if INVOKE is described and the name corresponding to the other service is specified in the name part, it will call another service. In this example, as described above, the service defined by D25 is designated in the activity part “2l1”. Therefore, the Wf synthesis unit 48 reads the workflow definition information C75-3 and C75-7 corresponding to the workflow definition 39 after C75-2 and C75-6 to refer to the WSDL of D25, and loads it into its memory unit. Continue to deploy.

  As a result, as shown in FIG. 9, four activity parts (activity part “3Rv” that defines the behavior when received, activity parts “3l1” and “3l2” that define the behavior corresponding to the actual business logic) , The activity part “3Rp”) that defines the behavior when the corresponding message is transmitted / received is additionally expanded in the memory.

  In this case, the activity part “3Rv” has a calling relationship with the activity part “2l1” via the WSDL of D25. Therefore, a call relationship is established between the activity part “2l1”, the activity part “3Rv” that defines the behavior when received, and the activity part “3Rp” that defines the behavior when sending the corresponding message. Become. Therefore, the Wf composition unit 48 creates a link relationship on the memory.

  The Wf composition unit 48 sequentially checks and activates the activity units in the same manner. Following the activity part “2l1”, an activity part “2Rp” that defines the behavior when the corresponding message is transmitted is activated. The activity part “2l1” has a link relationship, and the activity part “3Rv” that defines the behavior when received in the workflow definition 39 is followed by the activity part that defines the behavior corresponding to the actual business logic. “3l1” and “3l2” are activated.

  The activity parts “3l1” and “3l2” also correspond to activity parts (activity parts as indicated by D5 in FIG. 5) that define behavior corresponding to a certain actual business logic. In this part, if INVOKE is described and the name corresponding to the other service is specified in the name part, it will call another service. In this example, as described above, the activity defined by D28 is designated in the activity part “3l1”, and the service defined by D26 is designated in the activity part “3l2”. Therefore, the Wf synthesis unit 48 reads the workflow definition information C75-8 after C75-3 and C75-7 to refer to the WSDL including the related D27, and continues D26, D27 and D28 to its own memory unit. expand.

  There is no new activity added, but the Wf synthesis unit 48 refers to D26, D27, and D28 in order to associate the reference part of the activity part “3l1” and “3l2” that define the behavior corresponding to the actual business logic. To do. As a result of the reference, as shown in FIG. 10, it is certain that the service defined in D28 is specified in the activity part “3l1” and the service defined in D26 is specified in the activity part “3l2”. In this state, the Wf composition unit 48 determines this relationship and develops the items described in the WSDLs of D27 and D28 in its own memory unit as shown in FIG.

  The Wf synthesizing unit 48 sequentially reads the WSDL in response to the service call, and continues the same operation as described above until it becomes impossible to expand the activity unit on the memory or create the link relationship on the memory. If you can no longer expand the activity part on the memory or create a link relationship on the memory, the workflow parts that are integrated / synthesized by integrating and organizing the activity parts expanded on the memory C63 Generate as

  After generating the integrated / synthesized workflow definition C63, the Wf synthesis unit 48 passes the workflow definition C63 to the synthesis Wf definition 50 in order to save it permanently. In the composite Wf definition 50, the integrated / synthesized workflow definition C63 is stored, stored, and managed. In the composite Wf definition 50, not only one integrated and combined workflow definition C63 but also a plurality of them can be stored independently.

  FIG. 12 is a diagram showing the procedure and principle of how data related to various events is organized, related and stored based on the integrated Wf definition. This is mainly related to the event data association unit 51. The outline is as follows.

  When the event data receiving unit 49 passes the data C64 'related to the event to the event data associating unit 51, the event data receiving unit 49 refers to the combined Wf definition 50 that stores and manages the workflow definition that is integrated and combined.

  Since the service definition / process definition information C67 is managed in the composite Wf definition 50 as shown in FIG. 12, it is possible to sort out which service / process message instance corresponds to and search for a relationship C67 ′. To obtain and reference a subset C67 ″ of necessary service definition / process definition information.

  Subsequently, the message instance group C66 managed in the event storage DB 52 is searched, and the event related data C64 'corresponds to the event related to the subsequent event.

  The event data correlation unit 51 performs all necessary correlations between the data, and then stores the data C64 'related to the event in the event storage DB 52 as a record of a new message instance C65. At that time, a time stamp or the like is recorded.

An example of an operation for organizing, relating, and storing data related to various events based on the integrated Wf definition will be described below. Here, description will be made assuming that the event is related to a message.
The event data association unit 51 receives data C64 ′ related to the event. The event data C64 ′ describes an event ID, a message instance type, a TimeStamp, an event type, and the like. The event includes both an event related to the message and an event related to the message in the engine in a form of identifying each.

  Since the event instance data C64 'includes the message instance type, it is first confirmed. In the case of FIG. 12, it has a value of “2Y”. The event data association unit 51 stores and manages the integrated / synthesized workflow definition C63 to identify and search which service / process message instance corresponds to the value “2Y”. The inquiry C67 ′ is executed for 50.

  When the inquiry C67 'is received, a plurality of integrated / synthesized workflow definitions C63 managed in the synthesized Wf definition 50 are searched based on the designated value "2Y". In the case of FIG. 12, since the WSDL is the only one related to D26, D27, and D28, the integrated and synthesized workflow definition C63 can be uniquely determined. Based on this, a related service definition / process definition information subset C67 ”is created. In this case, for example, the message instance types have values“ 1X ”,“ 2X ”, and“ 3X ”. Is included in the service definition / process definition information subset C67 ”. Thereafter, the subset C67 ″ of the service definition / process definition information is transmitted as a response to the event data association unit 51.

  Upon receiving the service definition / process definition information subset C67, the event data association unit 51 receives the message instance types described here as “1X”, “2X”, and “3X”. In order to search for an event related to a message managed in the event storage DB 52, a search request is transmitted to the event storage DB 52.

  FIG. 12 shows a state in which two event groups related to messages having the message instance type “1X” and two event groups related to messages having the message instance type “3X” are allocated.

  At this stage, all relevant items are extracted from the event group related to the message having the message instance type “1X” and the event group related to the message having the message instance type “3X”. Only those that are related to the above are further limited and extracted.

  There are several ways of limiting. For example, there are a method of assigning a crawl message ID or the like, and a method of estimating by mining logic.

  Here, a method is assumed in which a crawl message ID specified by a time stamp, a source address, a transmission address, and a digest value of a message is embedded in a message, and in the event group related to the message, this crawl message ID is embedded in event data. is doing.

  By specifying the conditions related to the crawl message ID, only the events related to the event data C64 'are included in the event group related to the message having the message instance type “1X” and the message instance type “3X”. It can be extracted from the event group related to the message.

  Thereafter, they are returned to the event data associating unit 51 as the message instance group C66. As a result, it is possible to specify which event related to the message the data C64 'related to the event corresponds to.

  The event data correlator 51 performs this in the same manner as described above when it is necessary to perform other necessary correlations between data. After all implementation, data C64 'relating to the event is generated as a record of a new message instance C65.

  Then, it is stored in the event storage DB 52 as a record of the message instance C65, which is an event related to the message, in association with the one returned in the message instance group C66. At that time, a time stamp or the like is recorded.

[Second Embodiment]
In the first embodiment, functions of the business process monitor / tracking apparatus are mainly described, and no particular components are mentioned. Therefore, when elements functionally equivalent to those in FIG. 1 can be applied, this is the subject of the present invention.

  FIG. 20 is a schematic diagram when a service provider operating body holds the business process monitor / tracking apparatus according to the present invention and defines it as a service.

  A service provider operating body 100 shown in FIG. 20 includes a business process tracking apparatus based on the distributed workflow management method according to the present invention, and is a plurality of workflow systems 1 and 2 based on the distributed workflow management system, which is the main component. In addition, the Proxy system 4, the workflow systems 1, 2 and 3 that intermediary to this distributed workflow management method by combining a plurality of other companies / existing workflow systems 3 and the other companies / existing workflow systems 3 that are arranged in a unique manner. A distributed workflow monitor system 5 for organizing, integrating, and storing various event information collected from the Proxy system 4 is included.

  Here, the relationship between the multiple workflow systems 1 and 2 may be a set of independent sites or counter clustering for load distribution.

  Further, as a client system for accessing the distributed workflow monitor system 5, the client site 6 by the Web browser is not included in the service provider operating body 100 because it is a service access means.

  Further, the service provider operating body 100 provides a communication function according to each of the data communication unit 13 and the data communication unit 14 of the service user's multi-business application systems 7 and 8 in order to provide a connection service to the service user. I will provide a. Similarly, the communication function according to each of the data communication part 15 and the data communication part 16 which the service user's multiple business application systems 9 and 10 have is provided. Similarly, a communication function according to each of the data communication unit 17 and the data communication unit 18 of the service user's multiple business application systems 11 and 12 is provided.

  The service provider operating body 100 provides a communication function according to each of the data communication unit 17 and the data communication unit 18, but may not be able to directly communicate with the workflow system 3 managed internally. In such a case, communication is performed via the Proxy system 4.

  Since other aspects are the same as those in the first embodiment, a redundant description is omitted.

[Third Embodiment]
FIG. 21 shows a business process tracking apparatus according to the third embodiment in which the present invention is preferably implemented. In this business process tracking apparatus, a plurality of business application systems are provided including a workflow subsystem corresponding to a plurality of workflow systems based on a distributed workflow management system.

  FIG. 21 is a partial modification of the business process tracking apparatus based on the distributed workflow management method according to the present invention described in the first embodiment, and a plurality of business application systems 7 and 9 are included in the distributed workflow management system. 1 shows a system configuration in the case of supplying a workflow subsystem 101, 102 corresponding to a plurality of workflow systems 1, 2 based on the above. Since the subsequent configuration and operation are the same as those in the first embodiment, a redundant description is omitted.

It is the figure which described the outline | summary of the whole structure regarding the optimal form of the business process monitor and tracking apparatus based on the distributed workflow management method which is this invention. It is the figure which described the procedure outline | summary at the time of collecting event information from the normal workflow engine distributed in the present invention. It is the figure which described the procedure outline | summary at the time of collecting event information via a Proxy system from the other company's / existing workflow engine of original implementation among this invention. In the present invention, a workflow definition group (hereinafter referred to as Wf definition) that is uniquely held in a distributed workflow engine is collected, and a procedure for generating an integrated Wf definition, as well as the integrated It is the figure which described the procedure outline | summary at the time of maintaining Wf definition. It is the figure which described one expression form of Wf definition. FIG. 4 is a diagram illustrating a relationship with an integrated Wf definition after collecting a workflow definition (hereinafter referred to as Wf definition) group that is uniquely held in a distributed workflow engine in the present invention. The figure which described the procedure and principle for collecting the workflow definition (henceforth Wf definition) group uniquely hold | maintained in the normal workflow engine distributed in the inside of this invention, and producing | generating an integrated Wf definition It is. The figure which described the procedure and principle for collecting the workflow definition (henceforth Wf definition) group uniquely hold | maintained in the normal workflow engine distributed in the inside of this invention, and producing | generating an integrated Wf definition It is. The figure which described the procedure and principle for collecting the workflow definition (henceforth Wf definition) group uniquely hold | maintained in the normal workflow engine distributed in the inside of this invention, and producing | generating an integrated Wf definition It is. The figure which described the procedure and principle for collecting the workflow definition (henceforth Wf definition) group uniquely hold | maintained in the normal workflow engine distributed in the inside of this invention, and producing | generating an integrated Wf definition It is. The figure which described the procedure and principle for collecting the workflow definition (henceforth Wf definition) group uniquely hold | maintained in the normal workflow engine distributed in the inside of this invention, and producing | generating an integrated Wf definition It is. It is the figure which described the procedure and principle of how to arrange | position, relate and store the data regarding various events based on the integrated Wf definition among this invention. It is a screen schematic diagram for defining meanings for various events belonging to an AP label input unit in the present invention. It is a screen outline figure for belonging to a search function part and a tracking display creation part among the present invention, and displaying an integrated Wf definition or displaying an event group distributed on an integrated Wf definition. It is a screen outline figure for belonging to a search function part and a tracking display creation part among the present invention, and displaying an integrated Wf definition or displaying an event group distributed on an integrated Wf definition. It is a screen outline figure for belonging to a search function part and a tracking display creation part among the present invention, and displaying an integrated Wf definition or displaying an event group distributed on an integrated Wf definition. It is a screen outline figure for belonging to a search function part and a tracking display creation part among the present invention, and displaying an integrated Wf definition or displaying an event group distributed on an integrated Wf definition. It is the figure which described the system outline | summary of the conventional business process monitor and tracking apparatus. It is the figure which described the conventional distributed workflow management method and the system outline | summary. It is the figure which described the outline | summary of the utilization system in the service provider operation body which is another form of this invention. It is the figure which described the outline | summary of the system which incorporates a part function of the business process monitor and tracking apparatus by the business application system which is another form of this invention, and implement | achieves a function.

Explanation of symbols

1, 2 Workflow system based on distributed workflow management system
3 Original implementation and existing workflow system
4 Proxy system
5 Distributed workflow monitor system
6 Client site via web browser
7, 8, 9, 10, 11, 12 Business application system
13, 14, 15, 16, 17, 18 Data communication part
19, 20, 21, 22, 23, 24 Adapter
25, 26, 27, 28 Msg event extractor
29, 32, 37 Workflow engine
30, 33, 38 Eng event extractor
31, 34, 39 Workflow definition
35 Proxy section
36 Prx event extractor
40, 42, 45 Event data storage
41, 43, 44, 47 Common data transmitter
46 Common data receiver
48 Workflow Synthesis Department
49 Event data receiver
50 Composite Wf definition
51 Event Data Association
52 Event storage DB
53 Search function
54 Tracking display generator
55 Wf definition / service definition acquisition part
56 repository
57 Other workflow definitions
58 AP label input
59 Batch processing section
60 Web browser client site
61, 76, 77, 83, 95 Web browser
62 Screen frame that displays the entire workflow definition that has been merged and synthesized
64 input screen frame
65 Input field for definition name
66 Meaning input field
67, 74, 90, 98 OK button
68, 75, 86, 91, 99 Cancel button
69 Search button
70 List display button
71 Input field
72, 93 Mouse pointer
73 Check boxes attached to the entry
78, 85 Focus button
79 Detail button
80 labels
81, 89 Check boxes attached to symbols
82 Symbols related to service definition
84 Labels displayed with location information
87 Labels by definition name and semantic information
88 symbols
92 Check boxes
94 List display of records
96 Information about message instance records
97 Frame displaying statistical data details
100 Service provider management body
101, 102 Workflow subsystem
C1, C2, C5, C6, C21, C48 Processing request message
C3, C4, C7, C8, C22, C49 Processing response message
Events related to C9, C10, C11, C12, C13, C14, C15, C16, C17, C18, C19, C20, C23, C24 messages
C25, C25 ', C26, C54 Event data transfer message
C30, C31, C32, C33, C34, C35, C36, C37, C38, C39, C40, C41 Processing request message
Events related to C42, C43, C44, C45, C46, C47, C50, C51, C52, C53 messages
C60, C61, C62 definition transfer message
C63 Integrated and synthesized workflow definition
All data about C64 events
C64 'event data
C65 message instance
C66 message instances
C67 Service definition / process definition information
Query to find C67 'association
C67 ”subset of service definition / process definition information
C68 Wf definition search message
C69 Check status status
C70 search results
C71 Startup information argument
C72 Detailed inquiry result
C73 Display data
C74 Inquiry
C75 Workflow definition information
Workflow definition information by C75-1, C75-2, C75-3, C75-4, C75-5, C75-6, C75-7, C75-8 WS-BPEL, WSDL
C77, C78 definition name / semantic information
C79 result value
C80 message instance records
C81 Information required for drawing
C90 results
C91 Wf definition request message
C92 Query result
C93 Wf definition detailed information request message
C94 Detailed inquiry result data
D1 process definition
D2 service definition
D3 definition part
D4 Activity part that defines the behavior when the corresponding message is received
D5 Activity part that defines the behavior corresponding to the actual business logic
D6 Activity part that defines the behavior when sending the relevant message
D7 Message definition part
D8 Port definition part that defines the actual interface
D9 Binding part
D10 Service definition section
D20 Workflow engine behavior is described and standardized WS-BPEL part
D21, D23, D25, D26, D27, D28 WSDL part
D22, D24 Workflow engine behavior is described and standardized WS-BPEL part
B1 Event management device
B3, B4, B5 business system
B6 User terminal
B11 input section
B12 event queue
B13 Event Association
B14 Event management DB
B15 Business Process DB
B16 output section
B30, B30 ', B40, B40', B50, B50 'applications
B31, B31 ', B41, B41', B51, B51 'State DB
B32, B42, B52 Event extractor
B33, B43, B53 Event data converter
B34, B44, B54 Event data transmitter
B320, B420, B520 Event extraction definition data
A1, A2 organization
A3, A4 workflow management system
A5, A6 Workflow management system server
A7, A8 Existing interface
A9 Process instance
A11, A13 process template
A15, A16 state shadowing engine
A17, A18 Workflow management system client
A27, A28, A29, A30 users

Claims (14)

A workflow tracking system having a plurality of workflow execution devices that manage and execute workflows, and a workflow integrated management device that acquires information about workflows from each of the workflow execution devices and generates an integrated workflow that integrates the information.
Each of the workflow execution devices
Means for representing the content of an event that occurs in the own device when executing an arbitrary workflow managed by the own device, and recording unique event information for each event;
Means for transmitting the recorded event information and a workflow description representing the content of the workflow in a standardized data format to the workflow integrated management device;
The workflow integrated management device includes:
Means for obtaining the workflow description from each of the workflow execution devices;
Event association detection means for detecting an association with other events for each event specified by the event information acquired from each workflow execution device;
Means for integrating the plurality of workflows and generating the integrated workflow based on the workflow description and the event information acquired from each of the workflow execution devices, and the detection result of the event-related detection means;
Event information recording means for recording all the event information acquired from each of the workflow execution devices;
Means for referring to event information recorded in the event information recording means in response to a request from another device;
A workflow tracking system comprising:   The workflow execution device, in which the workflow description is defined in a format different from the standardized data format, has a built-in or connected standardization device for converting the workflow description into the standardized data format. The workflow tracking system according to claim 1.   The workflow tracking system according to claim 1, wherein the workflow integrated management device further includes means for adding arbitrary information in a form that can be recognized by a human to the event information.   4. The workflow integrated management apparatus according to claim 1, further comprising a patch processing unit that performs statistical processing based on event information recorded in the event information recording unit and generates statistical data. Workflow tracking system.   The workflow execution apparatus includes a plurality of adapters for converting a communication procedure unique to a business application system that is a communication partner when executing the workflow into a standardized communication procedure. 5. The workflow tracking system according to any one of 4 above. A workflow integrated management device that acquires information about a workflow from each of a plurality of workflow execution devices that manage and execute a workflow, and generates an integrated workflow that integrates the information.
Means for obtaining a workflow description representing the contents of the workflow in a standardized data format from each of the workflow execution devices;
Means for representing the content of an event that occurs in each workflow execution device when the workflow execution device executes the workflow, and acquiring event information unique to each event from each workflow execution device;
Event association detection means for detecting association with other events for each event specified by the acquired event information;
Means for integrating the plurality of workflows and generating the integrated workflow based on the workflow description and the event information acquired from each of the workflow execution devices, and the detection result of the event-related detection means;
Event information recording means for recording all the event information acquired from each of the workflow execution devices;
Means for referring to event information recorded in the event information recording means in response to a request from another device;
A workflow integrated management apparatus comprising:   7. The workflow integrated management apparatus according to claim 6, further comprising means for adding arbitrary information in a form that can be recognized by a human to the event information.   8. The workflow integrated management apparatus according to claim 6, further comprising patch processing means for performing statistical processing based on event information recorded in the event information recording means and generating statistical data. A workflow integrated management method using a plurality of workflow execution devices that manage and execute workflows, and a workflow integrated management device that acquires information about workflows from each of the workflow execution devices and generates an integrated workflow that integrates the information. And
Each workflow execution device represents the content of an event that occurs in the device when executing an arbitrary workflow managed by the device, and records unique event information for each event;
Each workflow execution device transmitting the recorded event information and a workflow description representing the content of the workflow in a standardized data format to the workflow integrated management device;
An event related detection step in which the workflow integrated management device detects an association with another event for each event specified by the event information acquired from each of the workflow execution devices;
The workflow integrated management device integrates a plurality of the workflows based on the workflow description and the event information acquired from each of the workflow execution devices and the detection result of the event related detection unit, and generates the integrated workflow. When,
Event information recording means for recording all the event information acquired from each workflow execution device by the workflow integrated management device;
The workflow integrated management device refers to event information recorded in the event information recording means in response to a request from another device;
A workflow integrated management method characterized by comprising:   The workflow execution device in which the workflow description is defined in a format different from the standardized data format converts the workflow description into the standardized data format and transmits the converted workflow description to the workflow integrated management device. The workflow integrated management method according to claim 9.   11. The workflow integrated management method according to claim 9, further comprising a step of adding arbitrary information in a form that can be recognized by a human to the event information.   12. The patch integrated management apparatus according to claim 9, further comprising a patch processing step of performing statistical processing and generating statistical data based on the event information recorded in the event information recording step. Workflow integrated management method.   A workflow integrated management program for causing a computer to execute the workflow integrated management method according to any one of claims 9 to 12.   A computer-readable information recording medium on which the workflow integrated management program according to claim 13 is recorded.

Images