KR20030052059A - Method of data integration using metadata in multi-database middleware systems - Google Patents

Abstract

PURPOSE: A method for integrating data using meta data in a multiple database middleware system is provided to store and manage meta data with respect to a global database schema in a multiple database middleware system and to integrate data of a local database using meta data in the case that data in a company are integrated totally. CONSTITUTION: A meta data database stores a global database schema and searching a local column corresponding to each global column(202). All local database related to the global database is registered(203), and a mapping operation with respect to all columns of the registered local database is started through a multiple database middleware system(205). A global table including names similar to a local table name of each local column is searched in accordance with a result of the mapping operation, and a global column including a name similar to a local column name is searched(208). If a similar degree is output on a screen in order of high degree, information with respect to a global column is appended as meta data of the global column for selecting the corresponding global column(210).

Description

Method of data integration using metadata in multi-database middleware systems}

The present invention relates to a data integration method using metadata in a multi-database middleware system and a computer-readable recording medium recording a program for realizing the method. In particular, the metadata for the global database schema in the multi-database middleware system The present invention relates to a data integration method using metadata in a multi-database middleware system for storing and managing data and to integrate data of a local database using metadata, and a computer-readable recording medium recording a program for realizing the method.

In the conventional multiple database middleware system, the schema integration method was supported in three steps.

First, the first step is to define the local schema by registering the local databases accessible from the global database.

Step 2 is a schema conversion step, which defines a global table to map a local schema table to a global table.

The third step is to integrate the global tables defined in the schema conversion process to create a global view for the user. These processes were defined using multiple database languages at each stage.

The local database registration statement in Phase 1 is as follows:

CREATE LDB <ldb name>

FROM <ldb name at host> OF <ldb type> AS <ldb model>

WITH <ldb attribute value clause>

[{<ldb attribute value clause>} ...]

In the above statement, <ldb name> is the local database name referenced in the global database, <ldb name at host> is the local database specific name, and <ldb type> is the type of local database, 'Informix', 'Oracle', It is expressed as 'Unisql' and <ldb model> is a model of local database. It is expressed as 'RDB' for relational database and 'OODB' for object-oriented database. Also, the <ldb attribute value clause> clause expresses the attributes of the registered local database in the following format.

<ldb attribute value clause> :: =

<ldb attribute name> <ldb attribute value>

<ldb attribute name> :: =

HOST | VERSION

| USER | PASSWORD

In the above sentence, <ldb attribute name> designates an attribute name of a local database to be registered, expresses an attribute value by <ldb attribute value>, and to designate a host name where a local database exists. Use the host reserved word as>, the version (VERSION) for the local database version, and the user (USER) and password (PASSWORD) reserved words for the user name and password respectively.

Next, the two-level global table definition statement is as follows.

CREATE TABLE <global table name>

