Information maintenance method based on dynamic configuration item management and configuration management database system

Abstract

The invention relates to an information maintenance method based on dynamic configuration item management and a configuration management database system. The method comprises the steps that metadata is adopted to construct a configuration item model comprising types, attributes and relation information; and based on the configuration item model, constructing a universal configuration item data storage structure, and performing dynamic management on the configuration item data. Compared with the prior art, the method has the advantages that physical decoupling of the configuration item model and the configuration item storage structure is realized through combination of metadata management of the configuration item model and general storage structure design of the configuration items, and more efficient and safer online dynamic configuration management can be realized on the premise of not influencing the data storage structure.

Description

Technical Field

[0001] The present invention relates to the field of database management, and in particular to an information maintenance method based on dynamic configuration item management and a configuration management database system. Background Art

[0002] As the process foundation for building ITIL, the Configuration Management Database (CMDB) stores and manages various configuration item information in the enterprise IT architecture, and as a basic data platform, supports the flow of service delivery processes and gives full play to the value of configuration item information. However, the management objects in the enterprise IT architecture are often complex and changeable. How to formulate a CMDB data management strategy that can cover different management objects and adapt to changes in the management object model is the main problem that needs to be solved in implementing CMDB.

[0003] A common solution is to create a physical table for each configuration item category, and store data in the corresponding physical table according to the configuration item category. If a new type of configuration item needs to be managed, a new physical table is created accordingly. If the configuration item model changes, the table structure of the corresponding physical table is adjusted.

[0004] Currently, there are two main methods for creating and adjusting physical tables for information maintenance:

[0005] 1. Implement through database changes: The information maintenance change process usually needs to go through certain approval procedures, which is time-consuming and lacks flexibility. It is unable to adapt to sudden situations and make quick temporary adjustments. During the change period, related business operations need to be suspended, which has a certain impact on business continuity.

[0006] 2. Implementation through scripts: It is difficult to cope with complex data scenarios, especially when the structure and relationship of configuration items change, script maintenance becomes difficult; script maintenance has threshold requirements for operators, and when an error occurs in the script, rollback cannot be achieved, resulting in inconsistent database status; script execution requires high database permissions to operate on database table structures and data, so it often contains sensitive information such as database credentials or API keys. If it is improperly handled or leaked, it may cause database permission abuse and data security risks. Summary of the invention

[0007] The purpose of the present invention is to overcome the defects of the above-mentioned prior art and to provide an information maintenance method and a configuration management database system based on dynamic configuration item management. By combining the metadata management of the configuration item model with the general storage structure design of the configuration item, the physical decoupling of the configuration item model and the configuration item storage structure is achieved, and more efficient and secure online dynamic configuration management can be achieved without affecting the data storage structure.

[0008] The purpose of the present invention can be achieved by the following technical solutions:

[0009] According to a first aspect of the present invention, there is provided an information maintenance method based on dynamic configuration item management, which is applied to a configuration management database, comprising:

[0010] Metadata is used to construct a configuration item model including type, attribute and relationship information, including: constructing a configuration item classification table to organize all different configuration items into a tree-level structure for type management, constructing a configuration item model table to manage the metadata corresponding to the structure, attribute and control information of the configuration item model, constructing a configuration item relationship model table to manage the subject-object relationship between various configuration items, and constructing a configuration item model version table to store model version information of various configuration items;

[0011] Based on the configuration item model, a universal configuration item data storage structure is constructed to dynamically manage the configuration item data, including: constructing a configuration item data table to store various types of configuration item data. The table structure adopts a model-free feature solution and is provided with a number of universal index fields and a universal storage field. The universal index field is set according to the index sequence metadata in the configuration item model. When the configuration item model is updated and the configuration item data are updated, the data in the universal storage field is updated; constructing a configuration item relationship table to store the relationship instances of the subject and object configuration items; constructing a configuration item data version table to store the version data of various types of configuration items, including the data version and the corresponding model version information; constructing a configuration item relationship version table to store the relationship version data of various types of configuration items.

[0012] Preferably, the configuration item classification table is constructed to organize all different configuration items into a three-layer classification tree structure for type management. The classification information described in the configuration item classification table includes classification number, classification name, classification level, and parent classification ID; wherein,

[0013] The classification number is a globally unique identifier of the classification, and serves as a numbering prefix rule for configuration items;

