How do I set up a Database connection?
Step 1: Define the Connection Type (responsible role: database server and infrastructure admin)
There are two scenarios:
A) Uplinked: You do not want to or cannot allow the EMS to access your database directly, but you want to use an on-premise Extractor instead.
Only if your database is not reachable from the EMS: Set up an Extractor server on-premise in your network. A detailed diagram showing the extraction flow can be found here.
Please refer to the documentation on system requirements of the on-premise server
Duplicate removal option
For uplinked connections, you can optionally activate the duplicate removal option via the application-local.yml file.
duplicate-removal: enabled: false/true strategy: CLOUD/LOCALduplicate-removal.enabled: Allows users to enable duplicate removal. It's
false by default. It can be set to trueto enable it.duplicate-removal.strategy: Allows users to specify the duplicate removal strategy. Allowed values: LOCAL or CLOUD.
CLOUD: Duplicates are removed when data is inserted to the data pool. This operation can increase the insertion time.LOCAL: Duplicates are removed using a Bloom filter. Bloom filter is a memory-efficient probabilistic data structure, meaning there is a possibility of false positive matches.
B) Direct: You want to allow the EMS to access your database directly.
Step 2: Modify your network settings to allow the Extractor to communicate to the database and the EMS (responsible role: infrastructure admin)
There are two scenarios that depend on the connection type selected in Step 1:
Network settings for scenario A (access through an on-premise Extractor)
Source System | Target System | Port | Protocol | Description |
|---|---|---|---|---|
On-premise Extractor server | Source system (on-premise) | Depending on the database, typical ports are 5432 for Postgres and 30015 for HANA for example. | TCP | JDBC connection from on-premise Extractor server to the database. The port is the one you normally use to connect to the database. |
On-premise Extractor server | EMS | 443 | TCP | HTTPS connection from on-premise Extractor server to Celonis cloud endpoint. The IPs of the EMS depending on the cloud cluster (which can be seen in the URL), and they can be found in the section below. |
Network settings for scenario B (direct access)
Source System | Target System | Port | Protocol | Description |
|---|---|---|---|---|
EMS | Source system (on-premise) | Depending on the database, typical ports are 5432 for Postgres and 30015 for HANA for example | TCP | JDBC connection from the EMS to the database. The port is the one you normally use to connect to the database. The IPs of the EMS depending on the cloud cluster (which can be seen in the URL), and they can be found in the section below. |
EMS IP addresses depending on the cluster
The respective clusters use multiple IPs each, so you need to enable all three of them in your firewall configuration to connect the on-premise Extractor server and the cloud endpoint.
Cluster | EMS IPs as target (scenario A) | EMS IPs as source (scenario B) |
|---|---|---|
eu-1 | 18.184.97.187 18.197.224.124 52.58.147.34 | 18.184.169.225 18.184.23.70 35.156.1.191 |
eu-2 | 13.80.109.60 | 13.73.158.49 |
eu-3 | 51.116.175.215 | 51.116.239.165 51.116.175.215 20.52.130.129 |
eu-4 | 18.158.219.136 3.126.213.135 18.193.90.201 | 18.193.182.112 18.193.93.30 18.196.83.72 |
eu-5 | "teamname.eu-5.celonis.cloud" | "teamname.eu-5.celonis.cloud" |
uk-1 | No static IP Use the hostname, i.e. teamname.uk-1.celonis.cloud" | No static IP Use the hostname, i.e. teamname.uk-1.celonis.cloud" |
us-1 | 18.213.10.214 18.210.138.205 18.212.45.36 | 35.173.85.93 52.2.234.158 52.201.190.146 |
us-2 | 52.183.80.180 | 52.283.80.180 |
ru-1 ru-2 | 85.192.32.89 185.127.150.12 | 89.208.210.107 185.127.150.12 |
jp-1 | 13.73.16.140 | 52.243.46.143 |
au-1 | 3.106.161.130 13.238.88.147 | 3.104.129.217 52.65.180.17 13.54.25.182 |
Step 3: Only if your database is not reachable from the EMS: Set up the database Extractor on-premise in your network (responsible role: infrastructure admin)
Please refer to the documentation on how to set up an on premise Extractor.
For downloads, contact Celonis Support.
If you would like to use a proxy (optional), please refer to the proxy configuration page.
Step 4: Configure a user with sufficient permissions in your database (responsible role: database admin)
In order to extract from a database, you need to create or use an existing user who has read (SELECT)access to all tables that should be extracted. The user should also access the schema information_schema to read metadata for the tables to be extracted.
Step 5: Creating the Data Connection in a Data Pool (responsible role: data engineer)
 |
Fill in your connection details of the database that you would like to connect to:
Name: The name that you would like the data connection to have
Database Type: The type of database (e.g. Postgres, Oracle, ...)
Server name: The database server name or IP of the database server
Port: The port to connect to the database server
Database name: The name of the database within the database server
Schema name: The schema to use. This is optional.
Additional properties: Additional properties like validateCertificate=false for a HANA database or integratedSecurity=true for domain users in MSSQL
User name: The username to connect to the database server (see step 3)
Password: The password of the user (see step 3)