JP5602474B2 - Information control method, program, and information control system - Google Patents

Description

  The present invention relates to an information control method, a program, and an information control system technology.

A distributed database system (hereinafter referred to as “system” as appropriate) that has a plurality of databases on a network, manages the data by distributing the data to the plurality of databases, and displays these databases as if they were a single database. (Refer to Non-Patent Document 1, for example).
Such a distributed database system has advantages such as being easy to deal with system changes and the like, and not losing all data at once in the event of a disaster.

"Distributed database programming", [online], [February 8, 2010 search], Internet <URL: http://publib.boulder.ibm.com/html/as400/v4r5/ic2962/info/db2/rbal1mstduw .htm>

However, in the distributed database system, since data is distributed in a plurality of databases, it is difficult to grasp in which database the necessary data is stored.
On the other hand, when the system is centrally managed by one database, there is a problem that all data may be lost at the same time when a disaster occurs.

  The present invention has been made in view of such a background, and an object of the present invention is to enable centralized management of data and facilitate management of the distributed database while retaining the advantages of the distributed database. .

In order to solve the above problems, the present invention has been completed. That is, the present invention stores a copy of data stored in each database and a cycle of read access or write access to the copy of the data in the common database, and the common database server stores these cycles. Based on the database management device , the database management device generates a message having a command for writing the data stored in itself or writes the data to itself from the database, broadcasts the message, and receives the message. The device executes the command in the message. Then, when the command is to write data, the database management apparatus executes the command command and then broadcasts the message so that the common database server collects a copy of the data from each database. Alternatively, the data update of the common database is reflected in each database.

  According to the present invention, it is possible to manage data centrally while facilitating the management of the distributed database while retaining the advantages of the distributed database.

It is a figure showing an example of composition of an information control system concerning this embodiment. It is a functional block diagram which shows the structural example of the common database server which concerns on this embodiment. It is a functional block diagram which shows the structural example of the database server which concerns on this embodiment. It is a functional block diagram which shows the structural example of the client terminal which concerns on this embodiment. It is a figure which shows the example of the data information for reading which concerns on this embodiment. It is a figure which shows the example of the data information for writing which concerns on this embodiment. It is a figure for demonstrating the outline | summary of the data reading process of this embodiment. It is a flowchart which shows the procedure of the read access period update process which concerns on this embodiment. It is a flowchart which shows the procedure of the data collection message issue process which concerns on this embodiment. It is a flowchart which shows the procedure of the process which acquires data from the database which concerns on this embodiment. It is a flowchart which shows the procedure of the data writing process to the data information for reading which concerns on this embodiment. It is a figure for demonstrating the outline | summary of the data writing process of this embodiment. It is a flowchart which shows the procedure of the write access period update process which concerns on this embodiment. It is a flowchart which shows the procedure of the data write message issue process which concerns on this embodiment. It is a flowchart which shows the procedure of the process which writes data in the database server which concerns on this embodiment. It is a figure for demonstrating the outline | summary of the process at the time of the database new connection which concerns on this embodiment. It is a flowchart which shows the procedure of the message issuing process for registration which concerns on this embodiment. It is a flowchart which shows the procedure of the reference data registration process which concerns on this embodiment. It is a figure for demonstrating the construction example of the information control system in this embodiment (the 1). It is a figure for demonstrating the construction example of the information control system in this embodiment (the 2). It is a figure for demonstrating the construction example of the information control system in this embodiment (the 3). It is a figure for demonstrating the construction example of the information control system in this embodiment (the 4).

  Next, modes for carrying out the present invention (referred to as “embodiments”) will be described in detail with reference to the drawings as appropriate. In addition, about the same component in each drawing, the same code | symbol is attached | subjected and description is abbreviate | omitted.

"System configuration"
FIG. 1 is a diagram illustrating a configuration example of an information control system according to the present embodiment.
The information control system 10 includes at least one client terminal 5, a plurality of databases 4, a database server (database management device) 3 that controls each database 4, a common database 2, and a common database server that controls the common database 2 (Common database controller) 1 is provided.
In the present embodiment, one client terminal 5, five databases 4 (“DB-A” to “DB-E”), five database servers 3, and each database server 3 includes one database 4. It is assumed that it is connected to. One database server 3 may control a plurality of databases 4.

  Each database 4 stores data 41 (first data, third data). That is, “DB-A” of the database 4 stores data 41 of “A: 1111”, “B: 2222”, and “D: 4444”, and “DB: B” stores “E: 5555 "is stored. Similarly, “DB-C” of database 4 stores data 41 of “G: 7777”, and “DB-D” stores data 41 of “F: 6666”. Data 41 of “C: 3333” is stored in “DB-E”. Here, in FIG. 1, each data 41 is described in the format of “X: YYYY”, but the portion corresponding to “YYYY” indicates actual data such as a file or image data, and the portion corresponding to “X”. Is key information. The key information is information for identifying actual data. For example, the key information is a data ID, a file name, or an address where the data 41 is stored.

