Metadata Management Method for Technical Architecture View and Related Devices

Abstract

The present invention discloses a metadata management method and related devices for a technical architecture view. The method obtains the database table definition of configuration item attributes from a configuration management database; selects a technical architecture view model from a technical architecture view system as a target model; determines the corresponding rules of the metadata of the target model based on the correspondence between the model attributes and the configuration item attributes, and registers the metadata; sets data acquisition and parsing tasks in the technical architecture view system based on the metadata; synchronizes data corresponding to the data source of the metadata in the configuration management database to the technical architecture view system based on the data acquisition and parsing tasks, and performs data parsing and storage according to the target model, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results. The present invention can keep the changes of the technical architecture view model and the configuration management database consistent, and has good synchronization.

Description

Technical Field

[0001] The present invention relates to the field of systems, and in particular to a metadata management method for a technical architecture view and related devices. Background Art

[0002] Existing technologies cannot use online technical architecture asset data for drawing, and can only manually draw architecture asset information on the map. Views and data cannot be automatically updated. As time goes by, the information in the architecture view will gradually become inaccurate, and the view will need to be modified or redrawn after it becomes invalid.

[0003] With the development of enterprise business and the expansion of system scale, the number of technical architecture view models is huge and the relationships are becoming more and more complex. The amount of data involved in each technical architecture view model is also quite large and changes frequently. It is difficult to manually obtain data through traditional manual methods and then accurately draw the view, making it impossible for the technical architecture view to keep pace with data changes. Summary of the Invention

[0004] In view of the above problems, the present invention provides a metadata management method and related devices from a technical architecture view that overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect, a metadata management method for a technical architecture view includes:

[0006] Obtaining database table definitions of configuration item attributes from a configuration management database, wherein each of the database tables includes corresponding configuration item attributes, and the configuration item attributes include: attributes of the configuration item and attributes of the configuration item relationship;

[0007] Selecting a technical architecture view model from a pre-established technical architecture view system as a target model, wherein the target model includes model attributes, and the model attributes include component attributes and component relationship attributes;

[0008] Determining a corresponding rule of metadata of the target model according to the corresponding relationship between the model attributes and the configuration item attributes, and registering the metadata in a technical architecture view metadata management system, wherein the metadata includes the corresponding rule;

[0009] According to the metadata registered in the technical architecture view metadata management system, setting corresponding data acquisition and parsing tasks in the technical architecture view system;

[0010] According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and the data is parsed and stored according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model.

[0011] Combine Figure 1 In certain optional embodiments of the embodiment shown, determining the corresponding rules of the metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes includes:

[0012] If the model attribute is completely covered by the configuration item attribute in one of the database tables, or if the model attribute is covered by a combination of the configuration item attributes in at least two of the database tables, then the correspondence between the configuration item attribute in the corresponding database table and the model attribute is determined, and the correspondence rule is determined according to the value selection rule in the configuration item attribute in the corresponding database table.

[0013] In combination with the previous embodiment, in some optional embodiments, the method further includes:

[0014] If the model attribute cannot be completely covered by the configuration item attribute in one of the database tables, and the model attribute cannot be covered by the combination of the configuration item attributes in at least two of the database tables, then according to the pre-established data processing rules, data processing is performed on the data source of each of the technical architecture view models that have registered the metadata in the technical architecture view system to determine the corresponding rules.

[0015] Combine Figure 1 In some optional embodiments, the method further comprises:

[0016] If the database table in the configuration management database changes, the corresponding metadata synchronized with the corresponding technical architecture view model in the technical architecture view system will be changed accordingly, wherein the change includes: adding metadata, deleting metadata and modifying metadata.

[0017] Combine Figure 1 In certain optional embodiments of the embodiment shown, according to the data acquisition and parsing task, synchronizing the data corresponding to the metadata data source in the configuration management database to the technical architecture view system, and parsing and storing the data according to the target model in the technical architecture view system, includes:

[0018] According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and according to the model architecture of the target model, the data is parsed and stored in the physical table corresponding to the model architecture.

[0019] Combine Figure 1 In certain optional embodiments of the embodiment shown, determining the corresponding rules of the metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes, and registering the metadata in the technical architecture view metadata management system, includes:

