doc.overops.com

On-Premises Installation

Prerequisites

Verify that you have a JDK installed before beginning this installation. Refer to the Software and Hardware Compatibility for additional requirements.

Note:

The default user created upon new installation is: default.user@company.com; this user is the owner of the default key: S1.

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

Please ensure you have

  • At least 16384 processes (ulimit -u)
  • At least 32768 files (ulimit -n)

Installing the Server

To install the server:

  1. Access the server: via Terminal, log in to the designated On-Premises server.
  2. Download the OverOps binaries: 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. Configure the database.

4.1 If using the internal database (default)
From the terminal, run setup:
/opt/takipi-server/bin/takipi-server.sh start -u <HOSTNAME>

4.2 If using an external DB
4.2.1 Create DB user, databases and grant privileges

4.2.2 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:

--db-ssl       to enable
--no-db-ssl    to disable

For MySQL

Ensure the following variables are properly configured in MySQL

max_connections - at least 500 (default is 150)
wait_timeout - at least 1200 seconds (default is 28000)

MySql - Running your server not on UTC timecode

There are several issues related to timezone set to other than UTC.
The prevent this issues from happening we strongly recommend that the server on which MySql is running runs on UTC timezone.

Examples:

  • Known issue with PDT timezone
  • timezones with duplicate entries
    • IST - India
    • IST - Israel
    • IST - Ireland
  • etc.

Oracle - Running your server or Oracle DB not on UTC timecode

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

Oracle

<TAKIPI-SERVER-HOME>/bin/takipi-server.sh start -u <HOSTNAME> 
   --db-type oracle 
   --db-url <oracle host>:1521" 
   --db-user <db username for Oracle> 
   --db-password <db user password>

MySQL

<TAKIPI-SERVER-HOME>/bin/takipi-server.sh start -u <HOSTNAME>
   --db-type mysql
   --db-url <JDBC-URL_OF_MYSQL_SERVER>
   --db-user <db username for MySQL>
   --db-password <db user password>
   --no-db-ssl

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

Activating 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.
    Please contact Overops support with
    • Your company name
    • Your name and email address
    • the License ID shown
      to receive your license code

OverOps returns the license key to the provided email address.

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

Installing the Collector

OverOps can be installed either with local or remote Collectors.
We recommend as the default installation the Remote Collector configuration but it might vary based on your unique requirements.

Remote Collector Installation

Linux

On-Premises Remote Collector Installation

Windows

Windows Remote Collector Install

Remote Collector Install - takipi.backend.url

For On-Premises deployments ensure that the
takipi.backend.url property points to your On-Premises Host and NOT to https://backend.takipi.com/
Read more about Collector properties here.

Installing the Rootless Collector

On-Premises Rootless Collector Installation

Local Collector Install - takipi.backend.url

For On-Premises deployments ensure that the
takipi.backend.url property points to your On-Premises Host and NOT to https://backend.takipi.com/

Optional: High-Availability and Load Balancing

Collector High Availability and Load Balancing

OverOps supports multiple Collectors that can be configured for high-availability and/or for load balancing. For high-availability, traffic is routed as round-robin according to the master endpoint configuration, as described in Configuring Collector High-Availability

For load balancing, routing depends on the load-balancer policy settings.
To build a Load Balancer using Nginx for multiple Collectors follow these instructions:
Load Balancing with Nginx

Agent Installation

Linux

On-Premises Rootless Agent Installation

Windows

You need access to the Internet for downloading the Windows Binaries or have them download prior to installation.

Windows Micro-Agent Installation

Attach a Micro-Agent

Attach a Micro-Agent

Advanced Configuration Tasks

On-Premises Advanced Tasks

Advanced - Command Line Arguments

On-Premises Advanced - Command Line Arguments

On-Premises Installation


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.