JP2007058506A - Document management server, document management system, and document management program and its recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management sever capable of minimizing the substantial down-time of a document management system when any failure is generated, and a document management server fails over, and to provide a document management system, a document management program and its recording medium. <P>SOLUTION: This management system 1 is provided with a fail-over type clustering function of executing document management processing based on processing requests from clients 4 to 6, and for, when any failure is generated in a document management server 1, handing over the document management processing to a document management server 2 in a standby status. This document management server 1 is provided with a message transmitting means for, when any failure is generated in the document management server 1, and clustering processing is executed, and fail-over is completed, transmitting a call-back message for reconnection to a client which has been connected to the document management sever 1 when any failure is generated. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a document management server, a document management system, a document management program, and a recording medium thereof.

  In an enterprise-scale document management system, downtime of the document management system may be a problem. For example, when a document management system is used in a mission-critical system, there is a fatal problem that the mission-critical business using the document management system cannot be continued because the document management system goes down.

  In order to shorten system downtime, system availability is required, and one of the solutions is a failover (Fail Over) type clustering technology. If failover type clustering technology is used, the document management system is composed of multiple server machines, and one of them (active system) normally operates the document management system. If a failure occurs, it becomes a standby server. Document management processing can be taken over. As a result, the downtime of the document management system can be shortened.

  A conventional clustering document management system will be specifically described below with reference to FIG. FIG. 12 is a schematic configuration diagram of a conventional clustering document management system. As shown in FIG. 12, the conventional clustering document management system includes a document management server 1, a document management server 2, a document management database 3, and clients 4-6. Normally, the document management server transaction is executed in the document management server 1.

  Here, when a failure occurs in the document management server 1, the conventional clustering document management system autonomously takes over (fails over) the task to the document management server 2 (standby node). However, the clients 4 to 6 detect a failure of the document management server 1 at the stage where an operation is requested in the connection session after failover. Thereafter, the clients 4 to 6 again perform the document management process by reconnecting to the document management server business of the document management server 2.

