JP6991026B2 - File management system - Google Patents

Description

The present invention relates to a file management device, a file management system, a file management method, and a file management program.

In recent years, an information distribution system in which a client device sends a request to a distribution server via a network, the distribution server performs processing according to the request, and sends a response to the client device has become widespread. In such an information distribution system, since the processing capacity of the distribution server is limited, processing is distributed among a plurality of distribution servers.

Here, in the information distribution system, since the same processing is performed among a plurality of distribution servers for a request, it is necessary to use the same setting file in each distribution server, and each distribution server needs to use the same setting file every time the setting file is updated. Updates the configuration file.

Japanese Unexamined Patent Publication No. 2001-356950

However, in the prior art, there is room for improvement in that the setting file of each distribution server is updated quickly. Specifically, in the prior art, it is necessary for each distribution server to periodically update the file, or for the administrator to manually update the setting file of each distribution server.

The present application has been made in view of the above, and an object of the present invention is to provide a file management device, a file management system, a file management method, and a file management program capable of rapidly synchronizing the settings of a distribution server.

The file management device according to the present application has a storage unit that stores setting files of a plurality of distribution servers distributed on a network, and when the setting file stored in the storage unit is updated, the setting file of the setting file is updated. It is characterized by including a notification unit for notifying the distribution server of an update notification.

According to one aspect of the embodiment, there is an effect that the settings of the distribution server can be rapidly synchronized.

FIG. 1 is a diagram showing an example of a file management system according to an embodiment. FIG. 2 is a diagram showing a configuration example of the file management device according to the embodiment. FIG. 3 is a diagram showing an example of user group information according to the embodiment. FIG. 4 is a diagram showing a configuration example of the relay device according to the embodiment. FIG. 5 is a diagram showing a configuration example of a storage device according to an embodiment. FIG. 6 is a diagram showing an example of a storage area. FIG. 7 is a diagram showing a configuration example of the update management device according to the embodiment. FIG. 8 is a diagram showing an example of processing by the update management device according to the embodiment. FIG. 9 is a diagram showing an example of processing of the update management device at the time of an update error. FIG. 10 is a flowchart showing a processing procedure executed by the file management device according to the embodiment. FIG. 11 is a hardware configuration diagram showing an example of a computer that realizes the function of the file management device according to the embodiment.

Hereinafter, a form for implementing the file management device, the file management system, the file management method, and the file management program according to the present application (hereinafter referred to as “embodiment”) will be described in detail with reference to the drawings. Note that this embodiment does not limit the file management device, file management system, file management method, and file management program according to the present application. Further, in each of the following embodiments, the same parts are designated by the same reference numerals, and duplicate explanations are omitted.

(Embodiment)
[1. File management system]
First, an example of a file management system according to an embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of a file management system according to an embodiment. As shown in FIG. 1, the file management system 100 according to the embodiment includes a file management device 1, a relay device 2, a storage device 3, an update management device 4, and a distribution server 5.

Here, as shown in FIG. 1, the file management system 100 includes a plurality of distribution servers 5. The plurality of distribution servers 5 perform the same processing for requests from client terminals (not shown). That is, the file management system 100 is a distributed processing system that performs distributed processing on requests by a plurality of distribution servers 5. In the following, the case where the distribution server 5 distributes article content such as news based on recommendations will be described, but the distribution server 5 is not limited to the article content, and may distribute advertisements and the like. Further, the file management system 100 can also be applied to various distributed processing systems.

Here, in the distributed processing system, it is necessary to synchronize the settings among the plurality of distribution servers 5. In other words, it is necessary to use the same setting file on the plurality of distribution servers 5. Such a setting file is stored in the file management device 1.

In the prior art, each distribution server inquires of the file management device about whether or not the setting file is updated, and updates the setting file when the setting file is updated. Therefore, depending on the timing of the inquiry of each distribution server, a time lag may occur in the update between the distribution servers.

