JP2000306013A - Workflow system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress a data defect between a client and a server as little as possible. SOLUTION: Concerning the workflow system in which plural clients 12a and 12b are connected through a transmission line 4 to a server 10 loading a workflow managing system 2 and the workflow managing system of the server is accessed from the plural clients, clients modules 15a and 15b for inputting execution request and real data from an operator to the workflow managing system and outputting the results and OLTP 16a and 16b for transmitting/ receiving data containing the execution requests, the real data and the results to the server are added to the respective clients. Further, OLTP 14a and 14b for transmitting/receiving data containing the results, the execution requests and the real data to the clients and API 13a and 13b for accessing the workflow managing system and obtaining the result with the execution requests and the real data received by the OLTP are added to the server.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a workflow system including a client server system.

[0002]

2. Description of the Related Art When information related to paperwork in a company or government office is shared by a plurality of departments and a plurality of persons, and the tasks are executed in order, the information, each department and each person in charge are required to execute the task. A workflow system for managing the flow of executed products on a computer network has been proposed.

[0003] Such a workflow system is generally constituted by a client server system. That is, as shown in FIG. 3, a plurality of clients 5 are connected to a server 3 on which a repository data file 1 and a workflow management system 2 are mounted via a transmission path 4.
a and 5b are connected. Each client 5a, 5b
Are assigned to persons in charge of performing various tasks using this workflow system.

[0004] Each client 5a, 5b has a server 3
A for accessing the workflow management system 2 of
A PI (application programming interface) 6 and a client module 7 for a person in charge as an operator to input an execution request and actual data to the workflow management system 2 and output a result are incorporated.

In the workflow system having such a configuration, when each person in charge performs various tasks by using the workflow system, the client 5a or 5b given to himself / herself obtains parameter information indicating the task type and actual data. Is input, the client module 7 in charge of the input / output processing of the clients 5a and 5b passes the parameter information and the actual data to the API 6, and activates the API 6.

[0006] The API 6 communicates with the server 3 via the transmission path 1.
Log-on (start up), and operate the workflow management system 2 with the parameter information and the actual data.

[0007] The workflow management system 2 reads out the work flow (execution procedure) specified by the parameter information from the repository data file 1 and specifies each work pointer constituting the work flow (execution procedure). ,
The actual data input to the specified work pointer is inserted, the process given to the relevant work pointer is executed, and the execution result (article) is transferred to the next work pointer. Then, the position (work pointer) where the flow of the task is currently registered is registered in the repository data file 1.

[0008] When necessary, the processing result is transmitted to the clients 5a and 5b that are the access requests (execution requests).

[0009]

However, the workflow system shown in FIG. 3 still has the following problems to be improved.

That is, as described above, generally, the workflow system is composed of a client-server system, so that an API (application programming interface) incorporated in each of the clients 5a and 5b is transmitted via the transmission path 4. Various information is exchanged with the workflow management system 2 of the server 2.

Specifically, between the clients 5a and 5b and the server 3, the API of the clients 5a and 5b
6 and the daemon of the server 3 perform data transmission, and more specifically, the transmission is performed using socket communication in TCP / IP (Transmission Control Protocol / Internet Protocol). In socket communication in TCP / IP, the reliability of data transmission between the clients 5a and 5b and the server 3 depends on TCP / IP.

Therefore, the server 3 or the client 5
When a failure of the tasks a and 5b, a disconnection of the transmission path 4, a failure of the network card adapter, a failure of the daemon of the server 3, and the like occur, there is a concern that data transmitted and received between the client and the server may be lost.

When data loss occurs, an error message is displayed on the clients 5a and 5b. The operator (person in charge) performs the same operation on the clients 5a and 5b again to activate the API 6. There is a need. Therefore, the operation becomes complicated.

The present invention has been made in view of such circumstances, and by installing an API on the server side instead of the client side, highly reliable data is transmitted as a data transmission procedure between the client and the server. Transmission procedures can be adopted to minimize the occurrence of system abnormalities caused by poor data transmission between the client and server.
An object of the present invention is to provide a workflow system that can significantly improve the reliability of the entire system.

[0015]

The present invention is applied to a workflow system in which a plurality of clients are connected to a server equipped with a workflow management system via a transmission line, and each client accesses the server's workflow management system. Is done.

In order to solve the above-mentioned problems, according to the present invention, for each client, an operator inputs an execution request and actual data to the workflow management system and outputs the result, OLTP (online transaction processing) for transmitting and receiving data including requests, actual data, and results to / from a server is added.

