JP2002007176A - Data control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that it is impossible to dynamically define any data structure definition since a data object input device 1 and a data object controller 2 are respectively provided with data structure definitions 5 and 10 in a conventional distributed object data control system, and that the contents are not fixed. SOLUTION: A data object controller 2 for storing a data object inputs a data structure by a data structure inputting part 16, and changes data structure definition 10 by using this, and transmits the changed data as a processing request message to a data object inputting device 1. The data object inputting device 1 which receives the processing request message changes data structure definition 5 by a processing request message analyzing part 25 and a data structure control part 24 by using the received processing request message, and dynamically changes the data structure definitions 10 and 5 of the data object controller 2, and the data object inputting device 1.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a data management system for dynamically managing data objects when distributed processing is performed by an information processing apparatus or an information communication system.

[0002]

2. Description of the Related Art Japanese Patent Application Laid-Open No. 9-34823 describes management of association between data objects in a distributed processing system.
Is disclosed in Japanese Patent Application Laid-Open Publication No. H10-209,878. FIG. 14 is a configuration diagram showing a conventional data management system. 14, 1 is a data object input device, 2 is a data object management device, and 3 is a data object input device 1.
2 shows a communication path connecting the data object management device 2 to the data object management device 2.

Next, the data object input device 1 will be described. 4 is a data object input unit for inputting data objects, 5 is a data structure definition defining the structure of the data object, and 6 is a data structure definition for the input data object, which is defined in advance in the system. An object generation unit that generates a data object entity by processing; a processing request message generation unit that edits a message for requesting the data object management device 2 to perform processing; Communication processing units for transmitting and receiving messages, and 4 to 8 constitute the data object input device 1.

Next, the configuration of the data object management device 2 will be described. Reference numeral 9 denotes a data object operation unit that performs addition, deletion, and editing operations on stored data objects, 10 denotes a data structure definition that defines the structure of the data object, and 11 denotes a data object input from the data structure definition 10. A data object retrieval unit for retrieving a data item, a processing request message analysis unit for analyzing a processing request message received from the data object input device 1, a data object storage unit for storing a received data object, and a data object storage unit A communication processing unit for transmitting / receiving a processing request message to / from the object input device 1, and 9 to 14 constitute the data object management device 2.

FIG. 15 is a flowchart showing the processing of the data object input device of the conventional data management system. Next, the processing of the data object input device 1 will be described using the procedure shown in FIG. As shown in FIG. 15, when a new data object is input from the data object input unit 4, the data object generation unit 6 refers to the data structure definition 5 to determine whether the input data object is defined in the system. Is determined (step 1502). If the data object is valid, an entity of the data object is created (step 1503). Next, a processing request message is created from the entity of the object created in step 1503 (step 1504). Next, the generated data processing request message is transmitted to the data object management device 2.
Is transmitted (step 1505), and the process ends (step 1506).

FIG. 16 is a flowchart showing the processing of the data object management device of the conventional data management system. Next, the processing of the data object management device 2 will be described with reference to FIG. As shown in FIG. 16, following the initial processing start step 1601, a process request message is received in step 1602, and step 1 is executed.
At 603, the received processing request message is analyzed to obtain a data object to be operated. Step 160
In step 4, it is determined whether the data item in the received data object is valid with reference to the data structure definition 10 defined in the own device. If the data item is valid, the received data object is stored in the data object storage unit 13 by the data object operation unit 9 in step 1605. According to the above-described procedure, it is possible to add / delete / change the data object input by the data object input device 1 according to the data structure in the data object management device 2.

[0007]

In the conventional distributed object data management system, the data structure definitions 5 and 10 are provided in both the data object input device 1 and the data object management device 2, and the contents are fixed. Therefore, there has been a problem that the data structure definition cannot be changed dynamically.

The present invention has been made to solve the above-described problem, and has as its first object to obtain a data management system capable of dynamically changing the structure definition of a data object. . It is a second object of the present invention to provide a data management system capable of correctly changing a data structure definition even when a communication path is disconnected.

[0009]

A data management system according to the present invention has a first data structure definition defining a structure of a data object, and inputs a data object by referring to the first data structure definition. And a second device that stores a data object input by the first device with reference to the second data structure definition, and a second data structure definition that defines the structure of the data object. Device, the second device has a second change means for changing the second data structure definition, when the change by the second change means has been performed, the changed data to the first device And the first device is configured to change the first data structure definition using the change data transmitted by the second device.

