Cross-platform asset synchronization method and system for configuration management database

Abstract

The invention provides a cross-platform asset synchronization method and system for a configuration management database, and the method comprises the steps: monitoring the creation, reading, updating and deletion events of resources, and triggering an asset synchronization instruction according to the events; in response to a trigger instruction of asset synchronization, generating a corresponding multi-dimensional synchronization task according to a dynamically configured synchronization strategy and according to preset condition filtering, priority ranking and dependency in the synchronization strategy; queuing the multi-dimensional synchronization tasks according to a synchronization strategy and a time level, generating an asynchronous task queue according to a queuing sequence, and sequentially scheduling and executing each task in the asynchronous task queue; and according to the specific requirements of the task and the type of the target system, dynamically adapting to a supported protocol, and sending the task to the corresponding target system for execution. Through the four-layer architecture design of event-driven triggering, rule engine decision, task queue scheduling and resource gateway adaptation, a complete asset synchronous closed loop is formed, and asset synchronous management of the CMDB is realized.

Description

Technical Field

[0001] The present invention belongs to the field of operation and maintenance management, and in particular relates to a method and system for synchronizing cross-platform assets in a configuration management database. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] In today's complex IT environment, there is a strong demand for configuration management database (CMDB) asset synchronization in areas such as business agility, compliance and auditing, refined operation and maintenance management, and the construction of active-active data centers. Therefore, CMDB asset synchronization is a very important part of enterprise informatization construction.

[0004] According to the inventors, there are many problems in the current CMDB asset synchronization process: The existing CMDB asset synchronization process often uses a timed polling mechanism, which involves periodically calling the CMDB API to scan the entire resource list and then triggering synchronization by comparing the differences before and after. This approach is labor-intensive and lacks the technical architecture's requirements for data timeliness.

[0005] On the other hand, after completing infrastructure changes, operations and maintenance personnel often use manual execution of synchronization scripts to achieve synchronization, which lacks effective closed-loop processing and increases the risk exposure of configuration changes.

[0006] Moreover, the existing CMDB asset synchronization process generally traces data changes through limited versions of database CRUD (Create, Delete, Modify, and Query), which has a large lag and increases the pressure on database table queries, increasing the workload.

[0007] Finally, during the CMDB asset synchronization process, a lot of data involves obtaining / operating from other platforms, that is, cross-platform synchronization processing. The existing cross-platform synchronization mainly relies on manual intervention, which is prone to operational risks and is not conducive to achieving full automation of cross-platform operations. Summary of the Invention

[0008] To address the above-mentioned issues, the present invention proposes a cross-platform asset synchronization method and system for a configuration management database. The present invention forms a complete asset synchronization closed loop through a four-layer architecture design consisting of event-driven triggering - rule engine decision-making - task queue scheduling - resource gateway adaptation. Each part has a clear division of labor and close dependencies, achieving logical coherence and technical complementarity in the combined design, and realizing asset synchronization management of the CMDB.

[0009] According to some embodiments, the present invention adopts the following technical solutions: A method for synchronizing cross-platform assets in a configuration management database comprises the following steps: Monitor resource creation, reading, updating, and deletion events, and trigger asset synchronization instructions based on these events; In response to the trigger instruction of asset synchronization, according to the dynamically configured synchronization strategy, the corresponding multi-dimensional synchronization task is generated based on the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; Queue multi-dimensional synchronization tasks according to synchronization strategies and time levels, generate asynchronous task queues according to the queueing order, and sequentially schedule and execute each task in the asynchronous task queue; According to the specific requirements of the task and the type of target system, the supported protocols are dynamically adapted and the task is sent to the corresponding target system for execution, thus achieving intelligent asset synchronization between the configuration management database and other systems.

[0010] As an optional implementation, during the process of monitoring resource creation, reading, updating and deletion events, the monitoring time frequency is set according to different event types, and each event is monitored for any of the following actions: creation, deletion and update.

