Overview

System Requirements

Axon.ivy Engine 10.0.3

See: Axon.ivy 10.0.3 System requirements

When Axon.ivy is installed on its own server:

• Java
  • Minimum: Java SE 17
• Memory (RAM)
  • Minimum: 8 GB
  • Recommended: 32 GB
    Depends highly on deployed applications and number of concurrent users
• Hard Disk:
  • Minimum: 20 GB
  • Recommended: 100 GB Solid State Disk (SSD) Disk
    Product installation and data of your projects
• Processor:
  • Minimum: 4 cores with 2 GHz
  • Recommended: 16 cores with 2.5 GHz
    Depends highly on deployed applications and number of concurrent users
• Operating Systems:
  • Windows: Windows Server 2022, 2019 and 2012 R2
  • Linux: Linux x64 (tested on Ubuntu 22.04)
• Database:
  • Microsoft SQL Server:
    • Supported: 2014, 2016, 2017, 2019, 2022
    • Tested: 2017, 2022
  • Oracle:
    • Supported: 19c
    • Tested: 19c, 21c
• Web Browser:
  • Firefox
  • Chrome
  • Safari
  • Opera
  • Microsoft Edge

NOTE: If Axon.ivy will be installed on the same server as inPoint is running, check the inPoint Server System Requirements and add the Recommended values for the Axon.ivy Engine to it!

Axon.ivy

Homepage: AXON Ivy

For Developers: DEV AXON Ivy

Axon.ivy is a Digital Business Platform that simplifies and automates the interaction of humans with their digital systems. The platform is typically in charge of the most precious business cases where companies produce value. Here is how we do it: What is Axon.ivy

Axon.ivy is a partner from us. We are building Workflows with their system and integrated it in inPoint.

Definition of some important words

See: Concepts Axon.ivy 10.0.3 Designer Guide

Workflow Axon.ivy Case and Task definition:
The ivy workflow manages the execution of process instances. A process instance is represented trough one Case and one or multiple Tasks. The Case exists from the first process step until the last process step and holds information of a process instance. When the Case gets finished even the process gets finished and backwards. A Case is processed though Tasks. Each Task defines an unit of work, which has to be done as one working step. Therefore a Task is assigned to a user or role which executes Task. A Task starts by a process-start element or a task-switch element and ends by the next task-switch element or an process-end element.
See: Workflow Case and Task

• Workflow: A workflow can be made of several processes.
• Process: A process can be made of several tasks.
• Task: A task can be assigned to a user or a role.
• Case: A case is a workflow run.
• Category or Process Category: Each task can be assigned to a category (process category).