[0020] According to the correspondence between the model attributes and the configuration item attributes, the data service address, attribute fields, business primary key fields and field mapping rules of the data source corresponding to the model attributes are defined in the technical architecture view metadata management system, thereby registering the metadata in the technical architecture view metadata management system.

[0021] In combination with the previous embodiment, in some optional embodiments, setting corresponding data acquisition and parsing tasks in the technical architecture view system based on the metadata registered in the technical architecture view metadata management system includes:

[0022] Based on the metadata registered in the technical architecture view metadata management system, data verification rules, data processing rules, data synchronization frequency, data warehousing rules and data synchronization trigger conditions are defined in the technical architecture view system to achieve the setting of corresponding data acquisition and analysis tasks.

[0023] In a second aspect, a metadata management device for a technical architecture view includes: a configuration item attribute obtaining unit, a target model obtaining unit, a corresponding rule determining unit, a task setting unit, and a task executing unit;

[0024] The configuration item attribute obtaining unit is configured to obtain a database table definition of configuration item attributes from a configuration management database, wherein each of the database tables includes corresponding configuration item attributes, and the configuration item attributes include: attributes of configuration items and attributes of configuration item relationships;

[0025] The target model obtaining unit is configured to select a technical architecture view model from a pre-established technical architecture view system as a target model, wherein the target model includes model attributes, and the model attributes include component attributes and component relationship attributes;

[0026] The corresponding rule determining unit is configured to determine the corresponding rule of the metadata of the target model according to the corresponding relationship between the model attributes and the configuration item attributes, and register the metadata in the technical architecture view metadata management system, wherein the metadata includes the corresponding rule;

[0027] The task setting unit is configured to set corresponding data acquisition and parsing tasks in the technical architecture view system according to the metadata registered in the technical architecture view metadata management system;

[0028] The task execution unit is used to synchronize the data corresponding to the data source of the metadata in the configuration management database to the technical architecture view system according to the data acquisition and parsing task, and parse and store the data according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model.

[0029] In a third aspect, a computer-readable storage medium stores a program thereon, which, when executed by a processor, implements the metadata management method of the technical architecture view described in any one of the above items.

[0030] In a fourth aspect, an electronic device comprises at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; and the processor is used to call program instructions in the memory to execute the metadata management method of the technical architecture view described in any one of the above items.

[0031] By means of the above technical solution, the present invention provides a metadata management method and related device for a technical architecture view, which can obtain the database table definition of the configuration item attributes from the configuration management database, wherein each of the database tables includes the corresponding configuration item attributes, and the configuration item attributes include: the attributes of the configuration item and the attributes of the configuration item relationship; select a technical architecture view model from a pre-established technical architecture view system as the target model, wherein the target model includes model attributes, and the model attributes include the attributes of the component and the attributes of the component relationship; determine the corresponding rules of the metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes, and register the metadata in the technical architecture view metadata management system. , wherein the metadata includes the corresponding rules; according to the metadata registered in the technical architecture view metadata management system, corresponding data acquisition and parsing tasks are set in the technical architecture view system; according to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and the data is parsed and stored according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to the pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model. It can be seen from this that the present invention can automatically change the corresponding metadata connected to the corresponding technical architecture view model as the scope or data involved in some attributes of the metadata changes, so that the technical architecture view model is consistent with the changes in the metadata, has good synchronization, and will not lag behind the changes in the metadata. The present invention does not impose any restrictions on this.

[0032] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0034] Figure 1 A flowchart showing a metadata management method of a technical architecture view provided by the present invention is shown;

[0035] Figure 2A schematic diagram showing the structure of a metadata management device according to a technical architecture view provided by the present invention is shown;

[0036] Figure 3 A schematic structural diagram of an electronic device provided by the present invention is shown. DETAILED DESCRIPTION

[0037] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0038] like Figure 1 As shown, a metadata management method for a technical architecture view includes: S100, S200, S300, S400 and S500;

[0039] S100, obtaining a database table definition of configuration item attributes from a configuration management database;

