IT architecture overview for Automation
IT Architecture Overview
Enterprises have on-premises applications and databases that are deployed within their corporate data center. These applications are typically not easily accessible to cloud services like Celonis Execution Management System (EMS).
With the Celonis on-prem Agent companies can let Celonis execute predefined actions in their on-premise applications.
The Celonis on-prem Agent provides a secure way for Celonis to selectively access customer-authorized on-premises applications without having to open ports in the corporate firewall.
Deep-dive IT architecture for Automation
One Agent can connect to arbitrary many on-premise applications that are located in the same network. The Agent can run centrally or locally (we recommend the installation on a central server).
We provide out-of-the-box connections to the most common on-prem applications, such as SAP. In addition, we provide a generic HTTP on-prem app that allows connecting with other custom on-pem systems assuming that they provide an API or web service.
See the image below to view the detailed communication flow between Agent and EMS:
Best practices for on-prem setup
Where should the Agent be installed?
We recommend installing the Agent on a central server, typically the same server as used for the Celonis Extractors.
How many Agents do I need?
One Agent can connect to arbitrary many on-premise applications that are located in the same network. For example, one Agent can connect both to SAP and HTTP.
We recommend distinguishing between QA/ sandbox and production. An exemplary setup could look as follows:
EMS QA team - One Agent to connect to all QA systems
EMS productive team - One Agent to connect to all productive systems