Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
Business fundamentals · API · continuity

4D, PostgreSQL & data synchronization

The continuity of a system also depends on the data that its applications share. The Reymann course connects 4D bases, web services, PostgreSQL and synchronization between 4D and Dolibarr.

Understand the rules supported by the existing

A business base contains more than tables: identifiers, relationships, calculations and input practices determine the behavior of applications. Exchanges must preserve this logic when a new tool enters the chain.

Patrice's experience combines a practice started with FileMaker in 1994 and the 4D environments used at Reymann. It pays particular attention to dependencies that have been built over time.

Providing 4D services

The technical work included testing web services between versions of 4D and the study of SOAP exchanges. Envelope mapping and XML/JSON conversion were part of the connection topics with other environments.

Compatibility must be observed in real exchanges: structure of a call, fields, types, expected response and error handling. An accessible service must also produce data that can be used by the application that consumes it.

Articulate PostgreSQL and platform services

Rey-Active and the PIM had PostgreSQL bases. The platform, the content produced and the processing had to retrieve their information while maintaining clear responsibilities.

We define the correspondences and the update rules before multiplying the connections: which tool refers, what information can change and how to control the differences between the systems.

Period documents & interfaces

A 2017 architectural study to organize applications and their exchanges.

Study of architecture Akeneo, Nextcloud and Rey-ActiveEnlarge
Study of architecture Akeneo, Nextcloud and Rey-Active

Design document from January 2017: study of exchanges between Excel imports, PIM Akeneo, images in Nextcloud and Rey’actif production platform.

Architecture study · design document · 27/01/2017

Synchronize 4D and Dolibarr

A 4D/ synchronization connectorDolibarr was part of the ecosystem. This articulation linked the existing system to commercial management and required tracking of data correspondence.

For a recovery or synchronization project, the method consists of preparing the mappings, checking representative datasets and controlling the results. Managing duplicates, missing data and reminders is part of the framework.

Understanding the exchanges

Connect applications and keep exchange control.

Example of a path with deferred processing: the connector prepares the data, organizes their transfer and keeps the results of the exchanges for monitoring and recovery.

Connect applications and keep exchange control.Enlarge the diagram
  1. 01

    Sources

    API, files and databases

    Identifiers • formats
    Incoming data ↓
  2. 02

    Adaptation

    Business correspondence

    Fields • units • references
    Transformed data ↓
  3. 03

    Processing queue

    Organize requests

    Priority • planning
    Tasks ready ▼
  4. 04

    Execution

    Treating tasks

    Controls • matches
    Writing in the target ▼
  5. 05

    Destination

    Application or ERP

    Objects • management rules
    Returns and variances ▼
  6. 06

    Follow-up and resumption

    Control returns

    Journal • status • reminder
Connect applications and keep exchange control.Enlarge the diagram
Functional diagram · synthetic reading of flows and control points.
Identify

Keep the reference of the source and that of the target application.

Transform

Describe correspondences and distinguish direct calls from deferred processing.

Take over

Find the state and context of an exchange to be retired.

Your job deserves
the right tools.

A specific need, a software to evolve, a project to frame.

Exchange on your project

Complementary expertise, the same high standards.