KR20010083845A - Enterprise meta data management method and system for managing distinct systems and metadata totally - Google Patents

Abstract

The present invention relates to an integrated metadata management method for integrated management of heterogeneous metadata existing on heterogeneous systems and databases in all fields of an environment related to a data warehouse. According to the present invention, in an integrated metadata server managing meta information for integrated management between heterogeneous systems, a metadata storage request is received, a heterogeneous system corresponding to the metadata storage request is determined, and the heterogeneous system is received. Access the server corresponding to the server, extract the metadata corresponding to the metadata storage request from the information database associated with the server, or the metadata file included in the server, and extract the extracted metadata from the heterogeneous system. Convert to a common format according to a predetermined conversion rule, and stores the converted metadata in an integrated metadata database coupled with the integrated metadata server. Through the present invention, by managing the flow of data and providing information to users, it is possible to provide consistency verification of DW data, securing data reliability, utilizing data analysis, and ease of use.

Description

Integrated metadata management method and apparatus for integrated management of heterogeneous systems and metadata {ENTERPRISE META DATA MANAGEMENT METHOD AND SYSTEM FOR MANAGING DISTINCT SYSTEMS AND METADATA TOTALLY}

The present invention relates to an integrated metadata management method for integrated management of heterogeneous metadata existing on heterogeneous systems and databases in all fields of an environment related to a data warehouse. An important part of operating a data warehouse (DW) environment is how to manage the flow of data. In the DW environment, the flow of data includes data flow into (ETL: Extraction, Transformation, Transport, Loading), data flow out (data analysis, Mining, OLAP, Data Mart creation), data flow up (management decision summary). Data, OLAP), and data flow down to the storage medium. In addition, you must manage when, how, who, where, why, and why data was created, utilized, and discarded. In other words, data life cycle should be managed. Provide accurate information on how data flows under any DW environment to DW operators, administrators, data analysts, and users.

One of the existing metadata management methods is the Integrated Case (CASE) Information Store metamodel system for process methodology and its integration support method (hereinafter referred to as the Integrated Case (CASE) Information Store metamodel system for process methodology and its integration support method). Let's look at the prior art 1).

Prior Art 1 consistently stores and shares the information generated by the CASE (Computer Aided Software Engineering) tools of the process methodology Data Flow Diagram (DFD) and Structure Chart (SC). Rather, the present invention relates to an Information Resource Dictionary System (IRDS) metamodel system of an integrated CASE information repository for supporting a software life cycle and a method of supporting the integration thereof. Prior art 1 establishes an information repository to store, share, and manage the information generated by these CASE tools in common, thereby supporting the standardization and complete automation of the software development process, and sharing information among the tools. .

The integrated CASE metamodel includes rules and constraints on the information that each tool should have, and when the generated information is stored in the CASE repository, the consistency check on the form and meaning of the information and the tools The storage model for all information is the metamodel of the information store.

The metamodel of the information store is the basis for tool integration and the integrity of the information stored in the information store, and determines which software lifecycle and methodology the information store-based CASE tools support. Thus, information repositories automatically integrate and manage information, providing standardization and complete automation of the software development process and sharing information between tools.

Hereinafter, the schema automatic storage system and its operation method (hereinafter, referred to as the prior art 2) will be described as another method of managing metadata.

Prior art 2 relates to a schema automatic storage system and a method of operating the same, which support a system for interpreting and verifying multimedia metadata. The purpose is to provide a schema automatic storage system and a method of operating the integrated management of each module. The effect is that you can easily save schemas when you need to handle various kinds of metadata, and even users who don't know how to use them can easily write metadata applications and increase the economics and efficiency of metadata authoring. There is.

Existing metadata management methods such as the prior art 1 and the prior art 2 are related to system related information, database (table, column, etc.) related information, tasks, work schedules, mapping information between tables, mapping information between columns, and application information. There is a problem in that metadata can not be managed and retrieved collectively.

In addition, the existing metadata management method has a problem that it is not possible to manage and query a plurality of heterogeneous systems with a single management program.

In addition, in the conventional metadata management method, heterogeneous metadata is stored in a heterogeneous format corresponding to each system, and there is a problem that standardized and integrated management is not possible.

Accordingly, an object of the present invention is to provide an integrated metadata management method and apparatus for integrated management of heterogeneous metadata existing on heterogeneous systems and databases in all fields of an environment related to a data warehouse.

Another object of the present invention is to manage data flow and provide information to users, thereby providing consistency verification of DW data, securing data reliability, utilizing data analysis, and ease of use.

Another object of the present invention is to provide an integrated meta information management method and apparatus for integrated management between heterogeneous systems that can manage and query information stored in a plurality of heterogeneous systems with one management program.

It is still another object of the present invention to provide the information necessary for verifying the accuracy and consistency of the data, and to provide information necessary for verifying the accuracy and consistency of the data constructed in the company and the managed data. It provides the following benefits to the whole company.

1) Speed up work

-Users can see the details of the system and data immediately without going through the computerized department, thus reducing the work processing time.

-In case of errors in the system and data, the error details related to them can be inquired immediately, thereby reducing the error processing time.

-The error history related to the change of system and data can be searched immediately, thus reducing the error processing time.

2) cost reduction

-Users can directly view all the information related to system and data without going through the computer department. Therefore, labor cost is reduced by reducing the workload of the computer department and the efficiency of computer manpower.

-All matters related to the system and data have been supplied to the relevant departments by manual management and printed out in spreadsheets or word processors, but the related information is saved in the database, which reduces the cost of purchasing tools and printed materials. .

3) Increase in sales

-Quickly and conveniently search for the information needed by the strategist when establishing a marketing strategy through customer relationship management, providing information to establish the appropriate customer marketing strategy in a timely manner, thereby preventing customer churn and increasing sales.

4) Standardization of work

-In order to efficiently build and use Business Process Meta Data, standardization of work is based on the standardization of work. Even if work is not standardized, managers, managers and users can recognize the necessity of standardization work in order to use Meta Data efficiently.

It is another object of the present invention to provide a method and apparatus for managing integrated meta information having a standardized single integrated metadata database.

It is still another object of the present invention to provide an integrated meta information management method and apparatus which provides a function for converting heterogeneous meta data between heterogeneous metadata into a standardized metadata form.

It is still another object of the present invention to provide an integrated meta information management method and apparatus capable of constructing an integrated mapping model for metadata analysis and correlation for each product constituting a data warehouse and customer relationship management environment.

It is another object of the present invention to provide a method and apparatus for integrated meta information management.

Still another object of the present invention is to provide an integrated meta information management method and apparatus that can improve user convenience through linkage with a web environment.

1 is a block diagram of an integrated metadata management system for integrated management between heterogeneous systems according to an embodiment of the present invention.

2 is a diagram illustrating a process of building an integrated metadata database according to an embodiment of the present invention.

3 is a diagram illustrating a configuration of a metadata management module according to an embodiment of the present invention.

4 is a view showing the configuration of a job management module according to an embodiment of the present invention.

5 is a view showing the configuration of a mapping module according to an embodiment of the present invention.

6 illustrates an MDM manager system menu in accordance with one preferred embodiment of the present invention.

7 is a view showing the configuration of a table-related metadata registration screen according to an embodiment of the present invention.

8 is a diagram illustrating a configuration of a table-related metadata modification screen according to an exemplary embodiment of the present invention.

9 is a diagram illustrating a configuration of a table-related metadata inquiry screen according to an exemplary embodiment of the present invention.

10 is a diagram illustrating a configuration of a table-related metadata deletion screen according to an exemplary embodiment of the present invention.

11 is a diagram showing the configuration of a column related metadata registration screen according to an embodiment of the present invention.

12 is a diagram illustrating a configuration of a column related metadata search and modification screen according to an exemplary embodiment of the present invention.

FIG. 13 is a diagram illustrating a configuration of a column-related metadata deletion screen according to an exemplary embodiment of the present invention. FIG.

14 is a view showing the configuration of a work program-related metadata registration screen according to an embodiment of the present invention.

15 is a diagram illustrating a configuration of a work program-related metadata modification screen according to an exemplary embodiment of the present invention.

16 is a diagram illustrating a configuration of a work program related metadata inquiry screen according to an exemplary embodiment of the present invention.

FIG. 17 is a diagram illustrating a configuration of a work program related metadata deletion screen according to an exemplary embodiment of the present invention. FIG.

18 is a diagram illustrating a configuration of a job log-related metadata inquiry screen according to an exemplary embodiment of the present invention.

