JP2011248852A - System cooperation apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To establish a data cooperation method which can perform conversion in data format using a conversion method which is different according to data even in the same data format in a system cooperation ensuring data compatibility between systems.SOLUTION: A data cooperation system uses, besides schema mapping definition defining corresponding relationship between data schema, an instance mapping definition defining corresponding relationship between the corresponding data schema and the actual data with respect to the actual data based on the data schema, thereby making it possible to perform conversion in data format in which the schema mapping definition used for each corresponding relationship of the actual data is changed.

Description

  The present invention relates to a system cooperation apparatus that cooperates data between a plurality of systems.

  In recent years, with diversification and sophistication of customer requests, systems for solving them have become larger and more complicated. For this reason, at the time of system renewal, batch migration to a new system is technically and costly difficult, and phased migration is necessary. In the case of a gradual transition, the new system and the old system coexist during the transition period. Since some of the functions of the old system may be used in the new system, both systems are not independent, and some data is retained redundantly in both systems. Therefore, a mechanism for ensuring the consistency of duplicate data between both systems is required.

  A conventional method for ensuring data consistency is database synchronization. This is a method of copying data (difference data) for the update to another database when data is updated for either database. As a result, the data can be kept in the same state among a plurality of systems, so that data consistency is ensured.

  If the data format used between multiple systems is different, it is necessary to convert the data format. Data format conversion is performed using data format conversion rules. Data format conversion rules provide a data schema that defines the data format for each system, and using the data item information of that data schema, the correspondence between data items is clarified between the systems The relationship is defined (hereinafter referred to as “schema mapping definition”).

  Patent Document 1 discloses a method of synchronizing a plurality of databases using the schema mapping definition.

JP 2003-331147 A

  However, in the technique described in Patent Document 1, there are cases where the conversion cannot be performed properly when there are a plurality of conversion rules that are candidates for use. For example, in one system, there is data called “train”, and in another system, data is managed separately for each type, such as “normal train” and “rapid train”, and data is copied between both systems. When performing, there will be a conversion rule from “train” data to “normal train” data and a conversion rule from “train” data to “rapid train” data. In this case, the second method cannot determine which conversion rule is used. In order to determine the conversion rule to be used, it may be possible to check the content of the “train” data and add a separate logic for determining the conversion rule according to the content. In this case, the copy destination cannot be determined until the logic is actually operated. In the above example of the train, if data that should be a “quick train” is handled as a “normal train” due to a logic error, there is a risk that proper operation management of the train cannot be performed. Data copy using logic in this way cannot be applied for risk because the data copy destination cannot be guaranteed. Also, the more complex the logic, the longer the processing and the lower the performance.

  An object of the present invention is to enable data linkage that ensures data consistency between systems even when there are a plurality of conversion rules for a data schema in consideration of the above points.

In order to achieve the above object, the present invention comprises the following arrangement. That is, in the system linkage apparatus that converts and copies the data format between the systems in order to ensure the consistency of the data when the data format is different between the multiple systems but the same data is held redundantly,
A data definition holding unit corresponding to each system that holds identification information for uniquely identifying each actual data from a set of actual data based on the data schema defined by the data format handled by each system; and
The identification information of each actual data and the definition of the data format are acquired from the data definition holding unit corresponding to each system, and the correspondence relationship of the actual data between systems to the user,
A mapping definition editing unit for displaying a screen for defining the correspondence of each data item between the actual data having the correspondence,
A mapping definition holding unit that holds the correspondence of actual data defined by the mapping definition editing unit as an instance mapping definition, and holds the correspondence of each data item as a schema mapping definition;
A data linkage device is provided.

  According to the present invention, even if there are a plurality of conversion rules for a data schema, data linkage that ensures data consistency between systems is possible.

It is a block diagram showing the system cooperation apparatus in embodiment. It is a hardware block diagram showing the outline of the system in an embodiment. It is a figure which shows an example of the instance mapping definition which defined the correspondence between the actual data based on the data schema definition in each system using the number of the array in which the actual data is stored. It is a figure which shows an example of the instance mapping definition which defined the correspondence between real data based on the data schema definition in each system using the ID attribute value which real data hold | maintains. It is a figure which shows an example of the schema mapping definition which defined the correspondence between the data items defined in the data schema definition in each system. It is a figure which shows an example of the instance mapping definition which expanded the format of the instance mapping definition 420, and made it possible to designate the timing of data conversion for every correspondence. It is a figure which shows an example of the instance mapping definition which extended the format of the instance mapping definition 420, and made it possible to designate the data item of conversion object for every correspondence. It is a figure which shows an example of the instance mapping definition which extended the format of the instance mapping definition 420, and made it possible to designate the data conversion timing and the data item of conversion object for every correspondence. It is a flowchart which shows the flow of the data conversion process which a system cooperation apparatus performs. It is a flowchart which shows the flow of the data conversion process which a system cooperation apparatus performs in the case of using the instance mapping definition of FIG. FIG. 9 is a flowchart showing a flow of data conversion processing executed by the system cooperation device when the instance mapping definition of FIG. 8 is used. FIG. 10 is a flowchart showing a flow of data conversion processing executed by the system cooperation device when the instance mapping definition of FIG. 9 is used. FIG. The format of the schema mapping definition in FIG. 5 is expanded, and the correspondence relationship when a plurality of conversion destination data items correspond to one conversion source data item and one conversion destination data item for a plurality of conversion source data items It is a figure which shows an example of the schema mapping definition which enabled the definition of the correspondence in case where corresponds. In the schema conversion part of the flowchart shown in FIG. 9 in the flow of data conversion processing executed by the system cooperation apparatus when the schema mapping definition of FIG. 13 is used, one conversion source data item is converted into one or more conversion destination data items. It is a flowchart which shows the flow converted into. In the schema conversion part of the flowchart shown in FIG. 9 in the flow of data conversion processing executed by the system linkage apparatus when the schema mapping definition of FIG. 13 is used, a plurality of conversion source data items are converted into one conversion destination data item. It is a flowchart which shows the flow to do. The figure which shows an example of the schema mapping definition which extended the format of the schema mapping definition of FIG. 5, and was able to specify the hierarchical data which has a some data item inside as a data item contained in conversion origin or conversion destination data It is. Of the data conversion processing flow executed by the system linkage apparatus when the schema mapping definition of FIG. 16 is used, in the schema conversion part of the flowchart shown in FIG. 9, hierarchical data as data items included in the conversion source or conversion destination data It is a flowchart which shows the flow of schema mapping when there exists.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. For the sake of explanation, two systems, System A and System B, are taken as examples of systems to be linked with the system.

  FIG. 2 is a block diagram illustrating a hardware configuration example according to the system cooperation of the present invention.

  System A 200, system B 210, and system cooperation apparatus 220 that are system cooperation targets are connected via a network 230.

  The system A 200 includes a processing device 201, an input / output device 202, a memory 203, an external storage device 204, and a communication device 207.

  The system B 210 includes a processing device 211, an input / output device 212, a memory 213, an external storage device 214, and a communication device 217.

  The system cooperation device 220 includes a processing device 221, an input / output device 222, a memory 223, an external storage device 225, and a communication device 224.

  Since the system A 200, the system B 210, and the system cooperation apparatus have the same hardware configuration, only the system A 200 will be described below.

  The processing device 201 reads the program 205 and data 206 held in the external storage device 204 onto the memory 203 and executes system processing. Processing operations and flowcharts in the system A 200 or the system B 210 to be described later are executed by the processing device 201 or 202, respectively.

  The input / output device 202 receives the execution instruction from the user and the input of data necessary for execution, and simultaneously displays the execution result to the user.

  The memory 203 is a main storage device for reading programs and data to be executed by the processing device 201.

  The external storage device 204 is an auxiliary storage device that holds a program 205 and data 206 necessary for execution.

  The communication device 207 outputs the data 206 of the system A 200 on the network 230 and inputs data flowing on the network 230 to the system A 200.

  In particular, the external storage device 225 of the system cooperation device 220 holds a program 226 and data 227 related to system cooperation processing. Specifically, the contents shown in FIG. 1 are held.

  FIG. 1 is a block diagram showing a software configuration example related to system cooperation of the present invention.

  The external storage device 225 stores a system cooperation processing program 100 and system cooperation processing data 110.

  The system cooperation processing program 100 is a software program including a mapping definition editing unit 101, a system data acquisition unit 102, an instance mapping processing unit 103, a schema mapping processing unit 104, and a system data updating unit 105.

  The mapping definition editing unit 101 displays the mapping definition editing screen to the user using the data schema and identification information held by the system A data definition holding unit 111 and the system B data definition holding unit 112, and displays the edited result as an instance mapping definition. 114 and the schema mapping definition 115 are held in the mapping definition holding unit 113.

  The system data acquisition unit 102 acquires the data schema and identification information from the system A data definition holding unit 111 (or system B data definition holding unit 112), and uses the data schema and identification information from the system A (or system B). A set of actual data is acquired, and the acquired set of actual data is transmitted to the instance mapping processing unit 103.

  The instance mapping processing unit 103 acquires the definition of the correspondence relationship between the system A and the system B among the instance mapping definitions 114 held in the mapping definition holding unit 113. After the instance mapping definition 114 is acquired, the system B (or system A) corresponding to the actual data for each actual data of the actual data set of the system A (or system B) transmitted from the system data acquisition unit 102 is acquired using the definition. ) Is uniquely identified, a schema mapping definition to be used is selected from the relationship between the data schemas of the actual data, and schema mapping definition information and system A (or system B) actual data are selected in the schema mapping processing unit 104. Send a set of together.

  The schema mapping processing unit 104 acquires a corresponding schema mapping definition 115 from the mapping definition holding unit 113 based on the schema mapping definition information received from the instance mapping processing unit 103. After acquisition, using the same definition, the data item included in the actual data of the system A (or system B) received from the instance mapping processing unit 103 is converted into the data item of the actual data of the system B (or system A), A set of actual data of system B (or system A) is transmitted to system data update unit 105.

  The system data update unit 105 acquires the data schema and identification information from the system B data definition holding unit 112 (or the system A data definition holding unit 111), and receives the data schema and identification information from the schema mapping process 104 using the data schema and identification information. A set of actual data of system B (or system A) is reflected in the data area of system B (or system A).

  The system cooperation processing data 110 includes a system A data definition holding unit 111, a system B data definition holding unit 112, and a mapping definition holding unit 113.

  The system A data definition holding unit 111 holds data schema that defines the data format of the system A that is a system linkage target and identification information that can uniquely identify each real data from a set of real data based on the data schema.

  The system B data definition holding unit 112 holds identification information that can uniquely identify each real data from a data schema that defines the data format of the system B that is a system linkage target and a set of real data based on the data schema.

  The mapping definition holding unit 113 holds a plurality of instance mapping definitions 114 and schema mapping definitions 115 created by the mapping definition editing unit 101.

  FIG. 3 is a diagram showing an example of instance mapping definition used in the system linkage processing of the present invention.

  The developer defines the instance mapping definition using actual data generated based on the data schema definition. As an example of the data schema definition of the system A, when the schema a301, the schema b302, and the schema c303 are considered, the actual data generated based on the data schema definitions are a [0] 311 and a [1] 312 respectively. , A [2] 313, b [0] 314, b [1] 315, b [2] 316, b [3] 317, c [0] 318, c [1] 319 for each data schema definition It is held as one element of array data. Similarly, the system B stores the schemas 341 and 342 as actual data 331, 332, 333, 334, 335, 336, 337, and 338.

  In this case, if the order in the array of the actual data to be held (hereinafter referred to as the array number) is always fixed, each actual data of the system A and the system B of the system B using the array schema number and the data schema name that is the basis of the array Each real data can be uniquely associated. The instance mapping definition 320 is an example in which the correspondence is described in a table format. The instance mapping definition may be in a format other than a table as long as the correspondence between actual data can be expressed.

  In FIG. 3, the actual data of the system A and the corresponding actual data of the system B are described for each row of the table, and as many as necessary are prepared. The second row 321 in FIG. 3 indicates that the actual data 312 having the array number 1 in the system A data and the actual data 333 having the array number 2 in the system B data have a correspondence relationship. . In this case, since the actual data is based on the schema a301 and the actual data based on the schema d341, a schema mapping definition describing the correspondence between the two schema definitions is required for the conversion of the actual data.

  FIG. 4 is a diagram showing an example of instance mapping definition as in FIG.

  In FIG. 3, it is assumed that the array number of the actual data to be held is always fixed. However, in FIG. 4, when the array number is not always fixed or the actual data is not organized like the array data, In this example, even if there is no order relationship between the data, it is possible to cope. In this example, an ID attribute is added as one data item of the data schemas 401, 402, 403, 441, and 442, and an ID value that can be uniquely identified is set for each actual data. An instance mapping definition is defined using this ID value.

  The second line 421 in the figure shows that the actual data 412 with the ID value k based on the data schema a401 of the system A and the actual data 433 with the ID value u based on the data schema d441 of the system B have a correspondence relationship. Yes.

  FIG. 5 is a diagram showing an example of the schema mapping definition used in the system linkage processing of the present invention. The instance mapping definitions 320 and 420 shown in FIG. 3 or FIG. 4 define the correspondence relationship of actual data, and do not define the correspondence relationship between data items of the actual data. Therefore, the schema mapping definition defines the correspondence between data items.

  The schema mapping definition defines the correspondence between data items for the data items of the actual data defined in the instance mapping definition 320. However, if this correspondence relationship is defined for each actual data, the correspondence relationship is required by the number of actual data, and the number becomes enormous. If the actual data type is the same, the internal data items are also the same, so the correspondence between the data items is defined for each type of actual data.

  In FIG. 5, when there is a correspondence between the data items of the schema A501, schema b505, and schema c509 that are the data schema of the system A and the data items of the schema d531 and the schema e536 that are the data schema of the system B, Correspondence can be defined as a schema mapping definition 520. Similar to the instance mapping definition, a format other than a table may be used as long as the correspondence between data items can be expressed. The second line 521 in FIG. 5 indicates that there is a correspondence between the data name a2 of the schema a501 of the system A and the data name d2 of the schema d531 of the system B.

  FIG. 6 is an extension of the instance mapping definition 420 shown in FIG. In this instance mapping definition 600, a conversion timing item 601 is added to the instance mapping definition 420 of FIG. In the conversion timing item 601, the timing for performing conversion for each correspondence can be specified. For example, an event such as data update is designated as a timing, such as “immediately after data update”, which means that conversion is performed immediately after data is updated by a user program process, etc., or at intervals of 2 seconds or 4 seconds. Periodic time such as “every 2 seconds” or “every 4 seconds”, which means conversion, can be designated as timing. This extension is possible not only for the instance mapping definition 420 of FIG. 4 but also for the instance mapping definition 320 of FIG.

  FIG. 7 is an extension of the instance mapping definition 420 shown in FIG. In this instance mapping definition 700, a conversion target data item 701 is added to the instance mapping definition 420 of FIG. In the conversion target data item 701, a data item to be converted can be designated for each correspondence. For example, “all data”, which means that all data items of actual data are to be converted, is designated, or only data items that have been updated by user program processing, etc. are to be converted “ It is possible to designate a specific data item as “difference data”. This extension is possible not only for the instance mapping definition 420 of FIG. 4 but also for the instance mapping definitions 320 and 600 of FIG. 3 or FIG. 8 is obtained by adding the conversion timing item 601 shown in FIG. 6 and the conversion target data item 701 shown in FIG. 7 to the instance mapping definition 420 shown in FIG. Similar to FIG. 6 and FIG. 7, it can be added to the instance mapping definition of FIG. FIG. 9 is a flowchart showing the flow of the system cooperation processing of the present invention when the instance mapping definitions 320 and 420 shown in FIG. 3 or 4 are used. In FIG. 9, a flow of data conversion and copying from system A to system B will be described as an example.

  First, the system linkage processing is started (900), and data is acquired from the system A (901). After the data acquisition, the instance mapping definition in which the correspondence information regarding the data of the system A is defined is read (902). One of the data acquired from the system A is extracted (903), and it is determined whether the data has been extracted to the end (904). If the data can be extracted, read the row in which the extracted data is defined in the read instance mapping definition.

  Then, the schema mapping definition in which the relation between the schema of the extracted system A data and the schema of the system B data defined in the read row is defined is searched from all the schema mapping definitions, and the corresponding ones. Is determined as a schema mapping definition using 905 (905).

  Thereafter, the schema mapping definition determined above is read (906).

  Each data item included in the actual data of the system A that has been extracted based on the read schema mapping definition information is copied (converted) to the data item included in the actual data of the system B (907).

  Thereafter, the process returns to 903. When the processing of the final data is completed, the converted data is reflected on the data of the system B all at once (908), and then the process is completed (909). As described above, the converted data can be reflected to the data of the system B every time one data conversion is performed, in addition to collectively reflecting the converted data at the end.

  FIG. 10 is a flowchart showing the flow of the system linkage process of the present invention when using the instance mapping definition 600 shown in FIG. The basic flow is the same as in FIG. 9, but after determining the schema mapping definition to be used (1005), processing for checking the timing of whether to perform data conversion using the conversion timing item 601 information of the instance mapping definition 600 ( 1006) is added. Thereby, the conversion timing can be adjusted for each data. For example, for data with a short data update time interval, the data conversion timing is set to a short time so that consistency can be secured frequently. For data with a long time interval, the data conversion timing is set to a long time. By setting, it is not possible to convert all data at the same timing, but it is possible to change the data conversion timing according to the update frequency for each data. FIG. 11 is a flowchart showing the flow of the system cooperation process of the present invention when the instance mapping definition 700 shown in FIG. 7 is used. The basic flow is the same as in FIG. 9, but after the schema mapping definition to be used is determined (1105) using the conversion target data item 701 information of the instance mapping definition 700, the value of the conversion target data item 701 is “difference”. It is checked whether it is “data” (1106), and if it is “difference data”, a process of extracting data with update from the data of system A (1107) is added. As a result, the data item to be converted can be adjusted for each data. For example, for data that has many data items that are not updated, set the data item to be converted to “difference data” so that only the data items that have been updated can be converted, and data that does not have many data items that are not updated. By setting the conversion target data item as “all data” so that all data can be converted without checking whether there has been an update, unnecessary conversion can be reduced.

  FIG. 12 is a flowchart showing the flow of the system cooperation process of the present invention when the instance mapping definition 800 shown in FIG. 8 is used. In this flow, the processes added in FIGS. 10 and 11 are added. In the instance mapping definition 800, the conversion timing 801 and the conversion target data item 802 can be specified at the same time. For example, since the conversion target data item 802 and the conversion timing 801 can be specified so that the difference data with update is converted at a timing according to the update frequency, data conversion can be minimized without waste. . This leads to an improvement in response speed and a reduction in memory usage, which is also effective for systems that require real-time processing and have severe restrictions on response speed and memory usage.

  FIG. 13 shows an example of a schema mapping definition when a plurality of conversion source data items or conversion destination data items correspond to one data item.

  FIG. 13 is a diagram showing an example 1300 of a schema mapping definition obtained by extending the schema mapping definition 520 shown in FIG. The schema mapping definition 1300 is used when a plurality of data items of the conversion destination data correspond to one data item of the conversion source data. In FIG. 13, in the part 1301 for defining mapping between data items, it is defined that the data items 1303, 1304, 1305 of a plurality of conversion destination data correspond to the data item 1302 of the conversion source data. For each correspondence, the position where the data item 1303, 1304 or 1305 of the conversion destination data appears in the data item 1302 of the conversion source data is designated as the start position 1306, and the size of the data item of the conversion destination data is designated as the size 1307. To do. With this definition, a correspondence relationship when a plurality of conversion destination data items correspond to one conversion source data item and a single conversion destination data item for a plurality of conversion source data items It is possible to define a correspondence relationship when

  FIG. 14 is a flowchart showing a flow of converting one conversion source data item into a plurality of conversion destination data items using the schema mapping definition 1300 shown in FIG. 13, and is a flowchart of the entire flowchart of the present invention shown in FIG. The details of the schema conversion 907 portion are shown. FIG. 14 shows a flow of converting one data item of conversion source data into one or more data items of conversion destination data. After starting schema conversion (1401), one data item included in the conversion source data is extracted (1402). At this time, it is determined whether there is no data item or all the data items have been extracted (1403). If no data item exists or all the data items have been extracted, the process is terminated. If the data can be extracted, the schema mapping definition is referred to and it is determined whether there is one or more conversion destination data items corresponding to the extracted data items (1404). If there is no conversion destination data item corresponding to the extracted data item, the process returns to 1402. When there is one or more data item of the conversion destination data corresponding to the extracted data item, refer to the start position 1306 and the size 1307 defined in the schema mapping definition shown in FIG. Data of the specified size is acquired from the specified start position of the item (1405), and copied to the data item of the conversion destination data (1406). Then, the process returns to 1404 again and repeats for the number of conversion destination data items. As a result, one data item of the conversion source data can be converted into a plurality of data items of the conversion destination data.

  FIG. 15 is a flowchart showing a flow of converting a plurality of conversion source data items into one conversion destination data item using the schema mapping definition 1300 shown in FIG. 13, and is a flowchart of the entire flowchart of the present invention shown in FIG. The details of the schema conversion portion 907 are shown. FIG. 15 shows a flow of converting one or more conversion source data items into data items of one conversion destination data. After the start of schema conversion (1501), the schema mapping definition 1300 is referred to among the data items included in the conversion source data, and it is determined whether there are one or more data items of the same conversion destination data (1502). . If there is no conversion source data item having the same data item of the conversion destination data, the processing ends (1506). If there are one or more data items of the conversion destination data, all of them are extracted (1503). At this time, it is determined whether there is no data item or all data items have been extracted (1504), and if there is no data item or all data items have been extracted, the processing ends (1506). ). When one or more data items are extracted, the start position 1306 and the size 1307 defined in the schema mapping definition shown in FIG. 13 are referred to, and for each data item of the conversion source data, from the specified start position. Data of a specified size is acquired, combined as one data item, and copied (converted) to a conversion destination data item (1505). Thereafter, the processing returns to 1502 and is repeated until all the conversion source data items are extracted. Thereby, a plurality of data items of conversion source data can be converted into one data item of conversion destination data.

  FIG. 16 shows an example of the schema mapping definition when converting hierarchical data having a plurality of data items therein among the data items included in the conversion source data or the conversion destination data.

  FIG. 16 is a diagram illustrating an example of a schema mapping definition obtained by extending the schema mapping definition 520 illustrated in FIG. This schema mapping definition is used when hierarchical data having a plurality of data items therein is specified as a data item included in conversion source data or conversion destination data. First, in the schema mapping definition 1600, hierarchical data 1602 and 1603 are described in the data type portion as shown in the correspondence definition of 1601. Here, when hierarchical data is specified as the data type, the ID 1605 of the sub schema mapping definition in which the correspondence between the hierarchical data specified in 1602 and 1603 is defined in the sub schema mapping ID portion in the same record. . Even in the sub schema mapping definition, the correspondence between data items is defined as in the schema mapping definition, but the data type of the hierarchical data specified in 1602 and 1603 is specified in the schema part as shown in one correspondence definition of 1604. To do. If the data type of the data item defined by the correspondence of the subschema mapping definition is further hierarchical data, the hierarchical data 1606 and 1607 are designated again as the data type, and the correspondence between the hierarchical data is defined. Specifies the sub schema mapping ID to be executed.