[0014] The classification level is set to three levels, the third level is the actual level of configuration item classification, and the first and second levels are only used to classify configuration items;

[0015] The parent category ID is used to define the hierarchical relationship of categories.

[0016] Preferably, the configuration item model table is constructed to manage metadata corresponding to the structure, attributes and control information of the configuration item model;

[0017] The metadata corresponding to the structural information includes the attribute group and type, the metadata corresponding to the attribute information includes the attribute name, data type and index order, and the metadata corresponding to the control information includes the entry method, entry configuration and verification rules.

[0018] Preferably, the types are divided into two levels, namely, attribute groups and attributes, wherein the attribute groups are used to classify and divide the attributes, and the affiliation between the attributes and the attribute groups is defined by the affiliation attribute groups.

[0019] Preferably, the attribute name is identification information of attributes of the same type;

[0020] The index order is used to define whether an attribute is an index field, and the mapping relationship between the configuration item attribute and the general index field in the configuration item data table is controlled by the index number.

[0021] Preferably, the configuration item relationship model table is constructed to manage the subject-object relationship between various configuration items. The information described in the configuration item relationship model table includes subject classification, object classification, relationship type, subject relationship attribute, object target domain, summary generation rule, and summary combination rule; wherein,

[0022] The subject classification and object classification are used to describe the role of classification in the relationship. The subject classification acts on the object classification with a certain relationship type.

[0023] The subject relationship attribute is used to define the attribute through which the subject configuration item establishes a relationship with the object configuration item;

[0024] The object target domain represents the attribute of the object configuration item used to identify the information of the object in the subject configuration item;

[0025] The summary generation rules and summary combination rules are used to define one-to-many relationships and combination rules for multiple object classifications.

[0026] Preferably, when the configuration item model is updated and the configuration item data are updated, the data in the general storage field is updated, specifically:

[0027] When the configuration item model is updated, the general storage fields in the configuration item data table do not change. When the configuration item model is updated and the configuration item data is updated, the data in the general storage fields is re-parsed and constructed according to the updated configuration item model.

[0028] Preferably, the configuration item relationship table is constructed to store relationship instances between subject and object configuration items, wherein a unique relationship primary key is created for each relationship instance, and the subject configuration item stores the relationship ID in the configuration item relationship table when saving, so as to query the object configuration item information by the relationship ID when querying or displaying.

[0029] Preferably, when the configuration item data involves a relationship during maintenance, a corresponding relationship instance is automatically created according to the configuration item relationship table, and a series of attribute information under the object is obtained through the relationship instance, and the attribute information is refreshed in real time as the object in the relationship instance changes.

[0030] According to a second aspect of the present invention, there is provided a configuration management database system, wherein the system adopts any one of the above methods to perform information maintenance.

[0031] Compared with the prior art, the present invention has the following beneficial effects:

[0032] 1) Different from the design of the database physical table structure, i.e., the management object model itself, in the script solution, the present invention realizes the physical decoupling of the configuration item model and the configuration item storage structure by combining the metadata management of the configuration item model with the general storage structure design of the configuration item. It can realize more efficient online dynamic configuration item management without affecting the data storage structure, thereby improving the efficiency of information maintenance.

[0033] 2) The present invention realizes dynamic management of indexes by combining dynamic modeling of configuration items and a general configuration item storage structure, weakens the differences between different configuration item fields, uniformly formats configuration items, and improves information maintenance efficiency.

[0034] 3) Based on the general storage structure design, data version information is recorded each time data maintenance is performed, supporting real-time version viewing, comparison and rollback.

[0035] 4) The configuration item relationship is modeled through the relationship subject, object and relationship type information, connected through the configuration item relationship ID and stored in the subject configuration item data. No matter how the object configuration item is modified, the subject configuration item can reproduce the relationship through the configuration item relationship ID, and automatic relationship maintenance can be achieved.

[0036] 5) Compared with the script solution, the maintenance of the configuration item model and data of the present invention can be standardized and solidified on the existing configuration management database system. Except for the system itself, there is no other maintenance cost in the daily operation and maintenance of the data. It can be completed only through page operations, which is easy to maintain.