19 is a diagram illustrating a configuration of a table mapping related metadata registration screen according to an exemplary embodiment of the present invention.

20 is a diagram illustrating a configuration of a table mapping related metadata detailed information inquiry and modification screen according to an exemplary embodiment of the present invention.

21 is a diagram illustrating a configuration of a table mapping related metadata inquiry and deletion screen according to an exemplary embodiment of the present invention.

22 is a diagram illustrating a configuration of a column mapping related metadata registration screen according to an embodiment of the present invention.

23 is a diagram showing the configuration of a column mapping related metadata modification screen according to an embodiment of the present invention.

24 is a diagram showing the configuration of a column mapping related metadata inquiry and deletion screen according to an embodiment of the present invention.

25 is a diagram illustrating a configuration of an application related metadata management screen according to an embodiment of the present invention.

FIG. 26 illustrates a configuration of a metadata management screen related to table / column association information according to an embodiment of the present invention. FIG.

FIG. 27 is a flowchart illustrating a process of storing meta data of a table, a column, a task, an application, and the like according to an exemplary embodiment of the present invention. FIG.

FIG. 28 is a flowchart illustrating a process of outputting metadata to a screen in response to a metadata inquiry request of a user according to an exemplary embodiment of the present invention. FIG.

<Explanation of symbols for the main parts of the drawings>

101: integrated metadata server 103: mapping server

105: work management server 107: basic information server

109: Data Warehouse Server 111: Metadata Management Module

113: Integrated Metadata Database 115: Mapping Module

117: Mapping Information Database 119: Work Management Module

121: Job Information Database 123: Basic Information Database

125: data warehouse database

According to a preferred embodiment of the present invention to achieve the above objects, in the management of the meta information for the integrated management between heterogeneous systems, the metadata server receives a metadata storage request, the metadata storage request Determine a heterogeneous system corresponding to and access a server corresponding to the heterogeneous system, extract metadata corresponding to the metadata storage request from an information database coupled with the server or a metadata file included in the server, Integrated management between heterogeneous systems converting the extracted metadata into a common format according to a predetermined conversion rule corresponding to the heterogeneous system and storing the converted metadata in an integrated metadata database coupled with the integrated metadata server for An integrated meta information management method and apparatus and system corresponding to the method may be provided.

The metadata may be stored in the integrated metadata database and then queried over the network.

In the integrated metadata management method for integrated management between the heterogeneous systems, when the integrated metadata server receives a metadata deletion request for a specific metadata, metadata corresponding to the metadata deletion request is received from the integrated metadata database. You can delete it.

In the integrated meta information management method for integrated management between the heterogeneous systems, when the integrated metadata server receives a metadata modification request for specific metadata, the metadata file included in the information database coupled with the server or the server includes the metadata file. Extract metadata corresponding to the metadata modification request, modify the extracted metadata corresponding to the metadata modification request, convert the modified metadata into a common format according to a predetermined conversion rule, and The converted metadata may be stored in an integrated metadata database coupled with the integrated metadata server.

The conversion rule may include at least a common format rule and a constraint.

The integrated meta information management method for integrated management between the heterogeneous systems may be processed in a batch operation.

The metadata may be metadata related to system information.

The metadata may be metadata regarding table information.

The metadata may be metadata regarding column information.

The metadata may be metadata regarding table mapping information.

The metadata may be metadata regarding column mapping information.

The metadata may be metadata regarding job information.

The metadata may be metadata regarding job schedule information.

The metadata may be metadata regarding application information.

In the integrated meta information management method for integrated management between the heterogeneous systems, upon receiving a metadata deletion request for a column, the metadata is deleted and the column mapping information corresponding to the column is extracted to extract the column mapping information corresponding to the column. The method may include deleting metadata corresponding to the information and deleting constraint and key information corresponding to the column.

In the integrated meta information management method for integrated management between the heterogeneous systems, upon receiving a request for deleting metadata about a table, the metadata corresponding to the column is deleted by extracting a column corresponding to the table, and corresponding to the column. Extract column mapping information to delete metadata corresponding to the column mapping information, delete metadata corresponding to the table, extract table mapping information corresponding to the table, and extract metadata corresponding to the table mapping information. And deleting the Constraints and Key information corresponding to the column.

The integrated meta information management method for integrated management between the heterogeneous systems may manage user authority information for restricting screen access and use for each of storing, modifying, inquiring, and deleting the metadata for each user.

The logical structure of the integrated metadata database may be configured to store metadata about system information, database information, column information, table information, mapping information, task information, and application information to execute various queries for the information. have.

Next, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an integrated metadata management system for integrated management between heterogeneous systems according to an exemplary embodiment of the present invention.

Referring to FIG. 1, the integrated metadata server 101 includes a metadata management module 111, which is coupled with the integrated metadata database 113.

The integrated metadata server 101 is connected to the mapping server 103 and the job management server 105 through the network 127. Here, the mapping server 103 includes a mapping module 115, and the mapping module 115 is coupled with the mapping information database 117. The job management server 105 includes a job management module 119, and the job management module 119 is coupled with a job information database 121. Here, the mapping server 103 may include a metadata file 133c associated with the mapping information database 117, and the job management server 105 may include the metadata file 133d associated with the job information database 121. It may include.

The integrated metadata server 101 is connected to the server 107 including the basic information database 123 and the server 109 including the DW database 125 via the network 127. Here, the server 107 may include a metadata file 133a associated with the basic information database 123, and the server 109 may include a metadata file 133b associated with the DW database 125. have.

The manager 129 of the integrated metadata server 101 may access the integrated metadata server 101 through the network 127 to register, modify, view, and delete metadata.

The user 131 may access the integrated metadata server 101 through the network 127 to inquire metadata.

The integrated metadata server 101 integrates and stores metadata about tables, column information and mapping information, task information, application information, and the like for basic information.

Therefore, management of metadata through the integrated metadata server 101 facilitates information management of heterogeneous systems including the respective information.

2 is a diagram illustrating a process of building an integrated metadata database according to an embodiment of the present invention.

Referring to FIG. 2, the metadata management module 111 includes a basic database 123, a DW database 125, a mapping information database 117, a job information database 121, metadata files 133a, 133b, and 133c. Meta data is extracted (201) from 133d).

The meta data management module 111 converts the extracted metadata according to a predetermined meta data conversion rule and stores 205 in the integrated metadata database 113 of the integrated metadata server 101.

Below are two examples of conversion rules.

Example 1) Reading Foreign Key information in Sybase tables.

1. Reference system table

sysobjects, sysreferences, syscolumns

A foreign key relationship is a constraint that is considered to be an object, and its type is present in RI in sysobjects.

2. Step

2-1. Using the sysreferences and sysobjects tables, the constraint information existing for each foreign key constraint is read and put in a temporary table.

Constraints on foreign keys are RI in sysobjects, and you can get the key name and creation time.

2-2. Each row in the temporary table represents a foreign key constraint. The number of columns belonging to a foreign key can be up to 16.

2-3. Read the column information for each constraint.

Choose one constraint. If a constraint exists, the loop repeats while the constraint does not exist.

-Get the number of columns in the constraint.

-Continue reading column names as many as the number of columns. Get column name from syscolumns using column ID. Column name gets both foreign column and referenced column name.

Store the information in the integrated metadata database 113.

Example 2) Read Index information given to Sybase table.

1. Reference system table.

sysobjects, sysindexes

2. Step

