JP2004265141A - Access history managing program, access history managing device and access history managing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an access history managing program, an access history managing device and an access history managing method capable of correctly managing an access history of a resource object in a detailed manner. <P>SOLUTION: A storing part 102 for storing files Fl to Fn as resource objects, an application information database 120 for managing all application execution parts 103<SB>l</SB>to 103<SB>m</SB>for obtaining various computer functions (virus check, periodical backup, word processing, spreadsheet and the like) capable of accessing the files, an access detecting part 104 for detecting access from either of the application execution parts 103l to 103m to the files and a managing part 106 for generating an access history by matching an accessed file and the application execution part in the case that access is detected by the access detecting part 104. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an access history management program, an access history management device, and an access history management method for managing resource objects (files, various types of information, etc.) handled on a computer system. An access history management program, an access history management device, and an access history management method capable of managing the access history accurately and in detail.
[0002]
[Prior art]
Patent Literature 1 discloses an access history presenting apparatus that manages an access history to a file as a resource object handled on a computer system and displays the access history as an access history icon on a desktop screen.
[0003]
Specifically, in a conventional access history presentation device, access history information when a user accesses (refers to or changes a file) various resource objects stored in a file space, that is, a file, is recorded. The access history information includes an access time, an access attribute (reference or change of a file), and an accessed file name.
[0004]
In the conventional access history presenting apparatus, the recorded access history information is presented to the user by the access history icon 10 shown in FIG. The access history icon 10 is a rectangular icon image for expressing reference and change of a file on a time axis.
[0005]
In the access history icon 10, the horizontal direction is set on the time axis, the upper half is assigned to display the change history of the file, and the lower half is assigned to display the reference history of the file.
[0006]
That is, in the access history icon 10, reference history marks 11 and 12 are added to positions on the time axis corresponding to each access time at which the file was referenced based on the above-described access history information.
[0007]
Similarly, the change history marks 13 and 14 are attached to the positions on the time axis corresponding to each access time at which the file change was executed. As described above, in the conventional access history presenting apparatus, it is possible to present to the user a temporal pattern related to the access history such as the user's reference or change of the file.
[0008]
Further, in the conventional access history presenting apparatus, as shown in FIG. 21, the above-described access history icon 10 is displayed on the desktop screen in association with the file icon.
[0009]
That is, the file icons 30, 31, and 32 and the mouse cursor 40 are displayed on the desktop screen 20 shown in FIG. These file icons 30, 31, and 32 are cpf. doc, holosig. pdf and abc. doc is an icon image representing each file.
[0010]
When the mouse cursor 40 is placed on the file icon 31 (holosig.pdf) as shown in FIG. 21B by the user's mouse operation, the mouse cursor 40 is displayed based on the access history information corresponding to the file (holosig.pdf). Then, the access history icon 10 is displayed in a pop-up.
[0011]
[Patent Document 1]
JP 2001-51762 A
[0012]
[Problems to be solved by the invention]
As described above, in the conventional access history presenting apparatus, the access history icon 10 shown in FIG. 21 (b) is used to visually display the access history such as the reference or change of the file (resource object) by the user. Has been described.
[0013]
Here, actually, in addition to the access to the file by the user's operation, the file is accessed by a process such as a backup process or a virus check process that is automatically executed regardless of the user's operation. In some cases.
[0014]
However, the access history icon 10 shown in FIG. 21B reflects an access history corresponding to a user operation, but does not reflect an access history corresponding to a backup process, a virus check process, and the like.
[0015]
In particular, in the case of an important file, there is a security need for the owner of the file to know all access histories without omission. However, the conventional access history presenting apparatus has a problem that the actual access history does not match the access history represented by the access history icon 10, and cannot meet the needs of the owner.
[0016]
Further, in the conventional access history presenting apparatus, the access history icon 10 merely presents a simple access history of referring to and changing a file, and provides more detailed access such as the purpose of access and the motive. There was a problem that the history could not be presented.
[0017]
The present invention has been made in view of the above, and an object of the present invention is to provide an access history management program, an access history management device, and an access history management method capable of managing an access history of a resource object accurately and in detail. .
[0018]
[Means for Solving the Problems]
In order to achieve the above object, the invention according to claim 1 provides a computer with a resource object management means for managing a resource object, and managing all applications which can access the resource object and realize various computer functions. Application management means, an access detection means for detecting access from the application to the resource object, and when the access detection means detects an access, associates the accessed resource object with the application and associates the access history with the application. An access history management program for functioning as an access history management means for managing.
[0019]
According to the present invention, all the applications that can access the resource object and realize various computer functions are managed, and when the access to the resource object from the application is detected, the accessed resource object and the application can be managed. And the access history is managed, so that the access history of the resource object can be managed accurately and in detail.
[0020]
According to a second aspect of the present invention, in the access history management program according to the first aspect, the access history management unit presents information of the access history in response to a request from a client.
[0021]
According to the present invention, access history information is presented in response to a request from a client, so that it is possible to meet a need that requires an accurate and detailed access history.
[0022]
According to a third aspect of the present invention, in the access history management program according to the first or second aspect, all of the applications include an application that is automatically executed in a batch process.
[0023]
According to the present invention, all applications include applications that are automatically executed in batch processing, so that access histories for automatically executed applications, such as virus checks and periodic backups, can be accurately and accurately provided. Can be managed.
[0024]
According to a fourth aspect of the present invention, in the access history management program according to any one of the first to third aspects, the access history information includes information for identifying an accessed resource object, It is characterized in that information for identifying an application and an access time are included.
[0025]
According to the present invention, the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and the access time. And it can be managed in detail.
[0026]
The invention according to claim 5 is a resource object management means for managing a resource object, an application management means capable of accessing the resource object and managing all applications for implementing various computer functions, and Access detection means for detecting an access to the resource object from the server, and access history management means for managing an access history by associating the accessed resource object with the application when the access detection means detects the access. And characterized in that:
[0027]
According to the present invention, all the applications that can access the resource object and realize various computer functions are managed, and when the access to the resource object from the application is detected, the accessed resource object and the application can be managed. And the access history is managed, so that the access history of the resource object can be managed accurately and in detail.
[0028]
According to a sixth aspect of the present invention, in the access history management device according to the fifth aspect, the access history management unit presents information of the access history in response to a request from a client.
[0029]
According to the present invention, access history information is presented in response to a request from a client, so that it is possible to meet a need that requires an accurate and detailed access history.
[0030]
According to a seventh aspect of the present invention, in the access history management apparatus according to the fifth or sixth aspect, all the applications include an application that is automatically executed in a batch process.
[0031]
According to the present invention, all applications include applications that are automatically executed in batch processing, so that access histories for automatically executed applications, such as virus checks and periodic backups, can be accurately and accurately provided. Can be managed.
[0032]
According to an eighth aspect of the present invention, in the access history management apparatus according to any one of the fifth to seventh aspects, the information of the access history includes information for identifying an accessed resource object, It is characterized in that information for identifying an application and an access time are included.
[0033]
According to the present invention, the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and the access time. And it can be managed in detail.
[0034]
According to a ninth aspect of the present invention, there is provided a resource object management step of managing a resource object, an application management step of managing all applications that can access the resource object and realize various computer functions, An access detecting step of detecting an access to the resource object from the server; and, if an access is detected in the access detecting step, an access history managing step of managing the access history by associating the accessed resource object with the application. And characterized in that:
[0035]
According to the present invention, all the applications that can access the resource object and realize various computer functions are managed, and when the access to the resource object from the application is detected, the accessed resource object and the application can be managed. And the access history is managed, so that the access history of the resource object can be managed accurately and in detail.
[0036]
According to a tenth aspect of the present invention, in the access history management method according to the ninth aspect, in the access history management step, information of the access history is presented in response to a request from a client.
[0037]
According to the present invention, access history information is presented in response to a request from a client, so that it is possible to meet a need that requires an accurate and detailed access history.
[0038]
According to an eleventh aspect of the present invention, in the access history management method according to the ninth or tenth aspect, all of the applications include an application automatically executed in a batch process.
[0039]
According to the present invention, all applications include applications that are automatically executed in batch processing, so that access histories for automatically executed applications, such as virus checks and periodic backups, can be accurately and accurately provided. Can be managed.
[0040]
According to a twelfth aspect of the present invention, in the access history management method according to any one of the ninth to eleventh aspects, the information of the access history includes information for identifying an accessed resource object. It is characterized in that information for identifying an application and an access time are included.
[0041]
According to the present invention, the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and the access time. And it can be managed in detail.
[0042]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of an access history management program, an access history management device, and an access history management method according to the present invention will be described in detail with reference to the drawings.
[0043]
FIG. 1 is a block diagram showing a configuration of an embodiment according to the present invention. In this figure, a server 100 provides a function of storing a file as a resource object, a function of executing various application programs (word processor, regular backup, virus check, etc.), a function of managing an access history to a file, and an access history. It is a computer device having the function of performing
[0044]
The server 100 is connected via a network 200 to a client 300 described later. ₁ ~ 300 _s And the administrator terminal 400. In the server 100, the communication interface 101 is connected to the client 300 connected to the network 200 according to a predetermined communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol). ₁ ~ 300 _s And communication with the administrator terminal 400.
[0045]
The network 200 is the Internet, an intranet, a LAN (Local Area Network), or the like. Client 300 ₁ ~ 300 _s Are computer devices provided on the user side, and are connected to the server 100 via the network 200 to perform file operations, access history inquiries, and the like.
[0046]
The administrator terminal 400 is a computer device provided on the side of the administrator who manages the server 100. The administrator terminal 400 is connected to the server 100 via the network 200, and installs an application program and registers application information to be described later.
[0047]
The storage unit 102 stores the client 300 ₁ ~ 300 _s File F uploaded ₁ ~ F _n Is stored. Application execution unit 103 ₁ ~ 103 _m Are functional modules that execute each application program (not shown) installed in the server 100.
[0048]
Examples of the application program include a program for implementing a word processor, a spreadsheet, a customer service, a file sharing service, a regular backup, a virus check, and the like.
[0049]
Here, the regular backup and the virus check are automatically executed irrespective of the user's operation. The regular backup is a function for periodically backing up each file stored in the storage unit 102 to a backup area. The virus check is a function for checking whether each file stored in the storage unit 102 is infected with a computer virus.
[0050]
Also, the application execution unit 103 ₁ ~ 103 _m Access the files stored in the storage unit 102 based on a user operation or automatically during execution of the application program.
[0051]
The access detection unit 104 stores the file F stored in the storage unit 102 ₁ ~ F _n It has a function to detect access to the file (file reference, update, etc.). The control unit 105 controls the client 300 ₁ ~ 300 _s And various kinds of requests from the administrator terminal 400 (information registration request, information acquisition request, information deletion request, etc.). Details of the operation of the control unit 105 will be described later.
[0052]
The management unit 106 manages access to the file information database 110, the application information database 120, and the access history information database 130 under the control of the control unit 105.
[0053]
The file information database 110 stores each file (file F) stored in the storage unit 102. ₁ ~ F _n ) Is a database that stores file information related to ()). Specifically, as shown in FIG. 2, the file information database 110 has fields of “file ID”, “physical file information”, “logical file information”, and “owner information”.
[0054]
“File ID (Identification Data)” is an identifier for identifying each file stored in the storage unit 102 (see FIG. 1), and is composed of a combination of alphabets and numerals.
[0055]
The “physical file information” is information indicating a storage location of the file in the storage unit 102 (in the figure, a directory is displayed). “Logical file information” is information on the name (file name and extension) of the file. “Owner information” is information on the owner of the file.
[0056]
Returning to FIG. 1, the application information database 120 stores the application execution unit 103 ₁ ~ 103 _m Is a database that stores application information on application programs to be executed.
[0057]
Specifically, as shown in FIG. 3, the application information database 120 includes fields of “application ID”, “physical application name”, and “logical application name”.
[0058]
“Application ID” is an identifier for identifying the application program, and is composed of a combination of alphabets and numbers. “Physical application name” is information on the name (function) of the application program recognized by the application execution unit. “Logical application name” is information on the name (function) of the application program.
[0059]
Returning to FIG. 1, the access history information database 130 stores the files (file F ₁ ~ F _n 2) is a database for storing access history information relating to the access history of FIG.
[0060]
More specifically, as shown in FIG. 4, the access history information database 130 stores “file ID”, “application ID”, “access time”, “owner information”, “logical file information”, and “logical application information”. Name "field.
[0061]
“File ID”, “owner information”, and “logical file information” correspond to “file ID”, “owner information”, and “logical file information” of the file information database 110 shown in FIG. “Access time” is information on the time at which the file was accessed. “Application ID” and “logical application name” correspond to “application ID” and “logical application name” in the application information database 120 shown in FIG.
[0062]
Next, the operation of the above-described embodiment will be described with reference to the flowcharts shown in FIGS. In step SA1 shown in FIG. 5, the control unit 105 of the server 100 determines whether or not there is a request for registration of application information from the administrator terminal 400. In this case, the determination result is “No”.
[0063]
In step SA2, the control unit 105 determines whether or not there is a request for obtaining application information from the administrator terminal 400. In this case, the determination result is “No”. In step SA3, the control unit 105 determines whether or not there is a request for updating the application information from the administrator terminal 400. In this case, the determination result is “No”.
[0064]
In step SA4, the control unit 105 determines whether or not there is a request to delete the application information from the administrator terminal 400. In this case, the determination result is “No”. In step SA5, the application execution unit 103 ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s It is determined whether there is a request for uploading a file to be stored in the storage unit 102 from any of the clients. In this case, the determination result is “No”.
[0065]
In step SA6, the application execution unit 103 ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s It is determined whether there is a file information registration request from any of the clients. In this case, the determination result is “No”.
[0066]
In step SA7, the application execution unit 103 ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s It is determined whether there is a request for obtaining file information in the file information database 110 from any one of the clients. In this case, the determination result is “No”.
[0067]
In step SA8, the application execution unit 103 ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s It is determined whether there is a request from any of the clients to delete the file stored in the storage unit 102. In this case, the determination result is “No”.
[0068]
In step SA9 shown in FIG. ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s It is determined whether there is a request from any one of the clients to delete the file information stored in the file information database 110. In this case, the determination result is “No”.
[0069]
In step SA10, the access detection unit 104 checks the file F stored in the storage unit 102. ₁ ~ F _n It is determined whether an access to is detected, and in this case, the determination result is “No”.
[0070]
In step SA11, the application execution unit 103 ₁ ~ 103 _m Any one of the application execution units ₁ ~ 300 _s Of the access history information stored in the access history information database 130 is determined, and in this case, the determination result is “No”. Thereafter, steps SA1 (see FIG. 5) to step SA11 are repeated until the determination result is “Yes”.
[0071]
Then, for example, an application program for performing regular backup is executed by the application execution unit 103 by the administrator terminal 400. ₁ Is installed, the administrator terminal 400 issues a request to the control unit 105 to register application information on the application program.
[0072]
Thereby, the control unit 105 sets the determination result of step SA1 shown in FIG. 5 to “Yes”. In step SA12, an application information registration process is executed.
[0073]
Specifically, in step SB1 shown in FIG. ₁ Then, “System0001” as “application ID”, “FileBackup” as “physical application name”, and “periodic backup” as “logical application name” are acquired as application information.
[0074]
In step SB2, the control section 105 passes the application information acquired in step SB1 to the management section 106. Thereby, the management unit 106 registers the application information (“System0001”, “FileBackup”, and “periodic backup”) in the application information database 120 shown in FIG. Thereafter, application information is sequentially registered in the application information database 120 by repeatedly executing the application information registration process.
[0075]
Further, for example, when an acquisition request for acquiring desired application information from the application information database 120 shown in FIG. 3 is issued from the administrator terminal 400 to the server 100, the control unit 105 executes the step shown in FIG. The determination result of SA2 is “Yes”. In step SA13, an application information acquisition process is executed.
[0076]
Specifically, in step SC1 shown in FIG. 8, the control unit 105 causes the management unit 106 to acquire the application information (for example, corresponding to application ID = System0001) for which acquisition has been requested from the application information database 120. In step SC2, the control section 105 transmits the application information acquired in step SC1 to the administrator terminal 400.
[0077]
Also, for example, when an update request for updating the application information registered in the application information database 120 shown in FIG. 3 is issued from the administrator terminal 400 to the server 100, the control unit 105 The determination result of step SA3 is “Yes”. In step SA14, an application information update process is executed.
[0078]
Specifically, in step SD1 shown in FIG. 9, control unit 105 acquires updated application information from administrator terminal 400. In step SD2, the control unit 105 passes the application information acquired in step SD1 to the management unit 106. Thereby, the management unit 106 updates the application information database 120 with the application information.
[0079]
Further, for example, when a deletion request for deleting the application information registered in the application information database 120 shown in FIG. 3 is issued from the administrator terminal 400 to the server 100, the control unit 105 performs the processing shown in FIG. The determination result of step SA4 is “Yes”. In step SA15, an application information deletion process is executed.
[0080]
Specifically, in step SE1 shown in FIG. 10, control unit 105 acquires application information to be deleted from administrator terminal 400. In step SE2, the control unit 105 passes the application information acquired in step SE1 to the management unit 106. Thereby, the management unit 106 deletes the application information from the application information database 120.
[0081]
Also, for example, the client 300 ₁ Accesses the server 100 and the application execution unit 103 _m Function as a word processor and store the created file in the storage unit 102, the client 300 ₁ Sends the file upload request to the application execution unit 103 _m Out.
[0082]
Thereby, the application execution unit 103 _m Sets the determination result of step SA5 shown in FIG. 5 to “Yes”. In step SA16, a file upload process is executed.
[0083]
Specifically, in step SF1 shown in FIG. _m Is the client 300 ₁ For example, file F ₁ To get. In step SF2, the application execution unit 103 _m Is the acquired file F via the access detection unit 104 ₁ Is newly stored in the storage unit 102 (for example, E: \ FILES \ 0001).
[0084]
In step SF3, the application execution unit 103 _m Is the client 300 ₁ From “File0001” as “File ID”, “E: \ FILES $ 0001” as “Physical File Information”, “Minutes.TXT” as “Logical File Information” and “Everything as Owner Information” Taro "is acquired as file information.
[0085]
In step SF4, the application execution unit 103 _m Passes the file information to the control unit 105 and requests registration in the file information database 110. As a result, the control unit 105 passes the file information to the management unit 106, and registers the file information in the file information database 110 illustrated in FIG.
[0086]
In one embodiment, the storage unit 102 stores the file F ₁ Is stored in the file F ₁ Can be registered in the file information database 110 only. In this case, for example, the client 300 ₁ Accesses the server 100 and executes the application execution unit 103 _m , A file information registration request is issued.
[0087]
Thereby, the application execution unit 103 _m Sets the determination result of step SA6 shown in FIG. 5 to "Yes". In step SA17, a file information registration process is executed.
[0088]
Specifically, in step SG1 shown in FIG. _m Is the client 300 ₁ From “File0001” as “File ID”, “E: \ FILES $ 0001” as “Physical File Information”, “Minutes.TXT” as “Logical File Information” and “Everything as Owner Information” Taro "to file F ₁ Is obtained as file information corresponding to.
[0089]
In step SG2, the application execution unit 103 _m Passes the file information to the control unit 105 and requests registration in the file information database 110. As a result, the control unit 105 passes the file information to the management unit 106, and registers the file information in the file information database 110 illustrated in FIG.
[0090]
Also, for example, the client 300 ₁ When an acquisition request for acquiring desired file information from the file information database 110 shown in FIG. _m Sets the determination result of step SA7 shown in FIG. 5 to "Yes". In step SA18, a file information acquisition process is executed.
[0091]
Specifically, in step SH1 shown in FIG. _m Is the client 300 ₁ , A file ID corresponding to the file information to be obtained is obtained.
[0092]
In step SH2, the application execution unit 103 _m Passes the file ID to the control unit 105 and requests acquisition of file information from the file information database 110.
[0093]
Thereby, the control unit 105 passes the file ID to the management unit 106, and causes the file information corresponding to the file ID to be acquired from the file information database 110 illustrated in FIG. In step SH3, the control unit 105 transmits the file information acquired in step SH2 to the client 300. ₁ Send to
[0094]
Also, for example, the client 300 ₁ When a deletion request for deleting a file stored in the storage unit 102 is issued from the server to the server 100, for example, the application execution unit 103 _m Sets the result of determination in step SA8 shown in FIG. 5 to "Yes". In step SA19, a file deletion process is executed.
[0095]
Specifically, in step SI1 shown in FIG. _m Is the client 300 ₁ The file requested to be deleted (for example, file F ₁ ) Is deleted from the storage unit 102. In step SI2, the application execution unit 103 _m Is the deleted file F ₁ Is passed to the control unit 105 to request deletion of file information.
[0096]
Accordingly, in step SI3, the control unit 105 causes the management unit 106 to delete the file information from the file information database 110 using the file ID as a key.
[0097]
Also, for example, the client 300 ₁ When a deletion request for deleting file information registered in the file information database 110 is issued from the server to the server 100, for example, the application execution unit 103 _m Sets the determination result of step SA9 shown in FIG. 6 to "Yes". In step SA20, a file information deletion process is executed.
[0098]
Specifically, in step SJ1 shown in FIG. _m Is the client 300 ₁ The file ID corresponding to the file information to be deleted is acquired.
[0099]
In step SJ2, the application execution unit 103 _m Passes the file ID to the control unit 105 and requests deletion of the file information from the file information database 110. Accordingly, the control unit 105 causes the management unit 106 to delete the file information from the file information database 110 using the file ID as a key.
[0100]
Next, the file F stored in the storage unit 102 ₁ ~ F _n A method of managing an access history when an access is made to the server will be described. For example, the application execution unit 103 ₂ When the application for virus check is executed by the application execution unit 103 ₂ Automatically saves the file F in the storage unit 102 by batch processing or the like. ₁ And run a virus check.
[0101]
Accordingly, the access detection unit 104 sets the determination result of step SA10 illustrated in FIG. 6 to “Yes”. In step SA21, access history information registration processing is executed.
[0102]
Specifically, in step SK1 shown in FIG. 16, the access detection unit 104 ₁ (For example, File0001) corresponding to the application execution unit 103 of the access source ₂ The application execution unit 103 stores the application ID (for example, System0102) corresponding to ₂ Get more. Next, the access detection unit 104 passes the acquired file ID and application ID to the management unit 106, and requests registration of access history information.
[0103]
In step SK2, the management unit 106 uses the file ID (= File0001) as a key to retrieve file information from the file information database 110 shown in FIG. 2 (in this case, File0001, E: $ FILES $ 0001, minutes.TXT, Taro). ) To get.
[0104]
In step SK3, the management unit 106 acquires application information (in this case, System0102, VirusCheck, and virus check) from the application information database 120 shown in FIG. 3 using the application ID (= System0102) as a key.
[0105]
In step SK4, the management unit 106 determines whether the “physical application name” (see FIG. 3) is registered in the application information acquired in step SK3. In this case, since VirusCheck is registered as the “physical application name”, the management unit 106 determines “Yes” as the result of the determination in step SK4.
[0106]
In step SK5, the management unit 106 determines the file F at the time of the virus check based on the file information obtained in step SK2 and the application information obtained in step SK3. ₁ Access history information (see FIG. 4) is generated.
[0107]
Specifically, the management unit 106 obtains File0001 (file ID), minutes,. Extract TXT (logical file information) and Taro (owner information). Next, the management unit 106 extracts System 0102 (application ID) and virus check (logical application name) from the application information.
[0108]
Next, the management unit 106 sends the application execution unit 103 ₂ To File F ₁ Obtains information on the access time at which access to the device was detected.
[0109]
Then, the management unit 106 generates access history information from the extracted information and the access time information. In step SK6, the management unit 106 registers the access history information generated in step SK5 in the access history information database 130 shown in FIG.
[0110]
On the other hand, when the “physical application name” (see FIG. 3) is not registered in the application information acquired in step SK3, the management unit 106 determines “No” in step SK4.
[0111]
In step SK7, the management unit 106, based on the file information acquired in step SK2 and the application information acquired in step SK3, performs the file F ₁ Generate access history information for
[0112]
However, in this case, the logical application name (see FIG. 4) in the access history information is not registered. In step SK6, the management unit 106 registers the access history information generated in step SK7 in the access history information database 130.
[0113]
Note that another application execution unit (the application execution unit 103) ₁ , 103 _m ) Accesses the file stored in the storage unit 102, the above-described access history information registration processing is executed, and the access history information is sequentially stored in the access history information database 130 shown in FIG.
[0114]
Also, for example, the client 300 ₁ When an acquisition request for acquiring desired access history information from the access history information database 130 shown in FIG. ₁ Sets the determination result of step SA11 shown in FIG. 6 to "Yes".
[0115]
In step SA22, access history information acquisition processing is executed. Specifically, in step SL1 shown in FIG. ₁ Is the client 300 ₁ , The file ID (single or plural) corresponding to the access history information to be obtained is obtained.
[0116]
In step SL2, the application execution unit 103 ₁ Passes the file ID acquired in step SL1 to the control unit 105, and requests acquisition of access history information from the access history information database 130.
[0117]
Accordingly, the control unit 105 passes the file ID to the management unit 106, and causes the access history information corresponding to the file ID to be acquired from the access history information database 130 illustrated in FIG. In this case, it is assumed that access history information corresponding to File0001 (minutes. TXT), File0002 (address book. DAT), and File0101 (purchase inquiry. TXT) shown in FIG. 4 has been acquired.
[0118]
In step SL3, the control unit 105 transmits the access history information acquired in step SL2 to the client 300. ₁ Send to Then, the access history information is stored in the client 300 ₁ Is received by the client 300 ₁ Displays the access history information on the screen 500 in a tree node format, as shown in FIG. In the figure, the minutes. TXT, address book. DAT and purchase inquiry. Access history information corresponding to three files, TXT, is displayed.
[0119]
Here, the minutes. This means that there are two types of references (accesses) to TXT. Address book. This means that there are four types of references (accesses) to the DAT. In the same way, purchase inquiry. This means that there were three types of references (accesses) to TXT.
[0120]
The address book shown in FIG. When the DAT expansion button 501 is clicked, a logical application name (see FIG. 4) included in the access history information is displayed as detailed information corresponding to four types of references, as shown in FIG. 18B. You.
[0121]
In this case, each application execution unit that executes “unregistered” (step SK7: FIG. 16), “virus check”, “periodic backup”, and “file sharing service” executes the address book. This means that the file corresponding to DAT has been accessed. Further, the address book shown in FIG. When the DAT expansion buttons 502 and 503 are clicked, the access time is displayed as shown in FIG.
[0122]
In the embodiment, as an example of the resource object, a file has been described as an example. However, if it is an access target, the resource object is not limited to this, and includes various information, data, memory data, and the like.
[0123]
As described above, according to one embodiment, the file F stored in the storage unit 102 ₁ ~ F _n (Resource objects), all application execution units 103 that realize various computer functions (virus check, periodic backup, word processor, spreadsheet, etc.) ₁ ~ 103 _m Is managed by the application information database 120, and when the access detection unit 104 detects an access to a file from the application execution unit, the accessed file is associated with the application execution unit and access history information (see FIG. 4). ), The access history of the resource object can be managed accurately and in detail.
[0124]
Also, according to one embodiment, as shown in FIGS. ₁ ~ 300 _s Since the information of the access history is presented in response to a request from one of the clients, it is possible to meet a need that requires an accurate and detailed access history.
[0125]
According to one embodiment, the application execution unit 103 ₁ ~ 103 _m Includes an application execution unit that is automatically executed in batch processing, so that access histories relating to the automatically executed application execution unit, such as virus check and periodic backup, can be managed accurately and in detail without omission.
[0126]
An embodiment according to the present invention has been described in detail with reference to the drawings. However, a specific configuration example is not limited to the embodiment, and a design change within a range not departing from the gist of the present invention. The present invention is also included in the present invention.
[0127]
For example, in the above-described embodiment, a program for realizing the function of the server 100 is recorded on the computer-readable recording medium 700 shown in FIG. Each function may be realized by causing the computer 600 shown in the figure to read and execute the functions.
[0128]
The computer 600 shown in the figure includes a CPU (Central Processing Unit) 610 that executes the above-described program, an input device 620 such as a keyboard and a mouse, a ROM (Read Only Memory) 630 that stores various data, a calculation parameter and the like. (Random access memory) 640 that stores the information, a reading device 650 that reads a program from the recording medium 700, an output device 660 such as a display or a printer, and a bus 670 that connects each unit of the device.
[0129]
The CPU 610 reads the program recorded on the recording medium 700 via the reading device 650, and executes the program to realize the functions described above. Note that the recording medium 700 includes an optical disk, a flexible disk, a hard disk, and the like.
[0130]
【The invention's effect】
As described above, according to the first, fifth, and ninth aspects of the present invention, it is possible to access the resource object, manage all applications that implement various computer functions, and control access from the application to the resource object. If detected, the access history is managed by associating the accessed resource object with the application, so that the access history of the resource object can be managed accurately and in detail.
[0131]
According to the second, sixth and tenth aspects of the present invention, the information of the access history is presented in response to a request from the client, so that it is possible to meet the need for accurate and detailed access history. It has the effect of being able to do it.
[0132]
According to the third, seventh, and eleventh aspects of the present invention, since all applications include an application that is automatically executed by batch processing, an application of an automatic execution type such as a virus check or a regular backup is used. This has an effect that the access history can be managed accurately and in detail without omission.
[0133]
According to the fourth, eighth, and twelfth aspects of the present invention, the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and access time. Therefore, there is an effect that the access history of the resource object can be managed more accurately and in detail.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an embodiment according to the present invention.
FIG. 2 is a diagram showing a table structure of a file information database 110 shown in FIG.
FIG. 3 is a diagram showing a table structure of an application information database 120 shown in FIG.
FIG. 4 is a diagram showing a table structure of an access history information database 130 shown in FIG.
FIG. 5 is a flowchart illustrating the operation of the same embodiment.
FIG. 6 is a flowchart illustrating the operation of the same embodiment.
FIG. 7 is a flowchart illustrating an application information registration process illustrated in FIG. 5;
FIG. 8 is a flowchart illustrating an application information acquisition process illustrated in FIG. 5;
FIG. 9 is a flowchart illustrating an application information update process illustrated in FIG. 5;
FIG. 10 is a flowchart illustrating an application information deletion process illustrated in FIG. 5;
11 is a flowchart illustrating a file upload process illustrated in FIG.
FIG. 12 is a flowchart illustrating a file information registration process shown in FIG. 5;
FIG. 13 is a flowchart illustrating a file information acquisition process illustrated in FIG. 5;
FIG. 14 is a flowchart illustrating a file deletion process illustrated in FIG. 5;
FIG. 15 is a flowchart illustrating a file information deletion process illustrated in FIG. 6;
FIG. 16 is a flowchart illustrating an access history information registration process shown in FIG.
FIG. 17 is a flowchart illustrating an access history information acquisition process illustrated in FIG. 6;
FIG. 18 is a diagram showing a display example of access history information in the same embodiment.
FIG. 19 is a block diagram showing a configuration of a modification of the same embodiment.
FIG. 20 is a diagram showing a conventional access history icon 10;
FIG. 21 is a diagram showing a display example of an access history icon on a conventional desktop screen.
[Explanation of symbols]
100 servers
101 Communication interface
102 storage unit
103 ₁ ~ 103 _m Application execution unit
104 access detector
105 control unit
106 Management unit
110 File Information Database
120 Application information database
130 Access history information database
200 Network
300 ₁ ~ 300 _s client
400 administrator terminal