FIG. 17 is a flowchart showing a flow of converting a hierarchical data item included in conversion source data into a hierarchical data item included in conversion destination data using the schema mapping definition 1600 shown in FIG. 9 shows details of the schema conversion portion 907 of the flowchart shown in FIG. FIG. 17 shows the flow of schema mapping when hierarchical data exists as data items included in conversion source data or conversion destination data. After starting schema conversion (1701), one data item included in the conversion source data is extracted (1702). At this time, it is determined whether the data item does not exist or all the data items have been extracted (1703). If the data item does not exist or all the data items have been extracted, the process is terminated. . If the data can be extracted, the schema mapping definition is referred to and it is determined whether or not the data of the extracted data item is hierarchical (1704). If it is not hierarchical data, the data is copied to the conversion destination data item (1707), and the process is terminated (1708). If it is hierarchical data, the subschema mapping ID to be used is determined by referring to the subschema mapping ID in the schema mapping definition (1705).
Thereafter, schema conversion is recursively called for the number of layers of hierarchical data (1707), and data items are copied at each layer.
Thereby, even when the data item is hierarchical data, the data item can be converted.

  As described above, according to the embodiment of the present invention, in addition to the schema mapping definition that is a definition of the correspondence between data schemas used in each system and is a conversion rule when copying data between systems, the data schema By performing data conversion using the instance mapping definition that defines the correspondence between actual data based on each data, even if there are multiple conversion rules for one data schema, before each system operation The conversion rule to be used can be determined and the copy destination data can be guaranteed. As a result, it is possible to avoid an unexpected failure during system operation regarding data copying.

  Furthermore, complex data conversion such as when the correspondence between data items is not one-to-one, but one-to-many or many-to-one, or there is hierarchical data that has multiple data items as data items Can also be performed.

  In addition, when the system is upgraded in stages, the current system and the new system must coexist. Even if the format and granularity of the data used between the two systems are different, the present invention can Since accurate data copy can be guaranteed, a new system can be freely designed and developed without depending on the data format and granularity of the current system. This facilitates the adoption of the latest and most effective system design technique, and the same result can be obtained regardless of whether the function is implemented on the old or new system, thereby facilitating a stepwise transition.

