Introduction

OverOps provides RPM installers for the Analysis Server, Collector and Java Micro-Agent.

❗️

Root Permissions Required

Installing with RPM requires root permissions (sudo) - without these user permissions, you won't be able to use the RPM installer.

Step 1: Verify the Required Resources

Before running the installation with the RPM installer, verify that your system has the required resources in place.

###Supported Operating Systems
The RPM Installer works with RedHat and Centos Linux operating systems. For Debian and Ubunto systems, see Install a CR Server Using the Deb Installer.

Step 2: Create a Provisioning File

1. When installing the server with RPM, you'll first need to create a provisioning file that contains the available variables
   If this file doesn't exist, you'll receive a warning notification, and the installation will be performed using the default values instead.
2. The path of the file varies depending on the operating system you use:

• Redhat, Centos - /etc/sysconfig/takipi-server
• Others - /etc/default/takipi-server

3. You can also change this path using the TAKIPI_INSTALL_CONFIG_FILE environment variable. This variable lets you change the location where OverOps should look for the provisioning file.

Here's an example of a provisioning file that contains all the available variables (note that all the variables of the file can be found in the --help file, which is documented in Command Line Arguments for On-Premises Servers.

#############################
# EXAMPLE PROVISIONING FILE #
#############################
#
export TAKIPI_HOST_URL=
#
# Should point to the takipi server address or a load balancer address.
# example:
# export TAKIPI_HOST_URL=http://mydomain.com:8080/
# If no host URL is provided the default will be 127.0.0.1
#
#
export TAKIPI_DB_TYPE=
export TAKIPI_DB_URL=
export TAKIPI_DB_USERNAME=
export TAKIPI_DB_PASSWORD=
#
# Or leave empty to use an embedded H2 database
#
#
export TAKIPI_USER_NAME=
export TAKIPI_USER_GROUP=
#
# Or leave empty to use the /opt/takipi-server owner instead
#
# example
# export TAKIPI_USER_NAME=UserName
# export TAKIPI_USER_GROUP=GroupName
#
#
export TAKIPI_STORAGE_FOLDER=
export TAKIPI_LOG_FOLDER=
export TAKIPI_TEMP_FOLDER=
#
# Or leave empty to use the default directories under /opt/takipi-server
# Example
# export TAKIPI_STORAGE_FOLDER=/opt/storage
# export TAKIPI_LOG_FOLDER=/var/log/takipi-server
# export TAKIPI_TEMP_FOLDER=/tmp/takipi-server
#
#
export TAKIPI_SERVER_PORT=
#
# Or leave empty to use the default port = 8080
#
#
export TAKIPI_VALIDATE_SUCCESS=
#
# Tell the init system (systemd e.g.) to wait until a successful initialization
#	Note that this may slow the startup time, therefore use only when appropriate - the default is     # false
#
#
export TAKIPI_REDIS_NODES=
export TAKIPI_REDIS_TYPE=
#
# For cluster installation, put redis configuration here
#  Redis cluster type (SINGLE, CLUSTER, ELASTICACHE or MASTER_SLAVE)
#		Default to SINGLE
# Redis nodes may be separated by semicolon (;)
#	export TAKIPI_REDIS_NODES=node1:port;node2:port

User and Group Parameters

The following parameters let you install run the server installation as a user or group.

Using the user/group parameters affects the permissions of files under /opt/takipi-server, since the
Systemd Linux Service Manager daemon runs the process with this user/group.

Installing the Server with RPM

1. Verify that you have a provisioning file like the one above. The default location for this file is: /etc/sysconfig/takipi-server.
2. Get the download link from OverOps, and then download the rpm file
3. Install the Server either via
   a. sudo rpm -i
   b. sudo yum install
4. Run sudo systemctl status takipi-server to verify that the daemon is running.

🚧

Important

When uninstalling the takipi-server via RPM, the system doesn't remove files that were created after the installation phase by default. This includes files such as configuration files, logging files, storage files, temp files, etc.

Installation configuration and work data are kept and can be used for re-installation/upgrade if needed, or manually deleted after the removal of the package.

Related Articles

Installing the Collector and Java Micro-Agent Using the RPM Software Package
Systemd Linux Service Manager