The common database 2 is a database 4 for copying and managing the data 41 of each database 4 in a unified manner, and stores read data information 21 and write data information 22 which will be described later.
The common database server 1 is a server that controls the common database 2, and generates and transmits messages and the like to collect copies of the data 41 of each database 4, and updates the data 41 updated in the common database 2 to each database 4. It has a function to reflect on.
In this way, by copying and managing the data 41 of each database 4 in the common database 2, the management can be facilitated without impairing the advantages of the distributed database system.

  Here, the message is information in which commands executed by each database server that has received the message and the common database server itself are stored. The message is generated in the common database 1 and transmitted by broadcast, so that the message is sent to each database server 3 in the information control system 10 and the common database server 1 itself. Then, the device that receives the message executes a command in the message, and has a function of collecting data 41 from the database 4 and writing the data 41 to the database 4 according to the command. For example, SQL (Structured Query Language) is used as the command.

Next, the configuration of the common database server 1, the database server 3, and the client terminal 5 according to the present embodiment will be described with reference to FIGS.
《Common database server》
FIG. 2 is a functional block diagram showing a configuration example of the common database server according to the present embodiment.
The common database server 1 includes a processing unit 100 that processes information, a transmission unit 110 that transmits data 41 and messages to the client terminal 5, and a reception unit 120 that receives data 41 and messages from the client terminal 5.
The processing unit 100 includes a read access cycle control unit 101, a write access cycle control unit 102, a data collection message issue unit 103, a data write message issue unit 104, a data write unit 105, a data read unit 106, and an access determination unit 107. And a registration message issuing unit 108.
When the data 41 is read by the application 501 (FIG. 4) executed on the client terminal 5, the read access cycle control unit 101 calculates the access cycle (read access cycle) and calculates the calculated read access cycle. Is reflected in the read data information 21 of the common database 2.
When the data 501 is written by the application 501 executed on the client terminal 5, the write access cycle control unit 102 calculates the access cycle (write access cycle), and calculates the calculated write access cycle. It has a function of reflecting in the write data information 22 of the common database 2.

The data collection message issuing unit 103 generates and transmits a data collection message 6 (FIG. 7) for collecting data 41 from each database 4 based on the read access cycle of the read data information 21 of the common database 2. Have
The data write message issuing unit 104 writes the data 41 updated in the common database 2 to the database 4 in which the data 41 is to be stored, based on the write access cycle of the write data information 22 in the common database 2. Thus, it has a function of generating and transmitting a data write message 7 (FIG. 12) for updating each database 4.

The data writing unit 105 reads the data 41 collected by the data collection message 6 or the information input from the client terminal 5 by using a command attached to the data collection message 6 (details will be described later), It has a function of writing to the write data information 22.
The data reading unit 106 has a function of reading data 41 to be written in the data write message 7 from the write data information 22.
The access determination unit 107 has a function of determining whether or not the read data information 21 and the write data information 22 are accessed by the client terminal 5 or the like.
The registration message issuing unit 108 has a function of generating and transmitting a registration message 8 (FIG. 16) having information of the database 4 when the database 4 is newly connected.

<Database server>
FIG. 3 is a functional block diagram showing a configuration example of the database server according to the present embodiment.
The database server 3 activates the command of the received data collection message 6 or data write message 7 and executes the command content, the data processing unit 301 that transmits the command content, the transmission unit 310 that transmits the message, and the reception unit 320 that receives the message. Have

<Client terminal>
FIG. 4 is a functional block diagram illustrating a configuration example of the client terminal according to the present embodiment.
The client terminal 5 has a plurality of applications 501.
The application 501 has a function of reading the data 41 stored in the common database 2 by accessing the common database 2 and writing the data 41 into the common database 2.

  2, the units 101 to 108 in the processing unit 100, the data processing unit 301 in FIG. 3, and the application 501 in FIG. 4 are HDDs (Hard Disk Drives) (not shown) of the devices 1, 3, and 5. The program stored in the program is implemented in a RAM (Random Access Memory) and executed by a CPU (Central Processing Unit).

<Reading data information>
FIG. 5 is a diagram illustrating an example of read data information according to the present embodiment.
The read data information 21 includes key information, data location, data, previous read access time, and read access cycle information.
As described above with reference to FIG. 1, the key information is information for identifying data. For example, the key information is a data ID, a file name, or an address where the data 41 is stored. . The data location is information about the database 4 in which the corresponding data 41 is stored (database name in FIG. 4). The data is actual data (second data). The data 41 stored in the common database 2 is a copy of the data 41 stored in each database 4. The previous read access time is the time at which the application 501 (FIG. 4) of the client terminal 5 last read-accessed the corresponding data 41. The read access cycle is a read access cycle by the application 501. Note that when there are a plurality of client terminals 5 on the information control system 10, the read access cycle is a read access cycle for all client terminals 5.

