OpManager Standard/ Professional Installation

Installing OpManager on Windows

Steps to install

Step 1: Download OpManager for Windows.

Step 2: Execute the downloaded "ManageEngine_OpManager_64bit.exe" file to install and follow the instructions in the installation wizard.

Step 3: Click 'Next' to start the installation process. Go through the license agreement and click 'Yes' to proceed to the next step.

Step 4: Choose the directory where you wish to install OpManager in the subsequent steps of the wizard.

Step 5: Specify the port number to run OpManager Web Server (OpManager uses 8060 as the default web server port) and click 'Next'.

Step 6: Register for technical support by providing your contact information such as Name, E-mail ID, etc., and click 'Next'.

Step 7: OpManager is bundled with PostgreSQL by default. However, it also supports MSSQL databases. Choose the desired database option and click 'Next'.

Step 8: Click 'Finish' to complete the installation process.

Installing OpManager on Linux

Steps to install

  1. Download OpManager for Linux.
  2. Login as root user.
  3. Assign the executable permission to the downloaded file using the following command:

    chmod a+x ManageEngine_OpManager_64bit.bin

  4. Execute ./ManageEngine_OpManager_64bit.bin with administrator privileges (sudo). This will display the installation wizard.
  5. Click 'Next' to begin the installation process. Go through the license agreement and proceed to the next step.
  6. In the subsequent steps of the wizard, select the OpManager Edition, the directory to install OpManager, and the port number to run OpManager Web Server. Proceed to the next step.
  7. Verify the installation details and click 'Next'.
  8. Click 'Finish' to complete the installation process.

It is recommended to install OpManager in the opt folder. By default, OpManager is installed in the /opt/ManageEngine/OpManager directory.

Troubleshooting steps:

  • Sometimes, you might encounter errors such as database connection not getting established or the server not starting up. To workaround these issues, comment the IPv6 related entries in the /etc/hosts file.
  • Check if the DNS resolves properly to the IP Address on the system in which OpManager is installed. Add an entry to /etc/host file with ipaddress and host name if there is trouble starting OpManager.

Installing OpManager on Linux using Console mode

This is a quick walk-through of the console mode installation of OpManager on a Linux box - an easy thing to do if you are working on a Windows box and want to install on a remote Linux system without a user interface.

Prerequisites:

To begin with, make sure you have downloaded the binary for Linux.

(https://www.manageengine.com/network-monitoring/download.html)

Steps to install

Step 1: Execute the binary with administrator privileges (sudo) and -i console option.

Step 2: Go through the license agreement and enter 'Y' to proceed. You can register for technical support by providing the required details. (Name, E-mail ID, Phone, Company Name)

Step 3: Select the location

Step 4: Choose the installation directory

Step 5: Configure the Webserver Port 

Step 6: Verify the installation details and press 'Enter' to complete the installation. 

Installing OpManager on Linux with MSSQL database

From version 12.8.330, MSSQL database is supported for Linux setups. As of now MSSQL database cannot be configured directly from the installation wizard for OpManager's Linux installation. Instead, perform a default installation with PgSQL database in Linux environment and then migrate the database to MSSQL.

Note: MSSQL database is not included with the setup for Linux installations.

Steps to migrate to MSSQL DB

After installing, follow the below steps before starting the product, to migrate from PgSQL to MSSQL database in Linux installations.

  1. Step 1: In terminal, go to <OpManager_Home>/bin directory and execute the DBConfiguration.sh file.
  2. Step 2: Provide the SQL server details with the DB name.
  3. Step 3: Leave the Migrate data from existing database option unchecked.
  4. Step 4: Then, click OK to start migration.

A success message will be displayed in a dialog box after the migration is successful.

Note:

  • The DBConfiguration.sh file can be executed either directly from the Linux machine or from X11 enabled environments.
  • Executing DBConfiguration.sh from the console mode is currently not supported.
  • For BCP utility details, please refer this link.

Installing OpManager on CIS Hardened server

Before installing the product, please check for the 'execute' permission in the /tmp directory with the 'mount' command. If the command returns the line containing /tmp as 'noexec' as highlighted below, it depicts that we aren't allowed to execute any file under the /tmp directory [even if the /tmp directory has 777 permission(i.e. rwxrwxrw)] due to which our installation might throw errors.

[root@ip-172-31-44-74 /]# mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,seclabel)

In such a case, we can go ahead with one of the below approaches:

a) Modify the 'noexec' permission in the /tmp directory to 'exec'.

To modify the permission in the /tmp directory, we would have to remount the directory with 'exec' permission with the below command:

mount -o remount,exec /tmp

b) Use another directory as temp directory for installation:

To use another directory as temp directory for the installation, we would have to create a tmp directory under any directory (preferrably /opt since it would have full access) and then mark it as temp before installing the product with the below commands:

mkdir /opt/tmp
export IATEMPDIR=/opt/tmp

Note: When following the first approach, it's advisable to remount the tmp directory with the noexec permission after a successful installation and verification of the product's functionality. Allowing the tmp directory to be executable could pose a security risk, as the directory typically has worldwide access (777 - rwxrwxrw) by default. To revoke this permission, use the following command:

mount -o remount,noexec /tmp

Regarding the second approach, it's important to note that the IATEMPDIR is simply an environmental variable, and any changes made to it will be reverted once the particular terminal session is closed.

After performing the above, please proceed with the installation of OpManager.

Note: The above mentioned steps have been carried out in Red Hat Enterprise Linux 7 OS with hardening level of CIS Benchmark - Level 1 machine. 

Starting OpManager on Linux

Steps for starting the setup as a service:

1. Install the product
2. Go to > <OpManager Home>/bin/
3. run the linkAsService.sh file by (sh linkAsService.sh)
4. Then start the product
systemctl start OpManager.service (or) /etc/init.d/OpManager.service

Note:

  1. Step 4 may vary based on the linux OS type and its version.
  2. After starting OpManager, enter the "cat nohup.out" command to see start up information.

 

Thank you for your feedback!

Was this content helpful?

We are sorry. Help us improve this page.

How can we improve this page?
Do you need assistance with this topic?
By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.