A minimal setup of a productive Axon Ivy Engine environment only requires the Axon Ivy Engine itself and a database management system to hold the system database. But to increase security, performance and reliability, other services must be additionally installed and integrated.

digraph overview {
  browser [ label="Browser", pos = "0,2.5!", width=1];

  frontendServers [ label="Reverse Proxy",pos = "2.25,2.5!" width=1.8 height=3.1 style="dotted" fontcolor="black" labelloc="t"];
  frontendNginx [ label="NGINX",pos = "2.25,3.4!" width=1.25 height=0.5];
  frontendApache [ label="Apache",pos = "2.25,2.8!" width=1.25 height=0.5];
  frontendIIS [ label="IIS",pos = "2.25,2.2!" width=1.25 height=0.5];
  frontendWAF [ label="WAF",pos = "2.25,1.6!" width=1.25 height=0.5];
  engine [label="Axon Ivy\nEngine", pos="5.4,2.5!", height="1", width="1.5", color="#C7D426", fontcolor="black"];
  userManagement [ label="User Management (optional)",pos = "5.4,0.7!" width=3 height=1.4 style="dotted" fontcolor="black" labelloc="t"];
  eDirectory [ label="eDirectory", width="1.1" pos="4.75,0.6!"];
  activeDirectory [ label="Active\nDirectory", width="1.1" pos="6,0.6!"];

  systemdb [ label="System Database", pos="8,2.5!" width=1.7 height=3.5 style="dotted" fontcolor="black" labelloc="t"]
  postgres [ label="PostgreSQL", pos="8,3.5!" width=1 height=0.5]
  mysql [ label="MySQL", pos="8,2.9!" width=1 height=0.5]
  mariadb [ label="MariaDB", pos="8,2.3!" width=1 height=0.5]
  mssql [ label="Sql Server", pos="8,1.7!" width=1 height=0.5]
  oracle [ label="Oracle", pos="8,1.1!" width=1 height=0.5]

  elasticsearch [ label="External\n Elasticsearch\n (optional)", pos="5.4,4.25!" width=1.5]

  browser -> frontendServers [ label="HTTPS"];
  frontendServers -> engine [ label="HTTP\nHTTPS" ];
  engine -> userManagement [ label="LDAP" ];
  engine -> systemdb [ label="JDBC" ];
  engine -> elasticsearch [label="HTTP\nHTTPS"];

  • Reverse Proxy: To increase security users should always access the Axon Ivy Engine over an reverse proxy like NGINX, Apache HTTP, Microsoft IIS or any other reverse proxy product.

  • User Management: Users can be imported from an external user management system like Microsoft Active Directory or Novell eDirectory.

  • Cluster: For scalability, to increase performance and provide high availability its possible to run the Axon Ivy Engine in a cluster.

  • Elasticsearch: An Elasticsearch server is bundled with the Axon Ivy Engine. For high traffic systems it may make sense to install the Elasticsearch Server on a dedicated node.

  • System Database: The Axon Ivy Engine needs a database management system to store its workflow data. The database in which the engine stores the data is called system database.