JP5418070B2 - Business operation support method and computer apparatus - Google Patents

Description

  The present technology relates to a technology for supporting a user's business operation in a client / server business processing system.

  For example, in a client-server type business processing system, a user proceeds with work such as data input while tracing a plurality of business processing screens using a client terminal. In addition, there is a system having a standby system in preparation for a failure. In such a system, when a failure occurs in the normal system and the connection with the normal system is cut off, the operation is switched to the standby system.

  However, in such a system, it is not always guaranteed that work can be resumed from the middle. Therefore, after switching to the standby system, the user may have to start the work from the beginning.

JP 2004-32224 A

  As described above, in the related art, when a user's work is interrupted due to a system failure, the user may have to start the work from the beginning, which is troublesome for the user. Further, in the prior art, when the work is interrupted, it has not been possible for the user to easily grasp what work has been completed.

  Therefore, an object of the present technology is to allow a user to resume work when the user's work is interrupted due to a system failure.

  The business operation support method according to the first aspect is configured to connect a normal system and a standby system that holds log data related to database update processing executed in the normal system via a network, and And a management database for storing log data identifiers, and a business operation support method executed by a computer having a storage device. And this business operation support method, when receiving data of a specific business process screen from the regular system, displaying the specific business process screen, storing the data of the specific business process screen in the storage device, Receiving input or selection data for a specific business process screen from the user and transmitting it to the regular system, and database update processing executed in the regular system in response to the input or selection data being transmitted to the specific business process screen When log data is received from the regular system, the log data is stored in a storage device, and the identifier of the log data is stored in the management database in association with the identifier of a specific business process screen; When a failure is detected, log data stored in the storage device is sent to the standby system. Corresponding to the latest log data out of the log data for which it was confirmed that the standby system was confirmed to be consistent with the steps to execute the processing to check the consistency of the log data in the standby system And a display step for acquiring and displaying data of a business process screen next to the business process screen to be displayed from the storage device.

  The business processing system according to the second aspect includes a normal system, a standby system that holds log data related to database update processing executed in the normal system, an identifier of a business processing screen, and an identifier of log data. A client computer having a management database and a storage device; When the above-mentioned regular system receives the data for the specific business process screen to the client computer and the input or selection data for the specific business process screen from the client computer, the database update process And means for transmitting log data relating to the database update processing to the client computer. In addition, when the standby system described above receives log data from the client computer, it checks the consistency by comparing the received log data with the log data held by the standby system itself, and the confirmation result Is transmitted to the client computer. Further, when the client computer described above receives data on a specific business process screen from the regular system, the client computer displays the specific business process screen and stores the specific business process screen data in the storage device. And means for receiving input or selection data for a specific business process screen from the user and sending it to the regular system, and after receiving input or selection data for a specific business process screen and receiving log data from the regular system Storing the log data in the storage device, storing the identifier of the log data in the management database in association with the identifier of the specific business process screen, and detecting the occurrence of a failure in the normal system, It must be consistent with the means to send the stored log data to the standby system and the standby system. And means for acquiring and displaying the data of the next business processing window of the most recent work processing screen corresponding to the log data or the business processing screen from the storage unit of the notification log data that has been certified.

  When a system failure occurs and the user's work is interrupted, the user can resume the work.