2-1. Using the sysindexes and sysobjects tables, index information existing in each table is read and stored in a temporary table (eg #tmpindx).

Index has an index id greater than 0 and less than 255.

2-2. Each row in the temporary table represents an index.

2-3. It goes through 3 steps loop to get column by table and index.

Select one table. If the table exists, the loop is repeated while the table does not exist.

-Select one index belonging to the table. If an index exists, the loop is repeated while there is no index for each table.

-Get the number of columns in the index.

To get the column name, use the index_col function to repeat the number of columns to get the column name.

Store the information in the integrated metadata database 113.

3 is a diagram illustrating a configuration of a metadata management module according to an exemplary embodiment of the present invention.

Referring to FIG. 3, the metadata management module 111 extracts metadata about a system, a database, a table, a column, mapping information, work information, and application information from a database of a heterogeneous system connected to the integrated metadata server 101. To convert and save.

The metadata management module 111 is composed of a transmitter 301, a receiver 303, an interface 305, a metadata processor 307, a memory 309, a database processor 311, and the like.

The transmission unit 301 receives the metadata providing screen created by the interface unit 305 or the information processed by the metadata processing unit 307 and transmits the information to the manager 129 or the user 131.

The receiver 303 receives the information transmitted from the manager 129 or the user 131 and transmits the information to the metadata processor 307.

The interface unit 305 receives the information processed by the metadata processor 307 or the metadata information extracted by the database processor 311 and generates a metadata providing screen using the information stored in the memory 309.

The metadata processing unit 307 converts the information or metadata transmitted from the receiving unit 303 or the database processing unit 311, or confirms an error or the like.

The memory 309 stores screen information and a program for the metadata providing screen created by the interface unit 305.

The database processor 311 extracts metadata from the integrated metadata database 113.

In addition, the database processing unit 311 stores the meta data received by the receiving unit 303 and converted by the metadata processing unit 307 in the integrated metadata database 113.

4 is a diagram illustrating a configuration of a job management module according to an exemplary embodiment of the present invention.

Referring to FIG. 4, the job management module 119 stores, deletes, and extracts jobs and job schedules related to data warehouse construction.

The job management module 119 is composed of a transmission unit 401, a reception unit 403, an interface unit 405, a job processing unit 407, a memory 409, a database processing unit 411, and the like.

The transmission unit 401 receives the screen related to the job management created by the interface unit 405, the screen related to the job schedule management, or the information processed by the job processing unit 407 and transmits the information to the manager 129.

The receiving unit 403 receives the information transmitted from the manager 129 and transmits the information to the job processing unit 407.

The interface unit 405 receives information processed by the job processing unit 407 or job information extracted from the database processing unit 411 and uses the information stored in the memory 309 to display a job management related screen or a job schedule management related screen. Create

The job processor 407 checks the error or the like transmitted from the receiver 403 or the database processor 411.

The memory 409 stores screen information and a program for a screen related to job management or a screen related to job schedule management created by the interface unit 405.

The database processor 411 extracts job data from the job information database 121.

In addition, the database processor 411 stores the job data received by the receiver 403 and converted by the job processor 407 in the job information database 121.

5 is a view showing the configuration of a mapping module according to an embodiment of the present invention.

Referring to FIG. 5, the mapping module 115 stores, deletes, and extracts mapping information between tables and mapping information between columns.

The mapping module 115 is composed of a transmitter 501, a receiver 503, an interface 505, a mapping processor 507, a memory 509, a database processor 511, and the like.

The transmitter 501 receives the table mapping management screen, the column mapping management screen, and the information processed by the mapping processor 507, which are created by the interface unit 505, and transmits the information to the manager 129.

The receiver 503 receives the information transmitted from the manager 129 and transmits the information to the mapping processor 507.

The interface unit 505 receives the information processed by the mapping processor 507 and the job information extracted by the database processor 511 to generate a table mapping management screen or a column mapping management screen by using the information stored in the memory 309. do.

The mapping processor 507 confirms an error of the information or the job information transmitted from the receiver 503 or the database processor 511.

The memory 509 stores screen information and a program for the table mapping management screen or the column mapping management screen created by the interface unit 505.

The database processor 511 extracts mapping data from the mapping information database 117.

In addition, the database processing unit 511 stores the mapping data received by the receiving unit 503 and converted by the mapping processing unit 507 in the mapping information database 117.

6 is a diagram illustrating an MDM manager system menu according to an embodiment of the present invention.

Referring to FIG. 6, the Meta Data Management (MDM) manager system extracts, converts, and stores metadata from a database of a heterogeneous system to provide integrated management of information on tables, columns, mapping information, task information, and application information. System.

The MDM manager system menu 601 includes user management 603, system management 605, DB (database) management 607, job (job) management 609, mapping management 611, application (application) management ( 613, and error management 615.

The user management 603 includes a user 617, a DB user 619, a notice 620, and the like.

System management 605 includes system 621, DBMS 623, business system 625, META code 627, system error code 629, and the like.

DB (database) management 607 includes a database 631, a subject area 633, table information 635, column information 637, and the like.

Job (job) management (609) includes job program (639), job HISTORY (641), job relationship (643), job log (645), job error (647), ACTIVE job (649), external file (651). , External file HISTORY 653, work tool 655, and the like.

Mapping management 611 includes table mapping 657, column mapping 659, and the like.

Application (application) management 613 includes an application 661, a table / column relationship 663, a user group / user-specific relationship 664, and the like.

Error management 615 includes error request 665, error handling 667, consistency verification 669, and the like.

7 is a diagram illustrating a configuration of a table-related metadata registration screen according to an exemplary embodiment of the present invention.

Referring to FIG. 7, the registration operation reads dictionary information directly from a physical database and shows table information not yet registered. The user can optionally register the table in the unregistered table.

The table-related metadata registration screen 701 is composed of an inquiry condition input portion 703, a previously registered table list 705, a list of registered target tables 707, a new table creation button 709, a registration button 711, and the like. It is.

The inquiry condition input portion 703 is composed of a work system 713, a database 715, and a search button 717.

The business system 713 and the database 715 are essential for the registration work, and at the same time, the basic unit of the registration work. If you click the Search button without selecting them, an error message box will appear and the search will not be performed.

The search button 717 in the registration operation indicates an existing registration table meeting the search condition in the existing registration table list 705, and a new registration target table list in the registration target table list 707, and the registration button 711 is activated. do. Here, the selection part 719 of the table to be registered in the registration is checked from the list shown in the registration target table list 707. When the registration button 711 is clicked, only the table checked for registration selection is registered.

Each work step is as follows.

1) read table information

2) read table constraints

3) Read Column Information

4) Read Column Constraints

5) Registering Table Information

6) Register Table Constraints

7) Register Column Information

8) Register Column Constraints

8 is a diagram illustrating a configuration of a table-related metadata modification screen according to an exemplary embodiment of the present invention.

Referring to FIG. 8, the table-related metadata modification screen 801 includes an inquiry condition input portion 803, a pre-registered table list portion 805, a detail history portion 807, a refresh button 809, And a correction button 811.

The inquiry condition input portion 803 includes a business system selection combo box list 813, a subject area selection combo box list 815, a database selection combo box list 817, a table selection combo box list 819, and a search button 821. ) And the like.

The previously registered table list portion 805 shows a list of a business system, a database ID, a database name, a table English name, a subject area, and the like of a table in which meta information is registered.

The detail part 807 includes a business system selection combo box list 823, a database selection combo box list 825, a table English name (827), a table Korean name (829), a table type (831), and a subject area selection combo box list. 833, table creator 835, first creation date 837, last modification date 839, last backup date 841, table description 843, and the like.

Correction can be done in two ways.

The refresh button 809 reads table information from the physical database dictionary in units of work systems and databases, and corrects information changes on already registered tables. This task is not a health problem, but a task to make sure that the information about the tables already registered in one batch matches the information contained in the DBMS of the physical system.

The correction button 811 is a basic method of correcting items requiring user input on a table basis.

Buttons 809 and 811 which cause the two tasks are only activated when a search for the corrective task is performed.

When the search button 821 is selected in the correcting operation, the previously registered table list meeting the condition is displayed in the previously registered table list portion 805 and the refresh button 809 is activated.

If a table to be modified is selected as a click event in the previously registered data table list 805, information on the selected table row is shown in the details section 807 below.

The subject area selection combo box list 833 appears to be limited to the work system to which the table belongs, and values can be registered only therein.

Modification is possible only by entering the table Korean name (829) and the table constructor (835). If no input is made, a warning message box appears.

When the modified value is entered in the MDM manager system, the screen is initialized and the modified information is reflected in the search result data table.

The refresh button 809 reflects the changes in the information of the tables already registered in the physical database in the previously registered table list part 805 using the selected business system and the database as the refresh condition.

For the refresh operation, the business system and the database are required choices and at the same time, the basic unit of the refresh operation. If you do not select them, a warning message box will appear and the refresh will be canceled.

When a refresh operation is normally performed, unlike in a physical database, a message box shows the number of tables on which a refresh operation has been performed and the refresh button 809 is deactivated.

In the refresh operation, the information of the physical database has a higher priority than the information of the currently registered MDM system, and when the values of the two data are different, the values read from the system are reflected. If there is no value in the physical database, MDM system information takes precedence.

9 is a diagram illustrating a configuration of a table-related metadata inquiry screen according to an exemplary embodiment of the present invention.

Referring to FIG. 9, the inquiry job is a function of retrieving table information already registered in the MDM system.