DESCRIPTION OF SYMBOLS 100 System cooperation processing program 101 Mapping definition edit part 102 System data acquisition part 103 Instance mapping processing part 104 Schema mapping processing part 105 System data update part 110 Data for system cooperation processing 111 System A data definition holding part 112 System B data definition holding part 113 Mapping data holding unit

Claims (9)

In the data linkage device that converts and copies the data format between systems in order to ensure data consistency when holding the same data with different data formats between multiple systems,
A data definition holding unit corresponding to each system that holds identification information for uniquely identifying each actual data from a set of actual data based on the data schema defined by the data format handled by each system, and each of the above The identification information and data format definition of each actual data is obtained from the data definition holding unit corresponding to the system, and the correspondence of the actual data between the systems and the correspondence of each data item between the corresponding actual data are obtained to the user. A mapping definition editor that displays a screen for defining relationships;
A mapping definition holding unit that holds the correspondence of actual data defined by the mapping definition editing unit as an instance mapping definition, and holds the correspondence of each data item as a schema mapping definition;
A data linkage apparatus comprising: A system data acquisition unit that acquires a set of actual data from the target system using the data schema and identification information held in the data definition holding unit;
The actual data acquired from one system by the system data acquisition unit uses the instance mapping definition to uniquely identify the actual data of other systems, and the relationship between the data schemas of the actual data is stored in the mapping definition holding unit. An instance mapping processing part for selecting the stored schema mapping definition;
The selected schema mapping definition information and their actual data are received together from the instance mapping processing unit, and the corresponding schema mapping definition is acquired from the mapping definition holding unit based on the schema mapping definition information. Using a definition, a schema mapping processing unit for converting a data item included in the received actual data of the one system into a data item of the actual data of the other system;
System data for receiving a set of converted real data from the schema mapping processing unit and transmitting the received set of real data to the target system using the data schema and identification information held in the data definition holding unit Update section,
A data linkage apparatus comprising: In the data definition holding unit,
The data linkage apparatus according to claim 1, wherein when the set of actual data is array data, an array number of the array data and a schema name of the data schema are used as the identification information. In the data definition holding unit,
An ID attribute is added as a data item to the data schema, an ID value capable of uniquely identifying the actual data is set in advance for the ID attribute of the actual data based on the data schema, and the ID value is set as the identification information. The data linkage apparatus according to claim 1, wherein the data linkage apparatus is used as a data linkage apparatus. In the data linkage apparatus, an item for specifying the conversion timing of the data format is added to the instance mapping definition, and in the instance mapping process, a process of determining the conversion timing of the data format is added,
The data linkage apparatus according to claim 2, wherein the schema mapping process is performed by changing the timing for each correspondence relationship of actual data using the conversion timing of the data format determined in the instance mapping process. In the data linkage apparatus, an item for specifying a data format conversion target data item is added to the instance mapping definition, and in the instance mapping process, a process for determining the data format conversion target data item is added,
Using the conversion target data item in the data format determined in the instance mapping process, the schema mapping process is performed for all data items for each correspondence of actual data or only for differential data items with updates. The data linkage device according to claim 2 or 5. In the data cooperation device according to claim 1,
When multiple data items of conversion destination data correspond to data items of conversion source data,
The data definition holding unit
In the schema mapping definition, the data item of the conversion source data is stored in association with the start position and size of the corresponding conversion destination data,
The schema mapping processing unit
For each data item of the conversion source data, data of the amount specified by the size from the start position is acquired and copied to the corresponding data item of the conversion destination in the schema mapping definition Cooperation device. In the data cooperation device according to claim 7,
When multiple data items of conversion source data correspond to data items of conversion destination data,
The data mapping apparatus, wherein the schema mapping processing unit combines the data items of the plurality of conversion source data and copies the data items to the corresponding data items of the conversion destination in the schema mapping definition. In the data cooperation device according to claim 1,
If the data items included in the conversion source data and conversion destination data are hierarchical data items that have more than one data item,
Define a schema mapping for the hierarchical data item as a subschema mapping, assign a unique ID to the subschema mapping,
In the data definition holding unit,
In the schema mapping definition, an item for specifying an ID for uniquely identifying the schema mapping, an item for specifying a data type of a data item included in conversion source data and conversion destination data, and an ID for the sub schema mapping are specified. Add items,
In the schema mapping processing unit,
A data linkage apparatus that recursively executes a schema mapping process by designating an ID of the subschema mapping at the time of conversion of data of the hierarchical data item.

Images