Workflow, Inventory & Network Control
Switch branches/tags
Nothing to show
Clone or download
jrozsa Add skip option to
Skips healthchecks and error checks.

Signed-off-by: Jozef Rozsa <>
Latest commit a17bced Oct 16, 2018


The project is a containerized package of:

Documentation & Use Cases


  • Docker
  • Docker Compose
  • JDK 1.8
  • License for FRINX ODL (you can find a trial license in the "Installation Guide" section below)

min 16GB RAM & min 4 vCPUs with normal startup, and 5GB RAM & 2 vCPUs with minimal config has been successfully tested for POCs and demos.

Tested on

  • Ubuntu 16.04 / 18.04
  • docker 18.03.1-ce, v18.06.1-ce
  • docker-compose 1.21.2, v1.22.0

Installation Guide

Trial license

We offer a one month trial license. No signup needed! License token:


Get the project

Clone the repository:

git clone

Navigate into the project folder:

cd FRINX-machine


The installation script is in the FRINX-machine folder. What does installation do:

  • Updates project submodules
  • Copies license token.
  • Pulls conductor project parts from maven repository.
  • Builds conductor-server .jar file.
  • Pulls and creates docker images.
  • Creates external volumes for data persistence.

Docker needs privileged mode, so should be executed with sudo. Otherwise it will prompt for password while executing.

Installation with the trial license token:

sudo ./ -l 0e57a786f7dbd27fa77db684cf3b234d6f23ed784e52cbfb107fd4317ba2646c66f7a141b0e823946d8f9d956852c95d33dc82f945779b1c9969049e94935b2a


The startup script can be found in the FRINX-machine folder. Here is what it does:

  • Creates the docker containers from the images and starts them.
  • Imports workflow definitions.

Docker needs privileged mode, so should be executed with sudo. Otherwise it will prompt for password while executing.

sudo ./

Min 16GB RAM & min 4 vCPUs with normal startup are recommended.

Minimal startup
sudo ./ -m

Starts application with lower RAM usage. Min 5GB RAM & min 2 vCPUs with minimal startup are recommended.


The script in the FRINX-machine folder:

  • Stops and removes containers.
  • Does not remove external volumes.

Using docker, also needs privileged mode:

sudo ./teardown

Removal of external volumes

Caution all data will be lost!

To remove the external volumes use:

sudo docker volume rm redis_data elastic_data

Docker expects external volumes to exist when starting the containers. They can be created with:

sudo docker volume create --name=redis_data
sudo docker volume create --name=elastic_data


Once started open your browser and open the following GUIs:

  • host:5000 --> FRINX workflow GUI
  • host:5601 --> Kibana (for log and inventory access)
  • host:8888 --> FRINXit (CLI for FRINX ODL)

Exposed ports

  • Conductor-server:

    • host:8080
    • host:8000
  • Conductor-ui:

    • host:5000
  • ODL:

    • host:8181
  • Frinxit:

    • host:8888
  • Microservices:

    • host:6000
  • Elasticsearch:

    • host:9200
    • host:9300
  • Kibana:

    • host:5601