In such a case, if each distribution server updates the setting file at the same time, traffic may be concentrated on the file management device and the transmission rate of the setting file may exceed the bandwidth limit. Further, in the prior art, when an update requiring a reboot of each distribution server is performed, the administrator must manually update each distribution server.

Therefore, in the file management system 100 according to the embodiment, when the setting file is updated by the file management device 1, the update notification is output to each distribution server 5. Specifically, as shown in FIG. 1, first, the file management device 1 updates the setting file (step S11).

The file management device 1 can also receive, for example, an update of the setting file from the administrator terminal M. In such a case, a hub for compiling the update information input from the administrator terminal M may be provided between the administrator terminal M and the file management device 1.

When the file management device 1 updates the setting file, the file management device 1 outputs an update notification to the relay device 2 (step S12). As a result, the relay device 2 adds the record based on the update notification input from the file management device 1 to the storage device 3 (step S13). Such a record includes, for example, the metadata of the setting file updated by the file management device 1, the path of the setting file, and the like.

The storage device 3 stores the record added by the relay device 2 and notifies the update management device 4 of the record (step S14). Then, the update management device 4 schedules the update of the setting file based on the record (step S15). Scheduling here means determining whether or not the distribution server 5 needs to be rebooted for updating the setting file, and the number of distribution servers 5 to be updated at one time. For example, the update management device 4 can determine the number of such units so that the update of the setting file is maximized within the bandwidth limitation.

Subsequently, the update management device 4 adds a record of the update instruction according to the scheduling result to the storage device 3 (step S16). At this time, if a reboot is required for the update, the update instruction includes information for instructing the reboot after the update. The storage device 3 notifies each distribution server 5 of the record of the update instruction (step S17). As a result, the distribution server 5 sequentially updates the setting file from the file management device 1 based on the update instruction of the update management device 4 (step S18).

As described above, in the file management system 100 according to the embodiment, by centrally managing the update of the settings of each distribution server 5, it is possible to quickly synchronize the settings of the distribution server 5. Although the case where the file management device 1 notifies the update notification to each distribution server 5 via the relay device 2, the storage device 3, and the update management device 4 has been described here, the file management device 1 sends the update notification. It may be output directly to each distribution server 5. Even in such a case, it is possible to suppress a time lag regarding the update of the setting file of each distribution server 5.

[2. Configuration of file management device 1]
Next, the above-mentioned file management device 1 will be described with reference to FIG. FIG. 2 is a diagram showing a configuration example of the file management device 1 according to the embodiment. As shown in FIG. 2, the file management device 1 includes a control unit 10 and a storage unit 13.

(2-1. About the storage unit 13)
The storage unit 13 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory (Flash Memory), or a storage device such as a hard disk or an optical disk. As shown in FIG. 2, the storage unit 13 stores the setting file 14 and the distribution history information 15.

(2-1-1. About the setting file 14)
The setting file 14 is a file in which information for changing the settings of the distribution server 5 shown in FIG. 1 is stored. Here, the case where the setting file 14 is the recommendation information for the user's content will be described. In the setting file 14, for example, model information 14a and user group information 14b are stored as recommendation information.

The model information 14a is information about a model for predicting information about a user. Specifically, the model information 14a is, for example, information associated with a demographic attribute or a psychographic attribute as information about a user. That is, the model information 14a is information on age, gender, location area, family structure, annual income, lifestyle, hobbies, interest categories, and the like.

Here, the model information 14a is updated periodically (for example, once every 6 hours) based on the log of each distribution server 5. This is because the model information 14a changes sequentially with the passage of time. That is, by periodically updating the model information 14a, the distribution server 5 can distribute the content suitable for the user's attribute.

The user group information 14b is information about a user group set for each variation of the content distributed by the distribution server 5. Here, the user group information 14b will be described with reference to FIG. FIG. 3 is a diagram showing an example of the user group information 14b according to the embodiment.

