Installation Guide

This document describes the installation process of the Camunda Optimize distribution, as well as various configuration possibilities available after initial installation.

Before proceeding with the installation, please read the article about supported environments.


Before installing Optimize, make sure you have a JRE (Java Runtime Environment), or better, a JDK (Java Development Kit) installed. It is required to install Java version 8.

Download JDK 8

Demo Distribution with Elasticsearch

The Optimize Demo distribution comes with an Elasticsearch instance. The supplied Elasticsearch server is not customized or tuned by Camunda in any manner. It is intended to make the process of trying out Optimize as easy as possible. The only requirement in addition to the demo distribution itself is a running engine (ideally on localhost).

To install the demo distribution containing Elasticsearch, please download the archive with the latest version from the download page and extract it to the desired folder. After that, start Optimize by running the script on Linux and Mac


or optimize-demo.bat on Windows:


The script ensures that a local version of Elasticsearch is started and waits until it is up running. Then it starts Optimize, ensures it is running and opens automatically a tab in a browser to make it very convenient for you to try out Optimize.

Production Distribution without Elasticsearch

This distribution is intended to be used in production. To install it, first download the production archive, which contains all the required files to startup Camunda Optimize without Elasticsearch. After that configure the Elasticsearch connection to connect to your pre-installed Elasticsearch instance and configure the Camunda BPM Platform connection to connect Optimize to your running engine. You can then start your Optimize instance by running the script on Linux and Mac:


or optimize-startup.bat on Windows:



You can start using Optimize right away by opening the following URL in your browser: http://localhost:8090

Then you can use the users from the Camunda Platform to login to Optimize. For details on how to configure the user access, please consult the user access management section.

Before you can fully utilize all features of Optimize, you need to wait until all data has been imported. A green circle in the footer indicates, when the import is finished.


All distributions of Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named environment. There are two files, one called environment-config.yaml with values that override the default Optimize properties and another called environment-logback.xml, which sets the logging configuration.

You can see all supported values and read about logging configuration here.

Optimize Container Configuration

The following YAML Paths correspond to settings available in the environment configuration.

  • container.ports.http - A port number that is used by the embedded jetty server to process HTTP connections
Default value: `8090`
  • - You can configure a host either by host name or IP address, to identify a specific network interface on which to listen
Default value: ``

Elasticsearch configuration

You can customize the Elasticsearch connection settings used by Optimize by changing the following properties:

  • es.connection.clusterName - The name of the Elasticsearch cluster Optimize should connect with.
Default value: `elasticsearch`
  • Define one or more Elasticsearch nodes Optimize can connect to:

    • - The address/hostname under which the Elasticsearch node is available.
  Default value: `localhost`
  • es.connection.nodes.tcpPort - The port number used by the Elasticsearch node to accept TCP connections.
  Default value: `9300`
  • es.connection.nodes.httpPort - The port number used by the Elasticsearch node to accept HTTP connections.
  Default value: `9200`

Camunda BPM configuration

To perform an import and provide the full set of features, Optimize requires connection to the REST API of the Camunda engine, which can be configured using the following properties.

  • engines.\${engineAlias}.rest - A base URL that will be used for connections to the Camunda Engine REST API
Default value: `http://localhost:8080/engine-rest`
  • engines.\${engineAlias}.name - The name of the engine that will be used to import data
Default value: `default`

Import of the dataset

By default, Optimize comes without any data available. To start using all the features of the system, you have to perform a data import from the Camunda BPM Platform. This process is triggered automatically on start.

If you are interested in the details of the import, please refer to the dedicated import overview section.

Hardware Resources

According to the tests with different datasets described on import overview page we can recommend to carefully choose hardware resources that are allocated to the server with Optimize.

Heads Up!

Exact hardware requirements highly depend on a number of factors such as: size of the data, network speed, current load on the engine and its underlying database. Therefore we cannot guarantee that following requirements will exactly match every case.

We recommend following minimum hardware for data sets:

  • Small Size Of Data

    • 2 CPU Cores
    • 512MB RAM for Camunda Optimize
    • 2 GB RAM for Elasticsearch
  • Medium Size Of Data

    • 3 CPU Cores
    • 4GB RAM for Camunda Optimize
    • 3 GB RAM for Elasticsearch
  • Large Size Of Data

    • 4 CPU Cores
    • 8GB RAM for Camunda Optimize
    • 4 GB RAM for Elasticsearch

Please be aware, that Optimize is using data structures, that are different from data stored by engine in relational database. The final amount of space on the hard drive required by Optimize will depend on your replication settings, but as a rule of thumb you could expect Optimize to use 30% of the space that your relational database is using.

Recommended Additional Configurations

Adjust engine heap size

Sending huge process definition diagrams via Rest-API might cause the engine to crash, because of the limited heap size. Thus, it is recommended to increase the heap size of the engine to at least 2 gigabyte or preferably more, e.g., by adding the following java command line property when starting the engine:


On this Page: