Navigation

Install a Simple Test Ops Manager Installation

Warning

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.

Unlike a production installation, this test installation uses one mongod for the Ops Manager Application database. In production, the database requires a dedicated replica set.

This procedure explains how to activate the Backup feature. This optional step requires you to install Snapshot Storage on the same host as the other Ops Manager components. You configure the backup database as you would the application database, using one mongod instead of a replica set.

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

1

Provision an Ops Manager host.

Provision a host for Ops Manager that meets the following requirements:

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

Using AWS

An AWS EC2 t3a.xlarge instance meets the memory requirements. Change the size of the instance’s root partition to 50 GB. Log in to the instance and execute df -h to verify the root partition has 50 GB of space.

Important

Ensure the ulimit settings meet the minimum requirements. For more information, see the MongoDB Ulimit Settings.

2

Configure yum to install MongoDB.

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

[mongodb-org-4.4]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/4.4/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-4.4.asc
3

Install MongoDB.

Issue the following command to install the latest stable release of MongoDB:

sudo yum install -y mongodb-org
4

Optional: Disable the mongod service.

The Ops Manager attaches to its application database on port 27017. If the host on which you want to install the application database is already running a mongod, you need to disable it.

Invoke the following command to disable the mongod service:

sudo systemctl disable mongod
5

Create the Ops Manager Application Database directory.

Issue the following two commands to create the data directory and change its ownership:

sudo mkdir -p /data/appdb
sudo chown -R mongod:mongod /data
6

Update the MongoDB configuration file.

When you install MongoDB, it creates a configuration file saved at /etc/mongod.conf. Open this file with your preferred text editor. Make the following changes to the file:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
systemLog:
  destination: file
  path: "/data/appdb/mongodb.log"
  logAppend: true
storage:
  dbPath: "/data/appdb"
  journal:
    enabled: true
  wiredTiger:
    engineConfig:
      cacheSizeGB: 1
processManagement:
  fork: true
  timeZoneInfo: /usr/share/zoneinfo
  pidFilePath: /var/run/mongodb/mongod.pid
net:
  bindIp: 127.0.0.1
  port: 27017
setParameter:
  enableLocalhostAuthBypass: false

Save the file when you have made the edits.

7

Start the Ops Manager Application Database mongod instance.

sudo -u mongod mongod -f /etc/mongod.conf
8

Download the Ops Manager package.

  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.

Note

The downloaded package is named mongodb-mms-<version>.x86_64.rpm, where <version> is the version number.

9

Optional: Copy the Ops Manager .rpm package to your host.

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

scp -i <keyfile> mongodb-mms-<version>.x86_64.rpm ec2-user@<public-ip>:~
10

Install Ops Manager.

Install the .rpm package by issuing the following command, where <version> is the version of the Ops Manager .rpm package:

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

The install creates the following:

  • The base directory for the Ops Manager software, which is:

    /opt/mongodb/mms/

  • A new system user, mongodb-mms, under which the host runs.

  • The /opt/mongodb/mms/conf/conf-mms.properties file, which contains the connection string to access the Application Database in mongo.mongoUri setting. The default value is locahost, port 27017, so no changes are necessary.

11

Start Ops Manager.

Issue the following command:

sudo service mongodb-mms start
12

Get your instance hostname.

If you are using an EC2 instance, the hostname is the Public DNS listed on the EC2 instance’s Description tab.

If you do not have a hostname, you can instead use the public IP address. To get the public IP address, paste this URL into your preferred browser:

https://www.google.com/search?q=myip
13

Open the Ops Manager home page and register the first user.

  1. In a browser, enter the following URL using the hostname. If do not have a hostname, use the public IP address instead:

    http://<OpsManagerHost>:<Port>
    
  2. Click the Register link and follow the prompts to register the first user and create the first project. The first user is automatically assigned the Global Owner role.

14

Configure Ops Manager.

Ops Manager walks you through several configuration pages. Required settings are marked with an asterisk. Enter information as appropriate. When configuration is complete, Ops Manager opens the Deployment page.

See also

To review the available Ops Manager configuration settings, see Ops Manager Application Settings.

15

Set up your first deployment.

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

  2. Click Add New to deploy a MongoDB instance.