Further, an OLTP for transmitting / receiving data including a result, an execution request, and actual data to / from the server, and accessing the workflow management system with the execution request and the actual data received by the OLTP, and retrieving the result. API (Application Programming Interface) to be obtained.

In the workflow system configured as described above, the API for accessing the workflow management system and obtaining a result is installed on a server on which the workflow management system is mounted. The data transmission between the server and each client is based on the TCP described above.
OLTP without adopting socket communication in / IP
(Online transaction processing).

Therefore, when the operator inputs an execution request and actual data to the workflow management system at each client, the execution request and the actual data are transmitted to the OLTP
Is transmitted to the server side, the API on the server side is activated, the workflow management system operates, and the result is transmitted to the client that has requested execution.

The O employed in this workflow system
As is well known, in addition to the normal data transmission function of transmitting and receiving data between a client and a server, when transmitting data between a client and a server, the LTP stores and holds the data transmitted to the other party at the transmission source. If the data is not transmitted normally due to a transmission error or a failure, it has a message recovery function of retransmitting the data and retransmitting the data when the failure is recovered.

Therefore, the reliability of data transmission between the client and the server can be improved, and the operation load on the operator (person in charge) when an abnormality occurs can be reduced.

[0022]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a workflow system according to an embodiment of the present invention. The same parts as those of the conventional workflow system shown in FIG. 3 are denoted by the same reference numerals, and detailed description of the overlapping parts will be omitted.

The repository data file 1, the workflow management system 2, and a plurality of server modules 11a,
A plurality of clients 12a and 12bb are connected via a transmission line 4 to the server 10 in which the server 11b is stored. Each server module 11a, 11b of the server 10
Are installed on the client 12a connected to the transmission path 4,
12b, and each server module 11
a and 11b correspond to the clients 12a and 12b on a one-to-one basis. In each of the server modules 11a and 11b, data is transmitted between APIs (application programming interfaces) 13a and 13b for accessing the workflow management system 2 and the corresponding clients 12a and 12b, respectively. OLTP (Online Transaction Processing) 14a, 14b.

On the other hand, in each of the clients 12a and 12b connected to the transmission path 4, a client module 15a is provided for an operator as an operator to input an execution request and actual data to the workflow management system 2 and output the result. , 15b, and each OLTP1 of the corresponding server module 11a, 11b in the server 10 via the transmission line 4.
OL for carrying out data transmission between 4a and 14b
TPs 16a and 16b are incorporated.

The OLTPs 14a, 14b, 16a, 1
6b, as described above, the clients 12a, 12b
In addition to the normal data transmission function of transmitting and receiving data between the server 10 and the client 12a, 12b,
When data is transmitted between devices, the sender temporarily stores the data sent to the other party, and if the data is not transmitted normally due to a failure or the like, resends the data and It has a message recovery function that resends data at the time of recovery.

In the workflow system configured as described above, the client 12a is used when the operator (person in charge) accesses the workflow management system 2 of the server 10 with the client 12a (12b) given to the operator. (12b) and the operation of the server 10 will be described with reference to FIG.

First, the operator (person in charge) operates the client 12a (12b) given to him / her to activate the client module 15a (15b) (S).
1). When the client module 15a (15b) starts up, the operator (person in charge) inputs parameter information and actual data as an execution request indicating the type of job to be executed (S2). In the case where this workflow management system is used to execute the travel expense adjustment, the parameter information is the travel expense adjustment code, and the actual data is the billing amount.

Next, a client module 15a (15b) that handles input / output processing of the clients 5a and 5b.
Uses this parameter information and actual data as OLTP 16a
(16b). Then, the OLTP 16a (16
b) transmits the input parameter information and actual data to the OLTP 14a (14b) of the corresponding server module 11a (12a) of the server 10 via the transmission path 4 (S3). In this case, the OLTP 16a (1
6b) temporarily stores and retains the parameter information and the actual data transmitted.

The corresponding server module 1 of the server 10
The OLTP 14a (14b) of 1a (11b) receives the parameter information and the actual data transmitted from the OLTP 16a (16b) of the client 12a (12b) (S4). If the information is normally received, the normal reception information is transmitted to the OLTP 16a (16b) of the transmission source client 12a (12b). If the data is not received normally (S5), the client 12a of the transmission source
A data retransmission request is sent to the OLTP 16a (16b) of (12b) (S6).

The OLTP 16a (16b) of the source client 12a (12b)
When the normal reception information is received from 4a (14b), the stored parameter information and the actual data are cleared. When the normal reception information cannot be received, or when the retransmission request is received, the stored parameter information and the actual data are retransmitted. .