A first device for defining a structure of a data object has a first data structure definition defining a structure of the data object, and a first device for inputting a data object with reference to the first data structure definition, and defining a structure of the data object. A second device for storing a data object input by the first device with reference to the second data structure definition, wherein the first device has a second data structure definition. Having a first change means for changing the first data structure definition with the input, when the change by the first change means is performed, and transmits the change data to the second device,
The second device is configured to change the second data structure definition using the change data transmitted by the first device. Further, the second device changes the second data structure definition after confirming that the change data transmitted from the first device does not duplicately change the second data structure definition. .

Further, the first device has a first message storage unit for storing change data to be transmitted. In addition, the second device has a second message storage unit that stores change data to be transmitted.

The change of the first data structure definition by the first device and the change of the second data structure definition by the second device are uniquely set to represent the data structure in the data structure definition. This is performed based on the data item. Furthermore, the data object is
The data items are classified according to the data type, and the data items are set in common for all the data types.

The data objects are classified by data type, and the data structure definition includes a virtual data structure definition commonly set for all data types.
It has an actual data structure definition associated with this virtual data structure definition and set for each data type.
Either one or both of the first device and the second device have a change history storage unit for storing a change history when a data structure definition is changed.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 FIG. 1 is a configuration diagram showing a data management system according to Embodiment 1 of the present invention. In FIG. 1, 1 is a data object input device as a first device, 2 is a data object management device as a second device, and 3 is a data object input device 1
4 shows a communication path connecting the data object management device and the data object management device. 5 is a data structure definition (first data structure definition) which defines the structure of the data object in the data object input device 1, and 8 is a data structure definition which is in the data object input device 1 and the data object management device 2. It is a communication processing unit that sends and receives messages. Reference numeral 10 denotes a data structure definition (second data structure definition) that defines the structure of the data object, and reference numeral 14 denotes a data object management device 2 that defines the data object structure. A communication processing unit that transmits and receives a processing request message.

Next, the configuration of the data object management device 2 will be described. 16 is a data structure input processing unit for inputting a data structure, 17 is a data object analysis unit for analyzing the input data structure, and 19 is an ID (data item unique to the data item) with reference to the data structure definition 10. No. 16, 17 and 19 are data item determination means to which No. is assigned.
A processing request message generator 20 edits a message for notifying the data object input device 1 that the data structure has been changed.
16, 17, 19, and 20 constitute the data object management device 2.

Next, the data object input device 1 will be described. 23, a data object generation unit that generates a data object with reference to the data structure definition 5;
Reference numeral 4 denotes a data structure management unit that detects a change from the data structure definition 5 based on the processing request message received from the data object management device 2 and operates the data structure definition 5.
Reference numeral 5 denotes a processing request message analysis unit for analyzing the processing request message received from the data object management device 2. Reference numerals 5, 8, 23 to 25 constitute the data object input device 1.

FIG. 2 is a diagram showing a structure of a processing request message transmitted and received between the data object input device and the data object management device of the data management system according to the first embodiment of the present invention. In FIG. 2, reference numeral 31 denotes a data structure identifier which is a unique identifier representing the type of a data object. Reference numeral 32 denotes a key when the data structure is managed by the data object analysis unit 17 and the data structure management unit 24. I unique within the structure
The data item No. 33 which is D is a data object and includes its reference.

FIG. 3 is a flowchart showing processing of the data object management device of the data management system according to the first embodiment of the present invention. FIG. 4 is a flowchart showing processing of the data object input device of the data management system according to the first embodiment of the present invention.

Next, the operation of the data object management device 2 will be described using the procedure shown in FIG. As shown in FIG. 3, when a data item that is a data structure component is newly input from the data structure input unit 16 (step 0302), the data item definition unit 19 in the data object analysis unit 17 causes the data structure definition unit 19 to execute the data structure definition. 10
To determine whether the input data item already exists in the data structure (step 030).
3). Next, in step 0304, if the input data item No. is a new data item, a new data item No. is acquired, and the data item is added to the data structure (step 0305). The processing request message generator 20 acquires the data item No. from the data structure definition 10 (step 0306), and generates a processing request message (step 0307). next,
The generated processing request message is transmitted, and the processing ends (step 0308).

Next, the operation of the data object input device will be described using procedure 0400 shown in FIG.
As shown in FIG. 4, when the processing request message transmitted from the data object management device 2 is received (Step 0402), the processing request message is analyzed, and the data structure identifier and the data item No. are obtained (Step 04).
03). Next, with reference to the data structure definition 5, it is determined whether the received data item No. is defined in the data structure (step 0404). If the data item does not exist (step 0405), the data structure definition 5
, The data item No. in the received processing request message is added (step 0406), and the fact that the data structure has been changed is notified to the data object generation unit 23 (step 0407), and the processing is terminated. (Step 0412).