(<table element> [{, <table element>} ...)

AS SELECT [DISTINCT | ALL] <ldb select list>

FROM <ldb entity-set name>

[WHERE <search condition>]

ON LDB <ldb name>

In the above statement, the global table name designated as <global table name> corresponds one-to-one with the name of the local entity set designated as <ldb entity-set name>.

The <table element>, a component of the global table, contains the definitions of the columns, constraints, and so on for the global table, and the columns defined as components of the global table are the attributes of the local set of objects listed by <ldb select list>. One-to-one correspondence in order.

The <column definition> that defines the columns of the global table is defined in the following format. At this time, the value of the local attribute corresponding to the global column is converted to the data type of the global column specified by <data type>.

<column definition> :: =

<column name> <data type>

[<default clause>]

[<attribute constraint definition> ...]

Finally, the three-level global view definition statement looks like this:

CREATE VIEW <global view name>

(<view column list>)

AS <query expression>

[WITH CHECK OPTION]

Here, global views do not have to be modifiable, unlike global tables, so global views and global tables do not need to have a one-to-one correspondence. Thus, <query expression> can refer to columns from one or more global tables or other global views. The elements of the <select list> retrieved by the <query expression> must have a one-to-one correspondence with each element of the <view column list>.

And, <view column list> defines the column names included in the view. Unlike the columns of the global table, data type or constraints cannot be defined. The data type and constraints of each column of the global view depend on the columns of the global table referenced by the view.

The possibility of modifying a global view is defined using the "WITH CHECK OPTION" clause.

When trying to modify a virtual class by using the "INSERT" and "UPDATE" commands, check whether the condition of <query expression> specified when creating the virtual class is met. If "WITH CHECK OPTION" is not specified, only a search of the global view is possible.

Therefore, in the current technical field, integrating data using only a multi-database query language in the above-described manner is not only difficult to generate a query statement but also generates a global table corresponding to each local table or integrates a global table. There is a problem in that, when creating a global view, a user must manually find a column of a global table or a column of a global view corresponding to a local column.

The present invention has been proposed to solve the problems described above. When the enterprise-wide data needs to be integrated, metadata for a global database schema is stored and managed in a multi-database middleware system, It is an object of the present invention to provide a method for integrating data in a database and a computer-readable recording medium having recorded thereon a program for realizing the method.

1 is an exemplary configuration diagram of a hardware system to which the present invention is applied.

2 is a flowchart illustrating a data integration method using metadata in a multiple database middleware system according to the present invention.

3 is an exemplary diagram showing a structure of a global schema or a local schema used in the present invention.

4A is an exemplary diagram illustrating a metadata structure of a global table according to the present invention.

4B is an exemplary view showing the structure of metadata of a global column according to the present invention.

5 is an exemplary view showing a candidate global column list corresponding to a local column according to the present invention.

* Explanation of symbols for the main parts of the drawings

11: central processing unit 12: main memory unit

13: auxiliary memory device 14: input device

15: output device

In order to achieve the above object, the present invention provides a data integration method using metadata applied to a multiple database middleware system, to store a global database schema and search for a local column that is likely to correspond to each global column. Constructing, in the metadata database, all similar names that are likely to correspond with global table names and global column names for global tables and global columns; Registering all local databases related to the global database and starting a mapping operation for all columns of the registered local databases through a multiple database middleware system; A third step of searching for a global table including names similar to a local table name of each local column and searching for a global column including a name similar to a name of a local column according to a result of the mapping operation of the second step; And a fourth step of adding information about the global column as metadata of the global column so as to select a corresponding global column among the outputs on the screen in a similar high order according to the search result of the third step. Characterized in that the made up.

In addition, the present invention provides a global table name for a global table and a global column to store a global database schema in a multi-database middleware system with a processor, and to search for local columns that are likely to correspond to each of the global columns. And a first function of constructing in the metadata database all similar names likely to correspond to global column names; A second function of registering all local databases associated with the global database and starting a mapping operation for all columns of the registered local databases through a multiple database middleware system; A third function of searching for a global table including names similar to a local table name of each local column and searching for a global column including a name similar to a name of a local column according to a result of the mapping operation of the second function; And a fourth function of adding information about the global column as metadata of the global column so that a corresponding global column may be selected among the outputted data on the screen in the order of similar high order according to the search result of the third function. A computer readable recording medium having recorded thereon a program for realization is provided.

The present invention defines global table names and global column names that are commonly used throughout the enterprise by storing and managing global schema and metadata for corporate data modeling in order to integrate data from regional databases within the enterprise. The database uses local table and global column metadata information to map local columns to global columns, eliminating the need to name global columns every time a global table is created, and all local columns that correspond to one global column. Automatic integration allows you to eliminate the need to manually find global columns that need to be merged in the global view, while avoiding the creation of unnecessary global tables by handling the mapping operations for columns of already normalized global tables. .

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is an exemplary configuration diagram of a hardware system to which the present invention is applied.

As shown in FIG. 1, a general hardware system includes a central processing unit 11, a main memory device 12 connected to the central processing device 11, and an auxiliary memory device 13 connected to the main memory device 12. And an input device 14 and an output device 15 connected to the central processing unit 11.

However, since the computer hardware environment having the configuration as described above is only a technique well known in the art, detailed description thereof will be omitted herein. However, the data integration method using metadata in the multiple database middleware system according to the present invention will be described in detail as follows.

FIG. 2 is a flowchart illustrating a data integration method using metadata in a multi-database middleware system according to the present invention, assuming that it is built in the main memory device 12 of FIG. 11) is executed according to the flow order of control.

