Primeur Online Docs
Data One Installation Manager
Data One Installation Manager
  • 🚀GETTING STARTED
    • Introduction to the installation process
    • Modules and components of Primeur Data One
      • Asynchronous and event-driven architecture
  • Data One Platform Modules vs Data One Platform Components
  • SYSTEM REQUIREMENTS
    • System requirements
      • Global system requirements 🚀
      • DOIM system requirements
      • CEMAN system requirements
      • Data Watcher system requirements
      • STENG system requirements
      • DMZ Gateway system requirements
      • Data Shaper system requirements
      • Storage requirements
  • TOPOLOGY PATTERNS
    • Network topology recommendations
    • Data One common domain topology patterns
  • INSTALL DATA ONE
    • Planning initial installation and master configuration
      • Data One runtime services, nodes, and components
    • Data One Domain Master Configuration reference
    • Performing initial installation and master configuration
      • Creating database objects for PostgreSQL
      • Creating database objects for Oracle
      • Executing the installer
      • Configuring load balancer rules for Data One WUI access on CEMAN
      • Configuring firewall rules
    • Running the system for the first time
      • Basic system control: starting, stopping and checking status
      • Launching Data One WUI
      • Wiring your STENG cluster together
  • INSTALL DATA SHAPER
    • Introduction to Data Shaper installation process
    • Planning Data Shaper installation
    • Data Shaper System Requirements
    • Data Shaper Domain Master Configuration reference
    • Performing Data Shaper initial installation and master configuration
      • Creating database objects for PostgreSQL
      • Creating database objects for Oracle
      • Executing Data Shaper installer
      • Configuring additional firewall rules for Data Shaper
  • CLI and Configuration files
    • dataone.sh reference
    • doim.sh reference
    • dataonedbmgr.sh reference
    • dataonedb.cfg reference
Powered by GitBook
On this page
  1. GETTING STARTED
  2. Modules and components of Primeur Data One

Asynchronous and event-driven architecture

An integration platform must be asynchronous because data producers and data consumers may have different timing constraints for data production and use. Data has to be used at any time and not necessarily as soon as it is produced. Data is a two-dimension entity: a piece of data without timing is useless and Primeur integrates data with a tight relation to time. In Primeur Data One, integration data flows react to events through Virtual Boxes, a powerful tool to define a set of data and associate events with its changes. This removes the need for systems to continuously check if new data is available or if anything has changed. This event-driven architecture supports real-time scenarios and makes the integration process more flexible.

Harmonization and orchestration or third-party integration tools

Primeur Data One federates different integration technologies through a single point of access and harmonizes them with a unique, simple, and intuitive User Experience. It keeps the operational autonomy of integrated technologies enabling their cooperation while allowing them to evolve autonomously without interference with other technologies. This preserves existing investments and allows companies to adopt the new technology smoothly.

PreviousModules and components of Primeur Data OneNextData One Platform Modules vs Data One Platform Components

Last updated 23 days ago

🚀