AixBOMS EAI

While common system environments in the CMDB environment struggle with programmed individual interfaces, scripts, data exchange at XML level, APIs, or discussions about interface data models and function models, in recent years, with the AixBOMS Integration Engine a standalone ETL product and feature environment has emerged that is second to none.

In current discussions about CMDB federation, reconciliation and CMDB integration, one can almost get the impression that the topic of „data (base) interface“ is being addressed for the first time.
Unfortunately, we are operating in an environment where no standard data models (CI data model, process data model, relational model) or methods exist. If manufacturers encounter difficulties within their own product suites or operate with the aforementioned outdated methods „during open heart surgery“, the consequences for heterogeneous product environments can be easily inferred.

Another method that is promoted is the „blind“ or unverified adoption of source data models or source data. Naturally, this saves on data modelling, but the idea of normalisation and standardisation in the target system (the CMDB) suffers enormously, which can have serious consequences for the use of the CMDB (visualisation, special applications, reporting, process integration, controlling, etc.).

As early as the 1990s, initial „Enterprise Application Integration (EAI)“ concepts became established. Interface standardisation and configuration, source and target data identification, release stability, and loader process control have led to more convenient methods and applications than classic proprietary interface programming.

For the CMDB environment, we have established that the requirements have become increasingly complex over time, both for (import and export) data structure, data volume, number of interfaces, and takeover check mechanisms.

AixpertSoft's consequence was the decision to use its own ETL tool (the Integration Engine), with which any data sources and targets (with corresponding loading jobs) can be connected in a user-guided manner.

Changes to data models, validation mechanisms, takeover rules, job control, or version changes are therefore greatly simplified. Even manual checks of data to be taken over (quality, changes) or parallelisation (simultaneous loading of different sources) are comfortably offered via dedicated interfaces and require no support from the manufacturer.

You can find more information at Integration Engine