[0040] Wherein, each of the database tables includes the corresponding configuration item attributes, and the configuration item attributes include: attributes of the configuration item and attributes of the configuration item relationship;

[0041] Optionally, the configuration management database is primarily a relational database, a distributed file storage database, or the like, such as ORACLE, MySQL, and MongoDB. The present invention can pre-select the corresponding adapter type and version based on the data source of the configuration management database to establish the data collection task. The adapter is primarily used to define the adaptation type for metadata acquisition based on the source of the configuration management metadata, but the present invention does not impose any limitations on this.

[0042] The optional configuration management database currently covers application, virtualization, network, platform, computing, computer room, storage, and security. For example, for applications, these primarily include configuration item types such as business, system, infrastructure software, and middleware. These include configuration items such as logical subsystems, physical subsystems, deployment units, JDK software, and Apache middleware. Each configuration item has a specific code, name, and other definitions.

[0043] Optionally, a plurality of configuration items and their database tables are stored in the configuration management database. One configuration item and its database table can be understood as one metadata, which is not limited in the present invention.

[0044] Optionally, for any metadata, a plurality of different configuration item attributes may be recorded in its database table, wherein each configuration item attribute may be defined by a corresponding attribute field, which is not limited in the present invention.

[0045] S200, selecting a technical architecture view model from a pre-established technical architecture view system as a target model;

[0046] Wherein, the target model includes model attributes, and the model attributes include attributes of components and attributes of component relationships;

[0047] Optionally, technical personnel can construct a corresponding technical architecture view model in advance according to the needs of the actual project, and the present invention does not limit this.

[0048] Optionally, the domain can divide the technical architecture view model into five major areas: system, storage, network, resource pool and computer room. Determine the technical architecture elements and relationships that need to be displayed in the five major areas, extract the technical architecture view model according to needs, and define the primary keys, types and data rules of the technical architecture view model entities, entity relationships and attributes.

[0049] Taking the system domain as an example, entities include physical subsystems, deployment units, and deployment instances. Relationships include those between deployment units and switches, between deployment units and network partitions, between deployment units and NAS storage, and between deployment units and SAN storage. All entities have corresponding attribute definitions, including attribute types, value selection rules, and attribute primary keys, which are not limited in this invention.

[0050] Optionally, although the technical architecture view model is pre-built, the metadata connected to the technical architecture view model may change as the metadata involved in the project changes, so it is necessary to obtain the technical architecture view model to facilitate subsequent connection with the corresponding metadata. The present invention does not limit this.

[0051] S300: Determine a corresponding rule for metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes, and register the metadata in a technical architecture view metadata management system;

[0052] wherein the metadata includes the corresponding rules;

[0053] Optionally, since the classification criteria of the model attributes and the configuration item attributes of the metadata may be different, it is difficult to have a one-to-one correspondence between the model attributes and the configuration item attributes of the metadata, so it is necessary to determine the correspondence rules of the metadata of the target model.

[0054] Optionally, for any target model, the metadata correspondence rule can characterize which configuration item attributes of which metadata each model attribute of the target model is composed of, thereby reflecting the correspondence between the target model and the metadata. The present invention does not impose any restrictions on this.

[0055] For example, combined with Figure 1 In some optional embodiments of the embodiment shown, determining the corresponding rules of the metadata of the target model according to the corresponding relationship between the model attributes and the configuration item attributes in S300 includes:

[0056] If the model attribute is completely covered by the configuration item attribute in one of the database tables, or if the model attribute is covered by a combination of the configuration item attributes in at least two of the database tables, then the correspondence between the configuration item attribute in the corresponding database table and the model attribute is determined, and the correspondence rule is determined according to the value selection rule in the configuration item attribute in the corresponding database table.

[0057] Optionally, the model attribute being completely covered by the configuration item attribute in one of the database tables can be understood as: the scope covered by the model attribute can be included in the scope covered by the configuration item attribute in one of the database tables, and the present invention does not impose any limitation on this.

[0058] That is, if the model attributes of the technical architecture view model can be fully covered by the attributes in a single database table in the configuration management database, a one-to-one relationship can be established between the model attributes in the technical architecture view and the configuration item attributes in the database table, and the value rules of the object entries can be clarified.