[0037] 6) Compared with the script solution, the present invention avoids a series of security issues caused by opening too high database permissions while realizing online dynamic modeling, and at the same time avoids the security and audit risks brought by the use of scripts, and is more secure. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 The following is a schematic diagram of the configuration management database architecture based on dynamic configuration item management of the present invention;

[0039] Figure 2 Dynamic management process examples for metadata-driven models;

[0040] Figure 3 It is an example of the configuration item data management process;

[0041] Figure 4 This is an example of the configuration item data update process. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0043] Example

[0044] Under the premise of ensuring the dynamic scalability of the configuration item model, this embodiment reduces the impact of the model on the data itself, especially the impact on the physical structure of data storage, and can complete the operation and management of the CMDB only through page configuration operations. A configuration management database implementation method based on dynamic configuration item management is provided, including:

[0045] Metadata is used to construct a configuration item model including type, attribute and relationship information, including: constructing a configuration item classification table to organize all different configuration items into a tree-level structure for type management, constructing a configuration item model table to manage the metadata corresponding to the structure, attribute and control information of the configuration item model, constructing a configuration item relationship model table to manage the subject-object relationship between various configuration items, and constructing a configuration item model version table to store model version information of various configuration items;

[0046] Based on the configuration item model, a universal configuration item data storage structure is constructed to dynamically manage the configuration item data, including: constructing a configuration item data table to store various types of configuration item data. The table structure adopts a model-free feature solution and is provided with a number of universal index fields and a universal storage field. The universal index field is set according to the index sequence metadata in the configuration item model. When the configuration item model is updated and the configuration item data are updated, the data in the universal storage field is updated; constructing a configuration item relationship table to store the relationship instances of the subject and object configuration items; constructing a configuration item data version table to store the version data of various types of configuration items, including the data version and the corresponding model version information; constructing a configuration item relationship version table to store the relationship version data of various types of configuration items.

[0047] Next, combine Figure 1 The solution of this embodiment is introduced in detail.

[0048] 1. Metadata-driven dynamic model management

[0049] Metadata is used to define the model information of configuration items, including the type, attributes and relationships of configuration item CI. Model information of different configuration items is stored in the same metadata database physical table. When the CI model is adjusted, only the metadata needs to be updated.

[0050] Metadata-driven dynamic model management includes configuration item type management, configuration item model management, configuration item relationship model management, and configuration item model version management, as follows:

[0051] (1) Configuration item type management

[0052] Configuration item type management refers to the process of targeted planning, definition and organization of different types of configuration items. Through type management, all different configuration items are organized into a three-level classification tree structure.

[0053] Configuration item type management requires the creation of a configuration item classification table to define and describe the configuration item classification information, which mainly includes the classification number, classification name, classification level, and parent classification ID, as follows:

[0054] 1) The classification number is the globally unique identifier of the classification, and is also the numbering prefix rule for configuration items.

[0055] 2) The classification hierarchy is divided into three levels in total. The third level is the actual level where the configuration item classification is located, while the first and second levels are only used to classify and divide the configuration items, and there is no corresponding configuration item model.

[0056] 3) The parent category ID is used to define the hierarchical relationship of categories.

[0057] Configuration item type management can be used to add, modify, and delete configuration item types through the page. In addition to the above main information, it can also be used to define classification level maintenance control (for example, whether it is necessary to fill out a change order or service order when maintaining the classification data), configuration item model version number, classification sorting, etc.

[0058] (2) Configuration item model management

[0059] Configuration item model management refers to the process of planning, defining, organizing and controlling the structure and attributes of various configuration items. Configuration item model management is mainly the unified management of metadata that describes the structure, attributes and control information of configuration items. A configuration item model table needs to be created to define and describe the structure, attributes and control information of the configuration item model, which mainly includes the attribute group, type, attribute name, attribute display name, data type, entry method, entry configuration, index order, and verification rules, as follows:

[0060] 1) Type and attribute group: used to define the structure of the model. Type is divided into two levels, namely attribute group and attribute. Attribute group is only used to classify attributes. The relationship between attributes and attribute groups is defined by the attribute groups.

[0061] 2) Attribute name and attribute display name: The attribute name is the identification information of the same type of attributes, and the attribute display name is used to show that it can be repeated.

[0062] 3) Data type, entry method and entry configuration: used to define the nature, characteristics and operation method of the attribute; the data types currently include text, number, value column, date, password, relationship and mapping, etc.; the entry methods include manual and automatic; the entry configuration is a supplementary field of the data type and has many uses. When the data type is a value column, it can be used to define enumeration values; when the data type is a relationship, it can be used to define relationship controls.

