JP2006330791A - Client server system, computer, program, and log information management method for client server system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a client server system or the like, capable of managing log information that is a client's operation history even in a stand-alone mode in which the client is operated in a separated state from a server. <P>SOLUTION: The client server system 10 comprises the server 40, and one or more clients 20 operable in a separated state from the server 40. Each client 20 writes log information that is its own operation history to a local log file 33 within each client 20, and transmits it when connected to the server 40. The server 40 writes the log information transferred from each client 20 in a server log file 53, and centrally manages log information of all the clients 20. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a client server system, a computer, a program, and a log information management method for a client server system, each including a server and one or more clients operable in a state of being disconnected from the server.

For an administrator who manages a network system, it is very important to manage information related to an operation history (hereinafter referred to as “log information”) indicating when and how much a user has accessed. In particular, in a large-scale client server system composed of a server and a large number of clients, unified access log management in the server is essential. For example, Patent Document 1 describes a method of managing access logs of both a server and a client by deploying a management device for managing log information between the server and the client. As described above, conventionally, log information in the client server system is managed on the premise that the server and the client are connected.
JP 2005-55992 A

  By the way, in a client server system, like a financial accounting system used between an accounting firm and its advisors, data is taken out from the accounting firm's network environment using a laptop computer, and slips are received at the advisor. There is a configuration that enables so-called mobile input, such as input. The client used in this type of system has two operation modes: a client mode that operates while connected to the server, and a stand-alone mode that operates while disconnected from the server, and performs mobile input. If (if you leave the network environment), operate in standalone mode. However, log information management in the conventional client-server system is based on the premise that the server and the client are connected as described above, and thus cannot support the stand-alone mode.

  In view of such a problem, the present invention is a log that is an operation history of a client not only in a client mode that operates while connected to a server, but also in a stand-alone mode that operates while disconnected from the server. An object is to provide a client server system capable of managing information, a computer, a program, and a log information management method for the client server system.

  The client-server system of the present invention includes a server, one or more clients having two operation modes: a client mode that operates while connected to the server, and a stand-alone mode that operates while disconnected from the server; A client-side system comprising: a client-side storage area for storing log information as an operation history; at least in a stand-alone mode; client-side writing means for writing log information to the client-side storage area; and client mode Transfer means for transferring log information written in the client-side storage area to the server, wherein the server transfers from the client a server-side storage area that collectively stores the log information of one or more clients. B Information, characterized in that it and a server-side writing means for writing the server-side storage area.

  The log information management method of the client server system of the present invention is a log information management method of a client server system comprising a server and one or more clients operable in a state separated from the server, A step in which a client writes log information, which is an operation history of each client, to a storage area in each client, and a step in which log information written in a storage area in each client is transferred to the server while being connected to the server. , Is executed.

  According to these configurations, the log information that is the operation history of each client is written in the client-side storage area (storage area in each client), so that the client is disconnected from the server during stand-alone mode operation. However, log information that is a client operation history can be stored. Further, since the log information written in the client side storage area of each client is transferred to the server, the log information of one or more clients connected to the server can be centrally managed on the server side. Therefore, regardless of the operation mode of the client, all log information can be efficiently managed on the server side.

  The client-side storage area is preferably initialized after the log information is transferred by the transfer means. According to this configuration, it is possible to prevent a shortage of write capacity in the client-side storage area.

  In this case, the client side writing means preferably writes the log information to the client side storage area even in the client mode.

  According to this configuration, the log information can be written by common processing regardless of the operation mode, so that the control configuration can be simplified.

  In this case, it is preferable that the transfer unit transfers the log information to the server at least when the system ends in the client mode and when the operation mode is switched from the client mode to the stand-alone mode.

  According to this configuration, log information can be reliably transferred from the client-side storage area to the server-side storage area. Note that “when the operation mode is switched” indicates when the client mode ends.

  In this case, during the operation in the client mode, the transfer means is one or more or all of the following: when the client system starts, when the application starts, when the application ends, when the file starts, when the file ends Also in terms of timing, log information is preferably transferred to the server.

  According to this configuration, it is possible to prevent a shortage of writing capacity in the client-side storage area, and it is possible to reduce the transfer amount of log information in one transfer and reduce the transfer load. Also, by increasing the timing of transfer by the transfer means, the server can quickly acquire and manage log information.

  In these cases, the server displays search means for searching log information stored in the server-side storage area, display means for displaying a search result by the search means, and a list of log information written in the server-side storage area. And are preferably further provided.

  According to this configuration, it is possible to search and display log information, which can be used to enhance access checks and information security.

  In these cases, it is preferable that the server further includes log management setting means for setting whether or not to function the client side writing means, the transfer means, and the server side writing means.

  According to this configuration, whether to manage log information can be set according to the needs of the user of the client server system.

  The computer of the present invention is used as a client or a server in the client-server system described in any one of the above items.

  By realizing a client-server system using this computer, not only in client mode that operates while connected to the server, but also in stand-alone mode that operates while disconnected from the server, Some log information can be managed.

  A program according to the present invention is a program for causing a computer to function as each means of a client or a server in the client server system described in any one of the above items.

  By executing this program, it is possible to manage log information that is client operation history not only in the client mode that operates while connected to the server, but also in the stand-alone mode that operates while disconnected from the server. A simple client-server system can be realized.

  Hereinafter, a client server system, a computer, a program, and a log information management method for a client server system according to an embodiment of the present invention will be described with reference to the accompanying drawings. The present invention writes log information, which is an operation history of a client, to a storage area in the client and transfers it to the server, so that log information in a state where the client is not connected to the server (standalone state) is also stored on the server side. It is related to the client server system that can be managed centrally. Therefore, a case where the present invention is applied to a financial accounting system used in an accounting office will be described as an example.

  FIG. 1 is a system configuration diagram of a financial accounting system (client server system) 10 according to an embodiment of the present invention. As shown in the figure, the financial accounting system 10 is composed of one or more clients 20 (only two are shown) and a server 40 that performs overall management thereof.

  One or more applications 51 for constructing the financial accounting system 10 are installed in the server 40, and each client 20 is linked to one or more or all of the one or more applications 51 included in the server 40. Then, an application 31 that can be used is installed. For example, an application for inputting journal data is installed in the client 20, and journal data is input using the application. On the other hand, the main accounting software of the financial accounting system 10 is installed in the server 40, and the journal data input to the client 20 is taken in to create various application forms and perform accounting processing. The server 40 can centrally manage operation history information (hereinafter referred to as “log information”) on all the applications 31 and 51 installed in the server 40 and the client 20.

  On the other hand, each client 20 has two operation modes: a client mode that operates while being connected to the server 40, and a stand-alone mode that operates while being disconnected from the server 40. The mode at the end of the previous start is set. However, even when the process is terminated in the state set in the client mode last time, when the server 40 is not connected at the time of activation, the mode is automatically switched to the stand-alone mode.

  Here, the control configuration of the server 40 and the client 20 will be described. As shown in the figure, the server 40 includes an input device 41 such as a keyboard and a mouse, a display 42 that displays input data and processing results, an operation instruction to the user, and a hard disk 43 (hereinafter referred to as “HD”). ), A media drive 44 for reading / writing various recording media such as a CD-ROM, and a communication interface 45 for transmitting / receiving data via a network 60 such as a LAN or an intranet, which are connected to an input / output interface 46, respectively. ing.

  The HD 43 stores various applications 51 such as financial accounting software, and company data 52 generated for each consultant of the accounting office using these applications 51, and log information transferred from each client 20 Has a server log file 53 (server-side storage area). The log information stored in the server log file 53 can be browsed, searched, edited, and output (see FIGS. 4 to 7), and is used for access check and information security enhancement. In addition to these, the HD 43 incorporates an operating system as basic software and drivers for controlling various devices (both not shown).

  The server 40 further includes a CPU (Central Processing Unit) 48, a ROM (Read Only Memory) 49, and a RAM (Random Access Memory) 50, which are connected to an input / output interface 46 via an internal bus 47. The ROM 49 stores a control program for controlling various processes such as a process for managing log information by the CPU 48 and also stores various control data.

  Further, the RAM 50 has a log management flag 56 indicating setting contents (setting contents on the access log setting screen D1, see FIG. 3) as to whether or not to manage log information, and is used as a work area for control processing. The work area (not shown) is always backed up so as to retain the stored data even when the power is turned off. The log management flag 56 is set to “1” when log information is managed, “0” when not managing log information, and is set to manage log information in the following description (“1”). ).

  The input / output interface 46 incorporates a logic circuit that complements the functions of the CPU 48 and handles interface signals with various peripheral circuits. The data and control signals output from the CPU 48 to the internal bus 47 are output as they are or after being processed in conjunction with the CPU 48. With the above configuration, the CPU 48 inputs various signals / data from each unit in the server 40 via the input / output interface 46 in accordance with the control program in the ROM 49, and in the RAM 50 based on the various signals / data input. These various data are processed and various signals and data are output to each part in the server 40 via the input / output interface 46, thereby controlling various processes such as a log information management process.

  On the other hand, the components of the client 20 (20a, 20b) are almost the same as those of the server 40, and the input device 21, display 22, HD 23, media drive 24, communication interface 25, input / output interface 26, internal bus 27, CPU 28, A ROM 29 and a RAM 30 are provided. The media drive 24 and the communication interface 25 are used to provide the journal data input to the client 20 to the server 40, and the server 40 can also import the journal data via the media drive 44 and the communication interface 45. It has become.

  In both clients 20a and 20b, the log management flag 36 in the RAM 30 is set to manage log information in accordance with the log management flag 56 of the server 40 ("1"). However, as shown in the figure, since the client A 20a is not connected to the network 60 and operates in the stand-alone mode, the operation mode flag 37 in the RAM 30 becomes “0” indicating the stand-alone mode. Yes. Further, since the client B 20b is connected to the network 60 and is set in the client mode, the operation mode flag 37 in the RAM 30 is “1” indicating the client mode.

  Each client 20a, 20b has various applications 31 such as journal data input software and company data 32 read from the HD 43 of the server 40 when the client mode is changed (the company data is edited by the client 20). In this case, the edited data) is stored, and a local log file 33 (client side storage area) for storing log information of each client 20 is included. The log information in the local log file 33 is read when the system is terminated in the client mode or when the operation mode is switched from the client mode to the stand-alone mode, and is sent to the server 40 via the communication interface 25, the network 60, and the communication interface 45. Transferred. The local log file 33 is initialized after the log information is transferred.

  Next, the functional configuration of the financial accounting system 10 will be described with reference to FIG. As shown in the figure, the client 20 includes a client side writing unit 210 that writes log information in accordance with an operation of the client 20, a local log file 33 into which log information is written by the client side writing unit 210, and a local log. And transfer means 220 that reads log information stored in the file 33 and transfers the log information to the server 40.

  Client side writing means 210 is login / logout to application 31, new creation / selection / deletion of journal data and company data, form printing, individual backup / restore, EXCEL, CSV format and other general-purpose file output, communication, operation mode transition In accordance with an operation such as (mobile migration), log information is written to the local log file 33 by real-time processing.

  The transfer means 220 stores the log information in the server 40 when the system is terminated in the client mode, when the operation mode is switched from the client mode to the stand-alone mode, when the application 31 is terminated, and when the file is terminated. Forward to. In the present embodiment, “end of file” means, for example, switching of company data (use data), and after entering the journal data of XX company, When the input is started, log information is written at the end of the entry of the journal data of XX company (see S03 in FIG. 8 and S15 in FIG. 9).

  On the other hand, the server 40 is stored in the server side writing means 410 for writing the log information transferred from the client 20, the server log file 53 in which the log information is written by the server side writing means 410, and the server log file 53. A search means 420 for searching for log information, a display means 430 for displaying a search result of the search means 420 and a list of log information stored in the server log file 53 on the display 42, and whether to manage the log information Log management setting means 440 for setting whether or not.