[0011] As a further implementation method, the priorities of various events are, from high to low, host dependency events, host events, module events, cluster events and business events. The monitoring frequency of each event decreases in accordance with the priority.

[0012] As an optional implementation, the synchronization strategy includes preset conditional filtering, and the conditional filtering rules include fuzzy or exact matching based on the business name, cluster name and module name, and filtering possible related events based on the matching results.

[0013] As an optional implementation, the synchronization strategy includes preset priorities, and the priorities are sorted according to asset sensitivity and business impact, following the priority order of host>module>cluster>business.

[0014] As a further implementation method, a weighted scoring mechanism is adopted in the priority sorting. Multiple evaluation dimensions are set for each asset change event, and different weights are assigned to each dimension. The event is scored according to the specific circumstances of each dimension. The higher the score, the higher the priority, to ensure that key events are handled first.

[0015] As an optional implementation, the synchronization strategy includes preset dependencies, which are analyzed by constructing an event dependency graph based on the asset topology in the configuration management database, with each asset change event as a node and the dependencies between events as edges; When a new event is generated, the predecessor dependent event of the event is searched from the event dependency graph to determine whether the predecessor event has been processed. If not, the new event is placed in the waiting queue; if the predecessor event has been completed, the new event is pushed to the executable queue; in the event of an exception or data backtracking, the process starts from the exception point or backtracking point based on the event dependency graph.

[0016] As an optional implementation method, the process of queuing multi-dimensional synchronization tasks according to synchronization strategies and time levels includes: creating and scheduling synchronization tasks based on synchronization strategies and different time level requirements. During the task creation phase, if the synchronization strategy stipulates real-time synchronization for specific services and timed synchronization for some services, when the event task queue receives an event, the task scheduling module parses the business, cluster and module information to which the event belongs, and places it in task queues with different corresponding response time levels according to the priority of the task and the required time level.

[0017] As an optional implementation method, in the task scheduling stage, a time polling algorithm is adopted to set the time unit. The time wheel pointer scans the task queues of different corresponding time levels in turn. When the pointer points to a task queue, it checks whether there are tasks in the queue. If so, the tasks are taken out in order of priority for processing to ensure that tasks at different time levels are executed in an orderly manner.

[0018] As an optional implementation method, based on the specific requirements of the task and the type of target system, the process of dynamically adapting the supported protocols includes: coordinating the pre-operation of each peripheral system, and formally submitting the update operation after the resource gateway receives the successful pre-operation feedback from all relevant peripheral systems. If any system returns a failure during the pre-operation stage, all systems that have executed the pre-operation will be immediately coordinated to roll back.

[0019] A cross-platform asset synchronization system for a configuration management database, comprising: The event monitoring module is configured to monitor resource creation, read, update, and delete events, and trigger asset synchronization instructions based on these events; The rule engine module is configured to respond to the trigger instruction of asset synchronization and generate corresponding multi-dimensional synchronization tasks according to the dynamically configured synchronization strategy and the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; The task queue scheduling module is configured to queue multi-dimensional synchronous tasks according to the synchronization strategy and time level, generate an asynchronous task queue according to the queue order, and sequentially schedule and execute each task in the asynchronous task queue; The resource gateway adaptation module is configured to dynamically adapt the supported protocols according to the specific requirements of the task and the type of target system, and send the task to the corresponding target system for execution, thereby achieving intelligent asset synchronization between the configuration management database and other systems.

[0020] Compared with the prior art, the present invention has the following beneficial effects: With the help of an event-driven architecture, the present invention can capture CRUD events of asset configurations in the CMDB in real time. Once there is a change in asset information, the system responds immediately and triggers the corresponding synchronization operation, avoiding the delay caused by manual periodic checks or polling, and ensuring that asset data is updated in a timely manner across relevant systems, always maintaining consistency and accuracy.

[0021] This invention allows for flexible configuration of conditional filtering, priorities, and dependencies based on diverse business needs. It can tailor synchronization strategies to complex and ever-changing business scenarios, meeting diverse synchronization requirements. Furthermore, it adapts to multiple protocols and can interact with diverse systems, such as asset management, job execution, and information collection, adapting to diverse technical environments and improving the system's versatility and scalability.