As shown in FIG. 3, the user group information 14b is information in which a "user ID", a "variation", and the like are associated with each other. The "user ID" is information of an identifier for identifying a user.

Further, the "variation" indicates, for example, the design on the web page when the distribution server 5 distributes the content. In the example shown in the figure, the content is distributed by the design A to the user whose user ID is "UI", and the content is distributed by the design B to the user whose user ID is "U2". Further, the content is distributed by the design C to the user whose user ID is "U3".

That is, in the file management system 100, it is possible to deliver the same content with different designs, observe the progress of the user's reaction (click count, browsing time, etc.) for each design, and optimize the content design. ..

The user group information 14b is updated, for example, by the administrator of the file management system 100. Further, in the above example, the case where the user group information 14b is information regarding a variation of the design has been described, but the present invention is not limited to this.

For example, the user group information 14b may be information on other variations such as information on variations in content selection methods such as targeting and content matching.

(2-1-2. Distribution history information 15)
Returning to the description of FIG. 2, the delivery history information 15 will be described. The distribution history information 15 is information in which a log of contents distributed in the past by the distribution server 5 is recorded. The distribution history information 15 is sequentially updated by, for example, the distribution server 5.

(2-2. About control unit 10)
The control unit 10 is a controller, and for example, various programs (file management programs) stored in a storage device inside the file management device 1 by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like. (Corresponding to one example) is realized by executing the RAM as a work area. Further, the control unit 10 is realized by, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

As shown in FIG. 2, the control unit 10 has an update unit 11 and an output unit 12, and realizes or executes the functions and operations of the file management process described below.

(2-2-1. About update section 11)
The update unit 11 updates the setting file 14. Specifically, the update unit 11 updates the model information 14a of the setting file 14 based on the distribution history information 15 stored in the storage unit 13. Specifically, the update unit 11 refers to the distribution history information 15, and updates the demographic attribute of the model information 14a if there is a change in the demographic attribute from the previous update. Further, the update unit 11 can update the psychographic attribute of the model information 14a with respect to the distribution history information 15 by using machine learning such as collaborative filtering.

Further, the update unit 11 receives the update of the user group information 14b from the administrator terminal M (see FIG. 1), and updates the user group information 14b of the setting file 14. When the update unit 11 updates the setting file 14 including the model information 14a and the user group information 14b, the update unit 11 notifies the output unit 12. As described above, the model information 14a is the information that is automatically updated, and the user group information 14b is the information that is updated based on the instruction from the administrator.

The setting file 14 updated by the updating unit 11 is not limited to the model information 14a and the user group information 14b, and may be information indicating setting conditions such as a program of each distribution server 5 and an operation system.

(2-2-2. About output unit 12)
When the setting file 14 stored in the storage unit 13 is updated, the output unit 12 outputs an update notification of the setting file 14 to the distribution server 5. As described above, in the present embodiment, the output unit 12 outputs an update notification to the relay device 2. The update notification includes the metadata of the updated data and the path indicating the location in the setting file 14.

[3. Configuration of relay device 2]
Next, the relay device 2 will be described with reference to FIG. FIG. 4 is a diagram showing a configuration example of the relay device 2 according to the embodiment. The relay device 2 is a device that relays the update notification output from the file management device 1 to the storage device 3. Further, as shown in FIG. 4, the relay device 2 includes a control unit 20 and a storage unit 22.

(3-1. About the storage unit 22)
The storage unit 22 stores the DB information 23. The DB information 23 is information regarding the update DB 33 of the storage device 3 described later. Specifically, the DB information 23 is, for example, information that defines in which storage area of the update DB 33 the record corresponding to the above update notification should be written.

(3-2. Control unit 20)
The control unit 20 includes an intermediary unit 21. When the intermediary unit 21 acquires the update notification, it refers to the DB information 23 and adds a record based on the update notification to a predetermined storage area of the storage device 3 defined in response to the update notification.