Patent Document 1 discloses a technique for automatically performing recovery when a document management system ends abnormally. In Patent Document 2, an electronic document management system, a program, and an electronic document that can prevent a situation in which an electronic document file cannot be opened due to a change in the system or a change in the environment and ensure readability of an electronic original A technique related to the management method is disclosed.
JP 2003-280963 A JP 2004-192204 A

  However, in a document management system equipped with the failover type clustering technology as described above, the client connected to the document management server first becomes the document management server when the next processing request in which a failure has occurred is issued to the document management server. Recognize that a failure has occurred. After that, the client will continue to execute document management operations by performing reconnection processing to the document management server. Generally, however, the reconnection instruction is entrusted to operations such as email notification by the system administrator. There are many parts. In other words, if the timing for reconnecting to a document management server in which a failure has occurred is too early, an error occurs during failover of the document management server, and if it is too late, the task is delayed.

  In view of the above problems, the present invention provides a callback message for reconnecting a client when a failure occurs, the document management server fails over, and is ready to accept a processing request from the client. A document management server, a document management system, a document management program, and a recording medium thereof capable of minimizing substantial downtime of the document management system including operations from clients by transmitting The purpose is to provide.

  According to the first aspect of the present invention, failover management clustering executes document management processing based on a processing request from a client, and takes over the document management processing to a standby document management server when a failure occurs in the document management server. When a failure occurs in the document management server and a clustering process is executed and failover is completed, the client is connected to the document management server when the failure occurs. Thus, the document management server is provided with message transmission means for transmitting a callback message for reconnection.

  According to a second aspect of the present invention, the document management server accesses a document management database based on message reception means for receiving a processing request from a client connected to the document management server and the received processing request. Document management means for executing document management processing, clustering management means for executing and managing clustering processing for taking over the document management processing to another document management server when a failure occurs in the document management server, and the clustering Clustering state monitoring means for polling system information as to whether or not failover has been completed for the management means, a connection user list for storing connection client information for managing clients connected to the document management server, Connect to the server using the connected user list Connected user monitoring means for monitoring the client, and when the clustering state monitoring means determines that the failover has been completed, the connected user monitoring means determines from the connected user list that a failure has occurred in the document management server. 2. The document management server according to claim 1, wherein a client connected to the server is detected, and the message transmission means transmits a callback message for reconnecting to the detected client. Features.

  The invention described in claim 3 is the document management server according to claim 2, wherein the connection client information includes a client name which is identification information of the client and a user name who operates the client.

  According to a fourth aspect of the present invention, the connection client information includes status information indicating whether or not a processing request from the client has been completed, and the connection user monitoring means is configured to receive the document management server from the connection user list. 4. The document management server according to claim 2, wherein the client is connected to the server when a failure occurs and the client is incomplete in the status information.

  The invention described in claim 5 is characterized in that the message created by the message transmitting means is a document management server according to claim 4 further including a message indicating “processing re-execution”.

  According to a sixth aspect of the present invention, failover management clustering executes document management processing based on a processing request from a client, and takes over the document management processing to a standby document management server when a failure occurs in the document management server. A document management server having a function, wherein the document management server specifies processing contents and parameters for executing the processing for specifying a processing request from a client connected to the document management server. A transaction log stored in series and a transaction monitoring unit that monitors the transaction log and executes a predetermined process are provided. When the document management server fails, the clustering process is executed and the failover is completed. The transaction monitoring means Status information has been described a process which is uncompleted, characterized in that the document management server to be executed by the document management server in the standby.

  According to a seventh aspect of the present invention, when the transaction monitoring unit fails to cause the standby document management server to execute a process in which the status information described in the transaction log is incomplete. A callback message for retrying the request process is transmitted to the client that issued the process that failed to execute and the client that issued the process subsequent to the process that failed to execute in the transaction log. 7. The document management server according to claim 6, further comprising a message transmission unit.

  According to an eighth aspect of the present invention, the document management server accesses a document management database based on message reception means for receiving a processing request from a client connected to the document management server, and the received processing request. Document management means for executing document management processing, clustering management means for executing and managing clustering processing for taking over the document management processing to another document management server when a failure occurs in the document management server, and the clustering Clustering state monitoring means for polling system information as to whether or not failover has been completed for the management means, a connection user list for storing connection client information for managing clients connected to the document management server, Connect to the server using the connected user list Characterized in that the connecting user monitoring means for monitoring the client and the document management server according to claim 6 or 7, wherein comprising a.

  According to the ninth aspect of the present invention, the connection client information includes a client name that is identification information of the client, a user name that operates the client, and status information that indicates whether the processing request from the client is completed. 9. A document management server according to claim 8, wherein the server is a document management server.

  The invention described in claim 10 is a document management program for causing a computer to realize the function of the document management server described in any one of claims 1 to 9.

  The invention described in claim 11 is characterized in that the document management program according to claim 10 is recorded as a recording medium.

  The invention according to claim 12 is the document management server according to any one of claims 1 to 9, which is connected to each other via a network, and the document management server when a failure occurs in the document management server. The document management system includes a document management server waiting for taking over a document management process to be executed by the management server, a document management database, and a client requesting the document management process.

  According to the present invention, when a failure occurs, the document management server fails over, and a processing request from the client is accepted, the client is notified of a callback message “reconnectable”, whereby the client It is possible to realize a document management server, a document management system, a document management program, and a recording medium thereof capable of minimizing substantial downtime of the document management system including operations from the above.

  In the best mode for carrying out the present invention, document management processing is executed based on a processing request from a client, and when a failure occurs in the document management server, the document management processing is taken over by the standby document management server. In a document management server equipped with a failover type clustering function, when a failure occurs in the document management server and the clustering process is executed and failover is completed, the client connected to the document management server when the failure occurs Message transmission means for transmitting a callback message for causing reconnection is provided.

  Preferred embodiments of the present invention will be described below in detail with reference to the accompanying drawings. The embodiments described below are preferable specific examples of the present invention, and thus various technically preferable limitations are given. However, the scope of the present invention is particularly limited in the following description. Unless otherwise described, the present invention is not limited to these embodiments.