[0059] The object entry mentioned here refers to the value selection rule of the object entry of the model attribute of the technical architecture view model, that is, the model attribute can involve multiple object entries, which is not limited in the present invention.

[0060] Optionally, the model attribute being covered by the combination of the configuration item attributes in at least two of the database tables can be understood as: the scope covered by the model attribute can be included in the scope covered by the configuration item attributes in at least two of the database tables, and the present invention does not impose any restrictions on this.

[0061] For example, the model attributes of the technical architecture view model need to be formed by splicing attributes in two or more database tables according to certain rules. Then the model attributes in the technical architecture view model need to establish a corresponding relationship with the configuration item attributes in two or more database tables. If specific rules are required for splicing, the rules need to be defined in advance and the value rules of the object entries need to be clarified.

[0062] For example, if the object entries of the model attributes of the technical architecture view model need to be obtained from two or more database tables, the structures of the relevant database tables must remain consistent, and a one-to-one relationship must be established between the model attributes of the technical architecture view model and the configuration item attributes of the database table. The present invention does not impose any restrictions on this.

[0063] When identifying the relationship between entities and database tables in the technical architecture view model, one principle to be maintained is that the primary key of the entity in the technical architecture view model and the business primary key of the configuration item in the database table need to be consistent. The present invention does not impose any restrictions on this.

[0064] Optionally, in combination with the previous embodiment, in certain optional embodiments, the method further includes:

[0065] If the model attribute cannot be completely covered by the configuration item attribute in one of the database tables, and the model attribute cannot be covered by the combination of the configuration item attributes in at least two of the database tables, then according to the pre-established data processing rules, data processing is performed on the data source of each of the technical architecture view models that have registered the metadata in the technical architecture view system to determine the corresponding rules.

[0066] Optionally, if the model attribute cannot be completely covered by the configuration item attribute in one of the database tables, and the model attribute cannot be covered by the combination of the configuration item attributes in at least two of the database tables, it means that the attribute range involved in the existing metadata does not completely include the model attribute, that is, the entire content of the model attribute cannot be obtained from the existing database table. Therefore, data processing can be performed on the data source of each of the technical architecture view models that have registered data sources in the technical architecture view system according to pre-established data processing rules, so as to determine the corresponding rules of the metadata of the target model. The present invention does not impose any restrictions on this.

[0067] The present invention does not limit the specific process of data processing; any feasible method falls within the scope of protection of the present invention. For example, Method 1: Processing object attributes according to certain rules to form relationship entities; Method 2: Processing multiple objects according to certain rules to form relationship entities.

[0068] Optionally, the present invention does not impose any specific limitation on the process of registering metadata, and any feasible method falls within the protection scope of the present invention.

[0069] For example, combined with Figure 1 In some optional embodiments of the embodiment shown, the S300 includes:

[0070] According to the correspondence between the model attributes and the configuration item attributes, the data service address, attribute fields, business primary key fields and field mapping rules of the data source corresponding to the model attributes are defined in the technical architecture view metadata management system, thereby registering the metadata in the technical architecture view metadata management system.

[0071] S400: Setting corresponding data acquisition and parsing tasks in the technical architecture view system according to the metadata registered in the technical architecture view metadata management system;

[0072] Optionally, the present invention does not impose any specific limitation on the process of registering the metadata of the target model.

[0073] S500: Synchronize the data corresponding to the metadata data source in the configuration management database to the technical architecture view system according to the data acquisition and parsing task, and parse and store the data according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results;

[0074] Wherein, the parsing rule is a rule for converting data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model;

[0075] Optionally, as previously mentioned, in order to display metadata in the technical architecture view system, the corresponding metadata must be parsed according to the parsing rules to obtain parsing results. Because the parsing rules specify the corresponding method and value selection rules for converting configuration item attributes to model attributes, the obtained parsing results conform to the scope of the model attributes and can be displayed as actual data for the corresponding model attributes. This is not a limitation of the present invention.