The table-related meta data inquiry screen 901 is composed of an inquiry condition input portion 903, a previously registered table list portion 905, and a table detail description portion 907.

The query condition input portion 903 includes a work system selection combo box list 909, a subject area selection combo box list 911, a database selection combo box list 913, a table selection combo box list 915, and a search button 917. ) And the like.

The registered table list portion 905 includes a business system, a database ID, a database name, a table name, a subject area, and the like.

The table detail portion 907 includes a column English name, a column Korean name, a table ID, a table name, and the like.

All selection items 911, 913, and 915 before selecting a work system from the work system selection combo box list 909 are deactivated.

The work system list of the work system selection combo box list 909 contains all work systems currently stored in the MDM database. When a business system is selected, you can select a database, subject area, and table that exist as all sub-concepts, and only the values corresponding to the selected business system are listed.

When a work system is selected, only databases corresponding to the selected work system appear in the database selection combo box list 913.

When a database is selected, the list of tables represents only the values that belong to that database.

When a work system is selected, a list of subject areas corresponding to the selected work system is displayed in the subject area selection combo box list 911.

Subject areas operate independently of the database and only appear to be dependent on the business system.

When a subject area is selected, the table list shows only the values that belong to that subject area.

The table selection combo box list 915 shows a list of tables that can be viewed in the selected business system and database or subject area.

The list of tables appears differently depending on whether a work system, database, or subject area is selected as a higher concept.

The table list shown in the example of the upper screen exists only in the meta work system's MDM database, and only the items whose subject area is the system.

If the search button is clicked, the table information registered in the MDM management system is searched using the values of the selected work system, database, subject area, and table.

If no condition is selected, all table information registered in the MDM management system is displayed.

When the search is completed, the search results are displayed in the previously registered table list portion 905.

The information of the searched result is composed of work system name, database ID, table English name, table Korean name, subject area, table type, table creator, first created date, last modified date, last modified user, last backup date, table description.

From among the search results displayed in the previously registered table list portion 905, the column to which the table to which the column information of the table is to be viewed is selected.

Then, column information of the selected table is displayed in the table detail portion 907.

In the table detail portion 907, column information of the table is displayed in a column Hangul name.

The table detail part 907 includes the column English name, column Korean name, table English name, table Korean name, database ID, database name, business system name, column type, column length, column description, integer digit, decimal place, column default value, column maximum Contains the value, null, creation date, constructor information, and so on.

10 is a diagram illustrating a configuration of a table-related metadata deletion screen according to an exemplary embodiment of the present invention.

Referring to FIG. 10, a delete operation reads dictionary information directly from a physical database and shows table information that is registered but does not exist in an actual database. The user can optionally delete a table from the drop target table.

The basic operation method of the delete operation is the same as the registration operation described in FIG.

The table-related metadata deletion screen 1001 includes a query condition input portion 1003, a previously registered table list 1005, a table to be deleted list 1007, a table button 1009 to be deleted, and a delete button 1011. have.

The inquiry condition input portion 1003 includes a work system selection combo box list 1013, a database selection combo box list 1015, a search button 1017, and the like.

The registered table list 1005 includes a business system, a database ID, a database name, a table English name, a subject area, and the like.

The deletion target table list 1007 includes a deletion selection check part 1019, a work system ID, a database ID, a table ID, a table Korean name, and the like.

The business system and database are essential for the deletion and at the same time the basic unit of the deletion. If you click the search button 1017 without selecting them, an error message box appears and no search is performed.

When the search button 10107 is clicked on, a previously registered table meeting the search condition is displayed in the previously registered table list 1005, the delete target table is shown in the delete target table list 1007 below, and the delete button is activated.

If there is no delete object, the message box “No table to delete exists” is displayed and the delete button 1011 is not activated.

The selection method of the object to be deleted is the same as that of registration, and the object to be deleted by clicking the delete button 1009 is to target all tables in which the deletion selection check part 1019 is checked in the object to be deleted.

The default target of deletion is to delete from all information MDM systems in the table of deletion targets.

If the delete button 1011 is selected, a dialog box is displayed to confirm whether to delete the file. If the confirm button is selected in the dialog box, the delete operation is performed. When the delete operation is completed, the message box “Deleted successfully” appears.

When a table is deleted, all information related to the table (column mapping, table mapping, table application associations, columns, table constraints, table operating policy, table modification information, table backup information, table consistency verification) is deleted.

11 is a diagram illustrating a configuration of a column related metadata registration screen according to an exemplary embodiment of the present invention.

Referring to FIG. 11, the column related metadata registration screen 1101 may include a query condition input portion 1103, a previously registered column list 1105, a register target column list 1107, a new column button 1109, and a register button ( 1111).

The inquiry condition input portion 1103 includes a work system selection combo box list 1113, a table selection combo box list 1115, a database selection combo box list 1117, a search button 1119, and the like.

The registered column list 1105 includes a column English name, a column Korean name, a table ID, a table name, and the like.

The registration target column list 1107 includes a registration column check part 1121, a work system ID, a database ID, a column ID, and the like.

The registration operation reads dictionary information directly from the physical database and displays column information that is not yet registered.

The business system, database, and tables are mandatory options for registration, and at the same time, the basic unit of registration.

If you click the search button 1119 without selecting them, an error message box appears and no search is performed.

The search button 1119 in the registration operation shows the pre-registered column meeting the search condition in the pre-registered column list 1105, and the new register-target column list is shown in the register-target column list 1107 below, and the register button ( 1111).

If there are no additional registration targets as a result of the search, a message box “No columns to register” is displayed and the registration button 1111 is not activated.

The registration button 1111 registers all column information existing in the new registration target column data table as MDM system data.

Column information does not exist independently of tables in a physical database. Therefore, the column cannot be selectively registered and only registers all the existing columns of the physical database.

When the registration operation is completed, the registration target column data table information is initialized and the result registered in the previously registered column list 1105 is reflected.

12 is a diagram illustrating a configuration of a column related metadata search and modification screen according to an exemplary embodiment of the present invention.

Referring to FIG. 12, the column-related metadata inquiry / modification screen 1201 includes an inquiry condition input portion 1203, a pre-registered column list portion 1205, a detailed inquiry / modification portion 1207, and the like.

The query condition input portion 1203 includes a business system selection combo box list 1209, a database selection combo box list 1213, a table selection combo box list 1211, a column selection combo box list 1215, and a search button 1217. And the like.

The previously registered column list portion 1205 shows a list of column English names, column Korean names, table IDs, table names, etc. of the columns in which meta information is registered.

The detail inquiry / modification part 1207 includes a business system selection combo box list 1219, a database selection combo box list 1221, a table English name (1223), a column English name (1225), a column Korean name (1227), and a column type (1233). ), Column length 1235, null presence 1237, column default value 1239, column maximum value 1241, refresh button 1229, modify button 1231, and the like. .

The default operation of the initial call screen is inquiry. All operation functions begin by selecting the search button 1217, and the selection of the search condition consists of selecting the work system in the inquiry condition input portion 1203. As shown in FIG. The operation result of the search button 1217 is determined by the selected search condition.

The inquiry / modification task is to retrieve column information already registered in the MDM system and to modify the information.

All selection conditions before selecting a work system are disabled.

The selection list of the work system contains all the work systems currently stored in the MDM database. When a work system is selected, the list is made using only the values corresponding to the database and tables that exist as all sub-concepts.

When a database is selected, the list of tables represents only the values that belong to that database.

The table list that appears in the table selection combo box list 1211 is different depending on the business system and the database selection. When the table is selected, the column name list appears in the column selection combo box list 1215 so that the column can be selected.

Search column information registered in MDM management system by using selected business system, database, table and column name.

If no condition is selected, all column information registered in the MDM management system is displayed.

When the search button 1217 is clicked on, the search result is displayed in the previously registered column list portion 1205 and the refresh button 1229 is activated.

The items of the search result are column English name, column Korean name, table English name, table Korean name, database ID, database, business system, column type, column length, column description, integer place, decimal place, column default value, column maximum value, Contains null, creation date, and constructor information.

The refresh button 1229 reflects the changes among the column information already registered in the physical database by refreshing the selected business system, database, and table.

For the refresh operation, business system, database, and table are required items and at the same time, the basic unit of refresh operation.

If you do not select them, a warning message box appears stating "Please select a business system, database, and table" and the refresh operation will be canceled.

When the refresh operation is normally performed, the number of columns in which the refresh operation is performed is different from the physical database, and the refresh button 1229 is deactivated.