As described above, in the file management system 100, the file management device 1 does not directly output the update notification to the storage device 3, but the record related to the update notification is added to the storage device 3 via the relay device 2. This makes it possible to prevent the data stored in the storage device 3 from being unintentionally rewritten by the file management device 1.

[4. Configuration of storage device 3]
Next, the storage device 3 will be described with reference to FIG. FIG. 5 is a diagram showing a configuration example of the storage device 3 according to the embodiment. The storage device 3 is a so-called database, and has a function of notifying a predetermined device when data is updated, in addition to the function of the database. Further, as shown in FIG. 5, the storage device 3 includes a control unit 30 and a storage unit 32.

(4-1. About the storage unit 32)
The storage unit 32 has an update DB 33. The update DB 33 has, for example, a plurality of storage areas 34a to c. For example, in the storage areas 34a to c, notification destination devices for notifying updates are registered for each storage area 34a to c. For example, the update management device 4 is registered as a notification destination in the storage area 34a, and the distribution server 5 is registered as a notification destination in the storage area 34b.

(4-2. Control unit 30)
The control unit 30 includes a notification unit 31. When the update DB 33 of the storage unit 32 is updated, the notification unit 31 notifies the notification destination device registered for each of the storage areas 34a to c of the update DB 33 of the data update.

FIG. 6 is a diagram showing an example of the storage area 34, and is an example of a record based on the update notification added by the relay device 2. As shown in FIG. 6, a record including items such as "date and time", "file name", "capacity", and "path" is added to the storage area 34 by the relay device 2.

“Date and time” indicates the date and time when the record was added, and “file name” indicates the name of the newly updated file in the setting file 14 (see FIG. 2). Further, "capacity" indicates the capacity of the file, and "path" indicates the location of the updated file.

When a record is added to the storage area 34, the notification unit 31 notifies the update management device 4, which will be described later in FIG. 7, of the addition of the record each time the record is added. Further, for example, when a record is added to another storage area 34, the notification unit 31 can notify the device registered in the storage area 34 of the addition of the record.

[5. Configuration example of update management device 4]
Subsequently, the update management device 4 will be described with reference to FIG. 7. FIG. 7 is a diagram showing a configuration example of the update management device 4 according to the embodiment. The update management device 4 is a device that manages the update of the settings of each distribution server 5. As shown in FIG. 7, the update management device 4 includes a control unit 40 and a storage unit 42.

(5-1. About the storage unit 42)
The storage unit 42 stores the determination condition information 43. The determination condition information 43 is information referred to by the determination unit 41 described later. Specifically, the determination condition information 43 includes, for example, information regarding the necessity of rebooting when the distribution server 5 updates the setting file 14, and the distribution server 5 and the file when the distribution server 5 uploads the setting file 14. Information about the processing load of the management device 1. The determination condition information 43 may be stored in the storage device 3.

(5-2. About control unit 40)
The control unit 40 includes a determination unit 41. The determination unit 41 determines whether or not a reboot is necessary with reference to the determination condition information 43 based on the record notified from the storage device 3. Further, the determination unit 41 writes an update instruction based on the determination result in the storage area 34 addressed to the distribution server 5 of the storage device 3.

As a result, the storage device 3 notifies the distribution server 5 of the update instruction. Then, the distribution server 5 uploads the updated file from the file management device 1 based on the update instruction.

By the way, if all the distribution servers 5 update at once, the traffic may be concentrated on the file management device 1 and the file transmission rate may exceed the bandwidth limit. Therefore, the determination unit 41 can also determine the number of distribution servers 5 to be updated at one time.

Even if the distribution server 5 is updated, the determination unit 41 can determine the number of units that fall within the above-mentioned bandwidth limitation. For example, the number can be determined based on the size of the file to be uploaded.

FIG. 8 is a diagram showing an example of processing by the update management device 4. Note that, in FIG. 8, the storage device 3 is omitted for the sake of simplicity. As shown in FIG. 8, the update management device 4 sequentially updates the distribution server 5.