[0022] The present invention schedules tasks according to time levels and reasonably allocates system resources. The asynchronous task processing mechanism avoids task blocking and allows the system to process multiple tasks simultaneously, greatly improving the overall processing capacity and operating efficiency. Moreover, unnecessary synchronous operations are reduced through conditional filtering, avoiding waste of resources and achieving optimal utilization of resources.

[0023] The present invention can ensure that synchronization tasks are executed in the correct order, preventing data inconsistency or system failures caused by sequence errors; at the same time, the priority management of synchronization tasks ensures that key asset information is synchronized first, enhances the stability and reliability of the system, and reduces the risk of business interruption due to asset data problems.

[0024] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0026] Figure 1 This is a flowchart of an asset synchronization method according to an embodiment; Figure 2 This is a schematic diagram of the structure of an asset synchronization system according to an embodiment. DETAILED DESCRIPTION

[0027] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0028] It should be noted that the following detailed descriptions are illustrative and intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present invention belongs.

[0029] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, they indicate the presence of features, steps, operations, devices, components and / or combinations thereof.

[0030] In the absence of conflict, the embodiments and features in the embodiments of this application can be combined with each other.

[0031] Example 1 A method for synchronizing cross-platform assets in a configuration management database, such as Figure 1 As shown, the following steps are included: Monitor resource creation, reading, updating, and deletion events, and trigger asset synchronization instructions based on these events; In response to the trigger instruction of asset synchronization, according to the dynamically configured synchronization strategy, the corresponding multi-dimensional synchronization task is generated based on the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; Queue multi-dimensional synchronization tasks according to synchronization strategies and time levels, generate asynchronous task queues according to the queueing order, and sequentially schedule and execute each task in the asynchronous task queue; According to the specific requirements of the task and the type of target system, the supported protocols are dynamically adapted and the task is sent to the corresponding target system for execution, thus achieving intelligent asset synchronization between the configuration management database and other systems.

[0032] In this embodiment, during the process of monitoring resource creation, reading, updating, and deletion events, the monitoring time frequency is set according to the different types of events, and each event is monitored for any of the following actions: creation, deletion, and update; The priorities of various events are, from high to low, host dependency events, host events, module events, cluster events, and business events. The monitoring frequency of each event decreases according to its priority.

[0033] In this embodiment, the synchronization strategy includes preset conditional filtering, and the conditional filtering rules include fuzzy or exact matching based on the business name, cluster name, and module name, and filtering possible related events based on the matching results; In addition, the synchronization strategy also includes preset priorities, which are sorted according to asset sensitivity and business impact, following the priority order of host>module>cluster>business.

[0034] Furthermore, in terms of priority sorting, a weighted scoring mechanism is adopted to set multiple evaluation dimensions for each asset change event, assign different weights to each dimension, and score the event based on the specific circumstances of each dimension. The higher the score, the higher the priority, to ensure that key events are handled first.

[0035] Finally, the synchronization strategy includes pre-set dependencies, which are analyzed by constructing an event dependency graph based on the asset topology in the configuration management database, with each asset change event as a node and the dependencies between events as edges; When a new event is generated, the predecessor dependent event of the event is searched from the event dependency graph to determine whether the predecessor event has been processed. If not, the new event is placed in the waiting queue; if the predecessor event has been completed, the new event is pushed to the executable queue; in the event of an exception or data backtracking, the process starts from the exception point or backtracking point based on the event dependency graph.

[0036] In this embodiment, the process of queuing multi-dimensional synchronization tasks according to synchronization strategies and time levels includes: creating and scheduling synchronization tasks according to synchronization strategies and different time level requirements. In the task creation stage, if the synchronization strategy stipulates real-time synchronization for specific services and timed synchronization for some services, when the event task queue receives an event, the task scheduling module parses the business, cluster and module information to which the event belongs, and puts it into task queues of different corresponding response time levels according to the priority of the task and the required time level.

