Proxy settings for on-prem clients
Note
Using proxies is optional and it is not required by on-premise extractors. It is only needed if your infrastructure demands it.
If you need to use a proxy server between the on-premise extractor and the source system or between the on-premise extractor and Data Integration in the cloud, you need to create a configuration file per connection and then link their configuration files in the extractor configuration.
Specifying the location of the configuration file
 |
In the file application.yml (see above) you need to add the configurations displayed on the left
proxy-config-path: This defines the path to the configuration of the proxy server between the source system and the extractor.
internal-proxy-config-path: This defines the path to the configuration of the proxy server between the extractor and the cloud endpoint. It is called "internal" because it is used for the communication of two components provided by Celonis.
The path always needs to be defined relative to the extractor file.
Example 1: If the configuration file proxy.yml for the proxy between the source system and the extractor is in the same folder, the configuration should look as follows:
application-local.yml
celonis: proxy-config-path: proxy.yml
Example 2: If the configuration file proxy.yml for the proxy between the extractor and Data Integration in the cloud is in the subfolder conf, the configuration should look as follows:
application-local.yml
celonis: internal-proxy-config-path: conf/proxy.yml
Creating a configuration file for the proxy server
For each separate proxy server you need to create a configuration file with the connection details:
enabled: true if the proxy server should be activated, false otherwise
host: the IP address or hostname of the proxy server
port: the port at which the server can be reached
user (optional): the user name for basic authentication with the proxy
password (optional): password for basic authentication with the proxy