Introduction

OverOps has implemented the Systemd Linux Service Manager, a suite of basic building blocks for a Linux system, into the OverOps solution. Sysdemd is the most widely-used service manager, supporting the latest operating system versions

🚧

Important

OverOps doesn't support the Linux Service Manager sysv or upstart, two technologies for managing daemons in On-Premises deployments. This means that when you use ./takipi-server.sh install... only the Systemd will work.

Using Systemd in On-Premises Installations

Choose from one of these options and follow the installation steps:
Install OverOps Using the RPM Installer
Install OverOps Using the Deb Installer

Installation Parameters

As part of the RPM and Deb installations, you'll need to use specific parameters, which are taken from the RPM and Deb provisioning files.

The parameters in these files are can be found in the Command Line Arguments for On-Premises Servers.

Installing the CR Server Using the install Flag

In addition to the stop and start flags, the CR Server run script also supports an install flag, which installs the CR Server as a daemon. This is unlike when you use the start flag, which installs the CR Server as a user process. The daemon runs under Systemd, which works on most new operating systems.

👍

Best Practice: Why and When Should You Use the Systemd Daemon?

OverOps recommends using the systemd daemon to obtain the following benefits:

• Automatic restart in case of failures
• Automatic start after reboot
• Easy and standard management for the service

in addition, when running with systemd - OverOps doesn't use the java-forever.jar and instead trusts systemd to respawn in case of errors.

We recommend using the install phase before the first run of the On-Premises server, otherwise you'll need to remove the directories /opt/takipi-server/log /opt/takipi-server/temp and /opt/takipi-server/storage first.