<Data information for writing>
FIG. 6 is a diagram showing an example of write data information according to the present embodiment.
The write data information 22 includes key information, data location, data, previous write access time, and write access cycle information.
The key information, data location, and data (third data) are the same as those in FIG. The previous write access time is the time when the application 501 (FIG. 4) of the client terminal 5 last accessed the corresponding data 41. The write access cycle is a cycle of write access by the application 501. Note that when there are a plurality of client terminals 5 on the information control system 10, the write access cycle is a write access cycle for all the client terminals 5.

<Data read processing>
Next, the data reading process according to the present embodiment will be described with reference to FIGS. 7 to 11 with reference to FIGS.
(Overview)
First, the outline of the data reading process of this embodiment will be described with reference to FIG. Detailed procedures in each process will be described later.
First, the application 501 of the client terminal 5 performs a read access for reading the data 41 of the common database 2 (S101), and the access determination unit 107 detects this read access (S102).
Then, the read access cycle control unit 101 calculates the read access cycle from the past read access time, and updates the read access cycle of the read data information 21 (S103). At this time, the read access cycle control unit 101 also updates the previous read access time of the read data information 21.

The data collection message issuing unit 103 of the common database server 1 generates a data collection message 6 based on the read access cycle of the read data information 21 at a predetermined time, and sends the data collection message to the information control system 10. 6 is broadcasted (S104).
In FIG. 7, a short cycle data collection message 6a and a long cycle data collection message 6b are generated and transmitted according to the length of the read access cycle.

The short-cycle data collection message 6a includes data 41 having a short read access cycle (in the example of FIG. 7, data corresponding to key information “A”, “B”, “C”, “D”, “F”). 41) is a data collection message 6 for collecting from each database 4.
The long-cycle data collection message 6b is data for collecting data 41 (data 41 corresponding to key information “E” and “G” in the example of FIG. 7) from each database 4 with a long read access cycle. This is a collection message 6.

  The short cycle data collection message 6a targets, for example, the data 41 whose read access cycle is 0 second to 1000 seconds, and the long cycle data collection message 6b includes, for example, the data 41 whose read access cycle is 1001 seconds or more. The data 41 to be collected is divided by the target. The short cycle data collection message 6a can be transmitted, for example, every 100 seconds, and the long cycle data collection message 6b can be transmitted, for example, every 2000 seconds. The read access cycle of 0 seconds is, for example, data 41 newly written in the common database 2 or the like.

Thus, by dividing the data collection message 6 according to the read access cycle and transmitting it, for example, it is possible to avoid generating and transmitting the data collection message 6 for every read access cycle, and to save communication resources. Can do.
In this embodiment, the data collection message 6 is divided into a short cycle and a long cycle. However, the data collection message 6 may be divided into three steps for short cycle, medium speed collection, and long cycle, or may be divided into four or more steps. . Further, the data collection message 6 may not be divided in this way. In this case, the data collection message 6 is generated and transmitted for every read access cycle.

  The data collection message 6 includes a header part and a command part (database search means). The header portion stores a header having information indicating that this message is a data collection message. In the command part, a command for acquiring data 41 from each database 4 is stored. The command is executed in the database server 3 when the database server 3 (not shown in FIG. 7) that controls and manages each database 4 obtains a message. When the database server 3 acquires the corresponding data 41 from the database 4 managed by the database server 3 according to the command, the database server 3 replaces the corresponding command part with the acquired data 41 and the corresponding key information (S105), and the data collection message 6 Broadcast. Note that “GET: X” such as “GET: A” and “GET: B” in FIG. 7 is a command for acquiring data 41 of key information “X”.

  When the data writing unit 105 receives the data collection message 6 (symbol 6c, 6d) that circulates all the database servers 3 (S106), the data writing unit 105 receives the data collection message 6 (6c, 6d) from the received data collection message 6 (S106). Each data 41 is extracted, and the data 41 is written in the read data information 21 according to the key information (S107) and simultaneously written in the write data information 22 (not shown in FIG. 7).

Next, detailed procedures of each process will be described with reference to FIGS.
(Read access cycle update processing)
FIG. 8 is a flowchart showing a procedure of read access cycle update processing according to the present embodiment.
First, the access determination unit 107 determines whether or not the read access to the read data information 21 has been performed by the application 501 (S201). The process of step S201 is a process corresponding to step S102 of FIG.
When the read access is not performed (S201 → No), the access determination unit 107 returns the process to step S201.
When the read access is performed (S201 → Yes), the read access cycle control unit 101 reads the previous read access time of the corresponding data 41 from the read data information 21, and reads the difference with the current time. An access cycle is calculated (S202).
Here, the difference between the current read access time (current time) and the previous read access time is defined as the read access cycle. However, the present invention is not limited to this, and all read access times are stored and all of these read access times are stored. It may be an average value between access times, or an average value for the past five times.

