DocumentationAPICommunitySupportLog In

# Local Server Installation

## Prerequisites

Before beginning the installation, please refer to the [OverOps Installation Prerequisites](🔗).


The server is installed under /opt/takipi-server and should have at least **200 GB** of free disk space.


Please make sure you have:

  • At least 16384 processes (`ulimit -u`)

  • At least 32768 files (`ulimit -n`)

Default User

The default user created upon a new installation is: [email protected]; this user is the owner of the default key S1.

## Install the CR Server

  1. Via Terminal, log in to the designated On-Premises server.

  2. From the link provided by OverOps, download the latest OverOps server tarball: `takipi-server-java.tar.gz.`

  3. Extract files to the /opt directory: `tar -xvf <Path_to_tar_file> -C /opt`

  4. Next, configure the database as follows:

Embedded database should be used for evaluation purposes only!

The embedded database coming with OverOps will not scale! There is no support for migrating your data out of it into a different database engine.

4.1 If you're using the embedded database (the default), from the Terminal, run setup: `/opt/takipi-server/bin/ start -u <HOSTNAME>`. 4.2 If you're using an external database, [create a database user, databases and grant privileges](🔗). 4.3 From the terminal, start the server.

MySQL SSL Data Connections

Data connections to MySQL via SSL are disabled by default. To disable data connections via SSL add the `--no-db-ssl` startup argument flag. This will update the configuration file and make SSL disabled persistent for future server restarts. To enable SSL use the `-db-ssl` flag to turn SSL on.

The options:


Ensure the following variables are properly configured in MySQL

MySQL- Running the CR Server on a Non-UTC Timezone

There are several issues related to timezones that are set to other than UTC (see list below). To prevent these issues from happening we strongly recommend that the server on which MySQL is running runs on a UTC timezone.


  • Known issue with the PDT timezone

  • timezones with duplicate entries, such as:

  • IST - India

  • IST - Israel

  • IST - Ireland.

Oracle - Running the CR Server or Oracle Database on a Non-UTC Timezone

There are several issues related to timezones set to other than UTC. To prevent these issues from happening, we strongly recommend that the server on which Oracle is running and Oracle itself are set to the UTC timezone.

Oracle - Partioning

OverOps requires that Partitioning on the Oracle instance is active. At the time of the writing, Partitioning was only available with Oracle Enterprise Edition.

Best Practice - If using an external DB always run the CR Server with GMT/UTC Timezone

To prevent issues related to properly displaying metrics with OverOps we recommend that whenever using an external DB that the CR Server will be configured to run in GMT Timezone at all times.

To properly apply this configuration, for new installations, there are 2 options:

  1. If you downloaded and want to use the OverOps Server tarball and you didn't install yet, you'll need to edit the following file located at: bin/init-files/takipi-server.init-systemd. Look for the following run line: [email protected][email protected]/bin/ start --skip-resource-validation --no-forever @[email protected] and add the flag "-Duser.timezone=GMT". After adding the flag the line will look like: [email protected][email protected]/bin/ start --catalina-opts -Duser.timezone=GMT --skip-resource-validation --no-forever @[email protected]

  2. If you already ran 'install', your CR Server will be started by the systemd process. You'll need to edit the following file locate at: /lib/systemd/system/takipi-server.init-systemd. Look for the line with "ExecStart" and add "--catalina-opts -Duser.timezone=GMT" after "start".

## Starting Oracle

## Starting MySQL

For a complete list of options for takipi-server type: `/opt/takipi-server/bin/ --help`

## Activate OverOps

To activate OverOps:

  1. From the browser go to `http://<HOSTNAME>:8080/activate` and follow the instructions.

  2. Send the License ID to OverOps [Support](🔗) with the following information:

  • Your company name

  • Your name and email address

  • The License ID shown to receive your license code

OverOps will return the license key to the email provide.

Only customers with a valid and active subscription are eligible for license codes!