(Embodiment 1)
In the document management system of this embodiment, when a failure occurs in the document management server, the client that has accessed the document management server transaction is recorded in the document management server, and the document management server transaction is set as the standby server. When failover occurs and connection from the client becomes possible, the client connected to this system at the time of the failure will receive a callback message with the message content indicating that failover is complete and reconnection is possible. A transmission function is provided.

  First, a schematic configuration of the document management system according to the present embodiment and functions of each unit will be described below with reference to FIG. FIG. 1 is a schematic configuration diagram of a document management system according to the present embodiment. As shown in FIG. 1, the document management system according to the present embodiment includes document management servers 1 and 2, a document management database 3 that stores document data, and clients 4 to 6.

  The document management server 1 includes a clustering state monitoring processing unit 7, a message transmission / reception processing unit 8, a connected user monitoring processing unit 9, a connected user list 10, a document management processing unit 11, and a clustering management processing unit 12. The document management server 1 according to the present embodiment is not limited to a personal computer server (PC server). For example, an MFP in which a function having a fallover clustering method provided in the document management server 1 according to the present embodiment is installed. (Multi Functional Peripheral) may be used.

  The clustering state monitoring processing unit 7 has a function of polling system information such as occurrence of failover. The message transmission / reception processing unit 8 has a function of transmitting / receiving a request message from a client. The connected user monitoring processing unit 9 has a function of monitoring clients that have accessed the document management server 1. The connected user list 10 has a function of storing connected client information for managing clients that are being accessed. The document management processing unit 11 has a function of performing document management operations. The clustering management processing unit 12 has a function of executing and managing clustering processing.

  Next, the connected user list 10 will be described below mainly using FIG. FIG. 2 is a diagram showing the connected user list 10 of the present embodiment. As shown in FIG. 2, the connected user list 10 includes a client name indicating the location information (machine name, IP address, etc.) of the clients 4 to 6 shown in FIG. 1, and a connection indicating a user operating on each client. Consists of the user name.

  Next, the update operation of the connected user list 10 at the time of client access in the document management system of this embodiment will be described. FIG. 3 is a flowchart for explaining the update operation of the connected user list 10 at the time of client access in the document management system of this embodiment.

  First, as shown in FIG. 3, for example, when the client 4 shown in FIG. 1 accesses the document management server business of the document management server 1, the document management server 1 sends a processing request from the client 4 to the message shown in FIG. It is received by the transmission / reception processing unit 8 (step 101). Subsequently, the message transmission / reception processing unit 8 determines the type of processing request from the client 4 (step 102), and in the case of the “connection start request”, the processing is transferred to the connected user monitoring processing unit 9 shown in FIG. Step 102 YES → Step 103).

Subsequently, the connected user monitoring processing unit 9 stores {client A, Mr. A} as the client connection information in the connected user list 10 shown in FIG. 1 (step 103).
Therefore, after processing the “connection start request” from the client 4 (step 103), the client 4 that has made the connection start request performs a document management operation.

  Further, the message transmission / reception processing unit 8 determines the type of processing request from the client 4 (step 102), and if it is not “connection start request” but “connection end request”, the connection user monitoring process shown in FIG. The process is transferred to the unit 9 (NO at step 102 → YES at step 104), and the user monitoring processing unit 9 deletes the client connection information regarding the client 4 making the “connection end request” from the connected user list 10 (step 105).

  Further, the message transmission / reception processing unit 8 determines the type of processing request from the client 4 (step 102), and in the case of other processing requests that are neither “connection start request” nor “connection end request”, FIG. The document management processing unit 11 executes processing (document management operation) requested by the client 4 by accessing the document management database 3 (step 102NO → step 104NO). → Step 106). Subsequently, the message transmission / reception processing unit 8 creates an operation result from the result executed by the document management processing unit 11 and transmits it to the client (step 107).

  Next, the operation of callback notification to the client when the failover is completed in the document management system of this embodiment will be described with reference to FIG. FIG. 4 is a flowchart for explaining the callback notification operation to the client when the failover is completed in the document management system of this embodiment.

  In this description, in the document management system of the present embodiment, when a client (user terminal) is accessing a document management server transaction by the operation of the document management server 1, a failure occurs in the document management server 1, and the document management Assume that the document management server transaction is failed over (taken over) to the server 2.

  First, as shown in FIG. 4, the clustering state monitoring processing unit 7 (see FIG. 1) of the document management server 1 periodically polls the clustering management processing unit 12 (step 201 → step 202 NO →). Repeat step 201).

  The clustering state monitoring processing unit 7 executes clustering processing by the clustering management processing unit 12 when a failure occurs in the document management server 1, and the document management server operation by the operation of the document management server 1 is changed to document management. If it is determined that the failover to be taken over by the server 2 has been completed, the connected user monitoring processing unit 9 detects a client stored in the connected user list 10 (step 202 YES → step 203).

  After detection, all information (data) on the connected user list 10 is deleted (step 203). Subsequently, the message transmission / reception processing unit 8 sends a “reconnectable” message (callback notification) to the client detected from the connected user list 10 (the client connected to the system at the time of failover). Create and send (step 204).

  Thereafter, the user of the client (the client that has received the callback notification among the clients 4 to 6 shown in FIG. 1) that has received the above-described message “reconnectable” (callback notification) Thus, reconnection processing is executed.

  Therefore, according to the present embodiment, after the completion of the failover of the document management system, it becomes possible to use again, by notifying all clients that were connected to the system at the time of the failure, By prompting the client to perform the above process, it is possible to obtain an effect of minimizing downtime due to a failure including a client operation of the document management system.