Next, the read access cycle control unit 101 refers to the corresponding read access cycle in the read data information 21, and determines whether or not the read access cycle has changed (S203).
As a result of step S203, when the read access cycle has not changed (S203 → No), the read access cycle control unit 101 advances the processing to step S205.
If the read access cycle has changed as a result of step S203 (S203 → Yes), the read access cycle control unit 101 updates the corresponding read access cycle in the read data information 21 to the read access cycle calculated in step S202. (S204). The process of step S204 is a process corresponding to step S103 of FIG.
Subsequently, the read access cycle control unit 101 updates the previous read access time in the read data information 21 to the current time (S205), and returns the process to step S201.

(Data collection message issue processing)
FIG. 9 is a flowchart showing a procedure of data collection message issuing processing according to the present embodiment. 9 is performed for each short-cycle data collection message 6a and long-cycle data collection message 6b in FIG. 7, for example, so that the short-cycle data collection message 6a and long-cycle as shown in FIG. The data collection message 6b can be generated and transmitted.
First, the data collection message issuing unit 103 determines whether or not the data collection message generation time has come (S301).

As a result of step S301, when the data collection message generation time has not come (S301 → No), the data collection message issuing unit 103 returns the process to step S301.
If the result of step S301 is the data collection message generation time (S301 → Yes), the data collection message issuing unit 103 refers to the read access cycle, acquires the key information of the corresponding data 41, and stores this key information. A data collection message 6 having a command for acquiring the corresponding data 41 from each database 4 is generated (S302). Here, for example, if the target data collection message 6 is for a short cycle, the data collection message issuing unit 103 refers to the read access cycle of the read data information 21 and corresponds to the short cycle condition. Get key information.
The data collection message issuing unit 103 broadcasts the generated data collection message 6 (S303), and returns the process to step S301. The process in step S303 is a process corresponding to step S104 in FIG.

  For example, when the read access cycle changes from a short cycle to a long cycle, the data 41 collected in the short cycle data collection message 6a (FIG. 7) is changed to the long cycle data collection message 6b (FIG. 7). ) Will be collected. In this way, it is possible to flexibly cope with changes in the read access cycle.

(Data acquisition process)
FIG. 10 is a flowchart showing a procedure of processing for acquiring data from the database according to the present embodiment.
First, when the data processing unit 301 receives the data collection message 6 (S401), the command added to the data collection message 6 is executed (S402).
When the command is executed, the data processing unit 301 searches the database 4 managed by itself for key information described in the command. Here, a return value is returned as a result of command execution. When the corresponding key information is not stored in the database 4 (when not stored), a predetermined code is returned as the return value. When the corresponding key information is stored in the database 4, the key is used as the return value. Data 41 corresponding to the information is returned.

The data processing unit 301 detects a return value returned as a result of the search, and determines whether or not the return value is a predetermined code indicating non-storage of key information (S403).
As a result of step S403, when the return value is a predetermined code indicating that the key information is not stored (S403 → Yes), the data processing unit 301 advances the process to step S406.
As a result of step S403, when the return value is not a predetermined code indicating that the key information is not stored (S403 → No), that is, when the data 41 corresponds to the key information, the data processing unit 301 sets the return value as the return value. (41), and replaces the portion of the command to be executed in the data collection message 6 with the acquired data 41 and key information corresponding to the data 41 (S405). Here, the process of step S404 is a process corresponding to step S105 of FIG. By replacing the command with the data 41 in this manner, the database server 3 that has received the data collection message 6 next time does not execute the corresponding command, thereby improving efficiency. Note that the process of step S405 can be omitted.

Next, the data processing unit 301 determines whether all commands existing in the data collection message 6 have been executed (S406).
If all the commands existing in the data collection message 6 have not been executed as a result of step S406 (S406 → No), the data processing unit 301 returns the processing to step S402 and executes the next command.
If all the commands existing in the data collection message 6 are executed as a result of step S406 (S406 → Yes), the data processing unit 301 broadcasts the data collection message 6 (S407).

(Data writing process)
FIG. 11 is a flowchart showing the procedure of the data writing process to the read data information according to the present embodiment.
When the data writing unit 105 receives the data collection message 6 (S501), it is determined whether there is no command in the received data collection message 6 (S502). Here, the process of step S501 is a process corresponding to step S106 of FIG.
If there is even one command as a result of step S502 (S502 → No), the data writing unit 105 regards this data collection message 6 as not having traveled all of the necessary database servers 3, and received data The collected message 6 is discarded (S503), and the process returns to step S501.
If there is no command in the received data collection message 6 as a result of step S502 (S502 → Yes), the data writing unit 105 considers that all of the database servers 3 that require the data collection message 6 have been visited. The data 41 is extracted from the data collection message 6 together with the corresponding key information (S504).