The server side writing unit 410 writes to the server log file 53 every time the log information is transferred by the transfer unit 220. However, if the number of logs registered in the server log file 53 exceeds a predetermined number (for example, 30,000),
A message to that effect is displayed on the display 42, and the user executes export in accordance with the message (see “Export” button 77, FIG. 4).

  The search means 420 searches the log information using various information (date and time when the log information was written in the local log file 33, information for identifying the client 20, etc.) as an index, and the search shown in FIG. A search process is executed by inputting a search condition on the screen D4.

  In addition to the above search screen D4, the display means 430 includes an access log setting screen D1 shown in FIG. 3, an access log display screen D2 shown in FIGS. 4 and 5, and an access log list display screen D3 (print preview screen) shown in FIG. ) Is displayed on the display 42. Details of each screen will be described later.

  The log management setting unit 440 sets whether or not to manage the access log as the entire financial accounting system 10 on the access log setting screen D1. Therefore, if the access log is set to be acquired, the information (the state of the log management setting flag 56 (see FIG. 1)) is used when each client 20 is connected to the server 40 (at the time of shifting to the client mode). And the log management setting flag 36 (see FIG. 1) in each client 20 is set to “1” (access log is acquired). Whether or not to acquire an access log can be set for each client 20, and log information can be managed only for the operation history of the client 20 set to “acquire access log”. good.

  Next, the details of each screen (D1 to D4) displayed on the display 42 of the server 40 will be described with reference to the screen display examples of FIGS. 3 shows an access log setting screen D1, FIGS. 4 and 5 show an access log display screen D2, FIG. 6 shows an access log list display screen D3, and FIG. 7 shows a screen display example of the search screen D4. .

  First, the access log setting screen D1 will be described with reference to FIG. As shown in the figure, on the access log setting screen D1, by selecting the radio button 71, either “Acquire access log” or “Do not acquire access log” can be selected. Based on the selection result, the CPU 48 (see FIG. 1) determines the value of the log management setting flag 56 in the RAM 50.

  Next, the access log display screen D2 will be described with reference to FIGS. FIG. 5 shows a display when the scroll bar 72 shown in the lower part of FIG. 4 is moved to the right side. As shown in both figures, on the access log display screen D2, the log information currently stored in the server log file 53 (see FIG. 1) is listed in the record display field 90. The log information includes “date and time (date and time written in the local log file 33)”, “access log classification”, “user name”, “name”, “computer name”, “application name”, The “version” of the application 31, “company code”, “company name”, “year-end date”, “declaration category etc.”, and “processing” set for each company are displayed.

  The “access log category” indicates the type of log classified in advance, and displays login, logout, data selection, data creation, setting, and the like. “End date” indicates the end date of the year of the accounting period. If the settlement is specially set such as interim settlement or less than one year in the first term, the end date is indicated. indicate. In addition, the “declaration classification, etc.” is classified and displayed as final return, scheduled return, intermediate return, etc. However, “End of Month” and “Declaration Category” are not displayed when an operation that does not apply is performed. “Processing” displays detailed processing contents other than the contents described in “Access log classification”, and is subject to processing such as input of printed form name, company data, and journal data. Displays the name of the corporation when the corporation is selected / changed / registered and the specific processing content.

  The content displayed in the record display field 90 can be appropriately edited (corrected / deleted / added) using the input device 41 of the server 40. The client 20 may be configured so that the server log file 53 can be referred to and the log information can be edited. In this case, however, it is preferable to set access rights for each client 20 and take measures to prevent information leakage.

  On the other hand, in the access log display screen D2, a “print” button 73, “file output” button 74, “screen split” button 75, “history selection” button 76, “export” button 77, “search” are displayed at the top of the screen. ”Button 78, a down menu 79 for selecting the order, a radio button 80 for designating the order as either ascending or descending, and the like, and various processes are executed by pressing these buttons. For example, when the “print” button 73 is pressed by operating the input device 41, the print preview screen (access log list display screen D3) shown in FIG. 6 is displayed, and the “print” button 93 on the screen D3 is pressed. , Print out.

  When the “file output” button 74 is pressed, a file output screen (not shown) for inputting a file name of an output file and selecting an output format (clipboard, CSV, EXCEL, SYLK, etc.) is displayed. Display the file and output the file according to the input contents on the screen.

  When the “divide screen” button 75 is pressed, the screen is divided into two using the position of the scroll bar 72 at the bottom of the screen as a base point. This makes it possible to display the log information in an easy-to-read manner, for example, by displaying the information of each field shown in FIG. 5 while leaving the “date and time” field in the record display field 90.

  When the “history selection” button 76 is pressed, a list (not shown) of log information files exported in the past (files exported by pressing an “export” button 77 described later, etc.) is displayed. It is possible to select and view and output a file required by the user. When the “Export” button 77 is pressed, an export screen (not shown) for inputting the storage location of the log information file currently displayed in the record display field 90 is displayed, and the input storage location is displayed. Save the file. By this export processing, the server log file 53 is initialized and all log information displayed in the record display field 90 is deleted.

  When the “Search” button 78 is pressed, the search screen D4 shown in FIG. 7 is displayed, and the log information currently displayed in the record display column 90 is searched according to the search conditions input on the screen D4. It can be performed. Note that the log information can be searched using the same screen D4 for the log information file displayed by pressing the “history selection” button 76.

  Further, in the down menu 79 for selecting the order of order, each field name is displayed as an option, and the result of sorting based on the item is displayed in the record display column 90. The radio button 80 can select whether the order of ascending or descending order. In this case, as shown in the figure, because “Normal Order: None” and “Descending Order” are set, the information of the field “Date” is displayed in descending order (new one is displayed on top) is doing).

  Next, the access log list display screen D3 will be described with reference to FIG. The screen D3 is a print preview screen for outputting the access log display screen D2 shown in FIGS. 4 and 5 as described above. The access log list 92 includes “date and time”, “access log classification”, “user name”, “name”, “computer name”, “application name”, “version”, “company” for each record of log information. Display each information of “Code”, “Company Name”, “End Date”, “Declaration Class etc.”, “Process”. The information displayed on the access log list 92 (information to be printed) can be appropriately changed (can be customized) according to the needs of the accounting firm.

  In the upper part of the screen, a “print” button 93 for printing out the access log list 92 and a “display position change” for changing the display position of the access log list 92 (for scroll display). Buttons 94 (“first”, “previous”, “next”, “final”) are provided.

  Next, the search screen D4 will be described with reference to FIG. The screen D4 is for searching the log information displayed in the record display field 90 of the access log display screen D2 shown in FIGS. 4 and 5 as described above, and includes “date”, “time”, “ “Access log category”, “User name”, “Name”, “Computer name”, “Application name”, “Version”, “Company code”, “Company name”, “End date”, “Declaration category, etc.” The search can be performed using any one or more of “processing” or all information as an index. The user designates information to be designated as a search condition by using the check box 95, and subsequently inputs the search condition. For example, in the case of the illustrated example, a record that includes “A” in “User Name”, “aaaa” in “Name”, and “Financial Accounting 2005” in “Application Name” is the search result. Will be displayed.

  In the down menu 96 on the right side of the screen, the information input as the search condition is “included”, “not included”, “equal”, “not equal”, “starts with”, “does not start with”. , “Ends with”, “does not end with”, etc. can be selected. In addition, in the case of “term end date”, “˜before” and “˜after” can also be selected.

  When the check box 97 at the bottom of the screen is designated, a print preview screen for displaying the search screen D4 and outputting the search result before the access log list display screen D3 shown in FIG. 6 is displayed. Can be displayed.

  Next, log information management processing (hereinafter referred to as “log management processing”) in the client 20 will be described with reference to the flowcharts of FIGS. 8 and 9. FIG. 8 shows processing when the client 20 is set to a stand-alone mode that operates in a state where it is disconnected from the server 40, and FIG. 9 shows a client mode that operates when the client 20 is connected to the server 40. The process when it is set is shown.

  As shown in FIG. 8, when the process is started by starting the application or changing the operation mode in addition to the system startup by turning on the client 20, it is first determined whether or not the access log acquisition function is in the “ON” state. (S01). That is, in this step, it is determined whether or not the log management flag 36 (see FIG. 1) in the RAM 30 of the client 20 is “1”. If it is “0” (S01: No), log management is performed. The process ends.

  On the other hand, if it is “1” (S01: Yes), the log information is written to the local log file 33 in accordance with the operation of the client 20 (S02). The log information is written in real time every time an operation targeted for “access log classification” (see FIG. 4) is performed. In the stand-alone mode, even when the usage data is switched (when the end of the file is instructed, such as company data) (S03: Yes), the log information cannot be transferred to the server 40, so the local data is not changed. Writing of log information to the log file 33 is continued (in the client mode, transfer processing to the server 40 is performed, see S16 in FIG. 9). In addition to the system termination operation, when an application termination operation or an operation mode change operation is performed, the log management process is terminated (S04: Yes).

  Next, processing when the client mode is set will be described. As shown in FIG. 9, when the system is started, it is determined whether or not the access log acquisition function is in the “ON” state (S11). If it is in the “ON” state (S11: Yes), the local log file If log information remains in the log 33, the log information is transferred from the local log file 33 to the server log file 53 (S12). Here, for example, when the log information could not be written to the server log file 53 due to forcible termination or the like at the time of the previous startup, or the log management process is executed when the client mode is changed to the current client mode when operating in the previous stand-alone mode Log information is transferred. When the transfer is completed, the local log file 33 is initialized (S13). Note that the system activation log information is written in the subsequent step (S14).

  Subsequently, as in the stand-alone mode operation, the log information is written to the local log file 33 in accordance with the operation of the client 20 (S14), and the use data is switched (S15: Yes using the end of the use file as a trigger). The log information is transferred from the local log file 33 to the server log file 53 (S16). Further, after the log information is transferred, the local log file 33 is initialized (S17), and writing of the log information to the local log file 33 is continued (S14).

  On the other hand, when the system termination operation is performed (S18: Yes also when the application termination operation or switching operation from the client mode to the stand-alone mode is performed), the log information is transferred from the local log file 33 to the server log file 53. (S19), the local log file 33 is initialized (S20), and the log management process is terminated.

  As described above, according to the present embodiment, the log information that is the operation history of each client 20 is written to the local log file 33 in the client 20, so that the client 20 is disconnected from the server 40. Log information can be stored even during mode operation. Further, since the log information written in the local log file 33 of each client 20 is transferred to the server 40 and written in the server log file 53 in the server 40, the logs of all the clients 20 connected to the server 40 are recorded. Information can be centrally managed on the server 40 side.

  Also, the log information at the time of system start-up of the client 20 is also once written in the local log file 33 (S14 in FIG. 9) when the log information does not remain in the local log file (not corresponding to S12 in FIG. 9). ), Since it is transferred to the server 40 (see S16 and S19 in FIG. 9), the load of network access can be reduced even when a plurality of clients 20 are activated simultaneously. Note that the log information at the time of system startup of the client 20 can be transferred at the time of S12 in FIG.

  In addition, the client 20 performs log information in a common process (a process of writing log information generated by an operation in the local log file 33 in real time, see S02 in FIG. 8 and S14 in FIG. 9) regardless of the operation mode. Therefore, the control configuration can be simplified.

  Further, at least when the system of the client 20 is terminated, when the application is terminated, and when the client mode is switched to the stand-alone mode, log information is transferred to the server 40 (see S19 in FIG. 9). Log information can be reliably transferred to the file 53. In addition, since the log information is transferred to the server 40 when the system of the client 20 is started or when the usage data is switched (see S12 and S16 in FIG. 9), the local log file 33 is prevented from having insufficient capacity. In addition, the transfer amount of log information per transfer can be reduced, and the load of transfer can be reduced. Further, on the server 40 side, log information can be acquired and managed quickly.

  Further, since it is possible to display a list of log information in the server log file 53, search log information, and display the search results (see FIGS. 4 to 7), it is useful for strengthening access checks and information security. Can do.

  Further, since it is possible to set whether or not to manage log information (see FIG. 3), it is possible to construct the financial accounting system 10 according to the needs of the accounting office.

  In the above example, the log information of the client 20 is written and managed in the server log file 53 on the server 40 side, but the log information of the server 40 itself is also written in the server log file 53 by real-time processing. The log information of the client 20 can be integrated and managed. Whether or not log information is managed is set separately for the server 40 and the client 20, and when either the server 40 or the client 20 is set to "do not acquire an access log" It is good also as a structure which manages only the log information of the other (server 40 or client 20) (refer access log setting screen D1, FIG. 3).

  In the above example, the log information in the local log file 33 is transferred to the server 40 via the communication interfaces 25 and 45 and the network 60. However, journal data and the like are transferred via the media drives 24 and 44. When the company data is taken into the server 40, the log information read from the local log file 33 may be provided. According to this configuration, log information can be provided to the server 40 even when the client 20 cannot connect to the network environment. Even when the client 20 that does not support network connection is used, the server 40 can manage log information.

  In the above example, the transfer means 220 (see FIG. 2) stores the log information at the time of client 20 system startup, system termination, application termination, and file termination (use data switching). However, in addition to this, log information may be transferred when the application is started and when the file is started, and the transfer timing may be set by the user. . Further, the server 40 may be configured to perform transfer according to a manual log information transfer instruction by the user.

  In the above example, log information is written to the local log file 33 regardless of the operation mode of the client 20. However, in the client mode connected to the server 40, the log information is directly stored in the server log file 53. May be written. That is, different writing processes may be performed depending on the operation mode, such as writing log information to the local log file 33 in the stand-alone mode and writing to the server log file 53 in the client mode.

  In the above example, the log information stored in the server log file 53 in the server 40 is searched and displayed. However, the log information stored in the local log file 33 in the client 20 is searched. Also, the display may be configured to be possible. In this case, the local log file 33 may be referred to by any operation of the server 40 and the client 20.

  It is also possible to provide each function in the financial accounting system 10 shown in the above example and each means in the server 40 or the client 20 as a program. Further, the program can be provided by being stored in a recording medium (not shown). CD-ROM, flash ROM, memory card (compact flash (registered trademark), smart media, memory stick, etc.), compact disk, magneto-optical disk, digital versatile disk, flexible disk, hard disk, etc. can be used as the recording medium. it can.

  In addition, the system configuration, the type of system, the application to be used, the processing steps, and the like can be appropriately changed without departing from the gist of the present invention, regardless of the above-described embodiments.