(Embodiment 2)
The present embodiment is an application example of the first embodiment. Therefore, description of common parts is omitted, and the document management system of the present embodiment will be described below with reference to the accompanying drawings, focusing on characteristic parts. By the way, in the first embodiment, when the document management server fails over, a callback message “reconnectable” is transmitted to all clients that have been connected after the failover is completed.

  However, depending on the client, there is a situation where the processing request is completed and only the connection with the document management server remains. Even if a callback message “reconnectable” is sent to such a client, it is not received and immediately reconnected to the document management server. Such a callback message is unnecessary and increases the network load. In addition, the operation of the client becomes complicated. This embodiment pays attention to such a problem and proposes a solution.

  In this embodiment, “status” information indicating whether or not the processing request has been completed is added to the connected user list 10 shown in FIG. 2, and the status among the clients that are connected when the document management server fails over is displayed. Sends a callback message of “reconnectable” after failover is completed to only clients that are “incomplete”.

  FIG. 5 shows the connected user list 10 of the present embodiment. As shown in FIG. 5, the connected user list 10 of the present embodiment is status information indicating completion / uncompletion of the document management operation at the time of failover with respect to the connected user list 10 of the first embodiment shown in FIG. Is added.

  Next, the update operation of the connected user list 10 at the time of client access in the document management system of this embodiment will be described. FIG. 6 is a flowchart for explaining the update operation of the connected user list 10 at the time of client access in the document management system of this embodiment.

  First, as shown in FIG. 6, for example, when the client 4 accesses the document management server business of the document management server 1, the document management server 1 sends a processing request from the client 4 to the message transmission / reception processing unit 8 shown in FIG. (Step 301). Subsequently, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 302), and in the case of the “connection start request”, passes the processing to the connected user monitoring processing unit 9 shown in FIG. 302 YES-> step 303).