Then, the data writing unit 105 stores the extracted data 41 as the data 41 of the reading data information 21 using the key information as a key (S505). The process of step S505 is a process corresponding to step S107 of FIG.
Next, the data writing unit 105 determines whether or not there is access to the corresponding data 41 in the writing data information 22 (S506).
As a result of step S506, when there is access to the corresponding data 41 in the write data information 22 (S506 → Yes), the data writing unit 105 returns the process to step S506.
If there is no access to the corresponding data 41 in the write data information 22 as a result of step S506 (S506 → No), the data writing unit 105 writes the data 41 extracted in step S504 using the key information as a key. The data 41 is stored as the data 41 of the included data information 22 (S507), and the process returns to step S501.

  In the present embodiment, a message is used to collect data 41 from each database 4. However, the present invention is not limited to this, and the common database server 1 executes a command for directly collecting data 41 from the database 4 to be collected. May be performed.

<Data writing process>
Next, the data writing process according to the present embodiment will be described with reference to FIGS. 12 to 15 with reference to FIGS.
(Overview)
First, the outline of the data writing process of this embodiment will be described with reference to FIG. Detailed procedures in each process will be described later.
First, the application 501 of the client terminal 5 performs a write access for writing the data 41 to the common database 2 (S601).
When the access determination unit 107 detects this write access (S602), the write access cycle control unit 102 calculates the write access cycle from the past write access time, and writes the write data information 22 The access cycle is updated (S603). At this time, the write access cycle control unit 102 also updates the previous write access time of the write data information 22.

When the predetermined time comes, the data reading unit 106 acquires the key information and the data 41 from the write data information 22 based on the write access cycle of the write data information 22 (S604). Then, the data write message issuing unit 104 generates a data write message 7 for writing the key information acquired by the data reading unit 106 and the data 41 to each database 4, and sends the data write message 7 to the information control system 10. The generated data write message 7 is broadcasted (S605).
In FIG. 12, a short cycle data write message 7a and a long cycle data write message 7b are generated and transmitted according to the length of the read access cycle.

The short-cycle data write message 7a corresponds to data 41 having a short write access cycle (in the example of FIG. 12, corresponding to key information “A”, “B”, “C”, “D”, “F”) This is a data write message 7 for writing the data 41) to be written into each database 4.
The long cycle data write message 7b is used to write the data 41 having a long write access cycle (data 41 corresponding to the key information "E" and "G" in the example of FIG. 12) to each database 4. Data write message 7

  The short cycle data write message 7a targets, for example, the data 41 having a write access cycle of 0 second to 1000 seconds, and the long cycle data write message 7b has, for example, a write access cycle of 1001 seconds or more. Thus, the data 41 to be written is divided. The short cycle data write message 7a can be transmitted, for example, every 100 seconds, and the long cycle data write message 7b can be transmitted, for example, every 2000 seconds. The write access cycle of 0 seconds is, for example, data 41 newly written in the common database 2 or the like.

Thus, by dividing the data write message 7 according to the write access cycle and transmitting it, for example, it is possible to avoid generating and transmitting the data write message 7 for every write access cycle. Can be saved.
In this embodiment, the data write message 7 is divided into a short cycle and a long cycle. However, the data write message 7 is divided into three phases for short cycle, medium speed writing, and long cycle, or divided into four or more phases. Also good. Further, the data write message 7 may not be divided in this way. In this case, the data write message 7 is generated and transmitted for every write access cycle.

  The data write message 7 is composed of a header part and a command part (database writing means). The header portion stores a header having information indicating that the message is for data writing. In the command portion, a command for writing data 41 to each database 4 is stored. The command is executed in the database server 3 when the database server 3 (not shown in FIG. 12) that controls and manages each database 4 acquires a message. The database server 3 writes the data 41 to the database 4 managed by the database server 3 according to the command (S606). At this time, the database server 3 may delete the corresponding command part. Note that “PUT: X” in FIG. 12 is a command for writing the data 41 added after this command using the key information “X” as a key. Actually, information indicating how many bytes of data 41 are written after the command is added together with “PUT: X”, but the illustration is omitted here.

Next, detailed procedures of each process will be described with reference to FIGS.
(Write access cycle update processing)
FIG. 13 is a flowchart showing the procedure of the write access cycle update process according to this embodiment.
First, the access determination unit 107 determines whether or not a write access to the write data information 22 has been performed by the application 501 (S701). The process in step S701 is a process corresponding to step S602 in FIG.
As a result of step S701, when the write access is not performed (S701 → No), the access determination unit 107 returns the process to step S701.
As a result of step S701, when the read access is performed (S701 → Yes), the data 41 sent from the application 501 is accompanied by key information, so the data writing unit 105 writes the data information 22 for writing. The data 41 is stored using the key information sent from the application 501 as a key (S702). That is, the key information is input to the common database server 1 when the user inputs a file name or folder name in which data is to be stored.

Next, the write access cycle control unit 102 acquires the corresponding previous write access time, and calculates the write access cycle by taking the difference between the acquired previous write access time and the current time (S703). ).
Here, the difference between the current write access time and the previous write access time is defined as the read access cycle. However, the present invention is not limited to this, and all the write access times are stored and all the write access times are stored. It may be an average value between access times, or may be an average value for the past five times.