When the parameter information and the actual data are received normally, the server module 11a (11b)
13a is started (S7). When activated, the API 13a (13b) drives the workflow management system 2 using the parameter information and the actual data received by the OLTP 14a (14b) (S8).

Specifically, as described above, the workflow management system 2 reads out the work flow (execution procedure) specified by the parameter information from the repository data file 1 and executes the work flow (execution procedure). Are specified, the actual data input to the specified work pointer is inserted, the process given to the relevant work pointer is executed, and the execution result (artifact) is To the work pointer. Then, the position (work pointer) where the flow of the task is currently registered is registered in the repository data file 1.

Then, if necessary, the API 13a (13b) transmits the processing result in the workflow management system 2 to the client 12a as the access request source via the OLTP 14a (14b) (S9).

The client module 15a (15b) of the client 12a requesting access has its own OL.
When the processing result is received by the TP 16a (16b), the processing result is displayed and output as needed (S10).

When the operator (person in charge) terminates the operation on the workflow management system 2 (S11), the operator (person in charge) uses his or her client 12a (12).
A log-off request to the workflow management system 2 is input to the client module 15a (15b) of b) (S12). Then, this logoff request is O
The data is transmitted from the LTP 16a (16b) to the server 10 via the transmission path 4 (S12).

The corresponding server module 1 of the server 10
When the log-off request is received by the OLTP 14a (14b) of its own (S13), the API 1a (11b) of its own
13a (13b) is activated (S14), and the workflow management system 2 is terminated (S15).

In the workflow system configured as described above, the AP that accesses the server workflow management system 2 formed in the server 10 and obtains the result is provided.
I13a and 13b are installed in the server 10 in which the workflow management system 2 is incorporated.

Then, the server 10 and each client 12
a, 12b, each client 12
OLTP (Online Transaction Processing) without using the above-described socket communication in TCP / IP, which is necessary when each client side directly accesses the workflow management system 2 of the server when APIs are installed in the a and 12b. 14a, 14
b, 16a, and 15b are employed.

The OLTPs 14a, 14b, 16a, and 15b employed in the workflow system of this embodiment are as follows:
In addition to the normal data transmission function of transmitting and receiving data between the clients 12a and 12b and the server 10, when transmitting data between the clients 12a and 12b and the server 10, the data transmitted from the source to the other party As shown in the flowchart of FIG. 2, when data is not transmitted normally due to a transmission error or a failure,
It has a function to retransmit.

Further, OLTP 14a. 14b, 16
Although not shown in the flowchart of FIG. 2, a and 15b have a message recovery function of retransmitting data when the failure is recovered.

Therefore, the clients 12a, 12b
The reliability of data transmission between the server and the server 10 can be improved, and the operation burden on the operator when an abnormality occurs can be reduced.

Further, each client 12a, 1
When setting a program for accessing the workflow management system 2 from the client module 15a or 15b from the client module 15a or 15b, the program engineer uses a complicated API 13
OLTPs 14a, 14b without being aware of the existence of
Since the program only needs to be created in consideration of b, the specification of access to the workflow management system 2 can be easily changed.

[0043]

As described above, in the workflow system of the present invention, the API for accessing the workflow management system is installed on the server side, and the data transmission procedure between the client and the server can be performed with highly reliable data. OLTP, which is a transmission procedure, is adopted.

Therefore, occurrence of system abnormalities or data loss due to poor data transmission between the client and the server can be suppressed as much as possible, and the reliability of the entire system can be greatly improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of a workflow system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing an access operation to a workflow management system in the workflow system.

FIG. 3 is a block diagram showing a schematic configuration of a conventional workflow system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Repository data file 2 ... Flow management system 4 ... Transmission line 10 ... Server 11a, 11b ... Server module 12a, 12b ... Client 13a, 13b ... API 14a, 14b, 16a. 16b OLTP 15a, 15b Client module

Claims (1)

[Claims] 1. A workflow system in which a plurality of clients are connected to a server equipped with a workflow management system via a transmission line, and each client accesses a workflow management system of the server. A client module for inputting an execution request and actual data to the workflow management system and outputting a result, and an OLTP (online transaction processing) for transmitting and receiving data including the execution request, actual data and result to and from the server The server comprises: an OLTP for transmitting / receiving data including the result, the execution request, and the actual data to / from the client; and accessing the workflow management system with the execution request and the actual data received by the OLTP. AP to obtain results
I (Application Programming Interface).