Container technology empowers you to pull up reproducible, documented and complete isolated infrastructures. Axon Ivy fully supports container environments such as Docker, Kubernetes or OpenShift. You can easily customize the configuration of an Axon Ivy Engine by using system environment variables or by providing configuration files like the ivy.yaml file.
The following example will override the URL of the system database configuration using environment variables:
docker run -e "IVY_SYSTEMDB_URL=jdbc:mysql://db:3306/AxonIvySystemDatabase" ...
Instead of using environment variables, you can simply provide an ivy.yaml file.
1# ivy.yaml 2SystemDb: 3 Url: jdbc:mysql://db:3306/AxonIvySystemDatabase
And let’s run the container with this configuration
docker run -v $(pwd)/ivy.yaml:/etc/axonivy-engine/ivy.yaml ...
On Windows use
%cd%/ivy.yaml instead of
For further docker examples have a look at our docker-samples GitHub repository.
If you plan to run Axon Ivy Engine in Kubernetes have a look at our kubernetes-samples GitHub repository.
You can provide the license either by:
Packaging it as part of your docker image in the
ADD licence.lic /etc/axonivy-engine/licence.lic
Mapping it into the
docker run -v $(pwd)/licence.lic:/etc/axonivy-engine/licence.lic ...
Provide it as environment variable
export IVY_LICENCE=$(cat <licence.lic>) docker run -e IVY_LICENCE=$IVY_LICENCE ...
set IVY_LICENCE=[string](Get-Content -Path <licence.lic> -raw) docker run -e IVY_LICENCE=$IVY_LICENCE ...
Mapping it as docker secret into file
You can use Docker Secrets to store passwords. Simply create a file in
/run/secrets which has the same name as the configuration entry. For
example, to provide
SystemDb:Password as secret file you need to create