JP2015166937A - Data management device and control method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data management technology for achieving cost reduction and responsibility.SOLUTION: A data management device includes: reception means for receiving a data file and a storage request of the data file from an external device; first control means for controlling the storage of the file substance and attribute information of the data file received by the reception means in a first storage part; detection means for detecting the file substance stored in the first storage part; second control means for, when the file substance is detected by the detection means, controlling the storage of the file substance in a second storage part different from the first storage part and the deletion of the file substance from the first storage part; and transmission means for transmitting a response to the storage request to the external device, therein a response to the external device by the transmission means is executed prior to control by the second control means.

Description

  The present invention relates to document data management technology.

  In a document management system, a database is often used to realize a function of searching for a target document file using a document attribute (for example, file name, size) associated with the document (data file) as a search key. For example, Patent Document 1 proposes a system in which file entities are managed by a volume database and document attributes are managed by an attribute database. As described above, the method of managing both the file entity and the document attribute by the database server is completed only by accessing the database, and therefore has an advantage in that the time required for responding to the user's request is shortened.

JP 2006-331273 A

  However, in general, the storage cost of a database server is higher than the storage cost of a general file server. Therefore, the cost of the entire system increases as the number of files to be managed increases. On the other hand, if only a document attribute is managed by a database server and a file entity is managed by an inexpensive file server, the cost of the entire system is expected to be reduced. However, file servers tend to be slower in processing speed than database servers. Therefore, in such a configuration, when a document operation is accepted from the client device, after both the processing of the file entity stored in the file server and the processing of the document attribute stored in the database are completed, the client device Will return a response. For this reason, in the configuration in which the file entity is managed by the file server, it takes a long time to return a response to the client device.

  The present invention has been made in view of the above-described problems, and an object thereof is to provide a data management technique capable of achieving both cost and responsiveness.

  In order to solve the above-described problems, a data management apparatus according to the present invention has the following configuration. That is, the data management device stores the data file and a storage request for the data file from an external device, and stores the file entity and attribute information of the data file received by the reception device in the first storage unit. First control means for controlling, detection means for detecting a file entity stored in the first storage unit, and when the detection unit detects a file entity, the file entity is stored in the first storage unit A second control unit that controls to delete the file entity from the first storage unit, a transmission unit that transmits a response to the storage request to the external device, The response to the external device by the transmission unit is executed prior to the control by the second control unit.

  ADVANTAGE OF THE INVENTION According to this invention, the data management technique which can make cost and responsiveness compatible can be provided.

It is a figure which shows the structure of the document management system which concerns on 1st Embodiment. It is a figure which shows the hardware constitutions of each apparatus which comprises a document management system. It is a figure which shows the software structure of each apparatus which comprises a document management system. It is a flowchart of the document registration process in a document management system. It is a flowchart of the document replication process in a document management system. It is a flowchart of the document deletion process in a document management system. It is a detailed flowchart of the process with respect to a file entity. It is a figure which shows an example of the document attribute management table for managing the attribute information of a data file. It is a figure which shows an example of the file entity management table for managing the file entity of a data file. It is a figure which shows an example of the user information management table for managing the authentication information of a user. It is a figure which shows an example of the document attribute management table 1100 in 2nd Embodiment. It is a detailed flowchart of the process with respect to the file entity in 3rd Embodiment.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings. The following embodiments are merely examples, and are not intended to limit the scope of the present invention.

(First embodiment)
As a first embodiment of the data management apparatus according to the present invention, a document management system using a database server (DBS) and a file server (FS) will be described below as an example.