Specifically, when the update management device 4 outputs an update instruction to the distribution server 5a, the distribution server 5a updates the file from the file management device 1 and then outputs a completion notification to the update management device 4.

Upon receiving the completion notification, the update management device 4 outputs an update instruction to the distribution server 5b. As a result, the distribution server 5b updates the file from the file management device 1 and then outputs the completion notification to the update management device 4. Then, the update management device 4 receives the completion notification and outputs an update instruction to the distribution server 5c.

In this way, the update management device 4 outputs an update instruction to the new distribution server 5 every time a file update completion notification is acquired from the distribution server 5. As a result, each distribution server 5 can update the settings sequentially, so that it is possible to suppress the time lag of setting updates between the distribution servers 5. In other words, it is possible to quickly synchronize the settings of the distribution server 5.

Here, the case where the update management device 4 outputs the update instruction to the distribution server 5 one by one has been described as an example, but if it is within the above-mentioned bandwidth limitation, the update instruction is sent to a plurality of distribution servers 5. It is also possible to output. In such a case, the settings of the distribution server 5 can be synchronized more quickly.

Further, since the update management device 4 updates the settings of the distribution server 5 in order, the remaining distribution server 5 for which the update instruction has not been acquired can handle the request from the client device. That is, if all the distribution servers 5 are updated at once, there is a possibility that the request from the client device cannot be processed during that time. That is, the update management device 4 can synchronize the settings of the distribution server 5 without stopping the service by updating the distribution server 5 in order.

For example, when the distribution server 5 fails to update, the update management device 4 can instruct the distribution server 5 to roll back (rewind). FIG. 9 is a diagram showing an example of processing of the update management device 4 at the time of an update error.

As shown in FIG. 9, the update management device 4 instructs the distribution server 5 to roll back when an error is notified from the distribution server 5a. As a result, the distribution server 5a performs a process of discarding the updated file and returning the setting to the state of the file before the update, for example.

This makes it possible to quickly restore the distribution server 5. Further, at this time, the update management device 4 instructs the distribution server 5b, which starts the update next to the distribution server 5a, to stop the update. This makes it possible to prevent an update error caused by the distribution server 5b.

Further, when the update management device 4 acquires the error notification from the distribution server 5a, the update management device 4 notifies the administrator terminal M of an alert based on the update error. This allows the administrator to respond quickly to such errors.

Here, the case where the update management device 4 receives an error notification from the distribution server 5 and instructs a rollback has been described, but the present invention is not limited to this. That is, the update management device 4 may instruct rollback, for example, when the KPI (Key Performance Indicator) is lowered before and after the update of the distribution server 5.

The KPI here indicates an evaluation index for the recommendation of the content distributed by the distribution server 5. For example, the larger the number of clicks on the content, the higher the KPI value, and the smaller the number of clicks on the content, the lower the KPI value.

That is, when the KPI deteriorates after the distribution server 5 is uploaded, the update management device 4 can suppress the deterioration of the performance of the distribution server 5 by returning the distribution server 5 to the setting before uploading.

The update management device 4 activates, for example, a timer corresponding to the update instruction (so-called watchdog timer), and determines that an update error occurs when the completion notification is not returned from the distribution server 5a within a predetermined time. You may do it.

[6. Processing procedure]
Next, the processing procedure executed by the file management apparatus 1 according to the embodiment will be described with reference to FIG. FIG. 10 is a flowchart showing a processing procedure executed by the file management device 1 according to the embodiment.

As shown in FIG. 10, first, the update unit 11 of the file management device 1 determines whether or not the update of the setting file 14 has been accepted from the administrator terminal M (step S101). When the update unit 11 does not accept the update of the setting file 14 from the administrator terminal M (steps S101, No), the update unit 11 determines whether or not it is the automatic update timing of the setting file 14.