FIG. 1 is a diagram illustrating an example of a business completed through a plurality of business processing screens. FIG. 2 is a diagram illustrating an example when a system failure occurs during the work for the business illustrated in FIG. FIG. 3 is a diagram illustrating an example of a login screen of the standby system. FIG. 4 is a diagram for describing the outline of the embodiment of the present technology. FIG. 5 is a system configuration diagram of a business processing system according to an embodiment of the present technology. FIG. 6 is a functional block diagram of a client terminal in the business processing system. FIG. 7 is a diagram illustrating an example of data stored in the management database. FIG. 8 is a diagram illustrating an example of data stored in the business process management table. FIG. 9 is a diagram illustrating a processing flow (first portion) of the business processing system during normal operation. FIG. 10 is a diagram illustrating a processing flow (second part) of the business processing system during normal operation. FIG. 11 is a diagram illustrating a processing flow (first portion) of the business processing system when a system failure occurs. FIG. 12 is a diagram illustrating an example of a reproduction list. FIG. 13 is a diagram illustrating a processing flow (second part) of the business processing system when a system failure occurs. FIG. 14 is a diagram illustrating a processing flow (third portion) of the business processing system when a system failure occurs. FIG. 15 is a diagram showing a processing flow of transaction comparison processing. FIG. 16 is a diagram illustrating a processing flow of the business processing system at the time of recovery. FIG. 17 is a functional block diagram of a computer. FIG. 18 is a diagram illustrating a processing flow of the business operation support method according to the first aspect of the present technology. FIG. 19 is a functional block diagram of a client computer according to the second aspect of the present technology.

  First, an outline of an embodiment of the present technology will be described with reference to FIGS. 1 to 4. Here, a description will be given on the premise of a business processing system having a regular system and a standby system. For example, as shown in FIG. 1, it is assumed that one job is completed through a plurality of job processing screens (screen 1 to screen 3 in FIG. 1). FIG. 1 shows an example of a business in which two transactions are executed per screen. Specifically, transactions TR1 and TR2 are executed on screen 1, transactions TR3 and TR4 are executed on screen 2, and transactions TR5 and TR6 are executed on screen 3.

  For example, as shown in FIG. 2, when a user is working in the order of a login screen, screen 1, and screen 2, and a system failure occurs on screen 2 (transaction TR4), the normal system changes to the operational system. Operation is switched to At this time, for example, as shown in FIG. 3, a login screen for logging in to the standby system is displayed. In this case, the processing up to the transaction TR3 on the screen 2 has been completed, but after logging into the standby system, it may be necessary to start again from the screen 1 (transaction TR1). In addition, since the user forgets that the transaction TR3 has been completed, the user may not be able to resume from the middle.

  Therefore, in this embodiment, when the user's work is interrupted due to a system failure, as shown in FIG. 4, as shown in FIG. Thus, it is possible for the user to easily recognize up to which work has been completed. In addition, the database update log that is output when the transactions TR1, TR2, and TR3 are executed is transferred from the regular system to the client terminal. When the client terminal displays each screen, the input contents from the update log are displayed. To reproduce. Hereinafter, embodiments of the present technology will be described in detail.

  FIG. 5 shows a system configuration of a business processing system according to an embodiment of the present technology. For example, a failure detection device 3 and a client terminal 9 are connected to a network 1 that is the Internet. Furthermore, a network device 50 in the normal system 5 and a network device 70 in the standby system 7 are connected to the failure detection device 3. Note that a web browser is installed in the client terminal 9 and is executed according to a user instruction.

  Further, the regular system 5 includes a network device 50, a Web server 51, an AP (application) server 52, a DB (database) server 53, and a DB 54 managed by the DB server 53. The network device 50, the Web server 51, the AP server 52, and the DB server 53 are connected via a LAN (Local Area Network) or the like. The DB server 53 includes a transaction transfer module 531 that transmits an update log of the DB 54 to the client terminal 9. In the present embodiment, the update log may be referred to as transaction data.

  Further, the standby system 7 includes a network device 70, a Web server 71, an AP server 72, a DB server 73, and a DB 74 managed by the DB server 73. The network device 70, the Web server 71, the AP server 72, and the DB server 73 are connected via a LAN or the like. The Web server 71 also includes a server-side business continuation module 711 that performs processing for business processing continuation. Further, the DB server 73 includes a transaction comparison module 731 that performs processing for confirming the consistency of the update log.

  In the business processing system shown in FIG. 5, since the database is synchronized between the active system 5 and the standby system 7, the update log of the DB 54 is remotely and immediately transferred from the active system 5 to the standby system 7 by the replication function. It is supposed to transfer. The standby system 7 holds the update log transferred from the regular system 5.

  FIG. 6 is a functional block diagram of the client terminal 9 shown in FIG. The client terminal 9 includes a business processing unit 901, a transaction receiving module 903, a reproduction module 905, a client side business continuation module 907, a management DB 909, a business processing management table 911, a flag file storage unit 913, and screen data. A storage unit 915 and a transaction data storage unit 917 are included. When the business processing unit 901 receives business processing screen data from the regular system 5 or the standby system 7, the business processing unit 901 stores it in the screen data storage unit 915, displays the business processing screen, and displays the screen data name (HTML (Hyper Text A record including Markup Language) file name), screen data update time, connection ID, and the like is added to the management DB 909. The business processing unit 901 determines whether the current business processing screen is a business start screen. If the business processing unit 901 determines that the current business processing screen is a business start screen, the business processing unit 901 sets a flag indicating that the business is in progress in the flag file storage unit 913. To do. Furthermore, the business processing unit 901 receives input or selection data for the displayed business processing screen from the user, and transmits the input or selection data to the regular system 5 or the standby system 7. When the transaction reception module 903 receives transaction data (update log) from the regular system 5, the transaction reception module 903 stores it in the transaction data storage unit 917 and registers the file name of the transaction data in the record of the management DB 909. When the reproduction module 905 receives a failure notification from the failure detection device 3, the reproduction module 905 determines whether or not the job is in progress based on the flag file storage unit 913. Identify the record. Then, the reproduction module 905 displays a business process screen related to the record to be reproduced, and transmits transaction data related to the record to be reproduced to the standby system 7. The client-side business continuation module 907 performs processing for resuming business processing in cooperation with the server-side business continuation module 711 in the standby system 7. Note that the cache of the client terminal 9 may be used as the screen data storage unit 915.

  FIG. 7 shows an example of data stored in the management DB 909. In the example of FIG. 7, the management DB 909 includes an item number column, a screen data name column for a business process screen, a screen data update time column, a transaction file name column, and a work in progress (status). A column and a connection ID column are included. In the column of item numbers, numbers for identifying records are set, and consecutive numbers are assigned in the order of registration in the management DB 909. In the screen data update time column, the update time of the data of the business process screen is set. A status identified from the business process management table 911 is set in the column of work in progress (status). In the connection ID column, a connection ID between the client terminal 9 and the normal system 5 or the standby system 7 is set.

  FIG. 8 shows an example of data stored in the business process management table 911. In the example of FIG. 8, the business process management table 911 includes an ID column, a screen data name column of the business process screen, a status column corresponding to the business process screen, a previous status column, and a process start. And a column of flags. Note that the data set in each column is determined in advance. In the immediately preceding status column, the status immediately before the transition to the business processing screen is registered, and when one business processing screen has a plurality of statuses, the status is determined based on the previous status. For example, when adding the record of item number n to the management DB 909, first, the business process management table 911 is searched based on the screen data name in the record of item number n. If only one status corresponding to the screen data name is detected from the business process management table 911, that status is set in the record of item number n. On the other hand, when a plurality of statuses corresponding to the screen data name are detected from the business process management table 911, the record of item number n-1 (including the same connection ID as the record of item number n) is selected. ), The status in which the work in progress (status) matches the previous status is specified, and the specified status is set in the record of item number n. In the processing start flag column, 1 is set if the business processing screen is the business start screen, and 0 is set if the business processing screen is not the business start screen.

  Next, processing of the normal system 5, the standby system 7, and the client terminal 9 in the business processing system shown in FIG. 5 will be described with reference to FIGS. First, normal processing will be described with reference to FIGS. 9 and 10. For example, the client terminal 9 receives an input of an access request from the user and transmits the access request to the regular system 5. The Web server 51 of the regular system 5 receives the access request from the client terminal 9, generates screen data (that is, Web page data) corresponding to the access request, and transmits it to the client terminal 9 (FIG. 9: Step S1).

  The business processing unit 901 of the client terminal 9 receives screen data (Web page data) from the regular system 5 (step S3). The business processing unit 901 stores the received screen data in the screen data storage unit 915 and displays it on the display device (step S5). Then, the business processing unit 901 receives an input or selection on the display screen from the user (step S7), generates a telegram including the input or selection data, and transmits it to the regular system 5 (step S9).

  Then, the Web server 51 of the regular system 5 receives a message from the client terminal 9 (step S11). Then, the Web server 51, the AP server 52, and the DB server 53 execute processing corresponding to the message, and the DB server 53 stores the update log (transaction data) of the DB 54 in the storage device in association with the message code. (Step S13).

  Then, the normal system 5 and the standby system 7 cooperate to perform replication processing (steps S15 and S17). As a result, the update log is transmitted from the regular system 5 to the standby system 7, and the database is synchronized between the regular system 5 and the standby system 7. It is assumed that the standby system 7 holds an update log from the regular system 5. The replication process is not different from the conventional process and will not be described further. Thereafter, the processing of the regular system 5 proceeds to step S29 (FIG. 10) via the terminal B.

  On the other hand, after step S9, the business processing unit 901 of the client terminal 9 activates the transaction reception module 903 (step S19). At this time, the business processing unit 901 delivers the screen data name, screen data update time, and connection ID of the current business processing screen to the transaction reception module 903. The processes after step S19 are performed in parallel with the processes of steps S11 to S17 described above.

  Then, after being activated, the transaction receiving module 903 determines whether the current business process screen is a business start screen based on the business process management table 911 (step S21). Specifically, the business process management table 911 is searched based on the screen data name, and when the process start flag corresponding to the screen data name is set to 1, it is determined that it is a business start screen. When it is determined that the current business process screen is the business start screen (step S21: Yes route), the transaction reception module 903 sets a flag indicating that the business is in progress in the flag file storage unit 913 (step S23). . Thereafter, the process proceeds to step S25.

  On the other hand, if the current business process screen is not the business start screen (step S21: No route), the process of step S23 is skipped and the process proceeds to step S25.

  Then, the transaction receiving module 903 adds a record including the item number, screen data name, screen data update time, connection ID, and status to the management DB 909 (step S25). For item numbers, new consecutive numbers are assigned. As for the status, the business process management table 911 is searched based on the screen data name, and the status corresponding to the screen data name is set in the record. As described above, when there are a plurality of corresponding statuses, the status is specified according to the previous status. Thereafter, the processing of the client terminal 9 proceeds to step S27 (FIG. 10) via the terminal A.

  Shifting to the description of FIG. 10, after the terminal A, the transaction receiving module 903 of the client terminal 9 transmits an activation request for the transaction transfer module 531 to the active system 5 and calls the transaction transfer module 531 (FIG. 10: Step S27). For example, the activation request includes the code (ID) of the message transmitted in step S9.

  Then, after the terminal B, the DB server 53 of the regular system 5 receives the activation request for the transaction transfer module 531 from the client terminal 9 and activates the transaction transfer module 531 (step S29). Then, after activation, the transaction transfer module 531 acquires transaction data corresponding to the message code included in the activation request from the storage device, and transmits the transaction data to the client terminal 9 (step S31).

  Then, the transaction reception module 903 of the client terminal 9 receives the transaction data from the regular system 5 and stores it in the transaction data storage unit 917 (step S33). The transaction reception module 903 registers the file name of the received transaction data in the record added to the management DB 909 in step S25 (step S35).

  Then, the transaction receiving module 903 determines whether or not the current business process screen is a predetermined business end screen (for example, a logout screen) (step S37). It is also possible to employ a configuration in which a processing end flag is provided in the business processing management table 911 to manage the business end screen. If it is determined that the current business process screen is the business end screen (step S37: Yes route), the transaction reception module 903 deletes the flag indicating that the business is in progress from the flag file storage unit 913 ( Step S39). Then, the process ends.

  On the other hand, if the current business process screen is not the business end screen (step S37: No route), the process ends without performing the process of step S39 (step S41).

  When transitioning to the next business process screen, the process returns to step S1 and the above-described process is repeated. In this way, transaction data is transmitted from the regular system 5 to the client terminal 9, and the transaction data is accumulated in the client terminal 9.

  Next, processing when a failure occurs will be described with reference to FIGS. 9 and 10 are executed in advance, and the management DB 909 stores data as shown in FIG. Further, it is assumed that the business process management table 911 stores data as shown in FIG. For example, when the failure detection device 3 detects the occurrence of a failure in the normal system 5 (FIG. 11: step S51), the failure detection device 3 transmits a start request for the reproduction module 905 to the client terminal 9 and calls the reproduction module 905 (step S53).

  The client terminal 9 receives the activation request for the reproduction module 905 from the failure detection device 3 and activates the reproduction module 905 (step S55). Then, after the activation, the reproduction module 905 searches the flag file storage unit 913 and determines whether or not a flag indicating that the job is in progress is set (step S57). If the flag indicating that the job is in progress is not set in the flag file storage unit 913 (step S57: No route), it is determined that there is no job currently being worked on, and the process ends.

  On the other hand, when the flag indicating that the job is in progress is set in the flag file storage unit 913 (step S57: Yes route), it is determined that there is a job in the middle of work, and the process proceeds to step S61.

  Then, the reproduction module 905 selects, from the management DB 909, the latest record from among the records whose transaction data file names have been registered (step S61). For example, when data as shown in FIG. 7 is stored in the management DB 909, the record of item number 4 becomes the latest record and is selected as a reproduction target. Then, the reproduction module 905 adds the transaction file name in the selected record to the reproduction list (step S63). The reproduction list is stored in the storage device of the client terminal 9.

  Then, the reproduction module 905 acquires a process start flag corresponding to the screen data name and status in the selected record from the business process management table 911 (step S65). For example, if the screen data name is “uketuke2.html” and the status is “accepting”, the process start flag (0) relating to ID3 in the business process management table 911 (FIG. 8) is acquired.

  Then, the reproduction module 905 determines whether the acquired process start flag is 1 (step S67). When the acquired process start flag is 0 (step S67: No route), the reproduction module 905 selects, from the management DB 909, a record immediately preceding the current record among records having the same connection ID as a reproduction target. (Step S69). For example, when the current record is the record of item number 4, the record of item number 3 having the same connection ID is selected. And it returns to the process of step S63 and repeats the process described above.

  On the other hand, when the acquired process start flag is 1 (step S67: Yes route), the process of the client terminal 9 proceeds to step S71 (FIG. 13) via the terminal C.

  For example, when data as shown in FIG. 7 is stored in the management DB 909, records are selected as reproduction targets in the order of item number 4, item number 3, item number 2, and item number 1. When the record of item number 1 is selected, the processing start flag corresponding to the screen data name “login.htm” and the status “login” (that is, the processing start flag related to ID1 in FIG. 8) is 1. Then, the process proceeds to the process of FIG. When records are selected in the order of item number 4, item number 3, item number 2, and item number 1, data as shown in FIG. 12 is stored in the reproduction list. In FIG. 12, in order from the top, the transaction file name “0000004” related to the record of item number 4, the transaction file name “0000003” related to the record of item number 3, the transaction file name “0000002” related to the record of item number 2, and The transaction file name “0000001” relating to the record of item number 1 is set.

  Moving to the description of FIG. 13, after the terminal C, the reproduction module 905 of the client terminal 9 specifies unprocessed records among the reproduction target records in ascending order of item numbers in the management DB 909 (FIG. 13: Step S71). ). For example, if the records of item number 4, item number 3, item number 2, and item number 1 are the records to be reproduced, in this step, the records are identified in the order of item number 1, item number 2, item number 3, and item number 4. Is done.

  Then, the reproduction module 905 acquires screen data related to the specified record from the screen data storage unit 915 and displays it on the display device (step S73).

  Then, the reproduction module 905 acquires transaction data relating to the identified record from the transaction data storage unit 917 (step S75). Then, the reproduction module 905 mines the transaction data, extracts the input content, and displays the input content on the currently displayed screen (step S77). Mining is not different from conventional processing, and will not be described further.

  Then, the reproduction module 905 transmits an activation request for the transaction comparison module 731 to the standby system 7, and calls the transaction comparison module 731 (step S79).

  The DB server 73 of the standby system 7 receives the activation request for the transaction comparison module 731 from the client terminal 9 and activates the transaction comparison module 731 (step S81).

  Further, the reproduction module 905 transmits the transaction data acquired in step S75 and the reproduction list stored in the storage device to the standby system 7 (step S83). Then, the process of the client terminal 9 proceeds to the process of step S91 (FIG. 14) via the terminal E.

  Then, the transaction comparison module 731 of the standby system 7 receives the transaction data and the reproduction list from the client terminal 9, and temporarily stores them in the storage device (step S85). Then, the process of the standby system 7 proceeds to the process of step S87 (FIG. 14) via the terminal D.

  14, after terminal D, the transaction comparison module 731 of the standby system 7 transmits the transaction data transmitted from the client terminal 9 and the transaction data transmitted from the regular system 5 during normal operation. The transaction comparison process is performed using (Step S87). The transaction comparison process will be described with reference to FIG.

  First, the transaction comparison module 731 mines the transaction data received from the client terminal 9, and stores the mining result in the storage device (FIG. 15: step S111).

  Further, the transaction comparison module 731 mines the transaction data having the same data name held in the standby system, and stores the mining result in the storage device (step S113).

  Then, the transaction comparison module 731 compares the mining results stored in the storage device and determines whether the mining results are the same (step S115). When the mining results are the same (step S115: Yes route), the transaction comparison module 731 determines that the transaction data received from the client terminal 9 is consistent between the client terminal 9 and the standby system 7 (step) S117). Then, this process is terminated and the process returns to the original process.

  On the other hand, when the mining results are different (step S115: No route), the transaction comparison module 731 does not match the transaction data received from the client terminal 9 between the client terminal 9 and the standby system 7 (there is a mismatch). Is determined (step S119). Then, the transaction comparison module 731 identifies transaction data after the transaction determined to be inconsistent from the reproduction list (step S121). As shown in FIG. 12, in the reproduction list, the lowest transaction data is the oldest and the highest transaction data is the latest. Therefore, for example, when data as shown in FIG. 12 is stored in the reproduction list and it is determined that the transaction data “0000003” is inconsistent, in this step, “0000003” and “ “0000004” transaction data is identified.

  Then, the transaction comparison module 731 deletes the identified transaction data from the standby system 7, and performs a rollback process on the DB 74 (step S123). As a result, the contents of the DB 74 are returned to the time point “0000002”. Then, this process is terminated and the process returns to the original process.

  Returning to the description of FIG. 14, after performing the transaction comparison process, the transaction comparison module 731 transmits the processing result (consistent / not consistent) to the client terminal 9 (step S89).

  Then, the reproduction module 905 of the client terminal 9 receives the processing result of the transaction comparison process from the standby system 7, and determines whether the processing result indicates consistency (step S93). When the processing result indicates that there is consistency (step S93: Yes route), the reproduction module 905 determines whether the processing has been completed for all the reproduction target records (step S95). When the process is completed for all the reproduction target records (step S95: Yes route), the process proceeds to step S105.

  On the other hand, if the processing has not been completed for all the reproduction target records (step S95: No route), that is, if the screen to be reproduced still remains, the processing of step S71 (FIG. 13) is performed via the terminal F. Return to and repeat the process described above. In the second and subsequent processes, since the transaction comparison module 731 has already been started, the processes in steps S79 and S81 can be omitted.

  On the other hand, when it is determined in step S93 that the processing result indicates inconsistency (inconsistency) (step S93: No route), the reproduction module 905 notifies the reproduction list that there is inconsistency. Transaction data after the completed transaction is specified (step S97). Note that the processing in this step is the same as the processing in step S121, and the reproduction list to be used is also the same, so that the same transaction data as the transaction data specified in step S121 is specified. Then, the reproduction module 905 deletes the identified transaction data from the transaction data storage unit 917 (step S99).

  In addition, the reproduction module 905 deletes the reproduction target records after the record being processed from the management DB 909 (step S101). For example, when data such as shown in FIG. 7 is stored in the management DB 909 and the current record of item number 3 is being processed, the records of item number 3, item number 4 and item number 5 are managed. Delete from DB909.

  Then, the reproduction module 905 displays a message indicating that the business process has not been completed on the currently displayed screen (step S103). Note that another message may be displayed as long as the user can be informed that the process for the currently displayed screen has not been completed. Thereafter, the process proceeds to step S105.

  If it is determined in step S95 that the processing for all the reproduction target records has not been completed, or after the processing in step S103, the reproduction module 905 waits for recovery (step S105), and a failure occurs. End the process.

  By carrying out the processing as described above, it is possible to reproduce and display the work screen that the user has performed so far, so that the user can easily grasp how far the work has been completed. become.

  Next, processing at the time of system recovery will be described with reference to FIG. It is assumed that the processing at the time of occurrence of the failure described above is executed in advance and the client terminal 9 is in a recovery waiting state. First, when the failure detection device 3 detects completion of switching to the standby system 7, a failure handling notification is transmitted to the client terminal 9 (FIG. 16: step S131).

  Then, the reproduction module 905 of the client terminal 9 receives the failure handling notification from the failure detection apparatus 3 (step S133), and activates the client side business continuation module 907 (step S135).

  Then, the client-side business continuation module 907 obtains the screen data name and connection ID corresponding to the latest transaction data from the transaction data notified of consistency from the management DB 909 after startup (step S137). . Then, the client-side business continuation module 907 transmits an activation request for the server-side business continuation module 711 to the standby system 7 (step S139).

  Then, the Web server 71 of the standby system 7 receives the activation request for the server-side business continuation module 711 from the client terminal 9 and activates the server-side business continuation module 711 (step S141).

  Further, the client-side business continuation module 907 of the client terminal 9 calls the server-side business continuation module 711 and then transmits the screen data name and connection ID acquired in step S137 to the standby system 7 (step S143).

  Then, the server side business continuation module 711 of the standby system 7 receives the screen data name and the connection ID from the client terminal 9, and temporarily stores them in the storage device (step S145). It should be noted that the screen data name and the connection ID can be included in the activation request, and in this case, the processing in steps S143 and S145 can be omitted.

  Then, the server-side business continuation module 711 re-establishes a connection for the received connection ID (step S147). Then, the server-side business continuation module 711 and the client-side business continuation module 907 cooperate to resume business processing (steps S149 and S151), and the recovery processing ends.

  By carrying out the processing as described above, the connection is re-established, and the business processing is resumed between the client terminal 9 and the standby system 7. Therefore, even if the operation is interrupted for the user, It will be possible to resume from.

  Although one embodiment of the present technology has been described above, the present technology is not limited to this. For example, the functional block diagrams of the normal system 5, the standby system 7, and the client terminal 9 described above do not necessarily correspond to the actual program module configuration.

  Further, the data stored in the management DB 909 and the business process management table 911 described above is an example, and the configuration as described above is not necessarily required. Further, in the processing flow, the processing order can be changed if the processing result does not change. Further, it may be executed in parallel. For example, the consistency of transaction data may be confirmed first, and then a business process screen may be displayed.

  The client terminal 9 and the various servers described above are computer devices, and as shown in FIG. 17, a display control unit connected to a memory 2501, a CPU 2503, a hard disk drive (HDD) 2505, and a display device 2509. A bus 2519 is connected to 2507, a drive device 2513 for the removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network. An operating system (OS) and an application program for executing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above, the OS, and necessary application programs.

  The embodiments of the present technology described above are summarized as follows.

  The business operation support method according to the first aspect is configured to connect a normal system and a standby system that holds log data related to database update processing executed in the normal system via a network, and And a management database for storing log data identifiers, and a business operation support method executed by a computer having a storage device. Then, when the business operation support method receives data of a specific business process screen from the active system, the specific business process screen is displayed, and the specific business process screen data is stored in a storage device (see FIG. 18: Step S1001), a step of receiving input or selection data for a specific business process screen from the user and transmitting it to the regular system (FIG. 18: Step S1003), and transmission of input or selection data for the specific business process screen When log data related to database update processing executed in the normal system is received from the normal system, the log data is stored in the storage device, and the identifier of the log data corresponds to the identifier of the specific business process screen Step for storing in the management database (FIG. 18: Steps S1005 and S1007) If the failure of the normal system is detected (FIG. 18: step S1009), the log data stored in the storage device is transmitted to the standby system, and the consistency of the log data is confirmed in the standby system. Step (FIG. 18: step S1011) for executing the processing for the transaction processing screen corresponding to the latest log data among the log data notified that the standby system is confirmed to be consistent or A display step (FIG. 18: step S1013) of acquiring and displaying data of the business process screen next to the business process screen from the storage device.

  In this way, the business process screen corresponding to the latest log data that is consistent or the next business process screen is displayed, so the user can easily grasp where to start work, Work can be resumed from the middle.

  In addition, the display step described above may include a step of displaying each business process screen from the business process screen at the start of the business process to the next business process screen corresponding to the latest log data. Good. In this way, a series of work contents that have already been completed can be easily confirmed.

  In addition, when receiving a notification that there is inconsistency in log data from the standby system, this business operation support method displays a business processing screen corresponding to the log data that has been notified of inconsistency, An inconsistency display step for displaying a message indicating that the business process on the business process screen is not completed may be further included. In this way, when the log is inconsistent, the business process screen in which a problem has occurred is displayed, so that the user can easily grasp the work to be resumed.

  Further, the inconsistency display step described above deletes log data notified of inconsistency and log data received after the log data from the storage device, and corresponds to the identifier of the deleted log data. A step of deleting the business process screen identifier from the management database may be included. In this way, the contents of the storage device and the management database can be rolled back to the point where consistency is achieved.

  Furthermore, the management database described above may further store an identifier of the connection between the normal system and the computer. Then, after the display step, this business operation support method transmits the business process screen identifier corresponding to the latest log data and the corresponding connection identifier to the standby system, and establishes a connection with the standby system. It may further include a step of reestablishing and causing the standby system to resume business processing. In this way, the connection with the standby system is re-established, and the work can be continued.

  When the computer according to the second aspect receives data of a specific business process screen from the regular system, the computer displays the specific business process screen and stores the data of the specific business process screen (FIG. 19: Storage Device) 1911) and screen data receiving means (FIG. 19: screen data receiving section 1901) and input data transmitting means for receiving input or selection data for a specific business processing screen from the user and transmitting it to the regular system (FIG. 19: When the log data related to the database update processing executed in the normal system is received from the normal system in response to the input data transmission unit 1903) and the input to the specific business process screen or transmission of the selected data, the log data is stored. The management database stores the log data identifier in association with the identifier of the specific business process screen. (FIG. 19: log data receiving means (FIG. 19: log data receiving unit 1905) to be stored in the management DB 1913) and a standby for holding an update log of the database in the active system when a failure occurs in the active system Log data transmission means (FIG. 19: log data transmission unit 1907) for transmitting the log data stored in the storage device to the host system and causing the standby system to perform processing for checking the consistency of the log data; From the storage device, the data on the business process screen corresponding to the latest log data or the next business process screen of the business process screen among the log data that has been confirmed to be consistent by the standby system is stored from the storage device. Screen re-displaying means (FIG. 19: screen re-display unit 1909) for acquiring and displaying.

  The business processing system according to the third aspect includes a normal system, a standby system that holds log data related to database update processing executed in the normal system, an identifier of a business processing screen, and an identifier of log data. A client computer having a management database and a storage device; When the above-mentioned regular system receives the data for the specific business process screen to the client computer and the input or selection data for the specific business process screen from the client computer, the database update process And means for transmitting log data relating to the database update processing to the client computer. In addition, when the standby system described above receives log data from the client computer, it checks the consistency by comparing the received log data with the log data held by the standby system itself, and the confirmation result Is transmitted to the client computer. Further, when the client computer described above receives data on a specific business process screen from the regular system, the client computer displays the specific business process screen and stores the specific business process screen data in the storage device. And means for receiving input or selection data for a specific business process screen from the user and sending it to the regular system, and after receiving input or selection data for a specific business process screen and receiving log data from the regular system Storing the log data in the storage device, storing the identifier of the log data in the management database in association with the identifier of the specific business process screen, and detecting the occurrence of a failure in the normal system, It must be consistent with the means to send the stored log data to the standby system and the standby system. And means for acquiring and displaying the data of the next business processing window of the most recent work processing screen corresponding to the log data or the business processing screen from the storage unit of the notification log data that has been certified.

  It is possible to create a program for causing the client terminal 9 and various servers to perform the processes described above, such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk. Or the like stored in a computer-readable storage medium or storage device. In addition, data in the middle of processing is temporarily stored in a storage device such as a computer memory.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1)