Subsequently, the connected user monitoring processing unit 9 stores the connected client name and the connected user as client connection information in the connected user list 10 shown in FIG. 1 (step 303).
Therefore, after processing the “connection start request” of the client 4 (step 303), the client 4 performs a document management operation.

  Further, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 302), and if it is not “connection start request” but “connection end request”, the connected user monitoring processing unit shown in FIG. 9 (step 302 NO → step 304 YES), the user monitoring processor 9 deletes the client connection information regarding the client making the “connection end request” from the connected user list 10 (step 305).

  Further, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 302), and in the case of other processing requests that are neither “connection start request” nor “connection end request”, FIG. The connected user monitoring processing unit 9 shown in the figure sets the status of the connected client (in this case, the client 4) from the connected user list 10 to “incomplete” (step 306). Then, the document management processing unit 11 executes the process requested by the client 4 (document management operation) by accessing the document management database 3 (step 307).

  Subsequently, the message transmission / reception processing unit 8 creates an operation result from the result executed by the document management processing unit 11, and transmits it to the client 4 (step 308). Then, the connected user monitoring processing unit 9 sets the status of the connected client from the connected user list 10 to “processing complete” (step 309).

  Note that when a failure occurs in steps 307 and 308, generally, the processing in steps 307 and 308 is discarded, or the update given to the document management database 3 by the processing is rolled back. This is not defined in the present embodiment. In the flowchart shown in FIG. 6, it is assumed that error processing such as appropriate rollback processing is performed and client access is terminated.

  As described above, according to the document management system of the present embodiment, for example, when an operation request from the client 4 is made, the connected user monitoring processing unit 9 first stores it in the connected user list 10 shown in FIG. The client 4 record is specified, and “uncompleted” is stored in the status field in the sense that the requested document management process will be started.

  Thereafter, the document management processing unit 11 executes the actual document management processing, and the message transmission / reception processing unit 8 returns the result to the client 4. Thereafter, the connected user list monitoring processing unit 9 stores “processing completed” in the status field to indicate that the processing request from the currently processed client 4 has been completed. The same processing is performed for the clients 5 and 6.

  Next, the operation of the callback notification to the client when the failover is completed in the document management system of this embodiment will be described with reference to FIG. FIG. 7 is a flowchart for explaining the callback notification operation to the client when the failover is completed in the document management system of this embodiment.

  In this description, a failure occurs in the document management server 1 while the document management processing unit 11 is processing a document management operation in response to a processing request from the clients 5 and 6. Assume that the document management server transaction is failed over (taken over) to the server 2.

  First, as shown in FIG. 7, the clustering state monitoring processing unit 7 (see FIG. 1) of the document management server 1 periodically polls the clustering management processing unit 12 (step 401 → step 402NO → Repeat step 401).

  The clustering state monitoring processing unit 7 executes clustering processing by the clustering management processing unit 12 when a failure occurs in the document management server 1, and the document management server operation by the operation of the document management server 1 is changed to document management. When it is determined that the failover to be taken over by the server 2 is completed, the connected user monitoring processing unit 9 detects a client stored in the connected user list 10 (YES in step 402 → step 403).

  Here, the detected clients are clients in which the above-described status information is set to incomplete, and are clients 5 and 6 in this example. After the detection, all information (data) on the connected user list 10 is deleted (step 403).

Subsequently, the message transmission / reception processing unit 8 sends a message (callback notification) to only the clients 5 and 6 (clients whose status information is set to incomplete) that can be reconnected and re-execute preprocessing ) Is created and transmitted (step 404).
After that, the users of the clients 5 and 6 that have received the callback notification described above execute reconnection processing to the document management server 2 according to the message, and try to retry the processing requested when a failure occurs.

  Therefore, according to the present embodiment, in addition to the effects shown in the first embodiment, when the document management system is reconnected after the failover is completed, only the client that needs to retry the incomplete processing is “ By performing a callback message (callback notification) indicating that reconnection is possible and re-execute the pre-processing, an effect of reducing the network load associated with the callback message can be obtained.