In the present invention, in providing a data integration method in a multi-database middleware system, the global schema by enterprise modeling is first performed by performing the process of FIG. 2 described later in FIG. 2 through the input device 14 of FIG. When registered as a middleware system, the global schema of the structure shown in FIG. 3 is stored in the main memory device 12 of FIG. 1. In FIG. 3, the top node represents a schema name, the middle node represents a table, and the bottom node represents a column.

That is, as shown in Figure 2, in order to perform the data integration method using metadata in the multiple database middleware system according to the present invention, first register the global schema (201), and the global table and the registered global schema Register metadata for the global column (202).

Here, the metadata for the global table may correspond to the Hangul name for the global table, the description of the global table, and the global table name as shown in the global table metadata structure of FIG. 4A as part of the table node information of FIG. 3. Enter similar names with. Similar names for global tables can be in Korean or English.

In addition, the metadata for the global column may correspond to the Hangul name for the global column, the description of the global column, and the global column name as shown in the global column metadata structure of FIG. 4B as part of the column node information of FIG. 3. Enter similar names with. If the data value of a column represents a value in a specific unit, enter the specific unit of the global column value. Similarly, similar names for global columns can be in Korean or English.

Meanwhile, when the local database is registered (203) and the local database is registered in the multi-database middleware system, the multi-database middleware system receives meta data related to the local database and, like the global schema input in step 201, the main memory of FIG. The device 12 generates a local schema with the structure as shown in FIG.

Next, verify that all regional databases are registered (204), if all regional databases are not registered, proceed to registering the regional database (203), and if all regional databases are registered, the corresponding candidate globals for the regional column. Retrieve the column (205). Here, the method for searching the global column may include a similar name compared to the similar name registered as metadata of the global table in the step 202 of registering the global table and the metadata for the global column with respect to the local table name to which the local column belongs. Detect whether there is a global table with the name, and if there is such a global table, compare the global column with the similar name with the similar name registered as the metadata of the global column in the step 202 of registering the metadata for the global table and the global column. Search. For the retrieved global column, the similarity ratio for the name of the global table to which the global column belongs and the similarity ratio for the name of the global column are calculated.

Then, it is determined whether the candidate global column is found (206), and if found, the candidate global column is displayed on the screen (207), and the information on the local column, the information on the candidate global columns, and the similarity ratio between the local column and the global column are output. do. As shown in the candidate global column list corresponding to the local column of FIG. 5, the local column information includes the name of the table to which the local column belongs, the name of the local column, the data type of the local column, and the like. Candidate global column information includes global table name, global column name, global column type, and global column unit if global column unit is entered.

If the candidate global column is not found in the process of checking whether the candidate global column is found (206), the information on the local column that does not find the candidate global column is registered as metadata of the global schema. (211) If it is determined that the mapping operation is performed for all local columns (212), if the mapping operation is not performed, proceed to the process of searching for a corresponding candidate global column for the local column (205), otherwise the operation To exit.

Thereafter, in step 207, the global column corresponding to the local column is selected from among the candidate global columns output in the process of outputting the candidate global column on the screen.

As a result of determination 208, if a global column corresponding to a local column is not selected among the output candidate global columns, information on a local column that does not find a candidate global column is registered in the global schema metadata as metadata of the global schema ( 211), check whether the mapping operation is performed for all local columns (212), and if the mapping operation has not been performed, proceed to the process of retrieving the corresponding candidate global column for the local column (205). Quit.

As a result of determination 208, if a global column corresponding to the local column is selected from the output candidate global columns, conversion information for converting the data to the global column is input using the data of the local column (209). At this time, if the conversion information is not input, the data of the local column and the data of the global column correspond to the same value when the command for searching the global database is performed.

Subsequently, after adding the local column information to the metadata of the global column (210), it checks whether the mapping operation is performed on all the local columns (212), and if the mapping operation is not performed, the corresponding candidate global for the local column. The process proceeds to step 205 of retrieving the column, otherwise the operation ends.

That is, in the present invention, after registering a local schema and attempting to create a corresponding global table, candidates to be matched using similar names registered as pre-registered global table metadata and similar names registered as metadata of the global column are selected. List in advance.

