On this page:

One of the ways to integrate with external systems is using the Extract, Transform, Load (ETL) system. The ETL system creates databases which can be accessed directly by 3rd party tools and solutions. It also allows scheduled execution of transformation scripts on the Data Center Operation server. Together this gives the ability to extract and enter data on the Data Center Operation server.

Based on the ETL system, it is possible to develop custom solutions, integrating DCO with a broad range of data sources.

ETL can be used in 2 ways: Importing Data in to and Exporting Data from Data Center Operation

External system integration using ETL

Importing Data

  1. Importing data in to Data Center Operation is used when ever data must be provided to DCO.
    The data is being imported via the ETL Import Database
    There are 2 ways of importing data. One where "Data is Ready" and one where "Data needs change" before being used in DCO.
    1. Data is Ready
      When data is ready the only thing that must be done is setting up the integration between the external system providing data and DCO.
      This is done at database level. The integration is configured using the server configuration interface and can be found here
    2. Data needs change
      When data needs to be changed/modified before it is used inside DCO this can be done using a transformation or a set of transformations called a job. More information here
      Once transformation(s) are in place the integration is configured using the server configuration interface and can be found here

Exporting Data

  1. Exporting data from Data Center Operation is used when ever data is used outside DCO.
    The data is exported using the ETL Export Database.
    The data exported from Data Center Operation cannot be changed by transformations inside the Data Center Operation server. If transformation is needed this must be done outside the server in a separate setup.
  2. Setting up the export is done using the server configuration interface as described here


Import and Export Database in External System Integration using ETL

Upgrading ETL External System Integration

No files (or databases) will be deleted when upgrading/restoring a DCO system. Upgrade of the ETL system is a part of the general DCO upgrade.

When upgrading an existing solution running ETL for importing and/or exporting data to DCO a couple of guidelines are:

  • Both import and export databases are viewed as "api-like" interface to the system.
  • At any point in time the data in the import and/or export database represents the currently best known state of the system.
  • The ETL databases do not contain the sole instance of any piece of data.


This means that it is always safe to drop any ETL database and recreate it without the risk of loosing data.

 Since no data is stored in the ETL database, it is highly recommended to drop the databases and recreate them rather than moving them. This will allow databases to follow potential new database schema(s). To use the old databases, these must be moved manually which is not recommended.


When upgrading from previous versions the old transformation files will be moved into the folder /data/pentaho_backup. The transformation files must manually be moved from /data/pentaho_backup into a potential new folder structure (described below). Restoring an old backup will place transformation files in the same structure as they were in the backed up system. Please note this might not be the correct folder structure since the structure has changed between versions.


When moving/copying files into the new folder structure make sure to preserve the ownership of the folders in order for the future script to be added and executed.

The transformation files must be placed in their respective folders on the DCO server.

The transformation files folder structure on the DCO server is /data/pentaho/export or /data/pentaho/import. You can find more information about the ETL Transformation here.

Skip to end of metadata
Go to start of metadata