A management database that is connected via a network to a normal system and a standby system that holds log data related to database update processing executed in the normal system, and stores an identifier of a business process screen and an identifier of the log data And a business operation support method executed by a computer having a storage device,
When receiving data of a specific business process screen from the regular system, displaying the specific business process screen, and storing the data of the specific business process screen in the storage device;
Receiving input or selection data for the specific business process screen from a user, and transmitting to the regular system;
When log data related to database update processing executed in the normal system in response to input to the specific business process screen or transmission of selection data is received from the normal system, the log data is stored in the storage device. Storing the identifier of the log data in the management database in association with the identifier of the specific business process screen;
When a failure occurrence of the normal system is detected, the log data stored in the storage device is transmitted to the standby system, and processing for confirming the consistency of the log data to the standby system is performed. Steps to be implemented;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system A display step of acquiring and displaying from a storage device;
Business operation support method executed by a computer.

(Appendix 2)
The displaying step comprises:
The business operation support method according to claim 1, further comprising a step of displaying the business process screen corresponding to the latest log data or each business process screen up to the next business process screen in order from the business process screen at the start of the business process. .

(Appendix 3)
When receiving a notification that the log data is inconsistent from the standby system, the business processing screen corresponding to the log data notified that there is a mismatch is displayed, and The business operation support method according to appendix 1 or 2, further including an inconsistency display step for displaying a message indicating that the business process is not completed.