[0076] Optionally, the present invention does not limit the specific process of synchronizing metadata, and any feasible method falls within the scope of protection of the present invention. For example, in conjunction with the previous embodiment, in certain optional embodiments, the step S500, based on the data acquisition and parsing task, synchronizes the data corresponding to the metadata data source in the configuration management database to the technical architecture view system, and performs data parsing and storage according to the target model in the technical architecture view system, including:

[0077] According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and according to the model architecture of the target model, the data is parsed and stored in the physical table corresponding to the model architecture.

[0078] Optionally, the present invention does not impose any specific restrictions on the frequency of data synchronization, which can be set according to actual needs and is not limited by the present invention.

[0079] According to the model architecture of the target model, the analysis results are stored in a physical table corresponding to the model architecture of the target model, which can be understood as achieving the docking of the analysis results with the target model.

[0080] Optionally, parsing rules can be constructed based on the value rules of different configuration item attributes of different data sources, so that the values of model attributes can be obtained by subsequent parsing according to the parsing rules. The present invention does not limit this. For example, it is assumed that model attribute 1 is composed of configuration item attribute 1 of metadata 1 and configuration item attribute 2 of metadata 1, and the value range of configuration item attribute 1 is A, B, and C, and the value range of configuration item attribute 2 is E and F. Then the value range of model attribute 1 can be A, B, C, E, and F. The value range of model attribute 1 can be used as part of the parsing rule, and the present invention does not limit this.

[0081] Optional, combined Figure 1 In some optional embodiments, the method further comprises:

[0082] If the database table in the configuration management database changes, the corresponding metadata synchronized with the corresponding technical architecture view model in the technical architecture view system will be changed accordingly, wherein the change includes: adding metadata, deleting metadata and modifying metadata.

[0083] Optionally, when a database table changes, the metadata connected to the corresponding technical architecture view model also needs to change accordingly; or, due to actual needs, when the scope of the model attributes of the technical architecture view model changes, the corresponding configuration item attributes of the database table to which it is connected also need to change accordingly, that is, the metadata to which it is connected also needs to change accordingly. The present invention does not impose any restrictions on this.

[0084] Optionally, the present invention can also develop corresponding data services based on the technical architecture view model and according to the requirements of displaying data in different types of technical architecture views, so as to perform real-time data calls when the technical architecture view is displayed in the foreground. The present invention does not impose any restrictions on this.

[0085] From this, it can be seen that the present invention can automatically change the corresponding metadata connected to the corresponding technical architecture view model as the scope or data involved in some attributes of the metadata changes, so that the data displayed on the technical architecture view model is consistent with the data of the metadata and will not lag behind the changes in the metadata. The present invention does not impose any restrictions on this.

[0086] like Figure 2 As shown, the present invention provides a metadata management device of a technical architecture view, comprising a configuration item attribute obtaining unit 100, a target model obtaining unit 200, a corresponding rule determining unit 300, a task setting unit 400, and a task executing unit 500;

[0087] The configuration item attribute obtaining unit is configured to obtain a database table definition of configuration item attributes from a configuration management database, wherein each of the database tables includes corresponding configuration item attributes, and the configuration item attributes include: attributes of configuration items and attributes of configuration item relationships;

[0088] The target model obtaining unit is configured to select a technical architecture view model from a pre-established technical architecture view system as a target model, wherein the target model includes model attributes, and the model attributes include component attributes and component relationship attributes;

[0089] The corresponding rule determining unit is configured to determine the corresponding rule of the metadata of the target model according to the corresponding relationship between the model attributes and the configuration item attributes, and register the metadata in the technical architecture view metadata management system, wherein the metadata includes the corresponding rule;

[0090] The task setting unit is configured to set corresponding data acquisition and parsing tasks in the technical architecture view system according to the metadata registered in the technical architecture view metadata management system;

[0091] The task execution unit is used to synchronize the data corresponding to the data source of the metadata in the configuration management database to the technical architecture view system according to the data acquisition and parsing task, and parse and store the data according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model.

[0092] Combine Figure 2 In the illustrated embodiment, in some optional embodiments, when the corresponding rule determining unit 300 determines the corresponding rule of the metadata of the target model based on the corresponding relationship between the model attribute and the configuration item attribute, it is specifically configured to execute:

[0093] If the model attribute is completely covered by the configuration item attribute in one of the database tables, or if the model attribute is covered by a combination of the configuration item attributes in at least two of the database tables, then the correspondence between the configuration item attribute in the corresponding database table and the model attribute is determined, and the correspondence rule is determined according to the value selection rule in the configuration item attribute in the corresponding database table.

[0094] In combination with the previous embodiment, in some optional embodiments, the apparatus further includes: a corresponding rule processing unit;

[0095] The corresponding rule processing unit is used to process data of the data source of each technical architecture view model that has registered the metadata in the technical architecture view system according to pre-established data processing rules if the model attribute cannot be completely covered by the configuration item attribute in one of the database tables, and the model attribute cannot be covered by the combination of the configuration item attributes in at least two of the database tables, so as to determine the corresponding rule.

[0096] Combine Figure 2 In certain optional embodiments of the embodiment shown, the apparatus further comprises: a changing unit;

[0097] The change unit is used to make corresponding changes to the corresponding metadata synchronized by the corresponding technical architecture view model in the technical architecture view system if the database table in the configuration management database is changed, wherein the changes include: adding metadata, deleting metadata and modifying metadata.

[0098] Combine Figure 2 In the illustrated embodiment, in certain optional embodiments, when the task execution unit 500 executes the data acquisition and parsing task, synchronizes the data corresponding to the metadata data source in the configuration management database to the technical architecture view system, and parses and stores the data according to the target model in the technical architecture view system, the task execution unit 500 is specifically configured to execute:

[0099] According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and according to the model architecture of the target model, the data is parsed and stored in the physical table corresponding to the model architecture.

[0100] Combine Figure 2 In some optional embodiments of the embodiment shown, the rule determination unit 300 is specifically configured to execute:

[0101] According to the correspondence between the model attributes and the configuration item attributes, the data service address, attribute fields, business primary key fields and field mapping rules of the data source corresponding to the model attributes are defined in the technical architecture view metadata management system, thereby registering the metadata in the technical architecture view metadata management system.

[0102] In combination with the previous embodiment, in some optional embodiments, the task setting unit 400 is specifically configured to perform:

[0103] Based on the metadata registered in the technical architecture view metadata management system, data verification rules, data processing rules, data synchronization frequency, data warehousing rules and data synchronization trigger conditions are defined in the technical architecture view system to achieve the setting of corresponding data acquisition and analysis tasks.

[0104] The present invention provides a computer-readable storage medium having a program stored thereon, characterized in that when the program is executed by a processor, the metadata management method of the technical architecture view described in any one of the above items is implemented.

[0105] like Figure 3 As shown, the present invention provides an electronic device 70, which includes at least one processor 701, and at least one memory 702 and a bus 703 connected to the processor 701; wherein the processor 701 and the memory 702 communicate with each other through the bus 703; the processor 701 is used to call the program instructions in the memory 702 to execute the metadata management method of the technical architecture view described in any one of the above items.

[0106] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus comprising the element.

[0107] Each embodiment in this specification is described in a related manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiment is generally similar to the method embodiment, so the description is relatively simple. For related parts, refer to the description of the method embodiment.

[0108] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

[0109] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included in the scope of protection of the present invention.

Claims

1. A metadata management method for a technical architecture view, characterized in that: include: Obtaining database table definitions of configuration item attributes from a configuration management database, wherein each of the database tables includes corresponding configuration item attributes, and the configuration item attributes include: attributes of the configuration item and attributes of the configuration item relationship; Selecting a technical architecture view model from a pre-established technical architecture view system as a target model, wherein the target model includes model attributes, and the model attributes include component attributes and component relationship attributes; Determining a corresponding rule for metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes, and registering the metadata in a technical architecture view metadata management system, wherein the metadata includes the corresponding rule. Determining the corresponding rule for metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes includes: If the model attribute is completely covered by the configuration item attribute in one of the database tables, or if the model attribute is covered by a combination of the configuration item attributes in at least two of the database tables, determining a correspondence between the configuration item attribute in the corresponding database table and the model attribute, and determining the correspondence rule based on the value selection rule of the configuration item attribute in the corresponding database table; According to the metadata registered in the technical architecture view metadata management system, setting corresponding data acquisition and parsing tasks in the technical architecture view system; According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and the data is parsed and stored according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model.