[0037] In this embodiment, during the task scheduling stage, a time polling algorithm is adopted to set the time unit. The time wheel pointer scans the task queues of different corresponding time levels in turn. When the pointer points to a task queue, it checks whether there are tasks in the queue. If so, the tasks are taken out in order of priority for processing to ensure that tasks at different time levels are executed in an orderly manner.

[0038] Based on the specific requirements of the task and the type of target system, the process of dynamically adapting the supported protocols includes: coordinating the pre-operation of each peripheral system, and formally submitting the update operation after the resource gateway receives the successful pre-operation feedback from all relevant peripheral systems. If any system returns a failure during the pre-operation phase, all systems that have executed the pre-operation will be immediately coordinated to roll back.

[0039] Example 2 A cross-platform asset synchronization system for configuration management databases, such as Figure 2 Shown, including: The event monitoring module is configured to monitor resource creation, read, update, and delete events, and trigger asset synchronization instructions based on these events; The rule engine module is configured to respond to the trigger instruction of asset synchronization and generate corresponding multi-dimensional synchronization tasks according to the dynamically configured synchronization strategy and the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; The task queue scheduling module is configured to queue multi-dimensional synchronous tasks according to the synchronization strategy and time level, generate an asynchronous task queue according to the queue order, and sequentially schedule and execute each task in the asynchronous task queue; The resource gateway adaptation module is configured to dynamically adapt the supported protocols according to the specific requirements of the task and the type of target system, and send the task to the corresponding target system for execution, thereby achieving intelligent asset synchronization between the configuration management database and other systems.

[0040] The configuration management database (CMDB) serves as the core data storage for the entire system, carrying configuration information for various assets, including businesses, clusters, modules, and hosts. When data in the CMDB is created, updated, or deleted—CRUD operations—the corresponding business, cluster, module, or host events are generated. For example, creating a new business or updating host configuration information triggers corresponding events.

[0041] This embodiment uses an event monitoring module to capture resource creation, reading, updating, and deletion (CRUD) events, providing trigger points for subsequent processing.

[0042] More specifically, as an asset and application-oriented configuration management platform, CMDB comprehensively manages enterprise infrastructure assets and can monitor various related event changes when configuration information changes.

[0043] As a typical embodiment, various time periods and monitoring time levels can be set as follows: Business events have a very low frequency of change and can be monitored on a daily basis or not at all. Cluster events have a low frequency of change and are monitored on a daily basis. Module events have low change frequency and are monitored at the hourly level; Host events have a high frequency of changes and are monitored at the minute level; Host dependency events change frequently and can be monitored at a minute or higher level.

[0044] Because each event type has a corresponding action (create, delete, and update), full data for each event type is obtained from the CMDB API hook, and the key data required by the target system is extracted from this full data. This approach can respond to changes in asset configurations in real time, eliminating the need for polling checks and reducing system resource consumption. It can also quickly detect changes at different levels, such as business, cluster, module, and host, providing a timely and accurate trigger mechanism for asset synchronization.

[0045] The rule engine module in this system has built-in functional modules such as condition filtering, priority setting, and dependency judgment.

[0046] The conditional filtering module selects events requiring synchronization based on pre-set conditions. The priority module ranks these filtered events by importance to ensure that critical events are prioritized. The dependency module analyzes the sequence and interdependencies between events to avoid synchronization errors. The rule engine integrates these processes to generate a specific synchronization strategy, determining which events require synchronization and how.

[0047] First, the conditional filtering module can filter out events that meet specific standards through conditional filtering, reducing unnecessary synchronization operations. The specific rules are: fuzzy / exact matching based on business name, cluster name, and module name, which is used for refined synchronization with different requirements such as multiple naming combinations created with downstream system assets and infrequent asset changes.