Here, if the update timing is not the automatic update timing (steps S102, No), the update unit 11 shifts to step S101. On the other hand, the update unit 11 updates the setting file 14 (step S102, Yes) when the update is accepted (step 101, Yes) and when the automatic update timing is reached (step S102, Yes). Then, the output unit 12 outputs an update notification to the relay device 2 (step S104), and ends the process.

[7. effect〕
As described above, the file management device 1 according to the embodiment includes a storage unit 13 and an output unit 12. The storage unit 13 stores the setting files 14 of the plurality of distribution servers 5 distributed and arranged on the network. When the setting file 14 stored in the storage unit 13 is updated, the output unit 12 outputs an update notification of the setting file 14 to the distribution server 5.

As a result, in the file management device 1 according to the embodiment, since each distribution server 5 can update the setting file 14 based on the update notification, the settings of the distribution server 5 can be quickly synchronized.

Further, in the file management device 1 according to the embodiment, the storage unit 13 stores the recommendation information of the content distributed by the distribution server 5 in the setting file 14, and the distribution server 5 distributes the content based on the recommendation information. ..

As a result, the file management device 1 according to the embodiment can rapidly synchronize the recommendation information having a relatively high update frequency with the distribution server 5, so that each distribution server 5 can always distribute the optimum content to the user. Will be.

Further, in the file management device 1 according to the embodiment, the storage unit 13 stores the model information 14a for predicting the information about the user in the setting file 14, and the distribution server 5 stores the content based on the model information 14a. Deliver to.

As a result, in the file management device 1 according to the embodiment, each distribution server 5 can quickly reflect the model information 14a that changes every moment to distribute the content.

Further, in the file management device 1 according to the embodiment, the storage unit 13 stores the user group information 14b regarding the user group set for each variation of the content distributed by the distribution server 5 in the setting file 14.

As a result, in the file management device 1 according to the embodiment, for example, the user group information 14b updated by the administrator can be quickly synchronized with each distribution server 5, so that the change intended by the administrator can be made to each distribution server. It becomes possible to reflect it promptly in 5.

Further, the file management system 100 according to the embodiment stores and updates the file management device 1, the relay device 2 that relays the update notification output from the output unit 12, and the update notification relayed by the relay device 2. The storage device 3 for notifying the notification to the distribution server 5 and the update management device 4 for managing the update of the setting file 14 by the distribution server 5 via the storage device 3 are provided.

As a result, in the file management system 100 according to the embodiment, the update of the setting file 14 of each distribution server 5 can be centrally managed, so that the settings of the distribution server 5 can be quickly synchronized.

Further, in the file management system 100 according to the embodiment, when the relay device 2 acquires the update notification, the record based on the update notification is stored in the predetermined storage area 34 of the storage device 3 defined in response to the update notification. To add.

As a result, in the file management system 100 according to the embodiment, records can be appropriately added to the storage device 3, so that it is possible to prevent the data in the storage device 3 from being unnecessarily rewritten.

Further, in the file management system 100 according to the embodiment, the storage device 3 notifies the update management device 4 of the addition of the record, and the update management device 4 is the distribution server 5 after the update of the setting file 14 based on the record. It is determined whether or not a reboot is necessary, and an update instruction based on the determination result is output to the distribution server 5.

As a result, in the file management system 100 according to the embodiment, each distribution server 5 can be automatically updated even if the distribution server 5 needs to be rebooted.

Further, in the file management system 100 according to the embodiment, the update management device 4 instructs the new distribution server 5 to update the setting file 14 every time the distribution server 5 acquires the update completion notification of the setting file 14.

As a result, in the file management system 100 according to the embodiment, it is possible to synchronize the settings of each distribution server 5 without stopping the service by the distribution server 5.

Further, in the file management system 100 according to the embodiment, when the update management device 4 acquires the update error of the setting file 14 from the distribution server 5, the update management device 4 instructs the distribution server 5 to roll back.

As a result, in the file management system 100 according to the embodiment, the distribution server 5 in which the update error has occurred can be quickly restored.

[8. Hardware configuration]
Further, the file management device 1 according to the above-described embodiment is realized by, for example, a computer 1000 having a configuration as shown in FIG. FIG. 11 is a hardware configuration diagram showing an example of a computer 1000 that realizes the function of the file management device 1 according to the embodiment. The computer 1000 has a CPU 1100, a RAM 1200, a ROM 1300, an HDD 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 1700.

The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400, and controls each part. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started, a program depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores a program executed by the CPU 1100, data used by such a program, and the like. The communication interface 1500 receives data from another device via the network N and sends it to the CPU 1100, and transmits the data generated by the CPU 1100 to the other device via the network N.

The CPU 1100 controls an output device such as a display or a printer, and an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 acquires data from the input device via the input / output interface 1600. Further, the CPU 1100 outputs the generated data to the output device via the input / output interface 1600.

The media interface 1700 reads a program or data stored in the recording medium 1800 and provides the program or data to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase change rewritable Disk), a magneto-optical recording medium such as MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. And so on.