(Appendix 4)
The inconsistency display step includes
The log data notified that there is an inconsistency and the log data received after the log data are deleted from the storage device, and the identifier of the deleted log data and the identifier of the corresponding business process screen are The business operation support method according to supplementary note 3, including a step of deleting from the management database.

(Appendix 5)
The management database further stores an identifier of a connection between the regular system and the computer;
After the displaying step, the identifier of the business process screen corresponding to the latest log data and the identifier of the corresponding connection are transmitted to the standby system, and the connection is reestablished with the standby system. The business operation support method according to any one of supplementary notes 1 to 4, further comprising: a step of causing the standby system to resume business processing.

(Appendix 6)
Screen data receiving means for displaying the specific business process screen when storing data of the specific business process screen from the regular system, and storing the specific business process screen data in a storage device;
Input data transmission means for receiving input or selection data for the specific business process screen from the user and transmitting it to the regular system;
When log data related to database update processing executed in the normal system in response to input to the specific business process screen or transmission of selection data is received from the normal system, the log data is stored in the storage device. Log data receiving means for storing the identifier of the log data in the management database in association with the identifier of the specific business process screen;
When the occurrence of a failure in the normal system is detected, the log data stored in the storage device is transmitted to a standby system that holds a database update log in the normal system, and the standby system is Log data transmission means for performing processing for checking the consistency of log data;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system Screen redisplay means for acquiring and displaying from a storage device;
Having a computer.