In the refresh operation, the information of the physical database has a higher priority than the information of the currently registered MDM system, and when the values of the two data are different, the values read from the system are reflected. However, if there is no value in the physical database, the MDM system information takes precedence.

The process of selecting a target for correction and correcting the information will be described below.

If a column to be modified is selected as a click event in the previously registered column list part 1205, information of the selected table column is shown in the detailed inquiry / modification part 1207 below.

When the modification is made, the modification information is reflected in the MDM system and the new modification information is reflected in the previously registered column list part 1205.

In addition, the values of the objects constituting the screen are initialized.

FIG. 13 is a diagram illustrating a configuration of a column-related metadata deletion screen according to an exemplary embodiment of the present invention. FIG.

Referring to FIG. 13, the column-related meta data deletion screen 1301 includes a query condition input portion 1303, a previously registered column list portion 1305, a column column to delete list portion 1307, a column button 1309 to delete, and deletion. Button 1311 or the like.

The inquiry condition input portion 1303 includes a work system selection combo box list 1313, a database selection combo box list 1317, a table selection combo box list 1315, a search button 1319, and the like.

The registered column list part 1305 includes a column English name, a column Korean name, a table English name, a table Korean name, and the like.

The deletion target column list part 1307 includes a deletion selection check part 1321, a work system ID, a database ID, a table English name, a column English name, and the like.

The delete operation reads dictionary information directly from the physical database and shows column information that is registered but does not exist in the actual database.

The basic operation of the delete operation is the same as the registration operation.

For deletion, work system, database, and table are essential choices and at the same time, basic unit of deletion. If you click the search button 1319 without selecting them, an error message box appears and no search is performed.

The search button 1319 in the delete operation shows the pre-registered column that meets the search condition in the pre-registered column list portion 1305, the delete target column list is shown in the delete target column list portion 1307 below, and the delete button Activate (1311).

If there is no object to delete, the message box “No column to delete exists” is displayed and the delete button is not activated.

The deletion target that recognizes the click of the delete button 1311 is to delete all column information existing in the deletion target table from the MDM system.

Since the default policy of deletion does not exist independently of tables in the physical database like registration, you cannot exclude lists that you do not want to delete.

If the delete button 1311 is selected, a dialog box for confirming whether or not to delete is displayed. If the confirm button (not shown) is clicked, the delete operation is performed.

When the delete operation is complete, a message box appears to indicate completion.

14 is a diagram illustrating a configuration of a work program related metadata registration screen according to an exemplary embodiment of the present invention.

Referring to FIG. 14, the work program related metadata registration screen 1401 is composed of an inquiry condition input part 1403, a pre-registered job list part 1405, a job registration part 1407, and the like.

The inquiry condition input portion 1403 includes a work system selection combo box list 1409, a system selection combo box list 1413, a work tool selection combo box list 1411, a search button 1415, and the like.

The pre-registered work list portion 1405 includes a work system, a work ID, a work tool ID, a system code, and the like.

The job registration portion 1407 includes a availability setting portion 1417, a job execution cycle selection combo box list 1418, a registration button 1421, a registration target job list portion 1423, and the like.

In the availability setting portion 1417, at least one of available and unavailable must be selected.

The registration target work list portion 1423 includes a work system name, work tool name, system name, work program name, and the like.

Work management refers to the management (work program registration, modification, deletion, inquiry, work log inquiry) of all work performed through the work tool.

1) Registration of a work program means to register information registered in a work tool as MDM metadata.

2) Modification refers to the modification of user input items among the contents registered in the MDM meta data and the collective modification of the information registered in the work tool.

3) Deletion compares the contents registered in the MDM metadata with the information registered in the work tool and removes the work deleted in the work tool from the MDM metadata.

4) Inquiry refers to search by condition of contents registered in MDM metadata.

5) Job log inquiry refers to inquiry of log information generated through execution of a job registered in a job tool.

In the work program related metadata registration screen 1401, the basic work is started by selecting a work system, a system, a work tool and pressing a search button 1415 similarly to the inquiry.

When the search button 1415 is pressed, search results of the selected work system, system, and work tool are displayed in the pre-registered work list portion 1405, and at the same time, the registered target work list portion 1423 can be registered in the pre-registered work list portion 1405. The object appears.

To register the actual work program, input the contents of the above condition items (availability, work execution cycle, etc.), and then drag in the registration target table of the registration target work list portion 1423 by the desired column, and then register. The button 1421 is pressed.

After the registration button 1421 is pressed, a confirmation message indicating that as many rows as selected are registered when registration is normally performed.

15 is a diagram illustrating a configuration of a work program-related metadata modification screen according to an exemplary embodiment of the present invention.

Referring to FIG. 15, the work program related metadata modification screen 1501 includes an inquiry condition input portion 1503, a pre-registered work list portion 1505, a detail history portion 1507, and a refresh button 1509. And a correction button 1511.

The inquiry condition input portion 1503 is composed of a work system selection combo box list 1513, a system selection combo box list 1517, a work tool selection combo box list 1515, a search button 1519, and the like.

The pre-registered work list portion 1505 includes a work system, a work ID, a work tool ID, a system code, and the like.

The detail portion 1507 includes a work system selection combo box list 1521, a system code selection combo box list 1523, a work program path input portion 1525, an initial creation date input portion 1527, and a work execution cycle input portion. 1515, a log file name input portion 1531, a work program description input portion 1533, and the like.

The work program related metadata modification screen 1501 is a screen for modifying information about a job meeting a specific condition. The work program is selected by selecting a work system, a system, a work tool, and clicking the search button 1519 to search for a registered work program. can do.

If one job is selected from the search results displayed in the previously registered job list part 1505, the stored information of the selected item is displayed in the detail item part 1507. The information may be modified by selecting or inputting each item of the detail portion 1507.

16 is a diagram illustrating a configuration of a work program related metadata inquiry screen according to an exemplary embodiment of the present invention.

Referring to FIG. 16, the work program related meta data inquiry screen 1601 is composed of an inquiry condition input portion 1603, a pre-registered work list portion 1605, a detail history portion 1607, and the like.

The inquiry condition input portion 1603 includes a work system selection combo box list 1609, a system selection combo box list 1613, a work tool selection combo box list 1611, a search button 1615, and the like.

The pre-registered work list portion 1605 includes a work system, a work ID, a work tool ID, a system code, and the like.

The detailed search condition input portion 1607 may include an initial creation date setting portion 1617, a change date setting portion 1619, a periodicity setting portion 1621, a work execution cycle selection combo box list 1623, and an availability setting portion ( 1625).

By default, all tasks are selected from the work system of the work system selection combo box list 1609, the system of the system selection combo box list 1613, the work tools of the work tool selection combo box list 1611, and then the search button 1615. Start by pressing.

In particular, the work tool selection combo box list 1611 is initially disabled and then activated when a system in the system selection combo box list 1613 is selected.

When a work system, a system, a work tool is selected and a search button 1615 is clicked on, a search result that satisfies a condition is displayed in the data table of the pre-registered work list portion 1605.

If the user wants to search more detailed than the basic search, the user selects each detailed search item in the detailed search condition input portion 1607 below and presses the detailed search button 1627.

If the periodicity setting part 1621 selects whether or not the periodic work is all, the search item for the periodic work is not included in the actual search condition.

In addition, the work execution cycle selection combo box list 1623 is activated only when the search item for periodic work is periodicity.

In the detailed inquiry condition input portion 1607, it is assumed that the inquiry condition is finally set as follows.

Date of creation: 2000.10.31

Date of Change: 2000.11.2

Periodic work: periodicity

Job execution cycle time: 20 minutes

Available: Yes

Each of the five conditions is connected by AND so that the entire search condition is set. When the detailed search button 1627 is pressed, a search result satisfying the five conditions is displayed in the data table of the previously registered work list portion 1605. appear.

17 is a diagram illustrating a configuration of a work program related metadata deletion screen according to an exemplary embodiment of the present invention.

Referring to FIG. 17, the work program-related metadata deletion screen 1701 is composed of an inquiry condition input portion 1703, a pre-registered work list portion 1705, a delete target work list portion 1707, and the like.

The inquiry condition input portion 1703 includes a work system selection combo box list 1709, a system selection combo box list 1713, a work tool selection combo box list 1711, a search button 1715, and the like.

The pre-registered work list portion 1505 includes a work system, a work ID, a work tool ID, a system code, a work classification, and the like.

The deletion target job list part 1707 includes a deletion selection check part 1725, a work system ID, a job ID, a work tool ID, a system code, and the like.

