Installing on-prem clients locally
Limited availability
This functionality is currently in limited availability. If you’re interested in trying it out, get in touch with us through servicedesk@celonis.com.
Installing on-prem clients on your own machine can be useful for training or testing purposes. If you’re an EMS user follow these steps to prepare the installation package with on-prem clients which you can later download for local installation.
![]() |
Note
We recommend installing the on-prem clients on a central server.
Before you begin
Make sure your system meets hardware and software requirements for clients. See System requirements.
Procedure:
In your EMS instance, go to Admin & Setting > On-prem clients.
In the upper-right corner, click Set up on-prem clients.
Select Install the clients on your own machine.
Enter a unique package name.
Select the operating system on which you want to install the clients.
The installer will start downloading automatically.
Procedure:
Install your clients:
On Windows:
Extract the ZIP package.
Follow the steps of the installation wizard.
Once the installation is completed, the On-prem Client Management Tool opens.
On MacOS, Linux:
Extract the installation package to the location where you want to install the clients.
Go to the Shared folder and run OPC-Managmenet-Tool.app.
Tip
Using a command-line interface?
on MacOS:
To make sure you don't run into any permission-related issues, in Terminal, go to the Shared folder and run:
xattr -cr opc-management-tool.app
Note
The -c flag removes all attributes, whereas -r applies recursively for the entire targeted .app directory contents.
Go to Shared > opc-management-tool.app > Contents > MacOS.
Start the On-prem Clients Management Tool using ./opc-management-tool cli.
On Linux:
In Terminal, go the Shared folder.
Start the On-prem Clients Management Tool. Run:
sudo ./opc-management-tool cli
(optional) Generate the encryption key to encrypt sensitive data in the installation package:
Click Generate encryption key.
Note
Java Simplified Encryption (Jasypt) is used to store and encrypt sensitive data in the application.yml file.
Define a passphrase which will be used to create the hash for the private encryption key.
Click Save.
This will automatically create the celonis-kms.yml file and encrypt all sensitive data like the application key and the proxy password.
Important
If you already connected your clients and want to enable encryption retroactively, you must authenticate again for the encryption to be applied.
(optional) Define the proxy server between the on-prem client and the source system or between the on-prem client and the EMS:
Click Use proxy for communication.
Define the properties of your proxy connection:
protocol: http or https
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
Click Save.
This will automatically ensure that your connection will use the proxy for communication.
Click Connect to EMS to generate the Verification URL.
Note
The AppKeys will be stored locally on your machine. We recommend that you additionally encrypt the AppKey in the Encryption Settings.
Copy the Verification URL.
You'll have to paste the Verification URL into your browser to verify the installation in the next stage.
(Optional) Connect to SAP. This step is only required when automating in SAP. For more information, see Connecting to SAP.
Procedure:
Go to the Verification URL.
Log in to EMS.
Review the request and select the required permissions.
Click Authorize.
Newly created clients will also now be visible in the On-prem clients overview page under Admin & Settings > On-prem clients.
What’s next
Create a Data Connection to connect to a specific source system and extract data from it into the EMS. For more information see, Data Connections.
If you want to start creating automations for your on-prem application, create a link between EMS and your on-prem system. See Creating on-prem connections.