As described above, according to the first embodiment, even when a data structure item is newly added by the data structure input unit in the data object management device in the data object generation in the distributed environment, the data item is generated. By uniquely managing No. and analyzing the data structure in the data object input device, the data structure can be dynamically changed.

Embodiment 2 FIG. FIG. 5 is a configuration diagram showing a data management system according to Embodiment 2 of the present invention.
In FIG. 5, 1 to 10 and 14 are the same as those in FIG. Reference numeral 17 denotes a data object analysis unit for analyzing a data structure in the data object management device 2, and reference numeral 35 denotes a data object analysis unit for analyzing a data item when data is input from the data object input unit 4 in the data object input device 1. And constitutes a first changing means. Reference numeral 36 denotes a data item duplication determination unit provided in the data object analysis unit 17 and determining duplication of data items.

FIG. 6 is a flowchart showing processing of the data object input device of the data management system according to the second embodiment of the present invention. FIG. 7 is a flowchart showing processing of the data object management device of the data management system according to Embodiment 2 of the present invention.

In the first embodiment, it is necessary to define a data structure before inputting data. In the second embodiment, however, a data object analyzing unit for analyzing a data object from the data object input unit 4 is used. 35
Thus, it is possible to change the data structure as needed while inputting data without defining the data structure in advance.

Next, the operation of the data object input device will be described with reference to FIG. First, when a data object is input (step 0602), the data object is transmitted to the data object analysis unit 35, and the data item in the input data object is defined in the data structure definition 5 with reference to the data structure definition 5. It is determined whether or not it has been performed (step 0603). When the same data item does not exist (step 0604)
Assigns a new data item number in the data object analysis unit 35 (step 060).
5). The data object generation unit 6 acquires the data item No. corresponding to the data item of the input data object (step 0606), and generates the data object (step 0607). Next, a processing request message is generated based on the generated data object and data item No. (step 0608),
The data is transmitted to the data object management device 2.

In the data object management device 2, FIG.
As shown in (1), when the processing request message is received (Step 0702), the processing request message analysis unit 12 acquires the data structure identifier and the data item No (Step 0703). Next, the data item duplication determination means 36 determines whether the received data item No. exists in the data structure definition 10 with reference to the data structure definition 10 (step 0704). Data structure definition 1
If there is no data item corresponding to 0 (Step 0705), the received data item is added to the data structure definition 10 (Step 0706), and the data item operation unit 9 is notified (Step 0707).

As described above, according to the second embodiment, even when a data structure definition is not prepared in advance, a corresponding data structure definition is automatically and dynamically generated simply by inputting a data object. be able to. Further, even when a data item is defined from a plurality of data input devices, it is possible to prevent a plurality of identical data items from being defined by the data item duplication determination means.

Embodiment 3 FIG. 8 is a configuration diagram showing a data management system according to Embodiment 3 of the present invention.
8, 1 to 10, 12, 14, 17, 35, 3
6 is the same as that in FIG. Reference numeral 37 denotes a message storage unit that stores a processing request message that the communication processing unit 8 could not transmit, and is a first message storage unit. Reference numeral 38 denotes a message storage unit of the communication processing unit 14, which is a second message storage unit. In the third embodiment, when the communication processing unit cannot transmit the processing request message,
The difference is that a message storage unit for storing the processing request message is provided. FIG. 9 is a flowchart showing processing of the data object input device of the data management system according to Embodiment 3 of the present invention.

The operation of the third embodiment will be described below.
Only differences from the second embodiment will be described with reference to FIG. In the second embodiment, when the communication path 3 is disconnected, the processing request message cannot be transmitted, so that the data item cannot be registered correctly. In the third embodiment, after generating a processing request message and transmitting the message, it is determined whether or not the communication has succeeded (step 0909). If the transmission has failed, the processing request message is stored in the message storage unit 37. It is temporarily stored (step 0910). Next, when the communication path 3 is restored or after a certain period of time, the processing request message is resent again (step 0911).

As described above, according to the third embodiment, even when the communication means is disconnected, the data item can be correctly changed when the communication means is next connected.

Embodiment 4 FIG. FIG. 10 is a diagram showing a data structure definition of the data management system according to the fourth embodiment of the present invention. The fourth embodiment is characterized in that, in the data structure definition used in the first to third embodiments, the data item No. is common to all data object types, thereby facilitating the data item duplication determination. And

The operation of the fourth embodiment will be described below. In FIG. 10, the number of data items in the data structure definition is set to the maximum number used in the system, and the data item No. is uniquely assigned. By making the data item No. common to all data object types, each data object uses a common data item No. for data items having the same meaning.
Deletion and duplication can be easily determined.