The process of retrieving the pre-registered work list to delete the work program is the same as the basic inquiry of FIG.

When the delete target job list appears in the delete target job list portion 1707, the delete selection check portion 1917 of the delete job is checked, and the delete button 1719 is clicked.

When you click the delete button 1719, a confirmation message box appears asking if you want to delete.

If you click the OK button in the Confirm Delete message box, the job is deleted.

18 is a diagram illustrating a configuration of a job log-related metadata inquiry screen according to an exemplary embodiment of the present invention.

Referring to FIG. 18, the job log related metadata inquiry screen 1801 is composed of an inquiry condition input portion 1803, an inquiry result list portion 1805, and the like.

The inquiry condition input portion 1803 includes a work system name selection combo box list 1807, a work tool name selection combo box list 1809, a work cycle setting portion 1811, a log generation start date setting portion 1813, and a log generation end date. The setting part 1815, the work person input part 1817, the person inquiring button 1819, the job log state setting part 1821, the search button 1823, etc. are comprised.

The inquiry result list portion 1805 includes a log ID, a work system name, a work ID, a work tool name, a work log status, and the like.

After selecting each search condition of the search condition input portion 1803 and pressing the search button 1823, a search for a desired condition is performed.

When the search for the inquiry condition is completed, the inquiry result list appears in the inquiry result list portion 1805.

When the person inquiring button 1819 is pressed, an employee inquiry screen (not shown) is called. When the employee name to be searched is selected on the employee inquiry screen (not shown) and the confirmation button (not shown) is selected, the name of the selected person in charge is displayed on the job person input part 1817.

19 is a diagram illustrating a configuration of a table mapping related metadata registration screen according to an exemplary embodiment of the present invention.

Referring to FIG. 19, the table mapping related metadata registration screen 1901 may include a target table information input portion 1901, a source table information input portion 1905, a table mapping result portion 1907, and a mapping rule input portion 1909. , Mapping description input portion 1911, add mapping button 1929, delete mapping button 1931, delete all mapping button 1933, update button 1935, apply button 1937, cancel button 1939, etc. Consists of.

The target table information input portion 1903 includes a work system selection combo box list 1913, a database selection combo box list 1919, a start job selection combo box list 1915, an end job selection combo box list 1921, a table selection Combo box list 1917 or the like.

The source table information input portion 1905 includes a work system selection combo box list 1923, a database selection combo box list 1925, a table selection combo box list 1927, and the like.

The table mapping result portion 1907 includes a target table ID, a target table name, a source business system name, and the like.

Manual registration and modification of table mapping information can be done, but target tables that have already been mapped by the loading tool cannot be registered, modified, or deleted.

In other words, if the start and end tasks are different from the mapped start and end tasks, they can be registered, modified and deleted.

The work system selection combo box list 1913 of the target table information input portion 1903 is clicked to select a work system to be modified.

When a work system is selected, information related to the selected work system is displayed in the database selection combo box list 1919, the start task selection combo box list 1915, and the end task selection combo box list 1921.

In this case, you must select a business system to select the database, start job, end job, and table information.

Click the Select Database combo box list (1919) to select the database you want to modify.

When a database is selected, table information related to the work system and the database is displayed in the table selection combo box list 1927.

After the database is selected, the start task selection combo box list 1915 of the target table information input portion 1903 is clicked to select a start task to be registered.

When you select a startup task, the table selection combo box list 1917 displays table information related to the work system, the database, and the startup task.

After selecting the start job, click the end job selection combo box list 1921 of the target table information input portion 1901 to select the end job to be registered.

When the end task is selected, table information related to the selected work system, database, start task, and end task is displayed in the table selection combo box list 1917.

Before selecting a target table from the table selection combo box list 1917, a database, start task, and end task must be selected.

The work system of the source table to be mapped to the selected target table is selected from the work system selection combo box list 1923 of the source table information input portion 1905.

Once the source work system is selected, the source database can be selected from the database selection combo box list 1925.

Select a database of source tables to be mapped to the selected target table from the database selection combo box list 1925.

Once the source database is selected, the source table can be selected from the table selection combo box list 1917.

As described above, after setting target table information and source table information to be registered for mapping, and clicking the add mapping button 1929, it appears in the table mapping result portion 1907 of the set mapping information screen.

The source table for which table mapping is set is deleted from the source table list.

By clicking the add mapping button 1929, the table mapping information is not registered but is displayed only on the screen. If you want to reflect the mapping registration, you must click the update button (1935). Here, when the mapping rule for the table mapping is input in the mapping rule input portion 1909, the mapping description is input in the mapping description input portion 1911, and the update button 1935 is clicked, the input mapping rule and the mapping description are input. Is also stored in the database together.

In the table mapping result portion 1907, when a row of table mapping information to be deleted is selected and the delete mapping button 1931 is selected, the selected table mapping information is deleted.

When the apply button 1937 is clicked on, the information manipulated through the table mapping information registration screen 1901 is stored in the integrated metadata database 113.

If the cancel button 1939 is clicked on, all of the information operated through the table mapping information registration screen 1901 is canceled.

20 is a diagram illustrating a configuration of a table mapping related metadata modification screen according to an exemplary embodiment of the present invention.

Referring to FIG. 20, the screen mapping related metadata detailed information inquiry and modification screen 2001 includes a target table information input part 2003, a source table information input part 2005, a mapping rule input part 2007, and a mapping description input. Portion 2009, button bar portion 2011, and the like.

The configuration and operation of the target table information input portion 2003 and the source table information input portion 2005 are the same as those described in FIG. 19.

The button bar portion 2011 includes a save button 2023, a cancel button 2025, and the like.

When the contents of the target table information input portion 2003, the source table information input portion 2005, the mapping rule input portion 2007, the mapping description input portion 2009, etc. are modified and the save button 2023 is clicked on, the changed values are changed. The contents are stored as table mapping information.

When the cancel button 2025 is clicked, the screen mapping related metadata detailed information inquiry and modification screen 2001 is terminated.

21 is a diagram illustrating a configuration of a table mapping related metadata inquiry and deletion screen according to an exemplary embodiment of the present invention.

Referring to FIG. 21, the table mapping related metadata inquiry and deletion screen 2101 includes a target table information input portion 2103, a source table information input portion 2105, a table mapping result portion 2107, and a search button 2108. , Delete button 2109, and the like.

The target table information input portion 2103 includes a work system selection combo box list 2111, a database selection combo box list 2113, a subject area selection combo box list 2115, a table selection combo box list 2117, and the like. have.

The source table information input portion 2105 includes a business system selection combo box list 2119, a database selection combo box list 2121, a subject area selection combo box list 2123, a table selection combo box list 2125, and the like. have.

The configuration and operation of the target table information input portion 2003 and the source table information input portion 2005 are the same as those described in FIG. 19.

In the target table information input portion 2003 and the source table information input portion 2005, the target table information and the source table information to be inquired are set and the search button 2108 is clicked. A list of search results that match the criteria appears.

When the table mapping result portion 2107 is deleted and the select selection check portion 2127 is checked and the delete button is clicked, the stored table mapping information is deleted.

22 is a diagram illustrating a configuration of a column mapping related metadata registration screen according to an exemplary embodiment of the present invention.

Referring to FIG. 22, the column mapping related metadata registration screen 2201 includes a target column information input part 2203, a source column information input part 2205, a column mapping result part 2207, and a mapping rule input part 2209. And a mapping description input part 2211, a mapping add button 2231, a mapping delete button 2233, a mapping delete button 2235, a registration button 2237, a cancel button 2239, and the like.

The target table information input portion 2203 includes a business system selection combo box list 2213, a database selection combo box list 2215, a table selection combo box list 2215, a start / end job selection combo box list 2219, and a column. And a selection combo box list 2221.

The source table information input portion 2205 includes a business system selection combo box list 2223, a database selection combo box list 2225, a table selection combo box list 2227, a column selection combo box list 2229, and the like. .

The table mapping result portion 2207 includes a target table ID, a target table name, a source business system name, and the like.

Registration, deletion, and deletion of table mapping information operate in the same manner as described in FIG. 19.

The operation of the registration button 2237 is the same as the apply button 1937 of FIG.

The operation of the cancel button 2239 is the same as the apply button 1939 of FIG.

FIG. 23 is a diagram illustrating a configuration of a column mapping related metadata modification screen according to an exemplary embodiment of the present invention. FIG.

