Getting Started
In this chapter, we help you to get up to speed with the Axon Ivy Engine with minimal effort. For productive use, the resulting configuration has to be updated later on; see Non-Demo Setup below.
You will learn how to install and configure an Axon Ivy Engine and, ultimately, how to bring your processes to life by deploying your Axon Ivy projects. As you will see, a minimal setup of an Axon Ivy Engine is straightforward. Next to the Axon Ivy Engine, you only need a browser of your choice (e.g., Firefox) and a database management system (e.g., PostgreSQL) for storing the data of the Axon Ivy Engine.
An Axon Ivy Engine ready to serve your applications includes these components:
Choose your Platform
At this point, you need to choose a server platform. The Axon Ivy Engine runs on all modern runtime environments. If you already know what you want, simply click on the corresponding link below. If not, read the short descriptions below and select thereafter.
Docker Image
We provide the Axon Ivy Engine as a Docker image. You can run the Axon Ivy Engine in a simple docker-compose setup or in orchestration platforms like Kubernetes or Openshift. This package provides optimal installation, configuration, and upgrade support.
For details, refer to Docker Image.
Debian
We provide a Debian package for Debian-based Linux systems like Ubuntu or Linux Mint. Besides the install capabilities, this package offers excellent support for later upgrades of the Axon Ivy Engine.
For details, refer to Debian Linux.
Linux
If you use a non-Debian-based Linux system, choose this option. Compared to the Debian package, you will miss the install and upgrade capabilities. Compared to Debian and Docker, more effort is required to install and subsequently, upgrade the Axon Ivy Engine.
For details, refer to Linux.
Windows
Windows is the operating system of choice in many places. Compared to Debian and Docker, more effort is required to install and later on upgrade the Axon Ivy Engine.
For details, refer to Windows.
Non-Demo Setup
Out of the box, the Axon Ivy Engine runs in Demo mode without a license. In this mode, it uses an in-memory, non-persistent database.
To run an Axon Ivy Engine in non-Demo mode (i.e., for development, integration, test/acceptance and production environments), you have to order a license for the Axon Ivy Engine and install the Axon Ivy Engine on a system that fulfills the system requirements.
Have a look at the integration capabilities of the Axon Ivy Engine! For example:
For security reasons, we highly recommend employing a reverse proxy.
You can synchronize your users from an external Identity Provider like Active Directory or Azure AD to minimize and centralize the administration effort.
For high availability, performance and scalability, you can cluster the Axon Ivy Engine and use a separate Elasticsearch server or cluster.