To create a list, look for a global table that contains a name similar to that of the local table, and again find a global column that contains a name similar to that of the local column for a global column that belongs to the candidate global table. Thus, for each of the local columns of the local table, the corresponding global table and global column are output as a list (see FIG. 5).

The user who wants to match the local schema with the global schema can select from the output list. If the corresponding list is not found in the output list, the information on the local table or local column is registered as metadata of the global schema to expand the global schema information.

According to the present invention, when the enterprise-wide data needs to be integrated through the above-described process, the global database schema is registered in a multi-database middleware system, and metadata related thereto is registered in the registered local database using the same. Makes it easy to map global columns to all local columns to which they belong. Due to the nature of the schema structure, when a global column and a local column are mapped to each other, the global table to which the local column belongs is determined naturally. This means that whenever a local column and a global column need to be mapped, the global table is renamed. Eliminate the difficulty of naming.

In addition, in the present invention, when multiple local columns correspond to one global column, metadata of all local columns corresponding to each global column in a multiple database middleware system without having to separately create a global view to integrate these columns It is possible to search the integrated data automatically by managing it.

Furthermore, global tables are created whenever needed, which eliminates the complexity of the structure of the global database, thereby facilitating enterprise-wide data integration management.

The method of the present invention as described above may be implemented as a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.).

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and various substitutions, modifications, and changes are possible in the art without departing from the technical spirit of the present invention. It will be clear to those of ordinary knowledge.

The present invention as described above, in order to integrate the data of the regional database in the enterprise, global table name, global column name to store and manage global schema and metadata for corporate data modeling in advance And the local database uses the global table and global column metadata information to map local columns to global columns, eliminating the need to name global columns every time a global table is created and responding to a single global column. By automatically merging all local columns, the global view eliminates the need to manually find the global columns that need to be merged in the global view, while also processing the mapping operations for the columns of already normalized global tables. Stop it That there is an effect.

Claims (5)

In the data integration method using metadata applied to a multiple database middleware system, To store the global database schema and search for local columns that are likely to be matched for each of the global columns, metadata for the global table and global columns and all similar names that are likely to match the global column name A first step of building in a database; Registering all local databases related to the global database and starting a mapping operation for all columns of the registered local databases through a multiple database middleware system; A third step of searching for a global table including names similar to a local table name of each local column and searching for a global column including a name similar to a name of a local column according to a result of the mapping operation of the second step; And A fourth step of adding information about the global column as metadata of the global column so that a corresponding global column may be selected among the outputted results in the order of similarity in high order according to the search result of the third step Data integration method using metadata in a multiple database middleware system including a. The method of claim 1, The global table search and global column search process, Instead of looking for an exact match between characters and characters that are running in an existing database, metadata is found in a multiple database middleware system that finds things that contain similar names, such as those found in information retrieval systems, and expresses similarities in percentage. Data integration method used. The method of claim 1, The global table, It contains a global table metadata structure, in which you enter a Hangul name for a global table, a description of the global table, and a similar name that is likely to match the global table name. Data integration method using metadata in a multiple database middleware system, characterized in that to display. The method of claim 1, The global column, It contains a global column metadata structure that inputs the Hangul name for the global column, a description of the global column, and a similar name that may match the global column name. When the column's data values represent values in a particular unit. A method of integrating data using metadata in a multiple database middleware system, characterized in that a specific unit of a global column value is input and a similar name for the global column can be expressed in a language other than Korean. In a multi-database middleware system with a processor, To store the global database schema and search for local columns that are likely to be matched for each of the global columns, metadata for the global table and global columns and all similar names that are likely to match the global column name A first function of building on a database; A second function of registering all local databases associated with the global database and starting a mapping operation for all columns of the registered local databases through a multiple database middleware system; A third function of searching for a global table including names similar to a local table name of each local column and searching for a global column including a name similar to a name of a local column according to a result of the mapping operation of the second function; And A fourth function of adding information about the global column as metadata of a global column so that a corresponding global column may be selected among the outputted screens in the order of similarity in high order according to the search result of the third function A computer-readable recording medium having recorded thereon a program for realizing this.