Referring to FIG. 23, the configuration of the column mapping related metadata modification screen 2301 includes a target column information input portion 2303, a source column information input portion 2305, a mapping rule input portion 2307, and a mapping description input portion ( 2309), button bar portion 2311, and the like.

The target table information input portion 2303 includes a business system selection combo box list 2313, a database selection combo box list 2315, a table selection combo box list 2317, a column selection combo box list 2319, and a start job selection combo. And a list of boxes 2321, an end job selection combo box list 2323, and the like.

The source table information input portion 2205 includes a business system selection combo box list 2329, a database selection combo box list 2233, a table selection combo box list 2333, a column selection combo box list 2335, and a start job selection combo. It consists of a box list 2337, an end job selection combo box list 2339, and the like.

The button bar portion 2311 includes a save button 2325, a cancel button 2327, and the like.

The modification of the column mapping information is operated in the same manner as described in FIG. 20.

24 is a diagram illustrating a configuration of a column mapping related metadata search and deletion screen according to an exemplary embodiment of the present invention.

Referring to FIG. 24, the column mapping related metadata inquiry and deletion screen 2401 includes a target column information input portion 2403, a source column information input portion 2405, a column mapping result portion 2407, and a search button 2408. And a delete button 2409 and the like.

The target column information input portion 2403 includes a business system selection combo box list 2411, a database selection combo box list 2413, a subject area selection combo box list 2415, a table selection combo box list 2418, and the like. have.

At least one table may be selected in the table selection combo box list 2418. When the search button 2408 is clicked on, column mapping information for which a column belonging to the selected target table 2418 is used as a target column is queried.

The source table information input portion 2405 includes a business system selection combo box list 2419, a database selection combo box list 2421, a subject area selection combo box list 2423, a table selection combo box list 2425, and the like. have.

At least one table may be selected in the table selection combo box list 2425. When the search button 2408 is clicked on, column mapping information for which a column belonging to the selected target table 2427 is a source column is inquired.

When target column information and source column information to be inquired are set in the target column information input part 2403 and the source column information input part 2405, and the search button 2408 is clicked on, the column mapping result part 2407 is searched. A list of search results that match the criteria appears.

When the column mapping result part 2407 is deleted and the check selection part 2429 is checked while the column mapping information is inquired, the stored column mapping information is deleted.

Inquiry and deletion of the column mapping information operate in the same manner as described in FIG. 21.

25 is a diagram illustrating a configuration of an application related metadata management screen according to an exemplary embodiment of the present invention.

Referring to FIG. 25, the application-related meta data management screen 2501 includes a query condition input part 2503, a pre-registered application list part 2505, a detail description part 2507, a registration button 2509, and a modification button 2511. ), Delete button 2513, and the like.

The inquiry condition input portion 2503 includes a work system selection combo box list 2515, an application English name 2519, an application program name / screen name 2517, a search button 2521, and the like.

The registered application list portion 2505 includes an application code, a work system name, a creation tool name, an application program screen name, and the like.

The detail part 2507 includes an application English name input part 2523, a work system name input part 2525, an application program screen name 2527, a creation tool name input part 2529, a development list input part 2253, and a generation The date input part 2533, the change date input part 2535, etc. are comprised.

Application management refers to management of all currently used applications, application screens and reports.

The purpose of application management is to efficiently and efficiently maintain the information of the most current application through data management of the application name and file name, directory location, developer, development purpose, creation date, and change date for the currently running application. Manage consistent applications

In addition, the purpose of application management is to manage the mapping relationship between the application and the data (column) to facilitate the rapid and accurate change of the application and data changes and functions, and to quickly analyze and recover the cause of the error when an error occurs.

Application management is managed through user and administrator input due to the nature of the data.

The detailed menu of the application management can register, modify, delete, and inquire the mapping between the application menu and the registered application and the registered data (column), which has the function of registering, modifying, deleting, and inquiring the application. It is divided into table / column association menu.

In addition, there are department-specific and employee-specific relationship menus that can map permissions for applications, organizations (departments), and employees, and authority for MDM applications to users registered as MDM users with department-specific and employee-specific relationship menus. You can also set

The application inquiry may inquire the currently registered application from the work system, the application English name (application code), and the application program name / screen name as a search condition.

Here, the application program name / screen name is a program name in the case of an application program, a screen name in the case of a screen, and a screen name in the case of all inputs.

The inquiry can be searched by the selected condition of any item among the selection combo box lists 2515, 2517, and 2519 constituting the inquiry condition input portion 2503.

The application English name selection combo box list 2519 and the application program name / screen name selection combo box list 2517 are linked to each other. Therefore, if the application English name selection combo box list 2519 is selected, the application program name / screen name selection combo box list 2517 is set, and if the application program name / screen name selection combo box list 2517 is selected, the application English name selection is selected. The combo box list 2519 is automatically set.

If the search button 2521 is pressed after the search condition is selected, a result matching the set search condition is displayed in the previously registered application list part 2505.

In the details section 2507, details about the selected column of the list of the previously registered application list section 2505 are displayed, and after changing each item by the user's input, the application information is changed by clicking the modify button 2511. Stored.

Application information may be registered before or after searching for the application information.

When application-related information is input to each item of the details section 2507 and the registration button 2509 is clicked, the input application information is stored.

After the detailed information is searched, one or more application information to be deleted is selected in the previously registered application list part 2505 and the delete button 2513 is clicked. Then, a deletion confirmation message box appears. If you click the confirm button (unregistered) in the deletion confirmation message box, the selected application information is deleted.

FIG. 26 is a diagram illustrating a configuration of a table / column association information related metadata data management screen according to an exemplary embodiment of the present invention. FIG.

Referring to FIG. 26, the metadata / data management screen 2601 related to table / column association information includes a query condition input portion 2603, a previously registered table / column association information list portion 2605, an application English name 2607, and a column list ( 2609), the selected column list list portion 2611, the add button 2627, the delete button 2629, the add all button 2651, the delete all button 2633, the apply button 2635, and the like.

The inquiry condition input portion 2603 includes the application work system selection combo box list 2613, the application English name selection combo box list 2615, the work system selection combo box list 2615, the subject area selection combo box list 2621, and the application. It consists of a program name / screen name selection combo box list 2621, a database selection combo box list 2623, a table selection combo box list 2625, and the like.

The registered table / column association information list portion 2605 includes an application English name, a business system name, a database ID, a subject area, a table name, and the like.

In the inquiry condition input portion 2603, the search can be performed even if the application search condition or the table search condition is not selected or selected.

The work system shown in the application work system selection window shows only the work system to which the registered application belongs, and the application English name (application code) and the application program name / screen name cannot be selected until the work system is selected.

If you select the application work system, you can select the application English name and the application program name / screen name.

The work system shows all available work systems and allows you to select the database and subject area belonging to the selected work system when selecting a work system. The database selection window and the subject area selection window are not correlated, so they do not affect each other in the selection.

When selecting a database or subject area, a list of tables belonging to the selection criteria is displayed in the table selection window.

If you click the search button after selecting the search condition, the contents mapped between the column and the application that satisfy the search condition will be shown in the table.

If you want to search again with a new search condition, you can clear the search condition and click the search button. If you want to initialize all the search conditions and search results, select the search function again and the contents of all search screens are initialized.

The lower part of the screen is used to select registration, modification and deletion functions.

Since the English name of the application 2607 at the bottom of the screen is associated with the application work system of the search condition, applications belonging to the work system selected when the application work system is selected are displayed.

The column list 2609 at the bottom of the screen is associated with the table search condition. In other words, selecting a table causes the columns defined in the table to appear in the column list.

The selected column list 2611 shows a list of columns mapped to the application.

Here, when one application code is selected from the application English name selection combo box list 2615, the content of the column mapped to the selected application is displayed in the selected column list 2611. In the column list 2609, the columns mapped to the application do not appear. Therefore, the columns shown in the column list 2609 when the application is selected are lists of columns that are not mapped to the corresponding application.

If it is necessary to map a column of a table other than the column belonging to the currently selected table to the selected application, select another table from the table selection combo box list 2625 to continue the operation.

The same applies to applications, so that you can work with multiple applications and multiple columns.

Mapping between applications and columns is possible only when one application is selected from the list of application English names below the screen. If not selected, an error message box will appear.

The operation of registering or deleting a mapping is performed only on the screen, not the actual mapping is registered or deleted. Therefore, when the change operation is completed after the work on the screen is clicked, if the apply button 2635 is clicked on, the work content on the screen is applied to the actual system.

