JP2006185117A - Workflow system, management method of workflow system, program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accelerate the database processing of a workflow system in a large-scale organization holding a large amount of jobs and to reduce maintenance work loads by realizing the acceleration of the database processing in each workflow of the workflow system operated by being distributed to the plurality of different workflows and the reduction of maintenance work by the batch management of the respective workflows. <P>SOLUTION: A server 600 respectively caches the contents of databases (an organization DB 608, a user DB 609 and a role DB 611) shared between the respective workflows distributed to the plurality of workflows (a servlet 1 and a servlet 2) in the respective workflows and accelerates the data base processing. Also, when the contents of the database are changed, the management program of the server 600 respectively refreshes the cache of each workflow related to the database. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a workflow system that is distributed among a plurality of different workflows and shares a database among the workflows, a workflow system management method, a program, and a recording medium.

  One infrastructure that improves the efficiency of electronic document approval is a workflow system. Since the workflow system constitutes a system in which targets such as workflow, organization, and person in charge depend on each other, if you try to change any of these targets, other targets will not be affected. I was forced to make changes that couldn't be done.

  For this reason, even if the workflow can be customized, for example, if an attempt is made to change an object such as an organization change, the object related to the organization must also be changed, and the search for the related object becomes complicated. There was a problem that could not be easily dealt with.

  In response to this problem, Japanese Patent Application Laid-Open No. 2000-250967 attempts to solve this problem by distributing the workflow management function and the execution environment.

  Specifically, the workflow control server is composed of tasks that form a logical business unit, business objects in a hierarchical structure including input / output data and processing conditions, and business object units in each layer of this hierarchical structure. It is intended to control and manage the workflow.