(Embodiment 3)
The present embodiment is an application example of the first and second embodiments. Therefore, description of common parts is omitted, and the document management system of the present embodiment will be described below with reference to the accompanying drawings, focusing on characteristic parts. Incidentally, when the document management server fails over, the second embodiment has a function of retrying a processing request from the client if the processing request from the connected client is “incomplete”.

  However, in the second embodiment, whether or not to execute a process retry is left to the client. In an environment where a series of processes are realized by a plurality of clients, a client does not retry the process. There is a problem that the flow process cannot be completed. This embodiment pays attention to such a problem and proposes a solution.

  Compared with the second embodiment, the present embodiment adds a transaction log in which a processing request from a connected client is stored in chronological order with processing contents and parameters for executing the processing. When a failover occurs, the document management server automatically retries the process for which the status described in the transaction log is set to “Incomplete”. If automatic retry fails, the failed process request is displayed. A callback message for retrying request processing is transmitted only to the issued client and the client that issued processing after the processing that failed in the transaction log.

  First, a schematic configuration of the document management system of the present embodiment will be described below with reference to FIG. FIG. 8 is a schematic configuration diagram of the document management system of the present embodiment. As shown in FIG. 8, the document management system of this embodiment is obtained by adding a transaction monitoring processor 13 and a transaction log 14 to the document management server 1 of the document management system of the first embodiment shown in FIG. It is.

  Here, the transaction log 14 will be described below with reference to FIG. FIG. 9 is a diagram showing the transaction log 14 of the present embodiment. As shown in FIG. 9, the transaction log 14 includes a client name indicating a client who requested processing in time series, processing contents requested by the client, processing parameters necessary for executing the processing contents, and processing thereof. It is composed of status information indicating completion / incompletion.

  Next, the management operation of the transaction log 14 at the time of client access in the document management system of this embodiment will be described. FIG. 10 is a flowchart for explaining the management operation of the transaction log 14 at the time of client access in the document management system of this embodiment.

  First, as shown in FIG. 10, for example, when the client 4 accesses the document management server business of the document management server 1, the document management server 1 sends a processing request from the client 4 to the message transmission / reception processing unit 8 shown in FIG. (Step 501). Subsequently, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 502), and in the case of the “connection start request”, passes the processing to the connected user monitoring processing unit 9 shown in FIG. 502 YES-> step 503).

  Subsequently, the connected user monitoring processing unit 9 stores the connected client name and the connected user as client connection information in the connected user list 10 shown in FIG. 1 (step 503). Then, the connected user monitoring processing unit 9 sets the status of the connected client from the connected user list 10 to “processing complete” (step 511).

  Further, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 502), and if it is not “connection start request” but “connection end request”, the connected user monitoring processing unit shown in FIG. 9 (step 502 NO → step 504 YES), the user monitoring processor 9 deletes the client connection information regarding the client making the “connection end request” from the connected user list 10 (step 505). Then, the connected user monitoring processing unit 9 sets the status of the connected client from the connected user list 10 to “processing complete” (step 511).

  Further, the message transmission / reception processing unit 8 determines the type of processing request of the client 4 (step 502), and in the case of other processing requests that are neither “connection start request” nor “connection end request”, FIG. The connected user monitoring processing unit 9 shown in the figure sets the status of the connected client (in this case, the client 4) from the connected user list 10 to “incomplete” (step 506). Subsequently, the transaction monitoring processing unit 13 stores the processing (document management operation) requested from the client 4 in the transaction log 14 (step 507). The transaction log 14 stores the name of the client that issued the process, the details of the process, and the process parameters, and the status is set to “incomplete” (step 507).

  Then, the document management processing unit 11 executes processing (document management operation) requested from the client 4 by accessing the document management database 3 (step 508). Subsequently, the message transmission / reception processing unit 8 creates an operation result from the result executed by the document management processing unit 11 and transmits it to the client 4 (step 508). Then, the transaction monitoring processing unit 13 stores in the transaction log 14 that the processing request made from the client 4 has been completed. At this time, the status is “completed” (step 510).

  Then, the connected user monitoring processing unit 9 sets the status of the connected client from the connected user list 10 to “processing complete” (step 511). Note that when a failure occurs in the above steps 508 and 509, the processing in steps 508 and 509 is generally discarded or the update given to the document management database 3 by the processing is rolled back. This is not defined in the present embodiment. In the flowchart shown in FIG. 10, it is assumed that error processing such as appropriate rollback processing is performed and client access is terminated.

  As described above, according to the document management system of the present embodiment, for example, when an operation request from the client 4 is made, the connected user monitoring processing unit 9 first stores it in the connected user list 10 shown in FIG. The client 4 record is specified, and “uncompleted” is stored in the status field in the sense that the requested document management process will be started. Thereafter, in accordance with the flowchart shown in FIG. 10, the transaction monitoring processing unit 13 processes the processing request made from the client 4 with respect to the transaction log 14 and identifies the client 4 that issued the processing, the processing content, and the processing Is stored, and “incomplete” indicating that the process is to be executed is stored in the status.

  Thereafter, the document management processing unit 11 executes the actual document management processing, and the message transmission / reception processing unit 8 returns the result to the client 4. Subsequently, the transaction monitoring processing unit 13 stores “processing completed” in the status field of the transaction log 14 in order to indicate that the processing request from the currently processed client 4 has been completed. The same processing is performed for the clients 5 and 6.

  Next, the operation of the callback notification to the client when the failover is completed in the document management system of this embodiment will be described with reference to FIG. FIG. 11 is a flowchart for explaining the callback notification operation to the client when the failover is completed in the document management system of this embodiment.

  In this description, a failure occurs in the document management server 1 while the document management processing unit 11 is processing a document management operation in response to a processing request from the clients 5 and 6. Assume that the document management server transaction is failed over (taken over) to the server 2.

  First, as shown in FIG. 11, the clustering state monitoring processing unit 7 (see FIG. 1) of the document management server 1 periodically polls the clustering management processing unit 12 (step 601 → step 602NO → Repeat step 601).

  The clustering state monitoring processing unit 7 executes clustering processing by the clustering management processing unit 12 when a failure occurs in the document management server 1, and the document management server operation by the operation of the document management server 1 is changed to document management. When it is determined that the failover to be taken over by the server 2 has been completed, the transaction monitoring processing unit 13 refers to the transaction log 14, and processes documents whose status is “incomplete” in time series via the message transmission / reception processing unit. A processing request is sent to a document management processing unit (not shown) of the server 2 (YES in step 602 → step 603).

  Subsequently, the document management processing unit of the document management server 2 executes a process (document management operation) whose status is “incomplete” by accessing the document management database 3 in time series (step 604). Then, the document management processing unit of the document management server 2 executes the process until there is no process with the status “incomplete” stored in the transaction log 14 (steps 603 → 604 → 605 → 608 are repeated).

  On the other hand, when the document management processing unit of the document management server 2 fails to execute the process (document management operation) whose status is “incomplete” (step 605 NO), for example, in the transaction log 14 shown in FIG. Assume that the execution of the incomplete processing of (client 5) is successful, but the execution of the incomplete processing of client C (client 6) fails.

  In this case, as shown in FIG. 5, the document management processing unit of the document management server 2 has failed in the thumbnail creation process of the client C (client 6), so the client C (client 6) and the next in the transaction log 14 The transaction monitoring processing unit 13 of the document management server 1 requests the re-execution of the process to the client B (client 5) that requested the document registration process (for the client that issued the transaction after the process failure). Thus, the message transmission / reception processing unit 8 is requested (step 606).

  Then, the message transmission / reception processor 8 creates a callback message for retrying the request processing for the client name (clients B and C), and sends the message (callback) to the clients 5 and 6. Notification) is transmitted (step 607). Thereafter, in the clients 5 and 6 that have received the callback notification, the user reconnects to the document management server 2 in accordance with the message, and the designated process is retried.

  If there is no processing whose status stored in the transaction log 14 is “incomplete” in step 608, or if a callback notification is made in step 607, the transaction monitoring processing of the document management server 1 is subsequently performed. The unit 13 clears the transaction log 14 (step 609). Then, the connected user monitoring processing unit 9 clears the connected user list 10 (step 610).

  As described above, according to the present embodiment, when the document management server 1 fails over when the document management server 1 fails over, the document management server 2 performs automatic retry after the failover is completed. It is possible to automatically restore processing at For this reason, the retry of the processing depending on the client is eliminated, and the effect that the complexity of the system operation is reduced can be obtained.