For example, when the computer 1000 functions as the file management device 1 according to the embodiment, the CPU 1100 of the computer 1000 realizes the function of the control unit 10 by executing the program loaded on the RAM 1200. Further, the data in the storage unit 13 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be acquired from another device via the network N.

Although some of the embodiments of the present application have been described in detail with reference to the drawings, these are examples, and various modifications are made based on the knowledge of those skilled in the art, including the embodiments described in the disclosure column of the invention. It is possible to carry out the present invention in other modified forms.

[9. others〕
Further, among the processes described in the above-described embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed can be performed. All or part of it can be done automatically by a known method. In addition, information including processing procedures, specific names, various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown in the figure.

Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or part of them may be functionally or physically distributed / physically in any unit according to various loads and usage conditions. Can be integrated and configured.

In addition, the processes described in the above-described embodiments can be appropriately combined as long as the processing contents do not contradict each other.

Further, the above-mentioned "section, module, unit" can be read as "means" or "circuit". For example, the update unit 11 can be read as an update means or an update circuit.

1 File management device 2 Relay device 3 Storage device 4 Update management device 5 Distribution server 11 Update unit 12 Output unit 14 Setting file

Claims (8)

A storage unit that stores the configuration files of multiple distribution servers distributed on the network,
A file management device including an output unit that outputs an update notification of the setting file to the distribution server when the setting file stored in the storage unit is updated .
A relay device that relays the update notification output from the output unit, and
A storage device that stores the update notification relayed by the relay device and notifies the distribution server of the update notification, and a storage device.
An update management device that manages the update of the setting file by the distribution server via the storage device.
A file management system characterized by being equipped with. The storage unit is
The recommendation information of the content distributed by the distribution server is stored in the setting file, and the recommendation information is stored in the setting file.
The distribution server
The file management system according to claim 1, wherein the content is distributed based on the recommendation information. The storage unit is
Model information for predicting information about the user is stored in the setting file, and
The distribution server
The file management system according to claim 1 or 2, wherein the content is delivered to the user based on the model information. The storage unit is
The file management system according to claim 2 or 3, wherein the user group information regarding the user group in which the variation of the content distributed by the distribution server is set for each user is stored in the setting file. The relay device is
One of claims 1 to 4, wherein when the update notification is acquired, a record based on the update notification is added to a predetermined storage area of the storage device specified in response to the update notification. The file management system described in one . The storage device is
Notifying the update management device of the addition of the record,
The update management device is
The file management according to claim 5 , wherein the necessity of rebooting the distribution server after updating the setting file is determined based on the record, and an update instruction based on the determination result is output to the distribution server. system. The update management device is
The file management system according to claim 6 , wherein each time a notification of completion of update of the setting file is acquired from the distribution server, a new distribution server is instructed to update the setting file. The update management device is
The file management system according to claim 7 , wherein when an update error of the setting file is acquired from the distribution server, a rollback is instructed to the distribution server.

Images