As for the change of the organization and the person, for example, the change of the person corresponds to the addition / deletion of the worker and the secretary agent, and the change of the organization corresponds to the attribute change of the secretary agent.
JP 2000-250967 A

  However, in the above-mentioned Patent Document 1, input / output data is included in the business object even for workflow common data such as organization / role. Each attribute needs to be updated, and particularly in a large-scale organization having a large amount of work, there is a problem that it leads to an increase in the maintenance workload of the system administrator.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to cache the contents of a database shared among the workflows distributed in a plurality of different workflows in each of the workflows. When the contents of the database are changed, by refreshing the cache of each workflow related to the database, in a workflow system that operates in a distributed manner among a plurality of different workflows, Workflow system and workflow system that realizes reduction of maintenance work through batch management of workflows, speeds up database processing of workflow system and reduces maintenance work load in large-scale organizations with a large volume of work To provide a management method and a program and recording medium.

  The present invention relates to a workflow system distributed in a plurality of different workflows, a sharing unit for sharing a database for managing information used in the workflow system among the workflows, and a cache for the contents of the databases in the workflows. It has a cache means and a refresh means for refreshing the cache of each workflow related to the database when the contents of the database are changed.

  According to the present invention, the contents of the database shared among the workflows distributed among the plurality of different workflows are respectively cached in the respective workflows, and when the contents of the database are changed, the contents of the respective workflows related to the database are changed. By refreshing each cache, in a workflow system that operates in a distributed manner among different workflows, the database processing in each workflow is accelerated, and the cache between each workflow is not rebooted even when the database is changed. There is an effect that consistency can be guaranteed.

  Therefore, batch management of each workflow can be realized, and both high-speed database processing of the workflow system and reduction of the maintenance work load can be achieved in a large-scale organization having a large amount of work.

  For example, slip information and route information for each category such as personnel and general affairs can be operated and managed independently without increasing the management burden on the administrator and without reducing the database processing efficiency. Information can be collectively managed as common information. As a result, it is possible to improve the efficiency of development including electronic documents in each subsystem of the distributed workflow and improve the operational efficiency of the system administrator.

  Hereinafter, details of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of a workflow system to which this embodiment is applied.

  The workflow system according to this embodiment includes a workflow and slip design computer terminal (workflow and slip design terminal) 400, and a workflow operation computer terminal (workflow operation) provided corresponding to a processor (person in charge) who performs a task. Terminal 300), various tables for executing workflows, and a workflow server 200 for storing various programs.

  The workflow and slip design terminal 400, the workflow operation terminal 300, and the workflow server 200 are each connected to a network 500 and operated.

  The workflow and slip design terminal 400 includes a slip designer program 401 and a system management program 402. The workflow and slip design terminal 400 communicates with a management program (not shown) on the workflow server 200 to create a slip definition and a workflow to be used in the workflow system. Create various definition information used in the system. For example, the workflow and slip design terminal 400 can register an organization table, role table, user table, user role table, delivery definition information, various slip information, and the like in the workflow server 200. In order to perform these operations, the workflow and slip design terminal 400 can connect to the workflow server 200 by inputting its own identification information.

  The workflow operation terminal 300 uses the Web browser 301 executed on the workflow operation terminal 300 to transmit access information regarding the slip to the workflow server 200 by HTTP, and receives the result. At this time, the generated display / calculation processing is executed by using a Java (registered trademark) applet 302 or the like. The workflow operation terminal 300 is arranged for a person in charge (for example, a drafter, a section manager, a department manager, etc.) who performs a predetermined job specified in advance.

  The workflow server 200 includes an RDBMS (Relational DataBaSe Management System) 205 that stores information related to the workflow system (organization table, role table, user table, user role table, delivery definition information, delivery information table, etc.), and a workflow operation computer terminal. WEB server 201 for accepting the request and executing the request, servlet engine 202, workflow program 203, and SMTP server 204 for realizing the workflow notification function.

  The workflow operation terminal 300 transmits a slip search request to the workflow server 200, and based on the search result returned from the workflow server 200, the approved slip (electronic document) stored in the external DB. Can be viewed.

  Hereinafter, a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and the slip design terminal 400 illustrated in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a block diagram showing an example of a hardware configuration of a computer applicable to the workflow server 200, the workflow operation terminal 300, the workflow and slip design terminal 400 shown in FIG.

  In FIG. 2, reference numeral 101 denotes a CPU, which is stored in a ROM 103 or a hard disk (HD) 104 (any other storage device such as a flexible disk, CD-ROM, DVD-ROM, etc.) 104. The entire computer is controlled by loading the program onto the RAM 102 and executing it. The RAM 102 is used as a work area for the CPU 101.

  A communication interface 107 enables connection to the network 500. An input device 105 corresponds to a pointing device such as a keyboard or a mouse. Reference numeral 106 denotes a display device, which includes a CRT, LCD, or the like.

  Note that the RDBMS 205 of the workflow server 200 illustrated in FIG. 1 is built in the HD 104 of the workflow server 200. The WEB server 201, the servlet engine 202, the workflow program 203, and the SMTP server 204 of the workflow server 200 are realized by the CPU 101 of the workflow server 200 loading a program stored in the HD 104 onto the RAM 102 and executing it. The

  Further, the Web browser 301 of the workflow operation terminal 300 shown in FIG. 1 is realized by the CPU 101 of the workflow operation terminal 300 loading and executing a program stored in the HD 104 on the RAM 102.

  Further, the Java (registered trademark) applet 302 of the workflow operation terminal 300 shown in FIG. 1 is executed by the CPU 101 of the workflow operation terminal 300 executing the program downloaded from the workflow server 200 on the Web browser 301. Realized.

  The slip designer program 401 and the system management program 402 of the workflow and slip design terminal 400 shown in FIG. 1 are loaded into the RAM 102 by the CPU 101 of the workflow and slip design terminal 400 by loading a program stored in the HD 104. This is realized by executing.

  FIG. 3 is a schematic diagram showing the flow of slips in the workflow system shown in FIG.

  In the workflow system according to the present embodiment, as shown in FIG. 3, using the workflow operation terminal 300, the person in charge defined by an organization and a role called a node for issuing a slip and approving / rejecting the slip. Do. A business process is defined as a group of nodes to which a slip is delivered.

  FIG. 4 is a data configuration diagram showing an example of the data structure of the organization table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This organization table is for storing information related to the organization for realizing the workflow.

  In the organization table shown in FIG. 4, the organization ID is an arbitrary organization name written as a code, and always covers the upper organization ID. The organization name indicates the name on the display of the organization ID. Furthermore, the parent organization ID indicates a higher organization ID.

  FIG. 5 is a data configuration diagram showing an example of the data structure of the role table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This role table is for storing information related to roles for realizing the workflow.

  In the role table shown in FIG. 5, the role ID is an arbitrary role name written as a code. The role name indicates a name on the display of the role ID.

  FIG. 6 is a data configuration diagram showing an example of the data structure of the user table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This user table is for storing user information for using the workflow.

  In the user table shown in FIG. 6, the user ID displays the user as an arbitrary code. The password is used for authentication together with the user ID when logging into the workflow system. Furthermore, the user name indicates the name on the display of the user ID.

  FIG. 7 is a data configuration diagram showing an example of the data structure of the post table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This post table is used to store post information for using the workflow.

  As shown in FIG. 7, each record in the post table includes “user ID” defined in the user table, “role ID” defined in the role table, and “organization” defined in the organization table. ID ”.

  FIG. 8 is a data configuration diagram showing an example of the data structure of the delivery definition information stored in the RDBMS 205 of the workflow server 200 shown in FIG. The delivery definition information is for storing information defining a route through which the slip is delivered.

  Here, as an example, an example is shown in which the roles are delivered in the order of “employee” → “department manager” → “department manager” → “department manager” → “president”. When the delivery route of the slip is defined in this way, the delivery definition information of this delivery route is created as information of five records as shown in FIG.

  Hereinafter, a method for creating the delivery definition information will be described.

  For example, when the slip name is “transportation expense”, the user first sets “transportation expense” as the slip name using the system management program from the workflow and slip design terminal 400, and then sets each node. To do. Taking node 1 as an example, by setting a code “U0007” indicating a department manager in node 1 and selecting a target organization (here, “A company” of organization ID “80” is selected), Role ID “004”, “Route organization ID” indicating “Voucher name” as “Transport expense”, “Organization ID” as “80”, “Node number” as “1”, “Route role ID” as “Director” Is set as an organization ID that plays a role. Here, “company A” with the organization ID “80” is selected as the target organization, and the delivery target person with the role ID “department manager” is not determined. Therefore, the route organization ID is “NULL” (indicated by a blank in the figure).

  FIG. 9 is a data configuration diagram showing an example of the data structure of the delivery information table stored in the RDBMS 205 of the workflow server 200 shown in FIG. This delivery information table is generated based on the delivery definition information shown in FIG. 8 during delivery processing in the workflow system shown in FIG. 10, which will be described later, and stores the route, status, etc. of the workflow. It is. The delivery information table corresponds to a case where a user with the user ID “U0012” has started. In this case, the slip is delivered as user IDs “U0012”, “U0007”, “U0003”, “U0002”, “U0001”.

  Hereinafter, the overall flow of the delivery processing procedure in the workflow system of the present invention will be described with reference to FIG.

  FIG. 10 is a flowchart showing an example of a first control processing procedure in the workflow system of the present invention, and corresponds to the delivery processing by the workflow program 203 of the workflow server 200 shown in FIG. In the figure, S5000 to S5013 indicate each step.

  First, when the CPU of the workflow server 200 (hereinafter referred to as the CPU of the workflow server 200) that executes the workflow program 203 receives a slip processing request from the workflow operation terminal 300 (step S5000), it starts delivery processing.

  The CPU of the workflow server 200 switches the delivery process based on the “draft”, “approval”, and “denial” request categories of the slip processing request received in step S5000 (step S5001).

  If the CPU of the workflow server 200 determines in step S5001 that the request category of the slip processing request received in step S5000 is “draft”, the CPU of the workflow server 200 in step S5002 As the information, node number “0” is set in the delivery information table. In the “processing user”, the user ID of the user who issued the draft is set.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, as shown in FIG. 8, the record of the node number “0” in the delivery information table includes “transportation cost” as the slip name, slip The slip number issued at the time of drafting (here, “00001”), the node number “0”, the processing user user ID “U0012”, and the status “processed” are set.

  Next, in step S5003, the CPU of the workflow server 200 sets the current node number to “1” and refers to the delivery definition information (FIG. 8) corresponding to the slip name of the slip processing request received in step S5000. Information of the number “1” (route role ID, route organization ID) is acquired, and the process proceeds to step S5008.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, the route role ID “004” and the route organization ID “NULL” are acquired.

  On the other hand, if the CPU of the workflow server 200 determines in step S5001 that the request category of the slip processing request received in step S5000 is “approved” or “denied”, the CPU of the workflow server 200 in step S5004. Acquires the current node number with reference to the delivery information table (FIG. 9).

  Next, in step S5005, the CPU of the workflow server 200 determines whether the request category of the slip processing request received in step S5000 is “approval” or “denied”, and determines that it is “denied”. In this case, in step S5007, after decrementing the current node number acquired in step S5004, the delivery definition information (FIG. 9) having the decremented current node number is referred to and the current node number information ( (Route role ID, route organization ID) is acquired, and the process proceeds to step S5008.

  On the other hand, if the CPU of the workflow server 200 determines in step S5005 that the request category of the slip processing request received in step S5000 is “approval”, the current node number acquired in step S5004 in step S5006. After that, the delivery definition information (FIG. 8) having the incremented current node number is referred to obtain the current node number information (route role ID, route organization ID), and the process proceeds to step S5008.

  In step S5008, the CPU of the workflow server 200 uses the route role ID and route organization ID acquired in step S5003, S5006, or S5007 to refer to the user post information (FIG. 7) to determine the next delivery target user. The ID is determined (from the post table (FIG. 7), the role ID is the route role ID and the organization ID is the user ID of the route organization ID). When the acquired route organization ID is “NULL” (in the case of blank in FIG. 8), the organization ID to which the user ID corresponding to the node number one smaller than the current node number belongs is set as “route organization ID”. The next delivery target user ID is determined. Furthermore, when the next delivery target user ID cannot be determined even after this (when the role ID is the route role ID and the organization ID is not the route organization ID record in the user post information (FIG. 7)). The next delivery target user ID is determined with the parent organization ID of the organization ID as the “route organization ID”, and this process is repeated until the next delivery target user ID is determined.

  For example, when a slip based on the delivery definition information shown in FIG. 8 is issued, as shown in FIG. 9, the route role ID “004” of the node number “1” and the route organization ID “NULL” are shown in step S5003. ”Is acquired, and the user ID to be delivered is determined based on the acquired route role ID“ 004 ”and route organization ID“ NULL ”. Here, since the acquired route organization ID is “NULL”, the organization ID “8010101010” to which the user ID “U0012” corresponding to the node number “0” that is one smaller than the current node number “1” belongs is “route”. The next delivery target user ID is determined as the “organization ID”. At this time, since there is no record of the role ID “004” and the organization ID “8010101010” in the user post information (FIG. 7), the parent organization ID “80101010” of the organization ID “8010101010” is set as the “route organization ID”. The next delivery target user ID is determined. Here, referring to the user post information (FIG. 7), the role ID “004”, the user ID of the organization ID “8010101010” is “U0007”, and this user ID “U0007” is determined as the next delivery target user ID. Is done.

  Next, in step S5009, the CPU of the workflow server 200 determines whether or not the slip processing request received in step S5000 is from the final approver.

  If the CPU of the workflow server 200 determines in step S5009 that the slip processing request received in step S5000 is from the final approver, in step S5010, the delivery information table (FIG. 9) reads the delivery information. And the SMTP server 204 notifies the drafter that all approval has been made, and the process ends.

  On the other hand, if the CPU of the workflow server 200 determines in step S5009 that the slip processing request received in step S5000 is not from the final approver, in step S5011, the CPU of the workflow server 200 in step S5000. It is determined whether the request category of the received slip processing request is “approval”, “draft” or “denial”. If it is determined that it is “denied”, in step S5013 the delivery information table ( The current node number is deleted from FIG. 9), and a workflow notification to the effect that the delivery target person is denied is sent by the SMTP server 204, and the process ends.

  On the other hand, if the CPU of the workflow server 200 determines in step S5011 that the request category of the slip processing request received in step S5000 is “approval” or “draft”, a delivery information table ( In FIG. 9, the next node number information is set (at this time, the “processing user” is set to the next delivery target user ID determined in step S5009), and the SMTP server 204 sends the workflow to the delivery target person. Notification is made and the process is terminated.

  Hereinafter, the distributed workflow in the present embodiment will be described with reference to FIGS.

  FIG. 11 is a system configuration diagram showing an example of the operating environment of the workflow system of the present invention.

  In FIG. 11, reference numeral 600 denotes a server, which corresponds to the workflow server 200 shown in FIG. A client 620 corresponds to the workflow and slip design terminal 400 shown in FIG.

  The server 600 includes a web server 601 and a plurality of application servers 602 and 603. Application server 1 (602) and application server 2 (603) are activated for each subsystem, and operate servlet 1 (604) and servlet 2 (605) of the workflow system as separate processes. Thus, the workflow system of the present invention is a workflow system distributed to a plurality of different entities (servlets).

The application server 1 (602) and the application server 2 (603) generate the database instance 1 (606) and the database instance 2 (607) on the memory of the server 600, respectively. Note that the application server 1 (602) is the organization DB 608. , User DB 609, route DB 610, role DB 611, slip DB 612, DB instance 1 (606) having each table is generated. The application server 2 (603) generates a DB instance 2 (607) having the same table as the application server 1 (602).

  In the system configuration of this embodiment, the organization DB (608), user DB (609), and role DB (611) of the DB instance 1 (606) are set as common databases in this system.

  Servlet 1 (604) accesses DB instance 1 (606) which is a default information table.

  The servlet 2 (605) accesses the DB instance 1 (606), which is a common database for the user DB (609), the organization DB (608), and the role DB (611), and the route DB (615) and the slip DB (613). ) Accesses the default DB instance 2 (607). Note that DB information accessed by each servlet is stored and managed in a management table stored in the HD of the server 600 or the like.

  As described above, in the system of the present invention, the connection destination of the database connected in the workflow system can be specified in units of subsystems (servlets), and the system information of the workflow system (organization information, user information, role information, slip information, etc.) Can be partially shared between subsystems.

  Each application server creates connection pooling, which is a memory cache for connection to the database, on the memory of the server 600. By this connection pooling, each application server secures a connection to the database in advance in the application layer, thereby reducing the load at the time of connection. Each application server registers a data source with a naming service or the like activated on the server 600 and caches database information on the memory of the server 600. In this way, database processing is speeded up.

  Note that switching between the application server 1 (602) and the application server 2 (603) is realized by switching URLs accessed from the client 620.

  FIG. 12 is a schematic diagram showing an example of a monitoring screen of the workflow server 600 operated in the workflow system of the present invention. This monitoring screen is returned from the management program operating on the server 600 by logging in to the server 600 as a system administrator from the client 620 and requesting this monitoring screen, and the system management program 402 (see FIG. 1) Displayed on (may be on a Web browser or the like).

  In FIG. 12, reference numeral 700 denotes a monitoring screen. The monitoring screen 700 includes a server information list display 701 and a database connection information list 702.

  The server information list 701 displays a list of host names 703 and information 704 of servlets activated for each subsystem. The servlet information 704 displays the servlet path.

  In the example shown here, two servers are generated, the host names are both “CAT” (705, 706), and the servlet names are WebJ (707) and WebC (708) from the servlet path.

  Note that the display of the DB connection information list 702 is switched by switching the radio button 719 of the server list 701.

  The DB connection information list 702 displays login information to each table (organization table 709, role table 710, route table 711, user table 712) of the organization DB, role DB, route DB, and user DB. These pieces of information are stored and managed in a management table stored in the HD or the like of the server 600.

  The login information includes a database login ID, password, host name, and server name.

  For example, the login information 713 in the organization table 709 includes a login ID “Ringi”, a password “kannon”, a host name “cat”, and a server name “webj”. kannon / cat / webj ".

  Reference numeral 714 denotes a server addition button for adding a server to the server list 701. When the server addition button 714 is pressed with the input device of the client 620, a notification to that effect is transmitted from the client 620 to the server 600. Upon receiving this notification, the server 600 controls to add new server information after the server currently selected in the server list 701. In the example shown in FIG. 12, a new server is added after the server 708.

  Reference numeral 715 denotes a server correction button for changing the server information selected by the radio button 719 of the server list 701. When the server correction button 715 is instructed to be pressed by the input device of the client 620, a notification to that effect is transmitted from the client 620 to the server 600. In the server 600 that has received this notification, the server information selected by the radio button 719 in the server list 701 is changed and controlled.

  A server delete button 716 is used to delete the server information selected by the radio button 719 in the server list 701. When the server delete button 716 is instructed to be pressed with the input device of the client 620, a notification to that effect is transmitted from the client 620 to the server 600. Upon receiving this notification, the server 600 controls to delete the server information selected by the radio button 719 in the server list 701.

  Reference numeral 717 denotes a DB connection change button for changing login information of the databases 709 to 712 connected to the currently selected servlet. When this DB connection change button 717 is instructed to be pressed by the input device of the client 620, a notification to that effect is transmitted from the client 620 to the server 600. Upon receiving this notification, the server 600 changes and controls the login information of the databases 709 to 712 connected to the currently selected servlet.

  A table content change button 718 is used to change the contents of each of the organization table 709, role table 710, route table 711, and user table 712 connected to the currently selected server. When this table content change button 718 is instructed to be pressed by the input device of the client 620, a notification to that effect is transmitted from the client 620 to the server 600. Upon receiving this notification, the server 600 changes and controls the contents of the organization table 709, role table 710, route table 711, and user table 712 connected to the currently selected server.

  When the content of a shared database that is permitted to be accessed by a plurality of servlets, for example, the organization table 709 is changed with WebJ (servlet 1) selected, it is normally assigned to WebJ (servlet 1). The cache of the organization table is the latest, but the cache of the organization table assigned to WebC (Servlet 2) remains the old information.

  That is, when the contents of the shared database are changed, the contents of the cache corresponding to each database assigned to each servlet become inconsistent between the servlets, and the consistency of the cache becomes a problem. Conventionally, in response to this problem, the application server is restarted so that the contents of the cache corresponding to the database assigned to each servlet are matched between the servlets.

  In the workflow system of the present invention, when the content of the shared database, for example, the organization table 709 is changed, the CPU of the server 600 not only refreshes the cache assigned to the selected servlet at the time of change but also caches the table. Controls that all servlet caches are refreshed.

  Hereinafter, with reference to the flowcharts of FIGS. 13 and 14, the cache refresh process at the time of changing the contents of the database table in the workflow system of the present invention will be described.

  FIG. 13 is a flowchart showing an example of the second control processing procedure in the workflow system of the present invention, and corresponds to the main processing of the cache refresh processing when the contents of the database table are changed. Note that the processing of this flowchart is realized by the CPU of the server 600 shown in FIG. 11 loading a program (management program) stored in the HD or other recording medium into the RAM and executing it. S801 to S803 indicate each step.

  First, when the CPU of the server 600 receives a notification indicating that the table content change button 718 shown in FIG. 12 has been instructed to be pressed by the input device of the client 620 from the client 620, the CPU 600 starts the processing of this flowchart.

  In step S801, the CPU of the server 600 waits for input of table content change information from the client 620 by the change input process, and receives the table content change input information from the client 620. In step S802, step S801 The change contents input in step 1 are written into the table built in the HD of the server 600 and the table contents are changed.

  After the contents of the table are changed, in step S803, the CPU of the server 600 performs a cache refresh process for refreshing all the caches of the table assigned to each servlet (details are shown in FIG. 14). Then, the process of this flowchart ends.

  FIG. 14 is a flowchart showing an example of a third control processing procedure in the workflow system of the present invention, and corresponds to the cache refresh processing shown in step S803 of FIG. Note that the processing of this flowchart is realized by the CPU of the server 600 shown in FIG. 11 loading a program stored in the HD or other recording medium into the RAM and executing it. S901 to S906 indicate each step.

  In step S901, the CPU of the server 600 acquires one servlet name connected to the table (the table) whose contents are changed in step S802 of FIG.

  Next, in step S902, the CPU of the server 600 stores DB login information (eg, 713 in FIG. 12) of the servlet (the servlet) acquired in step S901 in the HD of the server 600 or the like. From the management table.

  Next, in step S <b> 903, the CPU of the server 600 releases the servlet cache memory from the server 600 memory.

  Next, in step S904, the CPU of the server 600 creates connection pooling on the memory of the server 600, which is a memory cache for connecting to the table. Further, the CPU of the server 600 registers the data source of the table with a naming service or the like activated on the server 600, caches the information of the table on the memory of the server 600, and completes the cache refresh.

  Next, in step S905, the CPU of the server 600 tries to acquire the servlet name (unprocessed) connected to the table again. In step S906, the CPU of the server 600 determines whether or not the servlet has been acquired in step S905. If it is determined that the servlet has been acquired (there is a servlet that has not been cache-refreshed), step S902 is performed. The process is returned to and processing for the next servlet is performed.

  On the other hand, if the CPU of the server 600 determines in step S906 that the servlet could not be acquired in step S905 (there is no servlet that has not been cache-refreshed), the processing of this flowchart ends. That is, the processes in steps S902 to S905 are repeated until the cache refresh is completed for all servlets connected to the table. As a result, when updating the system information (each table) that is the operating environment, it is possible to perform individual cache refresh of each servlet instead of cache refresh by restarting the application server.

  As described above, the system information (organization information, user information, role information, slip information, etc.) of the workflow system can be partially shared between subsystems (servlets) so that the database (organization information) connected with the workflow system , User information, role information, slip information, etc.) can be specified in subsystem units (managed by the management table). When updating system information in the operating environment, the cache refresh by restarting the application server In addition, individual cache refresh of each workflow server (each servlet) was enabled.

  In this way, by realizing the collective management function of multiple application servers and multiple workflows, for example, slip information and route information can be independently managed and managed for each category such as HR and general affairs, and organization information and role information Etc. can be managed collectively as common information. As a result, it is possible to improve the efficiency of development including electronic documents in each subsystem and improve the operational efficiency of the system administrator.

  Therefore, it is possible to reduce the maintenance work load of the workflow system in a large-scale organization having a large amount of work.

  In addition, all the structures which combined any or all of each modification shown in the said embodiment are also contained in this invention.

  Further, the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The configuration of a data processing program that can be read by each information processing apparatus constituting the workflow system according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 15 is a diagram illustrating a memory map of a recording medium (storage medium) that stores various data processing programs that can be read by each information processing apparatus constituting the workflow system according to the present invention.

  Although not specifically shown, information for managing a program group stored in the recording medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, when a program or data to be installed is compressed, a program to be decompressed may be stored.

  The functions shown in FIGS. 10, 13, and 14 in the present embodiment may be performed by a host computer by a program installed from the outside. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a recording medium such as a CD-ROM, a flash memory, or an FD, or from an external recording medium via a network. Is.

  As described above, a recording medium in which a program code of software for realizing the functions of the above-described embodiments is recorded is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus is stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the program code.

  In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program code constitutes the present invention.

  As a recording medium for supplying the program code, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, A silicon disk or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  In addition, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program represented by software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading out a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. It becomes.

