Getting Started

Here you will learn how to install and configure an Axon Ivy Engine and ultimately how to bring your process to life by deploying your Axon Ivy projects. You will see that a minimal setup of an Axon Ivy Engine is straightforward. Next to the Axon Ivy Engine itself you only need a browser of your choice (e.g. Firefox) and a database management system (e.g. Postgres) for storing the data of the Axon Ivy Engine.

digraph overview {
  browser [ label="Browser", pos = "0,2.5!", width="1.3"];
  engine [label="Axon Ivy\nEngine", pos="3,2.5!", width="1.3", color="#C7D426", fontcolor="black"];
  systemdb [ label="System\nDatabase", pos="6,2.5!" width="1.3"]
  browser -> engine [ label="HTTP"];
  engine -> systemdb [ label="JDBC" ];

But first you have to choose a platform. The Axon Ivy Engine runs on all modern runtime environments:

  • Debian We provide a debian package for debian based Linux system like Ubuntu or Linux Mint. Next to great install capabilities, this package offers great support for later upgrades of the Axon Ivy Engine.

  • Docker The Axon Ivy Engine is provided as a docker image. This allows you to run the Axon Ivy Engine in a simple docker-compose setup or in container orchestration platforms like Kubernetes or Openshift. This package provides maximum installation, configuration and upgrade support.

  • Windows Windows is set as the operating system in many places. Compared to the Debian and Docker, more effort is required for installation and subsequent upgrades.

  • Linux If you are on a Linux system which is not Debian based then you will need to choose this one. Compared to the Debian package you will miss the great install and upgrade capabilities, which will need more work by you.

Productive Setup

To run an Axon Ivy Engine in production, you must order a license for the Axon Ivy Engine and install the Axon Ivy Engine on a system that fulfils the system requirements.

You should also be aware of all integration possibilities. For example:

  • We always highly recommend for security reasons the use of a reverse proxy.

  • Users can be managed in an external user management system to minimize the administration effort.

  • For high availability, performance and scalability the Axon Ivy Engine can be clustered.