<Device configuration>
FIG. 1 is a diagram showing a configuration of a document management system according to the first embodiment. One or more client PCs 101-1, 101-2,..., 101 -N (hereinafter simply referred to as client PC 101) are connected to the network 100, and a server group 102 constituting the document management system is further connected. Has been. Here, the network 100 represents the Internet or an intranet line.

  The server group 102 includes a Web server 103 that receives a request from the request transmission unit 301 of the client PC 101 and returns a response. The server group 102 includes a database server 104 (hereinafter referred to as DBS 104) that manages document attributes and file entities, and a file server 105 (hereinafter referred to as FS 105) that manages file entities. Physically, the Web server 103, the DBS 104, and the FS 105 may be configured as an integrated device. Further, the Web server 103 and the DBS 104 may be integrated, and the FS 105 may be configured as a separate device. Furthermore, part or all of the server group 102 may be configured to be realized by cloud computing.

  The Web server 103 is a server in which an HTTP server that processes a response to an HTTP request from the client PC 101 and an application server that performs bridging to the DBS 104 and FS 105 and performs data processing and the like. As an actual server configuration, the above-described HTTP server and application server may be different configurations, but are described as one Web server 103 here for the sake of simplicity.

  The DBS 104 collects and manages document attributes and file entities of various data files in a document management system, and enables easy search / extraction processing and the like. In particular, here, in order to realize high-speed and stable management, data management is performed using a database management program instead of building directly on the file system provided by the OS.

  The FS 105 is a storage device for managing file entities in the document management system. Since the FS 105 generally does not require a high level of computing capability, the I / O processing capability is lower than the DBS 104 when storing the same data.

  FIG. 2 is a diagram illustrating a hardware configuration of each device constituting the document management system. Each device (various servers in the server group 102 and the client PC 101) is realized by a general information processing device (PC) 200 executing a predetermined program.

  The CPU 201 is in charge of calculation and control of the information processing apparatus 200. The RAM 202 functions as an execution program area, a program execution area, and a data area as a main memory of the CPU 201. For example, the execution program is read from the external memory 211 described later to the RAM 202 and executed.

  A program ROM 203, which is a non-volatile memory, stores an operating system (OS) program that performs device control of the information processing apparatus 200. The program ROM 203 in the Web server 103 stores a program that receives a request transmitted from the client PC 101, performs processing according to the request, and transmits a response to the request. Further, the program ROM 203 in the Web server 103 stores a program for instructing the DBS 104 and the FS 105 to perform processing. A program ROM 203 in the DBS 104 stores a database management program and performs processing in response to a request from the Web server 103.

  The data ROM 204, which is a non-volatile memory, stores information necessary for providing the functions of the information processing apparatus 200. For example, in the DBS 104, information necessary for providing the function of the information processing apparatus 200 includes file entities and document attributes registered from the client PC 101, authentication information of the client PC 101 that is a user of the document management system, and the like. Conceivable. In addition, you may comprise so that the external memory 211 mentioned later may be used instead of data ROM.

  A network controller (NC) 205 is a functional unit for connecting to a network and executing communication control processing with devices connected to other networks. A keyboard controller 206 controls key input via a keyboard 209 described later. The display controller 207 is a functional unit that performs control for displaying information in the information processing apparatus 200 on a screen of a display 210 described later. The disk controller 208 is a functional unit that performs input / output control with the external memory 211. For example, the DBS 104 controls input / output of file entities and document attributes to be managed, and authentication information of the client PC 101 that is a user of the document management system.

  The keyboard 209 is a functional unit for an operator who operates the information processing apparatus 200 to perform an input operation. For example, when the operator performs maintenance work on the server group 102 in the first embodiment, it is conceivable that the keyboard 209 is operated while viewing information displayed on the display 210 described later. The display 210 is a display device such as an LCD.

  The external memory 211 is, for example, a hard disk (HD), a flexible disk (FD), a semiconductor memory, and the like, and is used for storing application programs and various data. Here, the application program refers to, for example, a program for realizing each processing unit described later in the Web server 103, a database management program in the DBS 104, and the like.

  FIG. 3 is a diagram showing a software configuration of each device constituting the document management system. Note that each server of the client PC 101 and the server group 102 may include a functional unit other than that shown in FIG. The functional units included in each server of the client PC 101 and the server group 102 are realized by the CPU 201 executing a program stored in the program ROM 203 or the data ROM 204.

  The client PC 101 includes a request transmission unit 301 and a response reception unit 302. The request transmission unit 301 is a functional unit for the client PC 101 to transmit a processing request to the server group 102 on the network using the network 100. The response receiving unit 302 is a functional unit for receiving the response of the process requested to the server group 102 by the request transmitting unit 301.

  The Web server 103 includes a request reception unit 303, a response transmission unit 304, a file entity processing unit 305, a document attribute processing unit 306, and an authentication information processing unit 307.

  The request receiving unit 303 is a functional unit for receiving a request transmitted from the client PC 101 on the network using the network 100. The response transmission unit 304 is a functional unit for transmitting the result of processing the request received by the request reception unit 303 to the client PC 101 as a response.

  The file entity processing unit 305 is a functional unit for processing a file entity management table 900 (FIG. 9), which will be described later, and a file entity of a data file in accordance with a request from the client PC 101. The document attribute processing unit 306 is a functional unit for processing document attributes recorded in a document attribute management table 800 (FIG. 8) described later according to processing from the client PC 101.

  The authentication information processing unit 307 is a functional unit for determining that the client PC 101 is a user registered in the document management system when a processing request is received from the client PC 101.

  The DBS 104 includes an authentication information management unit 308, a document attribute management unit 309, and a file entity management unit 310. The authentication information management unit 308 is a functional unit that manages data as shown in a user information management table 1000 (FIG. 10) described later. If the client PC 101 is a valid user of the document management system, the user information of the user is registered in the user information management table 1000. The document attribute management unit 309 is a functional unit that manages data as shown in a document attribute management table 800 (FIG. 8) described later. The file entity management unit 310 (first storage unit) is a functional unit constructed on a database for storing and managing data as shown in a file entity management table 900 (FIG. 9) described later.

  The FS 105 has a file entity management unit 311. The file entity management unit 311 (second storage unit) is directly constructed on, for example, a file system provided by an operating system (OS).

