Extensive configurable data exchange between TYPO3 intranet and website

Tags: TYPO3 API Data Migration Customer Portal Performance Employee portal

The aim of this project was to develop a robust, configurable data exchange between a TYPO3-based intranet and an external website, with the intranet serving as the central master database. All relevant data such as team and employee profiles, documentation, files and manuals are maintained and synchronized daily on the intranet. The specially developed interface transfers this data to the website via a flexible export and import system. A Typoscript-like configuration controls the data preparation and transfer so that new data areas can be easily integrated into the data exchange in future without the need for additional programming work.

 

Functionalities in detail

  1. TYPO3 intranet as master database:
    • The intranet acts as a central data source and contains all the information that is synchronized with the website in daily exchanges, including employee and team profiles, documentation, files and special pages.
    • Central management on the intranet enables consistent data maintenance and ensures that all relevant content on the website is always up to date.
  2. Daily synchronization via a tailor-made interface:
    • The website is synchronized with the intranet data on a daily basis. The system prepares the intranet data, transfers it via a specially developed API interface and synchronizes it efficiently with the website.
    • This means that content is always up-to-date and maintained without the need for manual intervention.
  3. Flexible export through Typoscript-like configuration:
    • The export process uses a Typoscript-like configuration that allows individual data areas of the intranet to be handled specifically and transferred to a suitable export format.
    • This configuration is extensible so that new export areas can be easily added through customization without the need for additional programming development.
  4. Master-source logic for the import:
    • The import process treats the intranet data as the master source. New data is automatically created, existing data is updated and data that no longer exists is deleted from the intranet on the website to avoid data inconsistencies.
    • This logic ensures that the content on the website is always synchronized and consistent.
  5. Configurable import to match exports:
    • The import process on the website side uses a configuration that is also similar to Typoscript and is aligned with the export formats. This means that both sides can be configured flexibly and the data exchange can be extended or adapted at any time by changing the configuration.
    • This approach makes it possible to adapt the data flow to new requirements and data areas easily and without additional programming work.