Setting up an ETL configuration

There are three parts to setting up an ETL configuration:

1. Setting up a database where you can either import data from or export data to. The import and export database can be located either Internal on the Data Center Operation or in an External database setup (server, etc.). Both configurations are done from the same configuration interface.
2. Setting up the ETL transformation, that moves the data either from the database to Data Center Operation (import) or from Data Center Operation to the database (export).
3. Setting a schedule for when the configuration should run.

To start setting up an ETL configuration login to web client with a user with the 'System Administration' permission, and navigate to Cogwheel -> Manage ETL Integration.

Internal Database

An Internal Database is a PostgreSQL instance running on the same server as Data Center Operation.
The database is created and deleted by Data Center Operation.
To create an internal database, you must provide the following:

• Configuration Name - the name that will later be shown inside the Data Center Operation client to distinguish between different databases, when configuring External Systems.
• Database Type - databases are used for either Import or export of data
• Database Name - the unique name used when creating the database. Import databases are always prefixed with 'staging_' and Export databases with 'export_'
• Username - unique username. The username is prefixed by 'etluser_'
• Password - password of the user. No special requirements.
• Allowed IP addresses - When integrating with external systems, it may be necessary to allow direct database access to the database. It is mandatory to enter the specific ip or range of ip addresses allowed to access the database. Information regarding IP ranges can be found here

Once saved, the database is created and will subsequently be available inside the Data Center Operation Client.

The internal database connection can be paused/started using the pause/start management button. This can be used in order to pause/start the scheduled communication with the database. Pressing start will not force the communication to run but enable the scheduled communication to run according to schedule.

External Database

An External Database is located outside of the Data Center Operation server. We have tested with PostgreSQL, MS Sequel Server and MySql database types and generally the only requirement is the existence of a JDBC4 compliant database driver. The database must be created, deleted and managed outside of Data Center Operation. The database must be set up using a UTF8 character encoding.

The same UI is used to create a configuration defining how to access the external database, and must include the following:

• Configuration Name - the name that will later be shown inside the Data Center Operation client to distinguish between different databases, when configuring External Systems.
• Database Type - databases are used for either Import or export of data
• Database Driver - choose what JDBC driver to use when connecting to the database. If the required driver does not appear in the list, it can be uploaded using the Upload database driver functionality
• Database Dialect - some databases speak several  different dialects, choose the one the matches your setup.
• Database Name - the name used when connecting to the database. External databases are never prefixed.
• Port Number - specify what port is used to communicate with the external database. Please note that it may be necessary to open ports in firewalls between the Data Center Operation server, and the server hosting the remote database.
• Username - unique username. The username is prefixed by 'etluser_'
• Password - password of the user. No special requirements.
• Database URL - entered values from the previous fields are combined into a database URL, if extra parameters are needed, they may be inserted into the URL.

Once saved, the configuration is created and will subsequently be available as an external database inside the Data Center Operation client.

The internal database connection can be paused/started using the pause/start management button. This can be used in order to pause/start the scheduled communication with the database. Pressing start will not force the communication to run but enable the scheduled communication to run according to schedule.