<Configuration of various management tables>
FIG. 8 is a diagram showing an example of a document attribute management table 800 for managing data file attribute information. As described above, the document attribute management table 800 is managed by the document attribute management unit 309 of the DBS 104.

  An item 801 represents a document ID for uniquely specifying a data file, and is identification information (ID) unique to the registered data file and given to the registered data file. For example, when the document ID is registered in the document attribute management table 800, the document ID is automatically assigned by the document attribute processing unit 306 in the Web server 103. The document ID only needs to be unique on the document management system. For example, a unique ID may be used by combining with another ID (for example, an ID assigned to the DBS 104).

  An item 802 represents the document name of the data file, and can be arbitrarily set when the data file is transmitted from the client PC 101 to the Web server 103.

  An item 803 represents an entity storage flag and indicates whether the file entity is managed by the file entity management unit 311 of the FS 105 or the file entity management unit 310 in the DBS 104. An item 804 represents storage location information (for example, full path information) of the file entity when the file entity is managed by the file entity management unit 311 of the FS 105. That is, when the file entity is managed by the file entity management unit 311 of the FS 105, the file entity is acquired based on the storage location information. When the file entity is managed by the file entity management unit 310 of the DBS 104, the file entity is acquired based on the file entity management table 900 (FIG. 9) described later.

  An item 805 represents a document operation type, and represents how the file entity processing unit 305 operates the file entity by the processing of FIG. 7 described later. In the following description, it is assumed that “Register” is stored when a new file entity is registered, “Duplicate” is stored when a file entity is copied, and “Delete” is stored when a file entity is deleted.

  FIG. 9 is a diagram showing an example of a file entity management table 900 for managing the file entity of the data file. As described above, the file entity management table 900 is managed by the file entity management unit 310 of the DBS 104.

  An item 901 represents a document ID, which is the same as the document ID in the document attribute management table 800 described above. That is, each record in the document attribute management table 800 and each record in the file entity management table 900 are linked using the document ID as a key.

  An item 902 represents a file entity, and the Web server 103 receives a file from the client PC 101 and stores file entity data. For example, in a general database management system (DBSMS), a file entity is stored using a data type storing a binary or character called a large object (LOB).

  FIG. 10 is a diagram showing an example of a user information management table 1000 for managing user authentication information. As described above, the user information management table 1000 is managed by the authentication information management unit 308 of the DBS 104. That is, the user information management table 1000 is information that defines whether or not a request from a user received via the client device 101 can be executed. When a request is received from a user who does not have file operation authority, the response transmission unit 304 returns a response indicating that the request is not permitted.

  An item 1001 is a user ID issued for each user, and is identification information (ID) that is unique on the document management system. An item 1002 is a user name given to each user ID, and is mainly used for screen display.

  An item 1003 is a mail address used for transmission of a notification from the document management system to the client PC 101. An item 1004 is a password required when the user logs in to the server group 102 via the client PC 101. The password may be automatically issued by the authentication information processing unit 307, or may be arbitrarily set via the client PC 101.