It is a schematic block diagram of the document management system in 1st Embodiment. It is the figure which showed the connected user list 10 in 1st Embodiment. 6 is a flowchart for explaining an operation of updating the connected user list 10 at the time of client access in the document management system according to the first embodiment. 6 is a flowchart for explaining an operation of a callback notification to a client when failover is completed in the document management system of the first embodiment. It is the figure which showed the connected user list 10 in 2nd Embodiment. It is a flowchart for demonstrating the update operation | movement of the connection user list | wrist 10 at the time of client access in the document management system of 2nd Embodiment. 12 is a flowchart for explaining an operation of a callback notification to a client when failover is completed in the document management system of the second embodiment. It is a schematic block diagram of the document management system in 3rd Embodiment. It is the figure which showed the transaction log 14 in 3rd Embodiment. 15 is a flowchart for explaining a transaction log management operation at the time of client access in the document management system according to the third embodiment. 14 is a flowchart for explaining an operation of a callback notification to a client when failover is completed in the document management system of the third embodiment. It is a schematic block diagram of the conventional document management system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Document management server 2 Document management server 3 Document management database 4, 5, 6 Client 7 Clustering state monitoring processing part 8 Message transmission / reception processing part 9 Connected user monitoring processing part 10 Connected user list 11 Document management processing part 12 Clustering management processing part 13 Transaction monitoring processing unit 14 Transaction log