(Appendix 7)
A management database that is connected via a network to a normal system and a standby system that holds log data related to database update processing executed in the normal system, and stores an identifier of a business process screen and an identifier of the log data And a program for causing a computer having a storage device to execute processing,
When receiving data of a specific business process screen from the regular system, displaying the specific business process screen, and storing the data of the specific business process screen in the storage device;
Receiving input or selection data for the specific business process screen from a user, and transmitting to the regular system;
When log data related to database update processing executed in the normal system in response to input to the specific business process screen or transmission of selection data is received from the normal system, the log data is stored in the storage device. Storing the identifier of the log data in the management database in association with the identifier of the specific business process screen;
When a failure occurrence of the normal system is detected, the log data stored in the storage device is transmitted to the standby system, and processing for confirming the consistency of the log data to the standby system is performed. Steps to be implemented;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system Obtaining and displaying from a storage device;
Business operation support program for causing a computer to execute

(Appendix 8)
A regular system,
A standby system that retains log data related to the database update process executed in the regular system;
A client computer having a management database and a storage device for storing an identifier of a business process screen and an identifier of the log data;
Have
The regular system is
Means for transmitting data of a specific business processing screen to the client computer;
Means for executing database update processing when receiving input or selection data for the specific business process screen from the client computer, and transmitting log data relating to the database update processing to the client computer;
Have
The standby system is:
When the log data is received from the client computer, consistency is confirmed by comparing the received log data with the log data held by the standby system itself, and the confirmation result is sent to the client computer. Means to transmit,
The client computer is
Means for displaying the specific business process screen when the specific business process screen data is received from the regular system, and storing the specific business process screen data in the storage device;
Means for receiving input or selection data for the specific business processing screen from a user and transmitting it to the regular system;
When the log data is received from the regular system after the input to the specific business process screen or the selection data is transmitted, the log data is stored in the storage device, and the identifier of the log data is stored in the specific business process screen. Means for storing in the management database in association with the identifier of the screen;
Means for transmitting the log data stored in the storage device to the standby system when a failure occurrence of the normal system is detected;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system Means for obtaining and displaying from a storage device;
Business processing system having.