<Operation of the device>
FIG. 4 is a flowchart of document registration processing in the document management system. This processing is executed by the Web server 103 in accordance with a registration processing request (storage request) from the client PC 101 which is an external device.

  In step S401, the request reception unit 303 of the Web server 103 receives the data file (file entity and document attribute) and the new registration request for the data file transmitted by the request transmission unit 301 of the client PC 101.

  In step S402, the document attribute processing unit 306 of the Web server 103 stores the document attribute received in S401 in the document attribute management unit 309 in the DBS 104. That is, the document attribute processing unit 306 requests the DBS 104 to add a record to the document attribute management table 800 (FIG. 8) managed by the document attribute management unit 309. At this time, control is performed so as to store “registration” indicating that the data file is newly registered as the document operation type of the document attribute management table 800.

  In step S403, the file entity processing unit 305 of the Web server 103 stores the file entity received in S401 in the file entity management unit 310 in the DBS 104.

  In step S404, the Web server 103 determines whether the document attribute and the file entity are correctly stored in the DBS 104 in the processes of S402 and S403. If the document attribute and the file entity are correctly stored and registered, the process proceeds to S405. If not correctly stored (if the storage has failed), the process proceeds to S407.

  In step S <b> 405, the Web server 103 performs registration confirmation processing for the corresponding records in FIGS. 8 and 9 described later of the DBS 104. In step S406, the Web server 103 notifies the client PC 101 that the document attribute and file entity have been correctly registered and confirmed in the DBS 104 in the process of S405.

  In step S407, the Web server 103 performs registration cancellation processing for the corresponding records in the DBS 104 in FIGS. In step S408, the response transmission unit 304 of the Web server 103 notifies the client PC 101 of the registration failure by completing the cancellation of all the document attribute and file entity registrations in the DBS 104 by the process of S407.

  In step S409, the file entity processing unit 305 of the Web server 103 executes processing on the file entity of the registered data file. Details will be described later with reference to FIG. That is, after the response to the document registration request by the client PC 101 is completed, the file entity processing unit 305 executes processing for the file entity. Here, the process of S409 has been described as being performed following S408. However, the process may be periodically executed by periodically checking a resident process, a batch file, or the like.

  By executing the above processing flow, the data file registration processing from the client PC 101 to the document management system is completed.

  FIG. 5 is a flowchart of document duplication processing in the document management system. This processing is executed by the Web server 103 in accordance with a replication processing request from the client PC 101 that is an external device.

  In step S501, the request reception unit 303 of the Web server 103 receives the document copy request transmitted by the request transmission unit 301 of the client PC 101. The document duplication request includes information for specifying a data file as a duplication source and information for specifying a duplication destination of the data file.

  In step S502, the document attribute processing unit 306 of the Web server 103 refers to the document attribute management unit 309 in the DBS 104 and acquires attribute information (for example, document name) of the data file specified by the document duplication request received in S401. To do.

  In step S503, the document attribute processing unit 306 of the Web server 103 acquires storage location information (full path information) on the FS from the document attribute management table 800 based on the attribute information of the data file acquired in S502. In step S504, the file entity processing unit 305 of the Web server 103 acquires the file entity stored in the storage location information acquired in S503 from the file entity management unit 311.

  In step S505, the document attribute processing unit 306 of the Web server 103 copies the document attribute acquired in S502, and based on the information specifying the data file copy destination received in S501, the document attribute management unit in the DBS 104 In 309, it is stored as a duplicate data file. At this time, as a document operation type of the document attribute management table 800, control is performed so as to store “duplicate” indicating a duplicate document as a document attribute.

  In step S506, the file entity processing unit 305 of the Web server 103 stores the file entity acquired in S504 in the file entity management unit 310 in the DBS 104 based on the information specifying the copy destination of the document received in S501. To do.

  In step S507, it is determined whether the document attribute and the file entity are correctly stored in the DBS 104 in the processes of S505 and S506. If the document attribute and the file entity are correctly stored and registered, the process proceeds to S508. If not correctly stored (if the storage has failed), the process proceeds to S510.

  In step S <b> 508, the Web server 103 performs registration confirmation processing on corresponding records in FIGS. 8 and 9 described later of the DBS 104. In step S509, the Web server 103 notifies the client PC 101 that the document attribute and file entity have been correctly registered and confirmed in the DBS 104 in the process of S508.

  In step S <b> 510, the Web server 103 performs registration cancellation processing for the corresponding record in FIGS. 8 and 9 in the DBS 104. In step S511, the response transmission unit 304 of the Web server 103 notifies the client PC 101 of the registration failure by completing the cancellation of all the document attribute and file entity registrations in the DBS 104 by the process of S510.

  Step S409 is the same as the process shown in D409 of FIG. 4, and details will be described later with reference to FIG.

  By executing the above processing flow, the data file copy registration processing from the client PC 101 to the document management system is completed.

  FIG. 6 is a flowchart of document deletion processing in the document management system. This processing is executed by the Web server 103 in accordance with a deletion processing request from the client PC 101 which is an external device.

  In step S601, the request reception unit 303 of the Web server 103 receives the document deletion request transmitted by the request transmission unit 301 of the client PC 101. The document deletion request includes information for specifying the data file to be deleted.

  In step S602, the document attribute processing unit 306 of the Web server 103 is a data file to be deleted as a document attribute to the document attribute management unit 309 in the DBS 104 based on the information specifying the data file received in S601. Is stored in the document attribute management unit 309. That is, control is performed so that “delete” is stored as the document operation type of the document attribute management table 800.

  In step S603, the Web server 103 determines whether the document attribute is correctly stored in the DBS 104 in the process of S602. If it is stored correctly, the process proceeds to S604, and if it is not stored correctly, the process proceeds to S606.

  In step S <b> 604, the Web server 103 performs registration confirmation processing for the corresponding record in FIG. 8 described later of the DBS 104. In step S605, the Web server 103 notifies the client PC 101 that the document attribute has been correctly registered and confirmed in the DBS 104 in the process of S604, that is, has been confirmed as a deleted document.

  In step S606, the Web server 103 performs registration cancellation processing for the corresponding record in FIG. In step S607, the response transmission unit 304 of the Web server 103 notifies the client PC 101 of the deletion failure by completing the cancellation of all the document attribute registrations in the DBS 104 by the process of S606.

  Step S409 is the same as the process shown in D409 of FIG. 4, and details will be described later with reference to FIG.

  By executing the above processing flow, the data file deletion processing from the client PC 101 to the document management system is completed.

  FIG. 7 is a detailed flowchart of the process for the file entity (S409) to be executed in the various processes shown in FIGS. This process is mainly executed by the file entity processing unit 305 in the Web server 103. As described above, the processing for the file entity (S409) may be configured to be periodically executed by periodic checks such as a resident process or a batch file.

  In step S701, the document attribute processing unit 306 refers to the document attribute management unit 309 in the DBS 104, and extracts one record whose document operation type is “registration” in the document attribute management table 800 (detection unit). If a record is extracted, the process proceeds to S704, and if no record is extracted, the process proceeds to S702.

  In step S <b> 702, the document attribute processing unit 306 refers to the document attribute management unit 309 in the DBS 104 and extracts one record whose document operation type is “duplicate” in the document attribute management table 800. If a record is extracted, the process proceeds to S704, and if no record is extracted, the process proceeds to S703.

  In step S703, the document attribute processing unit 306 refers to the document attribute management unit 309 in the DBS 104, and extracts one record whose document operation type is “deleted” in the document attribute management table 800. If a record is extracted, the process proceeds to S712, and if no record is extracted, the process ends.

  In step S704, the file entity processing unit 305 acquires a file entity from the file entity management unit 310 in the DBS 104 based on the extracted record. In step S705, the file entity processing unit 305 stores the file entity acquired in S704 on the file system in the FS 105. That is, at this point, the file entity temporarily exists in both the DBS 104 and the FS 105.

  In step S706, the document attribute processing unit 306 registers the storage location information (full path information) of the file entity on the file system stored in the FS 105 in S705 in the entity path on the FS in the document attribute management table 800.

  In step S707, the document attribute processing unit 306 updates the document operation type in the document attribute management table 800 managed by the document attribute management unit 309 in the DBS 104. Specifically, the “registration” or “duplication” information is deleted.

  In step S708, the file entity processing unit 305 deletes the file entity from the file entity management unit 310 in the DBS 104.

  In step S709, the Web server 103 determines whether the document attribute and the file entity are correctly stored in the DBS 104 in the processing of S706 to S708. If the document attribute and the file entity are correctly stored and registered, the process proceeds to S710. If the document attribute and the file entity are not correctly stored (if the storage has failed), the process proceeds to S711.

  In step S <b> 710, the Web server 103 performs registration confirmation processing for the corresponding records in FIGS. 8 and 9 in the DBS 104. In step S711, the Web server 103 performs registration cancellation processing for the corresponding record in FIGS.

  In step S712, the document attribute processing unit 306 acquires the actual path on the FS from the document attribute management table 800 based on the extracted record. In step S713, the file entity processing unit 305 deletes the file entity stored in the entity path acquired in step S712 from the file entity management unit 311 in the FS 105. In step S714, the file entity processing unit 305 performs a deletion confirmation process on the corresponding records in FIGS. 8 and 9 of the DBS 104.

  As described above, according to the first embodiment, the Web server 103 sends a response to the client prior to the file entity operation (FIG. 7) when the file operation to the DBS 104 based on the request from the client is completed. Send back. Thereafter, the Web server 103 performs file entity operations.

  That is, with this configuration, it is possible to realize a document management system with good responsiveness while reducing costs by storing a file entity with a large data capacity in the FS 105.

