Docs Menu

Docs HomeMongoDB Ops Manager

Install a Simple Test Ops Manager Installation


This setup is not suitable for a production deployment.

To evaluate Ops Manager, you can install the Ops Manager Application and Ops Manager Application Database on a single host. This setup provides all the functionality of Ops Manager monitoring and automation but provides no failover or high availability.

This test installation includes the following caveats:

To install and configure an evaluation version of Ops Manager on hosts running Red Hat Enterprise Linux 8.0:


Provision a host for Ops Manager. This host must meet the following requirements:

System Memory
15 GB
Disk Capacity
50 GB in / (The root directory of this host)
Host OS Permissions
Host OS
Red Hat Enterprise Linux 8.0

Cloud-based instances must meet the memory and storage requirements.

To verify the needed capacity, log in to the instance and execute the following commands:

vmstat -S M -s | grep "total memory"

The output for the command shows that this instance has 16 GB of RAM.

16384 M total memory
df -h | grep "/$"

The output for the command shows that this instance has 73 GB of storage capacity.

/dev/sda1 73G 58G 12G 84% /


Verify that the ulimit settings meet the minimum requirements.


Create a /etc/yum.repos.d/mongodb-org-6.0.repo file so that you can install MongoDB directly using yum:

name=MongoDB Repository

Invoke the following command to install the latest stable release of MongoDB Community:

sudo yum install -y mongodb-org

Ops Manager connects to its application database on port 27017. If the host on which you want to install the application database has a running mongod, disable that existing database.

To disable the mongod service, invoke the following command:

sudo systemctl disable mongod
  1. Invoke the following command to create the data directory:

    sudo mkdir -p /data/appdb
  2. Invoke the following command to change ownership of the data directory to MongoDB:

    sudo chown -R mongod:mongod /data

The installer creates a configuration file saved at /etc/mongod.conf.

  1. Open the MongoDB file with your preferred text editor.

  2. Edit the file to make the following changes:

    2 destination: file
    3 path: "/data/appdb/mongodb.log"
    4 logAppend: true
    6 dbPath: "/data/appdb"
    7 journal:
    8 enabled: true
    9 wiredTiger:
    10 engineConfig:
    11 cacheSizeGB: 1
    13 fork: true
    14 timeZoneInfo: /usr/share/zoneinfo
    15 pidFilePath: /var/run/mongodb/
    17 bindIp:
    18 port: 27017
    20 enableLocalhostAuthBypass: false
  3. Save the file when you have made the edits.

sudo -u mongod mongod -f /etc/mongod.conf
  1. Navigate to the Ops Manager Download Center.

  2. From the Platforms drop-down menu, click Red Hat + CentOS 6, 7, 8 / SUSE 12 + 15 / Amazon Linux.

  3. From the Packages drop-down menu, click RPM.

  4. Click Download.


MongoDB names the downloaded package mongodb-mms-<version>.x86_64.rpm. <version> represents the version number for Ops Manager.


To verify the integrity of the Ops Manager download, see Verify Integrity of Ops Manager Packages.


If you install Ops Manager on a remote host, such as a cloud service provider instance, use scp to copy the installer to your host:

scp -i <keyfile> mongodb-mms-<version>.x86_64.rpm \

To install the .rpm package, invoke the following command. <version> represents the Ops Manager version in the .rpm package:

sudo rpm -ivh mongodb-mms-<version>.x86_64.rpm

This command creates the following artifacts:

Ops Manager software base directory
New system user that owns the Ops Manager processes
Ops Manager configuration file with the connection string to access the Application Database. Don't change this value defaults from locahost:27017.

Invoke the following command:

sudo service mongodb-mms start

If you use an cloud service provider instance, find the hostname following the directions of the relevant provider:

If you don't have a hostname, use the public IP address. To find your host's public IP address, paste this URL into your preferred browser:
  1. In a browser, enter the following URL using the hostname. If do not have a hostname, use the public IP address instead:

  2. Click the Sign Up link.

  3. Follow the console prompts to register the first user and create the first organization and project. Ops Manager assigns the Global Owner role to the first user.


Ops Manager opens the configuration console. Ops Manager marks required settings with an asterisk.

Enter the information as appropriate. When you finish the configuration, Ops Manager opens the Deployment page.

  1. Click MongoDB Ops Manager in the upper left corner of the page to return to the Deployment page.

  2. Click Add to deploy a MongoDB instance.


    See also:

← Example Deployment Architectures