5. Configure the Engine (Linux)

Now, let’s configure the Axon Ivy Engine with a license and a system database.

First, you have to provide a valid Axon Ivy Engine license. Please refer to Licensing your Engine.

If you do not have a license at this time, skip this section and continue with the next section. Your Axon Ivy Engine will run in Demo Mode.

Besides the license, you need

  • to have a supported SQL database management system server up and running

  • a database user who has the rights to create new databases and execute data definition language (DDL), as well as data manipulation language (DML) statements. The configuration and creation of the system database differ depending on the database system you use. In the following chapters, we will use a PostgreSQL database server.

Important

We support that a DBA creates the database before you start the engine configuration. However, we do not support the external creation or migration of the database structure.

We require DDL permissions during installation and migrations. In normal operations, the database user provided to the engine needs DML permissions only.

There are multiple ways to configure the engine:

  • Using the Engine Cockpit Setup Wizard or Migration Wizard

    This is the most convenient way to configure the engine if this is a one-of-a-kind installation. Please refer to Setup Wizard or Migration Wizard for details.

  • Manually

    See below.

  • Scripted

    If you have several environments and want to set them up in a standardized way, your best option is to automate the manual steps using scripts. We do not provide a script template because there are too many ways to supply licenses, database user credentials, and other data.

5.1. Manual Setup

Shutdown the Axon Ivy Engine first by typing shutdown:

...
Go to http://ivy1:8080/ to see the info page of Axon Ivy Engine.
Axon Ivy Engine is running and ready to serve. [11596ms]
Type 'shutdown' and confirm with ENTER to stop the running engine instance
...

shutdown

...
Stopping Axon Ivy Engine ...
[  0%] Stopping Server
...

Let’s install the license. Copy the license file *.lic into folder configuration.

cp ~/licence.lic /opt/ivy/engine/configuration

To configure the system database, use the config-db command of the EngineConfigCli tool. Replace yourdatabaseserver with the hostname of the server running your DBMS system. Replace dbuser and password with the credentials of a database user with the permissions to create a new database and its structures (i.e., DDL permissions) on the database server.

./EngineConfigCli config-db org.postgresql.Driver \
jdbc:postgresql://yourdatabaseserver:5432/AxonIvySystemDatabase \
dbuser password

Now, let’s create the system database with the create-db command.

./EngineConfigCli create-db

Note

The Axon Ivy Engine uses the system database to store master data like users, user attributes, roles, etc. as well as runtime data like applications, process models, process model versions, cases, tasks, and process data.

Next, define an Axon Ivy Engine administrator by modifying ivy.yaml in directory /opt/ivy/engine/configuration/ as detailed below:

1# sample ivy.yaml which defines a single administrative account:
2Administrators:
3  admin:
4    Password: 1234
5    Email: sudo@acme.com

Note

Administrators manage the Axon Ivy Engine. For example, they add or remove users, assign users to roles, enable, disable and deploy applications, etc. You need at least one administrator to manage the Axon Ivy Engine. In case of license problems, the Axon Ivy Engine sends mail notifications to the administrators.

Note

The Axon Ivy Engine internal web server provides connectors for the following protocols:

  • The HTTP Protocol is used by web browsers to communicate with a web server. This protocol is not secure since the communication is not encrypted. Axon Ivy Engine uses port 8080 for HTTP by default.

  • HTTPS is like HTTP, but secure. It uses TLS to encrypt all communication between the web browser and server. Axon Ivy Engine uses port 8443 for HTTPS by default.

Have a look at the ivy.yaml to see how you can adjust parts of the web server and its connectors to your needs.

Now, start the Axon Ivy Engine again as a background process.

nohup ./AxonIvyEngine &

Note

If you have changed the HTTP Settings, the HTTP port of the Axon Ivy Engine may have changed!

Open a web browser and navigate to http://yourservername:yourportnumber/. As you see, the header with the demo mode message is gone. You now have a production-ready Axon Ivy Engine.