[0048] The conditional filtering module selects events for synchronization based on multi-dimensional precise or fuzzy matching rules. At the business level, for different business names, if the system contains Business A (data center) and Business B (office assets), and only Business A assets need to be synchronized, the module uses an exact match on the "Business A" name to filter out creation, update, and deletion events related to it. For infrequent asset changes, fuzzy matching can be used, such as when the business name contains the specific keyword "data," to filter out potentially relevant business events and avoid synchronizing large amounts of unrelated business data.

[0049] Regular expression matching is used at the cluster, module, and host levels. Assuming the downstream system naming convention is "cluster_module_host IP," to rename and filter events related to a specific cluster or module, the module uses regular expressions to match the cluster and module names. For example, matching "Operation and Maintenance Platform_SFTP_.*" would filter out all host events related to "Operation and Maintenance Platform_SFTP," providing accurate data for subsequent renaming and synchronization.

[0050] The priority module can ensure that key events are handled first through priority setting, ensuring that important asset information is updated in a timely manner.

[0051] The Priority Module sets sorting rules based on asset sensitivity and business impact. Regarding asset sensitivity, the priority order is host > module > cluster > business. For example, a host configuration change takes precedence over a module or cluster change. Regarding business impact, asset changes closely related to core business processes receive higher priority.

[0052] In the sorting algorithm, some implementations employ a weighted scoring mechanism. Each asset change event is evaluated based on multiple dimensions, such as asset type, change operation type (create, update, delete), and business importance, and each is assigned a different weight. For example, for a host configuration update event, asset type is weighted 0.5, update operation weighted 0.3, and core business importance weighted 0.2. Events are scored based on their specific characteristics in each dimension. Higher scores indicate higher priority, ensuring that critical events are handled first.

[0053] The dependency module analyzes events by constructing an event dependency graph. Based on the asset topology in the CMDB, each asset change event is represented as a node, and the dependencies between events are represented as edges. For example, a host configuration change event may depend on the initialization of its module, while a module change event may depend on the availability of cluster resource allocation.

[0054] When a new event is generated, the module searches the event dependency graph for its predecessor events and determines whether the predecessor events have been processed. If not, the new event is placed in the waiting queue; if the predecessor events have been completed, the new event is pushed to the executable queue. In the event of a system anomaly or data backtracking, the module uses the event dependency graph to reversely search for related events based on the dependency relationships, starting from the anomaly or backtracking point, to ensure data integrity and consistency and avoid duplicate data processing.

[0055] The synchronization policy generated by the rule engine module acts as a producer, sending relevant event information to the event task queue. The task queue receives business events, cluster events, module events, and host events from various sources. Within the event task queue is a task scheduling module. This module categorizes and sorts various events based on the synchronization policy and timescales (seconds, minutes, and hours). It then creates corresponding synchronization tasks and assigns them to the corresponding second-, minute-, or hour-level task queues.

[0056] The task queue creates and schedules synchronization tasks based on timescales (seconds, minutes, hours, and days). This hierarchical approach rationally arranges the order and timing of task execution based on different business scenarios and data timeliness requirements, improving system resource utilization efficiency. This allows for rapid response to urgent synchronization needs while also enabling the orderly processing of a large number of routine tasks.

[0057] The task queue creates and schedules synchronization tasks based on synchronization policies and time-based requirements. During task creation, the synchronization policy may specify real-time synchronization for specific services or timed synchronization for some services. When the event task queue receives an event, the task scheduling module first analyzes the event's associated service, cluster, module, and other information.

[0058] For second-level tasks, if a host relationship change event is triggered, this event has extremely high real-time requirements for the system, and the scheduling module directly assigns it to the second-level task queue.

[0059] For minute-level tasks, such as host configuration change events, we process them once per minute, package all the host configuration change events collected within a certain period into tasks, and put them into the minute-level task queue.

[0060] Hourly tasks are aimed at module change events, etc. The collected module change events are sorted out every hour, and corresponding synchronization tasks are created and placed in the hourly task queue.