(Second Embodiment)
In the second embodiment, an example of storing a file entity in a DBS for a specific document will be described. In other words, in the first embodiment described above, the file entities are stored in the FS 105 for all documents, but may be in accordance with the purpose of the user stored in the DBS 104. For example, since DBS is generally considered to be more robust and secure than FS, a document that is not desired to be managed by FS is also assumed. Therefore, in the second embodiment, a method for obtaining the same effect while solving such a problem will be described. Since the system configuration and operation are substantially the same as those in the first embodiment, only different parts will be described.

<Document attribute management table>
FIG. 11 is a diagram illustrating an example of the document attribute management table 1100 according to the second embodiment. Compared to the document attribute management table 800 (FIG. 8) in the first embodiment, an item 1101 is added.

  An item 1101 indicates whether or not the data is a confidential data file that places importance on security as the document storage type. Specifically, the file entity processing unit 305 refers to the item 1101 and determines whether or not to store the file entity in the file entity management unit 311 in the FS 105. Here, when the security emphasis is “ON”, control is performed so that the corresponding file entity is not stored in the file entity management unit 311 in the FS 105. This information is specified by the user, and is included in the document attribute of the data file transmitted by the request transmission unit 301 of the client PC 101 in S401 of FIG. 4, for example.

<Process for file entity (FIG. 7)>
In step S <b> 701, the document attribute processing unit 306 refers to the document attribute management unit 309 in the DBS 104 and extracts one record whose document operation type is “registered” in the document attribute management table 1100. However, if the security emphasis indicated by the item 1101 in FIG. 11 is “ON”, the corresponding record is not extracted. That is, if it is specified that the file entity is not stored in the FS 105, the determination is “NO” and the process proceeds to S702.

  In step S <b> 702, the document attribute processing unit 306 refers to the document attribute management unit 309 in the DBS 104 and extracts one record whose document operation type is “duplicate” in the document attribute management table 800. However, as in S701, if the security emphasis indicated by the item 1101 in FIG. 11 is “ON”, the corresponding record is not extracted. That is, if it is specified that storage of the file entity in the FS 105 is not allowed, “NO” is determined, and the process proceeds to S703.

  In other words, the file entity of the data file whose security priority is “ON” is prevented from being stored in the FS 105 by the file entity processing unit 305.

  As described above, according to the second embodiment, for a specific document, storage of the file entity in the FS is suppressed and stored in the DBS. With this configuration, it is possible to perform management with higher robustness and security with respect to a specific data file (a data file for which security is designated “ON”).