As described above, according to the fourth embodiment, it is possible to combine the data structure definitions into one regardless of the increase or decrease in the types of data objects.

Embodiment 5 FIG. 11 is a diagram showing a data structure definition of the data management system according to the fifth embodiment of the present invention. In FIG. 11, the data structure definition has a virtual data structure definition common to all data object types and an actual data structure definition different for each data object type.

The operation of the fifth embodiment will be described below. By storing the link (index) between the data item No. in the virtual data structure definition common to the system and the data item in the actual data structure definition,
It becomes possible to minimize the size of the actual data structure definition. In addition, since the linking of data items is a reference by an index, the actual data structure definition item is changed, and the arrangement of the data items in the virtual data structure definition and the arrangement of the data items in the actual data structure definition are not the same. Even if you do not, you can dynamically change the data structure definition.

As described above, according to the fifth embodiment, the size of the data structure definition can be minimized, and the arrangement of data items and the increase / decrease of the number of items can be dynamically changed.

Embodiment 6 FIG. FIG. 12 is a configuration diagram showing a data management system according to Embodiment 6 of the present invention. In FIG. 12, 1 to 10, 12, 14, 17, 3
5 to 38 are the same as those in FIG. 39
Denotes an operation history storage unit (change history storage unit) for storing an operation history when a data object or a data item is operated in the data object input device 1;
Denotes an operation history storage unit (change history storage unit) in the data object management device 2. FIG. 12 of the sixth embodiment
8 is different from FIG. 8 of the third embodiment in that operation history storage sections 39 and 40 for storing an operation history when a data object or a data item is operated are different. FIG.
15 is a flowchart showing processing of the data object input device of the data management system according to Embodiment 6 of the present invention.

The operation of the data object input device 1 according to the sixth embodiment, which is different from the third embodiment, will be described with reference to FIG. After generating the processing request message (1302), operation history management information (time stamp), operator information, operation type, etc. are added to the generated processing request message (1302).
3) Store history information in the operation history storage unit 39 (13)
04). By providing an operation history operation unit and an operation history display unit (not shown), the stored operation history information can be extracted.

Although the case where the operation history storage unit 39 is provided on the data object input device 1 side has been described above, the same applies to the case where the operation history storage unit 39 is provided on the data object management device 2 side. In this case, the above operation is performed in the process request message receiving process.

As described above, according to the sixth embodiment, it is possible to save and retrieve the operation history when operating a data object or a data item. Further, when the communication means is disconnected, it is possible to determine when, who performed what operation.

[0041]

Since the present invention is configured as described above, it has the following effects. A first device that has a first data structure definition that defines a structure of a data object and that inputs a data object with reference to the first data structure definition, and a second data that defines a structure of the data object A second device having a structure definition and storing a data object input by the first device with reference to the second data structure definition, wherein the second device modifies the second data structure definition Having a second changing means, when the change by the second changing means is performed, while transmitting the change data to the first device, the first device is transmitted by the second device Since the first data structure definition is changed using the change data, the second data structure definition is dynamically changed, and the first data structure definition is changed in accordance with the change of the second data structure definition. One data structure It is possible to perform the change of righteousness.

A first device which has a first data structure definition which defines the structure of the data object, and a first device for inputting the data object with reference to the first data structure definition; A second device for storing a data object input by the first device with reference to the second data structure definition, wherein the first device has a second data structure definition. Having a first change means for changing the first data structure definition with the input, when the change by the first change means is performed, and transmits the change data to the second device,
Since the second device is configured to change the second data structure definition using the change data transmitted by the first device, if a data object is input,
A first data structure definition can be formed,
The second data structure definition can be changed accordingly. Further, the second device changes the second data structure definition after confirming that the change data transmitted from the first device does not duplicately change the second data structure definition. Even if the same change data is transmitted from the first device, it is possible to prevent duplicate changes.

Further, since the first device has the first message storage unit for storing the change data to be transmitted, even if the communication path has failed, it can be transmitted again when it recovers. In addition, since the second device has the second message storage unit that stores the change data to be transmitted, even when the communication path has failed, it can be transmitted again when it recovers.

Further, the change of the first data structure definition by the first device and the change of the second data structure definition by the second device are uniquely set to represent the data structure in the data structure definition. Since it is performed based on the data item, the data structure can be easily changed. Furthermore,
Data objects are classified according to data types, and data items are set in common for all the above data types. Therefore, a single data structure definition can be used regardless of the increase or decrease in the types of data objects. it can.

