Celonis Configuration Store Setup Guide 1.6
Celonis Configuration Store Setup Guide 1.6
Celonis Configuration Store Setup Guide 1.6
Version 1.6
This document is copyright of the Celonis SE. Distribution or reproduction are only permitted
by written approval of the Celonis SE. Usage only permitted, if a valid software license is
available.
TABLE OF CONTENTS
Celonis is a powerful software for retrieving, visualizing and analyzing real as-is business processes
from transactional data based on event information. It provides users with the possibility to create and
share comprehensive process analyses giving them full transparency about the business processes at
hand.
This guide describes the setup of the Celonis Configuration Store. This can either be a new setup or a
migration from the internally used HyperSQL (HSQL) database to an external database system such as
PostgreSQL or Microsoft SQL Server (MSSQL). The Celonis Configuration Store is the central storage of
the application metadata, e.g. system settings, users, groups, definitions of analyses and data models
and contains all configuration done via the web frontend. The actual data to be analyzed resides in the
underlying database and is never part of the Celonis Configuration Store.
TARGET AUDIENCE
• System Administrators
• Technical Staff
ABBREVIATION EXPLANATION
DB Database
HSQL HyperSQL
Celonis supports the following database systems for the Celonis Configuration Store:
The installation of these database system is out of the scope of this guide. We recommend installing
the database system locally on the Celonis application server.
It is expected that the database system is already installed on the Celonis application server. The user
that is used by the Celonis application must have the following permissions:
• PostgreSQL: superuser
• MSSQL: database owner
We recommend using the database system exclusively for the Celonis Configuration Store data.
Validate if the drivers for external database systems are present in the application data folder.
Please note, when an external database system is used as Celonis Configuration Store, there are no
backups created automatically. The customer is responsible to back up the database files of the Celonis
Configuration Store.
For migrating an existing Celonis Configuration Store (powered by HSQLDB), please follow all steps
below.
For setup of a new Celonis Configuration Store (in a new installation), please only follow steps 1 and 3
to 5 as indicated below.
Windows
Linux
sudo sh stop.sh
Validate if the Celonis service terminated successfully in the process explorer overview. If the service
does not terminate after several minutes, terminate the service directly.
• The HSQL files are in "appfiles" (Windows) / “root” (Linux) folder of the Celonis installation
directory and consist of the following four files (do not select the appdata.lck file).
o appdata.lobs
o appdata.log
o appdata.properties
o appdata.script
• Zip these four files into a zip file (e.g. 7-Zip) name it properly and move the created zip-file into
your backup folder.
• Copy the file "config-custom.properties”, located in the Celonis installation directory, to your
backup folder and rename it "config-customer.properties.backup_YYYYMMDD" by replacing
the placeholder YYYYMMDD with the current date (YYYY – year, MM – month, DD – day).
STEP 2b: CREATE MIGRATION FOLDER AND COPY THE CONFIGURATION STORE
• Create the folder "migration" within the "appfiles" (Windows) / “root” (Linux) folder.
• Copy the HSQL database files into the folder "migration" excluding the “appdata.lck” file. The
files are in the "appfiles" (Windows) / “root” (Linux) folder of the Celonis installation directory
(for details see STEP 2 (MIGRATION ONLY): PREPARE MIGRATION
• STEP 2a: BACKUP THE CONFIGURATION STORE AND CONFIGURATION).
• Do not copy the appdata.lck file as it locks the HSQL database and the migrator tool cannot
establish a connection. If you copied it, delete it.
STEP 2c: COPY THE MIGRATOR TOOL INTO THE MIGRATION FOLDER
Please note, we recommend selecting the location of the database files in accordance to your backup
strategy.
The following fields must be activated in the “config-custom.properties” file, which is located in the
Celonis installation directory (see Table 2).
database.driverClassName=org.postgresql.Driver
database.url=jdbc:postgresql://localhost:<port>/celonis_configuration_store
PostgreSQL database.username=celonis_configuration_store_user
database.password=<password>
database.dialect=de.celonis.pm.utils.engine.CPMPostgresDialect
database.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
database.url=
jdbc:sqlserver://localhost:<port>/databaseName=celonis_configuration_store
MSSQL
database.username=celonis_configuration_store_user
database.password=<password>
database.dialect=org.hibernate.dialect.SQLServerDialect
Table 2: Configuration settings for the connection to the external database system.
Please note, the restart of the application is mandatory as the application server needs to create the
required tables in the external database system. The migration tool only copies the tables from the
file-based HSQL database into the new database system.
• Start the Celonis service and login as system administrator. You should only be able to login
with system administrator account using the default password, as no application data is
available yet. The default password is stored in the “config.properties” file within the Celonis
installation directory.
• You should not see any projects or analysis.
• In any other case the configuration of the new database system was not successful.
Troubleshooting
• Execute the migration tool from the folder “migration” (see STEP 2B: CREATE MIGRATION
FOLDER AND COPY THE CONFIGURATION STORE) using the command in Table 3.
java -jar celonis_configuration_store_migrator_v1-6.jar "hsql-pg"
"jdbc:hsqldb:file:<HSQL_files_location>/appdata"
PostgreSQL
"jdbc:postgresql://localhost:<port>/celonis_configuration_store"
"celonis_configuration_store_user" "<password>"
Figure 1 shows a successful example output of the migration tool, where the migrated tables are listed.
If the output is different, the migration tool is configured incorrectly.
Troubleshooting
• The location to the Celonis Configuration Store (HSQL file location) must contain the name of
the file-based database files, which is "appdata" by default.
• Check if you deleted the “appdata.lck” file, which locks the HSQL database files.
• Check if the port of the database connection is valid.
• Validate the username and password of the database system.
• Are the tables in the target database system already created? If not, go to STEP 5: START THE
CELONIS SERVICE AND VALIDATE THE SETUP.
STEP 6c: RESTART THE CELONIS SERVICE AND VALIDATE THE MIGRATION