[0063] 4) Index order: used to define whether the attribute is an index field, and to control the mapping relationship between the configuration item attribute and the general index field of the data table through the index number.

[0064] 5) Verification rules: used to define the verification control requirements of the attribute when entering, such as required fields, email format, etc. The verification rules are defined by regular expressions.

[0065] Configuration item model management is currently mainly created and modified through EXCEL. The creation and adjustment of configuration item models can be achieved through EXCEL import. In addition, users can also modify single attributes through the page.

[0066] (3) Configuration item relationship model management

[0067] Configuration item relationship model management refers to the process of planning, defining, organizing and controlling the relationships between various configuration items. Configuration item relationship model management mainly manages the characteristics of configuration item relationships. It is necessary to create a configuration item relationship model table to define and describe the subject-object relationship of configuration item relationships. It mainly includes subject classification, object classification, relationship type, subject relationship attribute, object target domain, summary generation rules, and summary combination rules. The details are as follows:

[0068] 1) Subject classification and object classification: used to describe the role of classification in a relationship. Subject classification acts on object classification with a certain relationship type.

[0069] 2) Relationship type: used to describe the classification of relationships. Common ones include contains, installed in, and consists of.

[0070] 3) Subject relationship attribute: It is used to define the attribute through which the subject configuration item establishes a relationship with the object configuration item. It can usually be understood as the foreign key of this configuration item.

[0071] 4) Object target domain: refers to the attribute of the object configuration item used to identify the object information in the subject configuration item, usually the primary key or identification information of the object.

[0072] 5) Summary generation rules and summary combination rules: Mainly used to define one-to-many relationships and combination rules for multiple object categories, such as physical locations, involving cities, buildings, computer rooms, cabinets, etc. When displaying data, object categories need to be effectively combined to ensure information completeness and readability.

[0073] Configuration item relationship model management can create, modify, and delete configuration item relationships through the page. In addition, it also supports defining different relationship controls through the UI.

[0074] Figure 2 Dynamic management process examples for metadata-driven models.

[0075] (4) Configuration item model version management

[0076] Configuration item model version management requires the creation of a corresponding configuration item model version table, which is mainly used to store model version data of various configuration items. The configuration item model version table adopts a design similar to the configuration item model table, except that the configuration item model version table also records the version number of the model.

[0077] If "Generate version" is selected as "Yes" when the configuration item model version is imported, the system will automatically generate version information; or when the user modifies a single attribute on the configuration item model page, a version will be automatically created.

[0078] 2. Dynamic management of common configuration item data

[0079] Through the universal configuration item data storage structure, the decoupling of the configuration item model structure and the physical storage structure is achieved. When the CI model changes, there is no need to change the physical storage structure of the configuration item data, and the original configuration item data can still be dynamically compatible with the new structure. Universal configuration item data dynamic management includes configuration item data management, configuration item relationship management, configuration item data version management, and configuration item relationship version management, as follows:

[0080] (1) Configuration item data management

[0081] Configuration item data management requires the creation of a corresponding configuration item data table, which is mainly used to store various types of configuration item data. In order to enable the configuration item table to store data of different configuration item categories and to cope with model changes, the configuration item table structure design adopts a solution to remove model features, setting a limited number of general index fields (set to 26 in this embodiment, which can be dynamically expanded according to actual conditions) and a general storage field (used to store complete data information of the configuration item). Figure 3 This is an example of a configuration item data management process.

[0082] General index fields are mainly used to meet daily data query and retrieval needs. Unlike conventional table field designs, they do not correspond to a specific field. The correspondence with the field is defined by the index order in the configuration item model. Generally speaking, fields that are frequently used for queries are set as general index fields.

[0083] The data type of the general storage field can be a long text field of LongText or text, which is mainly used to meet the full storage of different model structure data and the query needs of non-general index fields. The data format of the general storage field is the common data exchange format of XML or JSON.

[0084] When configuration item data is entered, the system parses and converts the data through the configuration item model, builds it into a common data exchange format, and then stores it; at the same time, the corresponding index fields in the configuration item data table are updated synchronously to ensure that the index data in the configuration item data table is consistent with the data in the general storage field.