Claims (12)

Computer
Resource object management means for managing resource objects,
An application management unit that can access the resource object and manages all applications that implement various computer functions;
Access detection means for detecting access from the application to the resource object;
An access history management unit that manages an access history by associating the accessed resource object with the application when the access is detected by the access detection unit;
Access history management program to function as 2. The access history management program according to claim 1, wherein the access history management unit presents information on the access history in response to a request from a client. 3. The access history management program according to claim 1, wherein all the applications include an application automatically executed in a batch process. 4. The information according to claim 1, wherein the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and an access time. Access history management program described in one. Resource object management means for managing resource objects;
An application management unit that can access the resource object and manages all applications that implement various computer functions;
Access detection means for detecting access from the application to the resource object;
When an access is detected by the access detection unit, an access history management unit that manages an access history by associating the accessed resource object with the application,
An access history management device comprising: 6. The access history management device according to claim 5, wherein the access history management unit presents information of the access history in response to a request from a client. 7. The access history management device according to claim 5, wherein all of the applications include an application automatically executed in a batch process. 8. The information according to claim 5, wherein the information of the access history includes information for identifying the accessed resource object, information for identifying the application, and an access time. An access history management device according to any one of the above. A resource object management process for managing resource objects;
An application management step capable of accessing the resource object and managing all applications that implement various computer functions;
An access detection step of detecting access from the application to the resource object;
When an access is detected in the access detection step, an access history management step of managing the access history by associating the accessed resource object with the application,
An access history management method comprising: The access history management method according to claim 9, wherein in the access history management step, information on the access history is presented in response to a request from a client. 11. The access history management method according to claim 9, wherein all of the applications include an application automatically executed in a batch process. The information of the access history includes information for identifying an accessed resource object, information for identifying the application, and an access time. The access history management method described in one.

Images