27 is a flowchart illustrating a process of storing meta data of a table, a column, a task, an application, etc. according to an exemplary embodiment of the present invention.

Referring to FIG. 27, when the integrated metadata server 101 receives a metadata storage request in operation S2701, the integrated metadata server 101 accesses a metadata providing server in operation S2703. Here, the metadata providing server may vary according to the metadata storage request. If the metadata storage request is for a table or column, the metadata providing server may be a server coupled with the basic information database 123. If the metadata storage request is for mapping information, the metadata providing server may be a server coupled with the data warehouse database 125. If the metadata storage request is for a mapping, the metadata providing server may be a server coupled with the mapping information database 117. If the metadata storage request is for a job, the metadata providing server may be a server coupled with the job information database 121.

After accessing the metadata providing server, the metadata corresponding to the metadata storage request is extracted from the metadata files 133 or the database 123, 125, 117, 121 of the server combined with the metadata providing server ( S2705).

The extracted metadata is converted into a common format (S2707), and the converted metadata is stored in the integrated metadata database 113 combined with the integrated metadata server 101 (S2709).

FIG. 28 is a flowchart illustrating a process of outputting meta data to a screen in response to a metadata inquiry request of a user according to an exemplary embodiment of the present invention.

Referring to FIG. 28, when the integrated metadata server receives a metadata information request in operation S2801, the metadata corresponding to the request is extracted from the integrated metadata database 113 in operation S2803.

After configuring the metadata content screen by using the extracted metadata (S2805), the metadata content screen is transmitted to the device that has made the metadata inquiry request (S2807).

The present invention is not limited to the above embodiments, and many variations are possible by those skilled in the art within the spirit of the present invention.

As described above, according to the present invention, it is possible to manage and query system related information, database (table, column, etc.) related information, tasks, work schedules, mapping information between tables, mapping information between columns, and application information as metadata. A method and apparatus for managing integrated meta information for integrated management between heterogeneous systems can be provided.

In addition, according to the present invention, by managing the flow of data and providing information to users, it is possible to provide consistency verification of DW data, securing data reliability, utilizing data analysis, and ease of use.

In addition, according to the present invention can provide an integrated meta information management method and apparatus for integrated management between heterogeneous systems that can manage and query information stored in a plurality of heterogeneous systems with one management program.

In addition, according to the present invention, it is possible to query the details of the system and the data managed in the enterprise in a timely manner and to provide information necessary for verifying the accuracy and consistency of the data, primarily to the computer department, and secondly to the enterprise. The following benefits can be provided to the whole:

1) Speed up work

-Users can see the details of the system and data immediately without going through the computerized department, so the work processing time can be shortened.

-In case of an error in the system and data, the error details related to the error can be viewed immediately, which can reduce the error processing time.

-As the error details related to the system and data change are applied immediately, the error processing time can be shortened.

2) cost reduction

-Users can directly view all the information related to the system and data without going through the computer department. Therefore, labor cost can be reduced by reducing the workload of the computer department and efficiency of computer manpower.

-All matters related to the system and data have been donated to related departments by manual management and printed out in spreadsheets or word processors. However, the database of related information can reduce the cost of purchasing tools and printed materials. Can be.

3) Increase in sales

-When establishing a marketing strategy through customer relationship management, it is possible to quickly and conveniently search for the information needed by the strategist to provide timely and appropriate information about the customer marketing strategy, thereby preventing customer churn and increasing sales.

4) Standardization of work

-In order to efficiently build and use Business Process Meta Data, standardization of work is based on the standardization of work. Even if work is not standardized, managers, managers and users can recognize the necessity of standardization work in order to use Meta Data efficiently.

In addition, the present invention can provide a method and apparatus for managing integrated meta information having a standardized single integrated metadata database.

In addition, according to the present invention can provide an integrated meta information management method and apparatus that provides a function for converting heterogeneous meta data between heterogeneous metadata into a standardized metadata form.

According to the present invention, it is possible to provide an integrated meta information management method and apparatus capable of constructing an integrated mapping model for meta data analysis and correlation for each product constituting a data warehouse and a customer relationship management environment.

In addition, the present invention can provide a method and apparatus for managing integrated meta information.

In addition, according to the present invention can provide an integrated meta information management method and apparatus that can improve the user's convenience through linkage with the web environment.

Claims (22)

In the integrated metadata server integrated metadata management method for the integrated management between heterogeneous systems, Receiving a request for storing metadata; Determining a heterogeneous system corresponding to the metadata storage request and accessing a server corresponding to the heterogeneous system; Extracting metadata corresponding to the metadata storage request from an information database associated with the server or a metadata file included in the server; Converting the extracted metadata into a common format according to a predetermined conversion rule corresponding to the heterogeneous system; Storing the converted metadata in an integrated metadata database coupled with the integrated metadata server Integrated meta information management method for integrated management between heterogeneous systems comprising a. The method of claim 1, The metadata is Stored in the integrated metadata database and viewed over a network Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems When the integrated metadata server receives a metadata deletion request for specific metadata, Extracting metadata corresponding to the metadata deletion request from an information database associated with the server or a metadata file included in the server; Deleting metadata corresponding to the metadata deletion request from the integrated metadata database; Integrated meta information management method for integrated management between heterogeneous systems further comprising a. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems When the integrated metadata server receives a metadata modification request for specific metadata, Extracting metadata corresponding to the metadata modification request from an information database coupled with the server or a metadata file included in the server; Modifying the extracted metadata in response to the metadata modification request; Converting the modified metadata into a common format according to a predetermined conversion rule; Storing the converted metadata in an integrated metadata database coupled with the integrated metadata server Integrated meta information management method for integrated management between heterogeneous systems further comprising a. The method of claim 1, The conversion rule is Including at least common formatting rules, constraints Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems Treated as a batch job Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about system information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about database information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Metadata about the table information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about column information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Metadata about the table mapping information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Meta data about column mapping information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about job information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about work schedule information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The metadata is Being metadata about application information Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems When you receive a request to delete metadata about a column, Deleting meta data corresponding to the column; Extracting column mapping information corresponding to the column to delete metadata corresponding to the column mapping information; Integrated meta information management method for integrated management between heterogeneous systems, characterized in that for executing. The method of claim 16, Deleting meta data corresponding to the column Extracting key information metadata corresponding to the column to delete metadata corresponding to the key information; Extracting the application related information by extracting the application related information corresponding to the column; Integrated meta information management method for integrated management between heterogeneous systems further comprising a. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems When you receive a request to delete metadata about a table, Extracting a column corresponding to the table and deleting metadata corresponding to the column; Extracting column mapping information corresponding to the column to delete metadata corresponding to the column mapping information; Deleting metadata corresponding to the table; Extracting table mapping information corresponding to the table and deleting metadata corresponding to the table mapping information; Integrated meta information management method for integrated management between heterogeneous systems, characterized in that for executing. The method of claim 1, The integrated meta information management method for the integrated management between the heterogeneous systems Managing user authority information to restrict screen access and use for each of storing, modifying, inquiring, and deleting the metadata for each user Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. The method of claim 1, The logical structure of the integrated metadata database is Meta data about system information, database information, error information, column information, table information, mapping information, task information, and application information is stored and configured to execute various queries for the information. Integrated meta information management method for integrated management between heterogeneous systems, characterized in that the. In the integrated metadata server, the integrated metadata management device for the integrated management between heterogeneous systems, Means for receiving a metadata storage request; Means for determining a heterogeneous system corresponding to the metadata storage request and connecting to a server corresponding to the heterogeneous system; Means for extracting metadata corresponding to the metadata storage request from an information database associated with the server or a metadata file included in the server; Means for converting the extracted metadata into a common format according to a predetermined conversion rule corresponding to the heterogeneous system; Means for storing the converted metadata in an integrated metadata database coupled with the integrated metadata server Integrated meta information management device for integrated management between heterogeneous systems comprising a. A memory in which a program is stored; A processor coupled with the memory to execute the program Including but not limited to: The processor by the program, Receiving a request for storing metadata; Determining a heterogeneous system corresponding to the metadata storage request and accessing a server corresponding to the heterogeneous system; Extracting metadata corresponding to the metadata storage request from an information database associated with the server or a metadata file included in the server; Converting the extracted metadata into a common format according to a predetermined conversion rule corresponding to the heterogeneous system; Storing the converted metadata in an integrated metadata database coupled with the integrated metadata server Integrated meta information management system for integrated management between heterogeneous systems, characterized in that for executing.