[0085] like Figure 4 As shown, when the configuration item model is updated, the general storage fields in the configuration item data will not change accordingly. When the configuration item data is updated, the data in the general storage fields will be re-parsed and rebuilt according to the new configuration item model.

[0086] Configuration item data management provides three maintenance methods: manual single maintenance, batch import maintenance, and interface maintenance. After the index order of the configuration item model is adjusted, users can complete the index data calibration of the configuration item data through the index data refresh function.

[0087] (2) Configuration item relationship management

[0088] Configuration item relationship management requires the creation of a corresponding configuration item relationship table, which is mainly used to store the relationship data of various configuration items. The configuration item relationship table is designed with a subject-object setting similar to the "configuration item relationship model management". The difference is that the configuration item relationship table mainly stores the instance ID of the relationship subject and object configuration items, and the system creates a unique relationship primary key for each relationship instance. When the subject configuration item is saved, the relationship ID will be stored in the data. When the data is queried or displayed, the object configuration item information will be queried through the relationship ID.

[0089] Configuration item relationships are mainly maintained automatically through relationship controls in configuration item data management. When maintaining configuration item data, if relationships are involved, corresponding configuration item relationship instances will be automatically created according to the configuration item relationship model. Through this relationship, a series of attribute information under the object can be obtained, and this attribute information will be refreshed in real time as the object in the relationship instance changes.

[0090] (3) Configuration item data version management

[0091] Configuration item data version management requires the creation of a corresponding configuration item data version table, which is mainly used to store the version data of various configuration items. The configuration item data version table adopts a design similar to the configuration item data table, except that the configuration item data version table also records the data version and the corresponding model version information. A new version will be automatically generated for each maintenance of the configuration item; on this basis, functions such as online version viewing, online version information comparison, and online version rollback are also implemented.

[0092] (4) Configuration item relationship version management

[0093] Configuration item relationship version management requires the creation of a corresponding configuration item relationship version table, which is mainly used to store relationship version data of various configuration items. Its design is similar to the configuration item relationship table, except that the configuration item relationship version table also records the data version number of the configuration item. When the configuration item data is maintained, if a relationship is involved, the configuration item relationship version data will be automatically created. The configuration item relationship version corresponds to the configuration item version through the data version number, which is convenient for tracing back the relationship information when the configuration item performs data rollback.

[0094] In this embodiment, when implementing CMDB modeling and adjustment, the compiled language JAVA is used, which has a faster execution speed than the interpreted script.

[0095] This embodiment also provides a configuration management database system, which uses the above method to maintain information and can complete the operation and management of the configuration management database only through page configuration operations.

[0096] In summary, the information maintenance method and configuration management database system based on dynamic configuration item management designed in this embodiment have the following advantages:

[0097] Efficiency: Different from the design of the database physical table structure, i.e. the management object model itself, in the script solution, this solution realizes the physical decoupling of the configuration item model and the configuration item storage structure through the metadata management of the model combined with the general storage structure design of the configuration item. It can realize online dynamic configuration modeling without affecting the data storage structure, without mastering the script language and writing scripts. In addition, when implementing modeling and adjustment, this system uses the compiled language JAVA, which is faster than the interpreted script.

[0098] Maintenance: Compared with the script solution, the maintenance of the configuration item model and data in this solution is standardized and solidified through system functions. In addition to the system itself, there is no other maintenance cost in the daily operation and maintenance of the data, which can be completed only through page operations. And through the transaction mechanism of the system, the consistency of the database state is guaranteed; in addition, this solution also realizes automatic maintenance of versions. Compared with version management that can only be achieved through database snapshots, this solution is more stable and efficient under the condition that all versions of the data are also saved.

[0099] Security: Compared with the script solution, this invention avoids a series of security issues caused by opening too high database permissions while achieving online dynamic modeling, and avoids the security and audit risks brought by the use of scripts. This proposal provides a convenient and easy-to-query baseline record, which not only records the data version changes, but also records the corresponding operators, providing clear and accurate records for auditing while ensuring security.