Next, the write access cycle control unit 102 refers to the corresponding write access cycle in the write data information 22 and determines whether or not the write access cycle has changed (S704).
If the result of step S704 is that the write access cycle has not changed (S704 → No), the write access cycle control unit 102 advances the processing to step S706.
If the read access cycle has changed as a result of step S704 (S704 → Yes), the write access cycle control unit 102 writes the write access cycle corresponding to the write data information 22 in step S703. The access cycle is updated (S705). The process in step S705 is a process corresponding to step S603 in FIG.
Subsequently, the write access cycle control unit 102 updates the previous write access time of the write data information 22 to the current time (S706).

Next, the data writing unit 105 determines whether or not there is access to the corresponding data 41 in the read data information 21 (S707).
As a result of step S707, when there is access to the corresponding data 41 in the read data information 21 (S707 → Yes), the data writing unit 105 returns the process to step S707.
If there is no access to the corresponding data 41 in the read data information 21 as a result of step S707 (S707 → No), the data writing unit 105 has no access to the corresponding data 41 in the read data information 21. The data 41 sent from the application 501 is stored as the data 41 of the read data information 21 using the key information as a key (S708).

(Data write message issue processing)
FIG. 14 is a flowchart showing the procedure of the data write message issuing process according to the present embodiment. 14 is performed for each short cycle data write message 7a and long cycle data write message 7b in FIG. 12, for example, so that the short cycle data write message 7a as shown in FIG. A long period data write message 7b can be generated and transmitted.
First, the data write message issuing unit 104 determines whether or not the data write message 7 generation time has come (S801).
As a result of step S801, when it is not the data write message generation time (S801 → No), the data write message issuing unit 104 returns the process to step S801.
If the result of step S801 is the data write message generation time (S801 → Yes), the data write message issuing unit 104 refers to the write access cycle and acquires the key information and the data 41 of the corresponding data 41. Then, a data write message 7 having a command for writing the data 41 to each database 4 is generated (S803). Here, the process of step S802 is a process corresponding to step S604 of FIG. Further, for example, if the target data write message 7 is for a short cycle, the data write message issuing unit 104 refers to the write access cycle of the write data information 22, and Key information and data 41 corresponding to the condition are acquired. If the data 41 is newly created, information on the stored database 4 is also added.
Then, the data write message issuing unit 104 broadcasts the generated data write message 7 (S804), and returns the process to step S801. Note that the process of step S804 is a process corresponding to step S605 of FIG.

  When the access cycle is changed, for example, when the access cycle is changed from a short cycle to a long cycle, this data 41 is written in the database 4 by the short cycle data write message 7a. It is written by the write message 7b. In this way, it is possible to flexibly cope with changes in the write access cycle.

(Data writing process)
FIG. 15 is a flowchart showing a processing procedure for writing data to the database server according to the present embodiment.
First, when the data processing unit 301 receives the data write message 7 (S901), the command added to the data write message 7 is executed (S902).
When the command is executed, the data processing unit 301 searches the database 4 managed by itself for key information described in the command. Here, a return value is returned as a result of command execution. When the corresponding key information is not stored in the database 4 (when not stored), the first code is returned as a return value. When the corresponding key information is stored in the database 4, the return value is For example, a second code is returned.

  When the second code is returned as the return value, if the information of the database 4 is added together with the command (when the data is newly written data), the information of the data 4 is also referred to and It is also determined whether or not it corresponds to the database 4. This determination result is also returned as a return value. When the information of the database 4 added together with the command is not information about the own database 4, the first code is returned, and when the information is about the own database 4, for example, A second code is returned.

The data processing unit 301 detects a return value returned as a result of the search, and determines whether this return value is a first code indicating non-storage of key information (S903).
As a result of step S903, when the return value is the first code indicating that the key information is not stored (S903 → Yes), the data processing unit 301 advances the process to step S906.
As a result of step S903, if the return value is not the first code indicating that the key information is not stored (S903 → No), that is, if the return value is the second code indicating that the key information is stored, the data The processing unit 301 writes the data 41 using the key information as a key (S904). Here, the process of step S904 is a process corresponding to step S606 in FIG.

  After step S904, the data processing unit 301 deletes the command and data 41 to be processed (S905). As described above, after the data is written, the command and data 41 are deleted from the data write message 7 so that the database server 3 that has received the data write message 7 next does not execute this command. Thus, efficiency can be improved. Note that the process of step S905 can be omitted.

Next, the data processing unit 301 determines whether or not all commands existing in the data write message 7 have been executed (S906).
If all the commands present in the data write message 7 have not been executed as a result of step S906 (S906 → No), the data processing unit 301 returns the process to step S902 and executes the next command.
As a result of step S906, when all commands existing in the data write message 7 are executed (S906 → Yes), the data processing unit 301 broadcasts the data write message 7 (S907).

  In the present embodiment, a message is used to write data 41 to each database 4. However, the present invention is not limited to this, and the common database server 1 executes a command for directly writing data 41 to the data write target database 4. May be performed.

