Skip to content

Components and modules

The ADIB features a large and continuously growing number of modules, which are detailed in the following sections. Thanks to its modular architecture, this “application bus” is suitable for both smaller companies with few data connections and large enterprises that need to integrate multiple existing applications and diverse data sources.

File and Database Modules

File Modules

  • Excel (XLS/XLSX): Tabular files often used for manual data maintenance or export. No server connection required.
  • CSV: Simple text files with delimiters, widely used as a universal exchange format.
  • Text Formats (e.g., EDIFACT): Structured text files for standardized data exchange, particularly in trade and logistics.
  • MS Access: A file-based relational database supporting SQL queries, stored locally.

Database Modules

  • Oracle Database: Enterprise-level database server connected via parameters (username, host, password, port). Suitable for large volumes of data.
  • MySQL Database: Open-source database server connected via username, host, password, and port, commonly used in web environments.
  • MS SQL Server: Database server integrated with Microsoft environments, connected via username, host, password, and port.

Administrative Modules

In addition to file and database modules, ADIB includes administrative modules that support processes rather than directly handling data sources or sinks. Examples include file transfer, sending notifications, or executing scripts. Source and destination are often standard systems such as MySQL, Excel, or file-based databases, while additional logic is handled via specialized web service or administrative modules.

  • File Transfer Modules (FTP, SCP, …): Used to move files between systems, either as pre-processes (fetching files before processing) or post-processes (uploading files after generation). Parameters include host, username, and password. Typical use cases include exporting an XML file from a database to the file system, uploading it via FTP to a target server, or downloading a client file for processing.
  • Email Module: Allows automatic sending of emails, usually as a post-process to notify completion or confirmation. It can also be used as a pre-process if an email is required before a step begins.
  • Script Modules: Integrate scripts into workflows for specialized logic or additional processing. Types include:
    • Shell (Bash) Scripts: Fully customizable for maximum flexibility; can generate files, perform transformations, or execute system commands.
    • Ruby Scripts: Preconfigured or templated scripts for recurring tasks such as database notifications. Users select and configure parameters without altering the code. Scripts are managed centrally for consistent, controlled use.
    • Logstash Scripts: Used, for example, to export data from Elasticsearch to a relational database, requiring database credentials and target parameters.
  • Other Programs: Any executable program on a Linux system can be started via these modules, offering near-unlimited flexibility.

Webservice Modules

Webservice modules enable communication between ADIB and external systems via APIs. They can operate independently or in combination with source and destination modules to retrieve, send, or process data without requiring the user to manage API details directly.

  • Flexible Webservices (RESTful focus): Used for general API requests (GET, POST, etc.) and can be combined with source/destination modules, e.g., sending database data to an API or retrieving API data into a database. Templates define request structures, methods, and can be customized by users.
  • Templates for Established Systems: Modules for common systems like Shopware, Salesforce, Magento, or Drupal include preconfigured templates, so users do not need to define API structures manually.

Application Modules

Application modules integrate specific systems to import, export, or synchronize data. They usually include predefined processes or interfaces. Examples include:

  • Contentserv (PIM/DAM):
    • Contentserv Lightning Export: Export data from ElasticSearch or the database. SQL queries can be executed directly on the database.
    • Flexible Import (CS-ISA-Import): Starts the import process via the Integration Connector (IC).
    • Data-Modeler: Export and import of attributes, classes, and value lists.
  • Shopware (via API): Integration through Shopware’s web API.
  • SAP (via ADIB-Flexmapping): Data exchange between ADIB and SAP using Flexmapping.
  • Other Systems: Placeholder for additional applications integrated via ADIB.

ADIB Portal Modules

  • cs-elasticsearch-elasticforms Search Portal: Reads data from Contentserv ElasticSearch, understanding its structure.
  • Source EditPortal: Defines the source from the database and writes to ElasticSearch. Used for clients unable to use Elastic, or for cloud scenarios with CSV-based workflows.
  • Dynamic Portal Creation: Supports the creation of searchable and editable portals (“Portal Station”) through web applications, dynamically linked to central tables via the Portal Manager.

Additional Functionality

The ADIB includes an extensive function library, such as:

  • Dynamic PDF generation
  • Comparison lists
  • Creation of shares for product data
  • Easy import/export for bulk data maintenance

Modules can be licensed individually depending on requirements.