(Third embodiment)
In the third embodiment, an example in which only the DBS 104 is used when the data capacity of a data file managed by the system is small will be described. That is, while the data capacity of the data file to be managed is small, the cost of the entire system does not increase so much even if it is configured to store only in the DBS 104. Further, by configuring so that the data is stored only in the DBS 104, the responsiveness of the process involving the acquisition of the file entity is improved as compared with a configuration using both the DBS 104 and the FS 105.

<Process for file entity>
FIG. 12 is a detailed flowchart of processing for a file entity in the second embodiment. This process is mainly executed by the file entity processing unit 305 in the Web server 103. However, as described above, the processing on the file entity (S409) may be executed periodically by periodically checking a resident process, a batch file, or the like.

  The difference is that Steps S1201 and S1202 are additionally performed with respect to the process (FIG. 7) for the file entity in the first embodiment.

  In step S1201, the file entity processing unit 305 acquires the total capacity of the file entity when stored in the file entity management unit 310 in the DBS 104. For example, the sum of the file entity of the data file received in step S401 and the file entity capacity already stored in the file entity manager 310 of the DBS 104 is calculated.

  In step S1202, the file entity processing unit 305 compares the total capacity obtained in S1201 with a preset capacity (predetermined capacity). Here, the limited capacity is a capacity set by the user. If the total capacity is equal to or greater than the limit capacity, the process proceeds to S701 and the same operation as in the first and second embodiments is performed. On the other hand, if the total capacity is less than the limit capacity, the process ends.

  As described above, according to the third embodiment, the file entity processing unit 305 prevents the file entity from being stored in the FS 105 while the total file entity capacity of all data files to be managed is less than the limit capacity. With this configuration, as long as the total capacity of the file entities of all the data files to be managed is less than the limit capacity, it is possible to improve the responsiveness of the process involving the acquisition of the file entities compared to the first embodiment. Become.