<When connecting to a new database>
Next, the operation of the information control system 10 when the database 4 is newly connected will be described with reference to FIGS.
(Overview)
First, an overview of the new database connection process according to the present embodiment will be described with reference to FIG. Detailed procedures in each process will be described later.
As shown in FIG. 16, “DB-X” is newly connected to the information control system 10 to which the databases 4 of “DB-A” to “DB-E” are connected (S1001).
Then, the administrator makes a registration message issuance request to the common database server 1 via the client terminal 5 (S1002).
The registration message issuing unit 108 of the common database server 1 that has received the registration message transmission request issues the registration message 8 and broadcasts the registration message 8 to the information control system 10 (S1003).

As shown in FIG. 16, the registration message 8 includes a header part and a command part.
The header portion stores information indicating that the message is a registration message. The command section stores key information written in the read data information 21 and write data information 22 and information on the database 4 drawn in the data location column.
By attaching information indicating that the message is for registration to the header part, even if each database server 3 receives this registration message 8, the command is not executed, and only the common database server 1 The command can be executed.

  When the common database server 1 receives the registration message 8 broadcasted (S1004), the data writing unit 105 reads the data contents stored in the registration message 8 into the reading data information 21 and the writing data information 22. Is newly registered as reference data (S1005). Here, the reference data is key information and data location in the read data information 21 and the write data information 22 and is information used when referring to the data. At this time, the information registered as the reference data for the read data information 21 and the write data information 22 is only the key information and the data location. The data 41, the previous read access time, the previous write access time, the read Each column of the access cycle and the write access cycle is blank.

Thereafter, the data 41 is collected or the data 41 written in the common database 2 is reflected in each database 4 by the method described above.
Alternatively, the read access cycle and the write access cycle may be temporarily set to 0 seconds, and the short-cycle data collection message 6a (FIG. 7) may be issued to collect the target data 41. Alternatively, the data collection message issuing unit 103 may generate and transmit the data collection message 6 at the same time when registration of the reference data is detected.
When the common database 2 and the common database server 1 are connected to the information control system 10 for the first time, the common database server 1 issues and transmits a registration message 8 in which information for all the databases 4 is stored.

(Registration message issuing process)
FIG. 17 is a flowchart showing a procedure of registration message issuing processing according to the present embodiment.
When the registration message issuing unit 108 receives the registration message issue request transmitted from the client terminal 5 (S1101), the registration message issuing unit 108 sends a registration message 8 having reference data such as key information and data location information. Generate (S1102). Here, the process of step S1101 is a process corresponding to step S1002 of FIG. The key information may be newly issued by the registration message issuing unit 108, or may be information input by the administrator via an input unit (not shown) of the client terminal 5. The data location information is information input by the administrator through an input unit (not shown) of the client terminal 5.
Then, the registration message issuing unit 108 broadcasts the registration message 8 (S1103). Note that the processing in step S1103 is processing corresponding to step S1003 in FIG.

(Reference data registration process)
FIG. 18 is a flowchart showing a procedure of reference data registration processing according to the present embodiment.
When the data writing unit 105 receives the registration message 8 (S1201), the command of the registration message 8 is executed (S1202). Here, step S1201 is processing corresponding to step S1004 of FIG.
Then, the reference data stored in the registration message 8 is registered in the read data information 21 and the write data information 22 in accordance with the command (S1203). Note that the processing in step S1203 is processing corresponding to step S1005 in FIG.

  In the present embodiment, the message is used to register the reference data in the new database 4. However, the present invention is not limited to this, and the reference data input from the client terminal 5 is read data information 21 and write data. It may be performed by the common database server 1 executing a command for directly registering in the information 22.

  In this way, even if the database 4 is newly connected, it is possible to easily manage the data 41 while maintaining the distribution of the data 41.

<< System construction example >>
Next, with reference to FIG. 19A to FIG. 19D, a construction example of the information control system 10 in the present embodiment will be described.
First, in FIG. 19A, there are independent systems 9A, 9B, and 9C having a client terminal 5, a database server 3, and a database 4, respectively.
In FIG. 19B, each of the systems 9A, 9B, and 9C is connected to form one system Z.
In FIG. 19C, the common database server 1 and the common database 2 according to the present embodiment are connected to the system 9C. At this time, the reference data of the registration message 8 in the process at the time of connecting to the new database described with reference to FIGS. Data is registered in the common database 2. Subsequently, the data collection described in FIGS. 7 to 11 is performed, so that the data 41 in the database 4 is collected in the common database 2.
Then, the system 9D is newly added in FIG. 19D, and the process at the time of connecting to the new database described with reference to FIGS.

According to the present embodiment, the common database 2 that stores a copy of each database 4 is provided, and the data 41 of each database 4 is set at regular intervals determined based on the access cycle (read access cycle / write access cycle). By copying to the common database 2, it becomes possible to perform unified management of the data 41 while maintaining the advantages of the distributed database 4, and to facilitate the management of the distributed database.
Further, based on the access cycle, frequently accessed data 41 is frequently rewritten, and data 41 with low access frequency is rewritten in a long cycle, so that communication resources can be used efficiently.
Even if the database 4 is newly connected, the data collection by the data collection message 6 is performed only by inputting the key information and the data location information from the client terminal 5, so that the new database 4 The system can be flexibly constructed even when added.