Claims (12)

A document management server having a failover clustering function that executes document management processing based on a processing request from a client and takes over the document management processing to a standby document management server when a failure occurs in the document management server. There,
A callback message for causing a client connected to the document management server to reconnect when a failure occurs in the document management server and a clustering process is executed to complete failover. A document management server comprising message transmission means for transmitting. The document management server includes a message reception unit that receives a processing request from a client connected to the document management server, and a document that executes a document management process by accessing a document management database based on the received processing request. When a failure occurs in the management unit and the document management server, failover is performed on the clustering management unit that executes and manages the clustering process that takes over the document management process to another document management server, and the clustering management unit. Clustering state monitoring means for polling system information as to whether or not completed, a connected user list for storing connected client information for managing clients connected to the document management server, and the connected user list Monitor clients connected to the server Comprising a connecting user monitoring means that, the,
When the clustering state monitoring unit determines that the failover has been completed, the connected user monitoring unit detects a client connected to the server when the document management server has failed from the connected user list, and transmits the message. The document management server according to claim 1, wherein the means transmits a callback message for causing reconnection to the detected client.   3. The document management server according to claim 2, wherein the connection client information includes a client name which is identification information of the client and a user name who operates the client.   The connected client information includes status information indicating whether or not a processing request from the client has been completed, and the connected user monitoring means connects to the server from the connected user list when a failure occurs in the document management server. 4. The document management server according to claim 2, wherein the client is a client that has been in progress and the status information is incomplete. 5.   5. The document management server according to claim 4, wherein the message created by the message transmission means further includes a message indicating “processing re-execution”. A document management server having a failover clustering function that executes document management processing based on a processing request from a client and takes over the document management processing to a standby document management server when a failure occurs in the document management server. There,
The document management server includes a transaction log in which processing details for specifying a processing request from a client connected to the document management server and parameters for executing the processing are stored in time series, and the transaction Transaction monitoring means for monitoring a log and executing a predetermined process,
When a failure occurs in the document management server and a clustering process is executed and failover is completed, the transaction monitoring unit performs processing in which status information described in the transaction log is incomplete. A document management server that is executed by a standby document management server.   When the transaction monitoring unit fails to cause the standby document management server to execute a process for which status information described in the transaction log is incomplete, the process that failed to execute is executed. In the transaction log, there is provided message transmission means for transmitting a callback message for retrying request processing to the client that has issued processing subsequent to the processing that failed in the transaction log. The document management server according to claim 6, wherein:   The document management server includes a message reception unit that receives a processing request from a client connected to the document management server, and a document that executes a document management process by accessing a document management database based on the received processing request. When a failure occurs in the management unit and the document management server, failover is performed on the clustering management unit that executes and manages the clustering process that takes over the document management process to another document management server, and the clustering management unit. Clustering state monitoring means for polling system information as to whether or not completed, a connected user list for storing connected client information for managing clients connected to the document management server, and the connected user list Monitor clients connected to the server Document management server according to claim 6 or 7, wherein further comprising a connecting user monitoring means that, the.   The connection client information includes a client name as client identification information, a user name operating the client, and status information indicating whether a processing request from the client is completed. 8. The document management server according to 8.   A document management program for causing a computer to realize the function of the document management server according to any one of claims 1 to 9.   A recording medium on which the document management program according to claim 10 is recorded.   The document management server according to any one of claims 1 to 9, which is connected to each other via a network, and document management to be executed by the document management server when a failure occurs in the document management server A document management system comprising: a document management server waiting to take over processing; a document management database; and a client requesting document management processing.

Images