(Other examples)
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (12)

Receiving means for receiving a data file and a storage request for the data file from an external device;
First control means for controlling the file entity and attribute information of the data file received by the receiving means to be stored in the first storage unit;
Detecting means for detecting a file entity stored in the first storage unit;
When the detection unit detects the file entity, the file entity is stored in a second storage unit different from the first storage unit, and the file entity is controlled to be deleted from the first storage unit. Two control means;
Transmitting means for transmitting a response to the storage request to the external device;
Have
The data management apparatus according to claim 1, wherein the response to the external device by the transmission means is executed prior to the control by the second control means. The second control means stores, in the first storage unit, storage location information indicating a storage location in the second storage unit of a file entity stored in the second storage unit. Item 2. The data management device according to Item 1. The storage location information is stored in the first storage unit as a part of attribute information of a data file corresponding to a file entity stored in the second storage unit. Data management device. The attribute information includes identification information indicating in which of the first storage unit and the second storage unit the file entity of the data file corresponding to the attribute information is to be stored,
The said data management apparatus suppresses control by a said 2nd control means, when the said attribute information contains the identification information which should be stored in a said 1st storage part. The data management device according to any one of the above. The identification information is information indicating whether the data file corresponding to the identification information is a confidential data file,
When the identification information indicates that the data file is a confidential data file, the data management device permits the control by the second control means, and the identification information indicates that the data file is not a confidential data file. 5. The data management apparatus according to claim 4, wherein in this case, control by the second control unit is suppressed. The data management device further includes an acquisition unit that acquires a total capacity of one or more file entities stored in the second storage unit,
6. The data management device according to claim 1, wherein when the total capacity acquired by the acquisition unit is less than a predetermined capacity, the control by the second control unit is suppressed. The data management device according to item. When the receiving means receives a copy request for a data file whose file entity is already stored in the second storage unit from an external device,
The first control means acquires attribute information of the data file from the first storage unit, acquires a file entity of the data file from the second storage unit, and stores the acquired file entity and attribute information. Storing as a duplicate data file in the first storage unit;
7. The transmission unit according to claim 1, wherein the transmission unit transmits a response to the replication request to the external device prior to the control by the second control unit for the file entity of the replication data file. The data management device according to claim 1. When the receiving means receives a deletion request for a data file whose file entity is already stored in the second storage unit from an external device,
The first control means assigns information indicating that the data file is a data file to be deleted to attribute information of the data file that is the target of the deletion request,
The transmission means transmits a response to the deletion request to the external device;
The data management apparatus according to any one of claims 1 to 7, wherein the second control unit deletes a file entity of the data file from the second storage unit. A storage unit that stores authentication information that defines whether the request received by the receiving unit is executable;
9. The transmission unit according to claim 1, wherein when the execution of the request received by the reception unit is not permitted based on the authentication information, the transmission unit transmits a response indicating that the request is not permitted to the external device. The data management device according to any one of the above. The data management apparatus according to claim 1, wherein the first storage unit is a storage unit constructed on a database. A method for controlling a data management device, comprising:
Receiving a data file and a storage request for the data file from an external device;
A first control step for controlling to store the file entity and attribute information of the data file received in the reception step in the first storage unit;
A transmission step of transmitting a response to the storage request to the external device;
A detection step of detecting a file entity stored in the first storage unit;
When the file entity is detected by the detection step, the file entity is stored in a second storage unit different from the first storage unit, and the file entity is controlled to be deleted from the first storage unit. Two control steps;
A method for controlling a data management apparatus, comprising:   The program for functioning a computer as each means of the data management apparatus as described in any one of Claims 1 thru | or 10.

Images