1 Common database server (common database controller)
2 Common database 3 Database server (database management device)
4 Database 5 Client Terminal 6 Data Collection Message 7 Data Write Message 8 Registration Message 10 Information Control System 21 Read Data Information (Stores Second Data)
22 Data information for writing (4th data is stored)
41 data (first data, third data)
DESCRIPTION OF SYMBOLS 101 Read access period control part 102 Write access period control part 103 Data collection message issuing part 104 Data write message issuing part 105 Data writing part 106 Data reading part 107 Access judgment part 108 Registration message issuing part 301 Data processing part 501 application

Claims (12)

Information control method by information control system comprising: at least one client terminal; a plurality of databases; at least one common database; a common database control device that controls the common database; and a database management device that manages the database Because
The common database corresponds to the second data, which is a copy of the first data stored in each database, and the access cycle when the client terminal reads and accesses the second data. Attached and stored,
The common database controller, according to the previous SL access cycle,
A command for causing the database management device to perform a search process for searching the first data stored in the database and a transmission process for transmitting the first data searched by the search process is stored. Generates a message that
Broadcast the generated message,
The database management device that has received the broadcast-transmitted message,
If the database to be searched indicated by the message is a database managed by the search processing in the command stored in the received message, the first database is first extracted from the database according to the command of the message. Data for
Further, by the transmission process in the command, the acquired first data is stored in the message and broadcasted,
The common database controller is
The information control method characterized by storing the first data stored in the message broadcasted from the database management device as the second data in the common database. The common database controller is
Rotates all the database management devices that are to be visited, stores information on all the database management devices that are to be visited, and extracts the first data from the message returned to itself And
The extracted first data is stored in the common database as the second data.
The information control method according to claim 1. The common database controller is
Monitoring the access cycle;
The information control method according to claim 1, wherein when the access cycle changes, information on the access cycle stored in the common database is updated. The common database controller is
The information control method according to claim 1, wherein the messages are grouped according to the access period. The common database stores information related to the database,
The common database controller is
2. When a database is newly connected to the information control system, information related to the connected database input via the client terminal is stored in the common database. Information control method described in 1. Information control method by information control system comprising: at least one client terminal; a plurality of databases; at least one common database; a common database control device that controls the common database; and a database management device that manages the database Because
The common database includes fourth data that is a copy of third data stored in each database, and an access cycle when the client terminal performs write access to the fourth data. Stored in correspondence,
The common database controller, according to the previous SL access cycle,
To cause the database management apparatus to perform a writing process of writing the fourth data stored in the common database to the database storing the third data corresponding to the fourth data And a message in which the fourth data is stored,
Broadcast the generated message,
The database management device that has received the broadcast-transmitted message,
When the database that is the target of the writing process in the command stored in the received message is a database that is managed by itself, the writing process of the command in the message causes the database to An information control method characterized by writing fourth data . The common database controller is
Monitoring the access cycle;
The information control method according to claim 6, wherein when the access cycle changes, information on the access cycle stored in the common database is updated. The common database controller is
The information control method according to claim 6, wherein the messages are grouped according to the access cycle. The common database stores information related to the database,
The common database controller is
7. When a database is newly connected to the information control system, information related to the connected database input via the client terminal is stored in the common database. Information control method described in 1. Program for executing the information control method according to the computer in any one of claims 1 to 9. At least one client terminal;
Multiple databases,
Second data, which is a copy of the first data stored in each database, and an access cycle when the client terminal performs read access to the second data are stored in association with each other. At least one common database;
According to the access cycle, the database management device is caused to perform a search process for searching the first data stored in the database and a transmission process for transmitting the searched first data by the search process. A message storing a command is generated, the generated message is broadcasted, and the first data stored in the broadcast-transmitted message from the database management apparatus is used as the second data. A common database controller to store in the database;
When the broadcast-transmitted message is received, the search target database indicated by the message by the search processing in the command stored in the received message is a database managed by itself, A database management device that acquires first data from the database according to the command of the message, and further stores and transmits the acquired first data in the message by the transmission processing in the command; and
An information control system comprising: At least one client terminal;
Multiple databases,
The fourth data, which is a copy of the third data stored in each database, and the access cycle when the client terminal performs write access to the fourth data are stored in association with each other. At least one common database;
Write processing for writing the fourth data stored in the common database to the database storing the third data corresponding to the fourth data in the database management device according to the access cycle A common database control device that generates a message storing the command and the fourth data, and broadcasts the generated message ;
When the broadcast-transmitted message is received, if the database that is the target of the writing process in the command stored in the received message is a database that is managed by itself, the command in the message A database management device for writing the fourth data to the database by the writing process;
An information control system comprising:

Images