The data objects are classified by data type, and the data structure definition includes a virtual data structure definition commonly set for all data types.
Since the actual data structure definition is associated with the virtual data structure definition and set for each data type, the size of the data structure definition can be reduced. In addition, one or both of the first device and the second device,
Since there is a change history storage unit that stores a change history when the data structure definition is changed, the change history can be referred to as appropriate.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing a data management system according to a first embodiment of the present invention.

FIG. 2 is a diagram showing a structure of a processing request message transmitted and received between the data object input device and the data object management device of the data management system according to the first embodiment of the present invention.

FIG. 3 is a flowchart showing processing of the data object management device of the data management system according to the first embodiment of the present invention.

FIG. 4 is a flowchart showing processing of the data object input device of the data management system according to the first embodiment of the present invention.

FIG. 5 is a configuration diagram showing a data management system according to a second embodiment of the present invention.

FIG. 6 is a flowchart showing processing of the data object input device of the data management system according to the second embodiment of the present invention.

FIG. 7 is a flowchart showing processing of a data object management device of a data management system according to Embodiment 2 of the present invention.

FIG. 8 is a configuration diagram showing a data management system according to a third embodiment of the present invention.

FIG. 9 is a flowchart showing processing of the data object input device of the data management system according to the third embodiment of the present invention.

FIG. 10 is a diagram showing a data structure definition of a data management system according to a fourth embodiment of the present invention.

FIG. 11 is a diagram showing a data structure definition of a data management system according to a fifth embodiment of the present invention.

FIG. 12 is a configuration diagram showing a data management system according to a sixth embodiment of the present invention.

FIG. 13 is a flowchart showing processing of the data object input device of the data management system according to the sixth embodiment of the present invention.

FIG. 14 is a configuration diagram showing a conventional data management system.

FIG. 15 is a flowchart showing processing of a data object input device of a conventional data management system.

FIG. 16 is a flowchart showing processing of a data object management device of a conventional data management system.

[Explanation of symbols]

1 data object input device, 2 data object management device, 3 communication path, 4 data object input unit, 5, 10 data structure definition, 6, 23 data object generation unit, 7, 20 processing request message generation unit, 8, 14 communication Processing unit, 9 data object operation unit, 12, 25 processing request message analysis unit, 16
Data structure input unit, 17, 35 Data object analysis unit, 19 data item determination unit, 24 data structure management unit, 31 data structure identifier, 32 data item No., 33 data object, 36 data item duplication determination unit, 37, 38 Message storage unit, 39, 40 Operation history storage unit.

Claims (9)

[Claims] 1. A data management system comprising: a first device for inputting a data object; and a second device connected to the first device by a communication path and storing the input data object. Has a first data structure definition that defines the structure of the object,
A first device for inputting a data object with reference to the first data structure definition, having a second data structure definition defining the structure of the data object, and referring to the second data structure definition; A second device for storing a data object input by the first device, the second device having a second changing means for changing a second data structure definition, When the change is performed by the change unit, the change data is transmitted to the first device, and the first device uses the change data transmitted by the second device to change the data. A data management system configured to change one data structure definition. 2. A data management system comprising: a first device for inputting a data object; and a second device connected to the first device by a communication path and storing the input data object. Has a first data structure definition that defines the structure of the object,
A first device for inputting a data object with reference to the first data structure definition, having a second data structure definition defining the structure of the data object, and referring to the second data structure definition; And a second device for storing a data object input by the first device, wherein the first device changes a first data structure definition in accordance with the input of the data object. Having the change data transmitted to the second device when the change is performed by the first change means, and the second device transmits the change data transmitted by the first device. The data management system is configured to change the second data structure definition using 3. The second device changes the second data structure definition after confirming that the change data transmitted from the first device does not duplicately change the second data structure definition. The data management system according to claim 2, wherein 4. The data management system according to claim 2, wherein the first device has a first message storage unit for storing change data to be transmitted. 5. The data management system according to claim 1, wherein the second device has a second message storage unit for storing change data to be transmitted. 6. A change in the first data structure definition by the first device and a change in the second data structure definition by the second device are uniquely set to represent the data structure in the data structure definition. The data management system according to claim 1, wherein the data management is performed based on a data item. 7. The data management system according to claim 6, wherein the data objects are classified according to data types, and the data items are set in common for all the data types. 8. A data object is classified according to a data type, and a data structure definition includes a virtual data structure definition commonly set for all the data types.
The data management system according to any one of claims 1 to 7, further comprising an actual data structure definition associated with the virtual data structure definition and set for each data type. 9. The apparatus according to claim 1, wherein one or both of the first device and the second device include a change history storage unit for storing a change history when a change is made to the data structure definition. The data management system according to claim 1.