It is a figure which shows schematic structure of the workflow system to which this embodiment is applied. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a computer applicable to the workflow server, the workflow operation terminal, the workflow, and the slip design terminal illustrated in FIG. 1. It is a schematic diagram which shows the flow of the slip in the workflow system shown in FIG. FIG. 2 is a data configuration diagram illustrating an example of a data structure of an organization table stored in an RDBMS of the workflow server illustrated in FIG. 1. It is a data block diagram which shows an example of the data structure of the role table memorize | stored in RDBMS of the workflow server shown in FIG. It is a data block diagram which shows an example of the data structure of the user table memorize | stored in RDBMS of the workflow server shown in FIG. FIG. 2 is a data configuration diagram illustrating an example of a data structure of a post table stored in an RDBMS of the workflow server illustrated in FIG. 1. FIG. 2 is a data configuration diagram illustrating an example of a data structure of delivery definition information stored in an RDBMS of the workflow server illustrated in FIG. 1. FIG. 2 is a data configuration diagram illustrating an example of a data structure of a delivery information table stored in an RDBMS of the workflow server illustrated in FIG. 1. It is a flowchart which shows an example of the 1st control processing procedure in the workflow system of this invention. It is a system configuration figure showing an example of the operation environment of the workflow system of the present invention. It is a schematic diagram which shows an example of the monitoring screen of the workflow server operated with the workflow system of this invention. It is a flowchart which shows an example of the 2nd control processing procedure in the workflow system of this invention. It is a flowchart which shows an example of the 3rd control processing procedure in the workflow system of this invention. It is a figure explaining the memory map of the recording medium (storage medium) which stores the various data processing program which can be read by each information processing apparatus which comprises the workflow system which concerns on this invention.

Explanation of symbols

600 server 601 Web server 602 Application server 1
603 Application server 2
604 Workflow system servlet 1
605 Workflow system servlet 2
606 DB instance 1
607 DB instance 2
620 clients

Claims (4)

In a workflow system distributed across different workflows,
A sharing means for sharing a database for managing information used in the workflow system between the workflows;
Cache means for caching the contents of the database in each of the workflows;
Refresh means for refreshing the cache of each workflow associated with the database when the contents of the database are changed;
A workflow system characterized by comprising: In a management method of a workflow system that is distributed among a plurality of different workflows and shares a database among the workflows,
A cache step of caching the contents of the database in each of the workflows;
A refresh step of refreshing each workflow cache associated with the database when the contents of the database are changed;
A method for managing a workflow system, comprising:   A program for a computer to execute the workflow system management method according to claim 2.   A recording medium storing a computer-readable program for executing the workflow system management method according to claim 2.

Images