[0061] During the task scheduling phase, a round-robin algorithm is employed. Using seconds as the unit, the time wheel pointer sequentially scans the second-level, minute-level, and hour-level task queues. When the pointer points to a task queue, it checks whether there are any tasks in the queue. If so, the tasks are retrieved and processed in order of priority. This ensures the orderly execution of tasks at different time levels, improves system resource utilization, and meets the data timeliness requirements of different business scenarios.

[0062] Synchronous tasks in the event task queue are transmitted as consumers to the resource gateway adapter module. This module adapts to multiple protocols to meet the needs of interacting with resource management and control platforms, monitoring platforms, operation platforms, security operations platforms, network management platforms, and other peripheral systems. Based on the specific requirements of the task and the characteristics of the target system, the synchronization task is sent to the corresponding target system for execution via the adapter protocol, thus achieving intelligent asset synchronization between the CMDB and other systems. Furthermore, this module supports asynchronous task execution, effectively avoiding system congestion caused by synchronous operations and improving the overall system's operational efficiency and responsiveness. During the specific implementation process, the resource gateway abstracts cross-platform operation differences. By adapting to multiple protocols, the CMDB can actively trigger external system collaboration, forming an automated ecosystem of "asset change - system response - business closed loop", ensuring the compatibility and versatility of asset synchronization in different environments. The first is protocol adaptation: The resource gateway layer protocol adapter module connects to the access protocols such as RESTful, gRPC, SSH, SNMP, etc. specified by the external system. At this time, the protocol adapter module will construct a request that meets the requirements according to the protocol.

[0063] Based on the adaptation type, the external system is classified into different scenarios: Resource management and control platforms send synchronization tasks involving host configuration changes to bastion hosts, monitoring platforms, and security operations platforms to perform operations such as asset creation, user push, asset grouping, and tag management, thereby achieving comprehensive asset management to meet the multi-dimensional needs of supervision, security, and monitoring.

[0064] The job execution platform will perform a series of automated command operations such as operating system level initialization, user initialization, security baseline initialization, and environment initialization on the hosts involved in the configuration change to complete the effective change of the configuration baseline.

[0065] Information collection platforms specifically collect operating system, hardware, and software information related to host configuration changes to complete differentiated configuration inspections.

[0066] The second is to ensure cross-platform transaction consistency.

[0067] For resource management platforms, cross-platform transaction consistency ensures asset consistency across different types of peripheral systems, such as physical machines in local data centers and their supporting monitoring platforms and bastion hosts.

[0068] The resource gateway uses the two-phase commit (2PC) protocol: In the first phase, the resource gateway coordinates the pre-operation of various peripheral systems. When the resource gateway receives the pre-operation success feedback from all relevant peripheral systems, it enters the next phase. In the second phase, the update operation is formally submitted. If any system returns a failure during the pre-operation phase, the resource gateway immediately coordinates all systems that have executed the pre-operation to roll back the update. This ensures that data in each system is not inconsistent due to partial success and partial failure, maintaining the atomicity and consistency of cross-platform transactions.

[0069] Furthermore, if any anomalies occur during asset synchronization with external systems, timely and effective notification and follow-up are provided. When the resource gateway detects an asset synchronization failure, it sends an alert to relevant operations and maintenance personnel via email, SMS, instant messaging, and other channels based on predefined alert rules. This alert details the failed asset synchronization task, the affected CMDB asset information, the target external system, and the specific cause of the error, enabling operations and maintenance personnel to quickly locate the problem.

[0070] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of one or more computer-usable storage media (including but not limited to disk storage, CD - ROM , optical storage, etc.).

[0071] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0072] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0073] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0074] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made by those skilled in the art that fall within the spirit and principles of the present invention and do not require creative effort are intended to be within the scope of protection of the present invention.

Claims

1. A method for synchronizing cross-platform assets in a configuration management database, characterized in that: The following steps are involved: Monitor resource creation, reading, updating, and deletion events, and trigger asset synchronization instructions based on these events; In response to the trigger instruction of asset synchronization, according to the dynamically configured synchronization strategy, the corresponding multi-dimensional synchronization task is generated based on the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; Queue multi-dimensional synchronization tasks according to synchronization strategies and time levels, generate asynchronous task queues according to the queueing order, and sequentially schedule and execute each task in the asynchronous task queue; According to the specific requirements of the task and the type of target system, the supported protocols are dynamically adapted and the task is sent to the corresponding target system for execution, thus achieving intelligent asset synchronization between the configuration management database and other systems.

2. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: When monitoring resource creation, reading, updating, and deletion events, set the monitoring time frequency based on the event type and monitor any of the following actions for each event: creation, deletion, and update; The priorities of various events are, from high to low, host dependency events, host events, module events, cluster events, and business events. The monitoring frequency of each event decreases according to its priority.

3. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: The synchronization strategy includes preset conditional filtering, and the rules of the conditional filtering include fuzzy or exact matching based on the business name, cluster name and module name, and filtering possible related events based on the matching results.

4. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: The synchronization policy includes preset priorities, which are arranged in order of asset sensitivity and business impact, and follow the priority order of host > module > cluster > business.

5. A cross-platform asset synchronization method for a configuration management database as claimed in claim 4, characterized in that: In terms of priority sorting, a weighted scoring mechanism is adopted to set multiple evaluation dimensions for each asset change event, assign different weights to each dimension, and score the event based on the specific circumstances of each dimension. The higher the score, the higher the priority, to ensure that key events are handled first.

6. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: The synchronization strategy includes preset dependencies, which are analyzed by constructing an event dependency graph based on the asset topology in the configuration management database, with each asset change event as a node and the dependencies between events as edges; When a new event is generated, the preceding dependent event of the event is searched from the event dependency graph to determine whether the preceding event has been processed. If not, the new event is placed in the waiting queue. If the preceding event has been completed, the new event will be pushed to the executable queue; in the event of an exception or data backtracking, it will start from the exception point or backtracking point according to the event dependency graph.

7. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: The process of queuing multi-dimensional synchronization tasks according to synchronization strategies and time levels includes: creating and scheduling synchronization tasks according to synchronization strategies and different time level requirements. During the task creation phase, if the synchronization strategy stipulates real-time synchronization for specific businesses and timed synchronization for some businesses, when the event task queue receives an event, the task scheduling module parses the business, cluster, and module information to which the event belongs, and places the task into task queues of different corresponding response time levels according to the task priority and required time level.

8. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that During the task scheduling phase, a time polling algorithm is used to set the time unit. The time wheel pointer scans the task queues of different corresponding time levels in turn. When the pointer points to a task queue, it checks whether there is a task in the queue. If so, the tasks are taken out in order of priority for processing to ensure that tasks at different time levels are executed in an orderly manner.

9. A cross-platform asset synchronization method for a configuration management database as claimed in claim 1, characterized in that: Based on the specific requirements of the task and the type of target system, the process of dynamically adapting the supported protocols includes: coordinating the pre-operation of each peripheral system, and formally submitting the update operation after the resource gateway receives the successful pre-operation feedback from all relevant peripheral systems. If any system returns a failure during the pre-operation phase, all systems that have executed the pre-operation will be immediately coordinated to roll back.

10. A cross-platform asset synchronization system for a configuration management database, characterized by: include: The event monitoring module is configured to monitor resource creation, read, update, and delete events, and trigger asset synchronization instructions based on these events; The rule engine module is configured to respond to the trigger instruction of asset synchronization and generate corresponding multi-dimensional synchronization tasks according to the dynamically configured synchronization strategy and the condition filtering, priority sorting and dependency relationships preset in the synchronization strategy; The task queue scheduling module is configured to queue multi-dimensional synchronous tasks according to the synchronization strategy and time level, generate an asynchronous task queue according to the queue order, and sequentially schedule and execute each task in the asynchronous task queue; The resource gateway adaptation module is configured to dynamically adapt the supported protocols according to the specific requirements of the task and the type of target system, and send the task to the corresponding target system for execution, thereby achieving intelligent asset synchronization between the configuration management database and other systems.

Images