DESCRIPTION OF SYMBOLS 1 Network 3 Failure detection apparatus 5 Regular system 7 Standby system 9 Client terminal 50, 70 Network apparatus 51, 71 Web server 52, 72 AP server 53, 73 DB server 54, 74 DB
531 Transaction transfer module 711 Server side business continuation module 731 Transaction comparison module 901 Business processing unit 903 Transaction reception module 905 Reproduction module 907 Client side business continuation module 909 Management DB
911 Business process management table 913 Flag file storage unit 915 Screen data storage unit 917 Transaction data storage unit

Claims (6)

A management database that is connected via a network to a normal system and a standby system that holds log data related to database update processing executed in the normal system, and stores an identifier of a business process screen and an identifier of the log data And a business operation support method executed by a computer having a storage device,
When receiving data of a specific business process screen from the regular system, displaying the specific business process screen, and storing the data of the specific business process screen in the storage device;
Receiving input or selection data for the specific business process screen from a user, and transmitting to the regular system;
When log data related to database update processing executed in the normal system in response to input to the specific business process screen or transmission of selection data is received from the normal system, the log data is stored in the storage device. Storing the identifier of the log data in the management database in association with the identifier of the specific business process screen;
When a failure occurrence of the normal system is detected, the log data stored in the storage device is transmitted to the standby system, and processing for confirming the consistency of the log data to the standby system is performed. Steps to be implemented;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system A display step of acquiring and displaying from a storage device;
Business operation support method executed by a computer. The displaying step comprises:
The business operation support according to claim 1, further comprising: displaying each of the business process screens up to the next business process screen corresponding to the latest log data in order from the business process screen at the start of the business process. Method. When receiving a notification that the log data is inconsistent from the standby system, the business processing screen corresponding to the log data notified that there is a mismatch is displayed, and The business operation support method according to claim 1, further comprising: an inconsistency display step for displaying a message indicating that the business processing is not completed. The inconsistency display step includes
The log data notified that there is an inconsistency and the log data received after the log data are deleted from the storage device, and the identifier of the deleted log data and the identifier of the corresponding business process screen are The business operation support method according to claim 3, further comprising a step of deleting from the management database. Screen data receiving means for displaying the specific business process screen when storing data of the specific business process screen from the regular system, and storing the specific business process screen data in a storage device;
Input data transmission means for receiving input or selection data for the specific business process screen from the user and transmitting it to the regular system;
When log data related to database update processing executed in the normal system in response to input to the specific business process screen or transmission of selection data is received from the normal system, the log data is stored in the storage device. Log data receiving means for storing the identifier of the log data in the management database in association with the identifier of the specific business process screen;
When the occurrence of a failure in the normal system is detected, the log data stored in the storage device is transmitted to a standby system that holds a database update log in the normal system, and the standby system is Log data transmission means for performing processing for checking the consistency of log data;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system Screen redisplay means for acquiring and displaying from a storage device;
Having a computer. A regular system,
A standby system that retains log data related to the database update process executed in the regular system;
A client computer having a management database and a storage device for storing an identifier of a business process screen and an identifier of the log data;
Have
The regular system is
Means for transmitting data of a specific business processing screen to the client computer;
Means for executing database update processing when receiving input or selection data for the specific business process screen from the client computer, and transmitting log data relating to the database update processing to the client computer;
Have
The standby system is:
When the log data is received from the client computer, consistency is confirmed by comparing the received log data with the log data held by the standby system itself, and the confirmation result is sent to the client computer. Means to transmit,
The client computer is
Means for displaying the specific business process screen when the specific business process screen data is received from the regular system, and storing the specific business process screen data in the storage device;
Means for receiving input or selection data for the specific business processing screen from a user and transmitting it to the regular system;
When the log data is received from the regular system after the input to the specific business process screen or the selection data is transmitted, the log data is stored in the storage device, and the identifier of the log data is stored in the specific business process screen. Means for storing in the management database in association with the identifier of the screen;
Means for transmitting the log data stored in the storage device to the standby system when a failure occurrence of the normal system is detected;
Data of the business processing screen corresponding to the latest log data or the business processing screen next to the business processing screen among the log data notified that the consistency is confirmed by the standby system Means for obtaining and displaying from a storage device;
Business processing system having.

Images