2. The method according to claim 1, characterized in that The method further comprises: If the model attribute cannot be completely covered by the configuration item attribute in one of the database tables, and the model attribute cannot be covered by the combination of the configuration item attributes in at least two of the database tables, then according to the pre-established data processing rules, data processing is performed on the data source of each of the technical architecture view models that have registered the metadata in the technical architecture view system to determine the corresponding rules.

3. The method according to claim 1, characterized in that The method further comprises: If the database table in the configuration management database changes, the corresponding metadata synchronized with the corresponding technical architecture view model in the technical architecture view system will be changed accordingly, wherein the change includes: adding metadata, deleting metadata and modifying metadata.

4. The method according to claim 1, wherein According to the data acquisition and parsing task, synchronizing the data corresponding to the metadata data source in the configuration management database to the technical architecture view system, and parsing and storing the data according to the target model in the technical architecture view system, includes: According to the data acquisition and parsing tasks, the data corresponding to the data source of the metadata in the configuration management database is synchronized to the technical architecture view system, and according to the model architecture of the target model, the data is parsed and stored in the physical table corresponding to the model architecture.

5. The method according to claim 1, characterized in that The determining of the corresponding rules of the metadata of the target model according to the corresponding relationship between the model attributes and the configuration item attributes, and registering the metadata in the technical architecture view metadata management system, includes: According to the correspondence between the model attributes and the configuration item attributes, the data service address, attribute fields, business primary key fields and field mapping rules of the data source corresponding to the model attributes are defined in the technical architecture view metadata management system, thereby registering the metadata in the technical architecture view metadata management system.

6. The method according to claim 5, characterized in that The step of setting corresponding data acquisition and parsing tasks in the technical architecture view system according to the metadata registered in the technical architecture view metadata management system includes: Based on the metadata registered in the technical architecture view metadata management system, data verification rules, data processing rules, data synchronization frequency, data warehousing rules and data synchronization trigger conditions are defined in the technical architecture view system to achieve the setting of corresponding data acquisition and analysis tasks.

7. A metadata management device for a technical architecture view, characterized in that: include: Configuration item attribute acquisition unit, target model acquisition unit, corresponding rule determination unit, task setting unit and task execution unit; The configuration item attribute obtaining unit is configured to obtain a database table definition of configuration item attributes from a configuration management database, wherein each of the database tables includes corresponding configuration item attributes, and the configuration item attributes include: attributes of configuration items and attributes of configuration item relationships; The target model obtaining unit is configured to select a technical architecture view model from a pre-established technical architecture view system as a target model, wherein the target model includes model attributes, and the model attributes include component attributes and component relationship attributes; The corresponding rule determining unit is configured to determine the corresponding rule of the metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes, and register the metadata in the technical architecture view metadata management system, wherein the metadata includes the corresponding rule, and determining the corresponding rule of the metadata of the target model based on the corresponding relationship between the model attributes and the configuration item attributes includes: If the model attribute is completely covered by the configuration item attribute in one of the database tables, or if the model attribute is covered by a combination of the configuration item attributes in at least two of the database tables, determining a correspondence between the configuration item attribute in the corresponding database table and the model attribute, and determining the correspondence rule based on the value selection rule of the configuration item attribute in the corresponding database table; The task setting unit is configured to set corresponding data acquisition and parsing tasks in the technical architecture view system according to the metadata registered in the technical architecture view metadata management system; The task execution unit is used to synchronize the data corresponding to the data source of the metadata in the configuration management database to the technical architecture view system according to the data acquisition and parsing task, and parse and store the data according to the target model in the technical architecture view system, so that the technical architecture view system parses the data according to pre-established parsing rules to obtain corresponding parsing results, wherein the parsing rules are rules for converting the data corresponding to the metadata in the configuration management database into data that conforms to the technical architecture view model.

8. A computer-readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the metadata management method of the technical architecture view according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: The electronic device includes at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; the processor is used to call program instructions in the memory to execute the metadata management method of the technical architecture view as described in any one of claims 1 to 6.

Images