It is a system configuration figure of a financial accounting system. It is a functional block diagram of a financial accounting system. It is a figure which shows an example of an access log setting screen. It is a figure which shows an example of an access log display screen. It is a figure which shows the state which moved the scroll bar of the access log display screen of FIG. It is a figure which shows an example of an access log list display screen. It is a figure which shows an example of a search screen. It is a flowchart which shows the log management process at the time of stand-alone mode operation | movement. It is a flowchart which shows the log management process at the time of client mode operation | movement.

Explanation of symbols

  10: financial accounting system, 20: client, 33: local log file, 36: log management flag (client side), 37: operation mode flag, 40: server, 53: server log file, 56: log management flag (server side) 210: Client side writing means, 220: Transfer means, 410: Server side writing means, 420: Search means, 430: Display means, 440: Log management setting means

Claims (9)

Server,
A client-server system comprising one or more clients having two operation modes: a client mode that operates while connected to the server, and a stand-alone mode that operates while disconnected from the server;
The client
A client-side storage area for storing log information as an operation history;
At least in the stand-alone mode, client-side writing means for writing the log information to the client-side storage area;
Transfer means for transferring the log information written in the client-side storage area to the server in the client mode;
The server
A server-side storage area that collectively stores the log information of the one or more clients;
A client-server system comprising: server-side writing means for writing the log information transferred from the client into the server-side storage area.   The client-server system according to claim 1, wherein the client-side writing unit writes the log information to the client-side storage area even in the client mode.   The said transfer means transfers the said log information to the said server at least at the time of the system end in the said client mode, and the operation mode switch from the said client mode to the said stand-alone mode. Client server system.   The transfer means is operating in the client mode, when the client system is started, when an application is started, when an application is ended, when a file is started, when a file is ended, or when all or all of The client server system according to claim 3, wherein the log information is transferred to the server also at a timing. The server
Search means for searching the log information stored in the server-side storage area;
5. The display device according to claim 1, further comprising: a display unit configured to display a search result by the search unit and a list of the log information written in the server-side storage area. The client server system described in 1. The server
6. The log management setting means for setting whether or not to function the client side writing means, the transfer means, and the server side writing means, according to any one of claims 1 to 5. Client server system.   A computer used as a client or a server in the client-server system according to any one of claims 1 to 6.   The program for functioning a computer as each means of the client in the client server system of any one of Claim 1 thru | or 6, or a server. Server,
A log information management method for a client server system comprising one or more clients operable in a disconnected state from the server,
The client
Writing log information, which is an operation history of each client, into a storage area in each client;
A log information management method for a client server system, comprising: transferring the log information written in a storage area in each client to the server while being connected to the server.

Images