[0100] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. An information maintenance method based on dynamic configuration item management, characterized in that: Applicable to configuration management databases, including: Metadata is used to construct a configuration item model including type, attribute and relationship information, including: constructing a configuration item classification table to organize all different configuration items into a tree-level structure for type management, constructing a configuration item model table to manage the metadata corresponding to the structure, attribute and control information of the configuration item model, constructing a configuration item relationship model table to manage the subject-object relationship between various configuration items, and constructing a configuration item model version table to store model version information of various configuration items; Based on the configuration item model, a universal configuration item data storage structure is constructed to dynamically manage the configuration item data, including: constructing a configuration item data table to store various types of configuration item data. The table structure adopts a model-free feature solution and is provided with a number of universal index fields and a universal storage field. The universal index field is set according to the index sequence metadata in the configuration item model. When the configuration item model is updated and the configuration item data are updated, the data in the universal storage field is updated; constructing a configuration item relationship table to store the relationship instances of the subject and object configuration items; constructing a configuration item data version table to store the version data of various types of configuration items, including the data version and the corresponding model version information; constructing a configuration item relationship version table to store the relationship version data of various types of configuration items.

2. The information maintenance method based on dynamic configuration item management according to claim 1, characterized in that: The configuration item classification table is constructed to organize all different configuration items into a three-level classification tree structure for type management. The classification information described in the configuration item classification table includes classification number, classification name, classification level, and parent classification ID; wherein, The classification number is a globally unique identifier of the classification, and serves as a numbering prefix rule for configuration items; The classification level is set to three levels, the third level is the actual level of configuration item classification, and the first and second levels are only used to classify configuration items; The parent category ID is used to define the hierarchical relationship of categories.

3. The information maintenance method based on dynamic configuration item management according to claim 1, characterized in that: The configuration item model table is constructed to manage metadata corresponding to the structure, attributes and control information of the configuration item model; The metadata corresponding to the structural information includes the attribute group and type, the metadata corresponding to the attribute information includes the attribute name, data type and index order, and the metadata corresponding to the control information includes the entry method, entry configuration and verification rules.

4. The information maintenance method based on dynamic configuration item management according to claim 3 is characterized in that: The types are divided into two levels, namely, attribute groups and attributes, wherein the attribute groups are used to classify and divide the attributes, and the affiliation between the attributes and the attribute groups is defined by the affiliation attribute groups.

5. The information maintenance method based on dynamic configuration item management according to claim 3 is characterized in that: The attribute name is identification information of attributes of the same type; The index order is used to define whether an attribute is an index field, and the mapping relationship between the configuration item attribute and the general index field in the configuration item data table is controlled by the index number.

6. The information maintenance method based on dynamic configuration item management according to claim 1, characterized in that: The configuration item relationship model table is constructed to manage the subject-object relationship between various configuration items. The information described in the configuration item relationship model table includes subject classification, object classification, relationship type, subject relationship attribute, object target domain, summary generation rule, and summary combination rule; wherein, The subject classification and object classification are used to describe the role of classification in the relationship. The subject classification acts on the object classification with a certain relationship type. The subject relationship attribute is used to define the attribute through which the subject configuration item establishes a relationship with the object configuration item; The object target domain represents the attribute of the object configuration item used to identify the information of the object in the subject configuration item; The summary generation rules and summary combination rules are used to define one-to-many relationships and combination rules for multiple object classifications.

7. The information maintenance method based on dynamic configuration item management according to claim 1, characterized in that: When the configuration item model is updated and the configuration item data is updated, the data in the general storage field is updated, specifically: When the configuration item model is updated, the general storage fields in the configuration item data table do not change. When the configuration item model is updated and the configuration item data is updated, the data in the general storage fields is re-parsed and constructed according to the updated configuration item model.

8. The information maintenance method based on dynamic configuration item management according to claim 1, characterized in that: The configuration item relationship table is constructed to store the relationship instances between the subject and object configuration items, wherein a unique relationship primary key is created for each relationship instance. When the subject configuration item is saved, the relationship ID is stored in the configuration item relationship table, which is used to query the object configuration item information by the relationship ID when querying or displaying.

9. The information maintenance method based on dynamic configuration item management according to claim 8, characterized in that: When the configuration item data involves a relationship during maintenance, a corresponding relationship instance is automatically created according to the configuration item relationship table, and a series of attribute information under the object is obtained through the relationship instance. The attribute information is refreshed in real time as the object in the relationship instance changes.

10. A configuration management database system, characterized in that: The system uses the method described in any one of claims 1 to 9 to perform information maintenance.

Images