Navigation
This version of the documentation is archived and no longer supported. It will be removed on EOL_DATE. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.
This version of the manual is no longer supported. It will be removed on EOL_DATE.

Install a Simple Test Ops Manager Installation

On this page

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, the simple test installation uses only one mongod for the Ops Manager Application database. In production, the database requires a dedicated replica set.

This procedure includes optional instructions to activate the Backup feature, in which case you would install Snapshot Storage on the same server as the other Ops Manager components. The backup database uses only one mongod and not a dedicated replica set, as it would in production.

This tutorial installs the test deployment on servers running either Red Hat Enterprise Linux 7.0.

Procedure

Warning

This setup is not suitable for a production deployment.

To install and configure an evaluation version of Ops Manager:

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 /
Host OS Permissions root
Host OS Red Hat Enterprise Linux 7.0

Using AWS

An AWS EC2 m3.xlarge instance meets the memory requirements. Change the size of the instance’s root partition to 50 GB. Log into 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.

Issue the following command to set up a yum package management system repository definition:

echo "[mongodb-org-4.0]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/4.0/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-4.0.asc" | sudo tee /etc/yum.repos.d/mongodb.repo
3

Install MongoDB.

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

sudo yum install -y mongodb-org mongodb-org-shell
4

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
5

(Optional) Create the Ops Manager backup data directory.

To configure the Backup feature as well, issue the following additional commands for the backup database:

sudo mkdir -p /data/backup
sudo chown mongod:mongod /data/backup
6

Start the Ops Manager Application Database mongod instance.

Start MongoDB as the mongod user, specifying:

Setting Command Option Value
Port --port 27017
Absolute path for MongoDB data files --dbpath /data/appdb
Absolute file path for MongoDB logs --logpath /data/appdb/mongodb.log
Amount of cache the WiredTiger storage engine uses for the application database. --wiredTigerCacheSizeGB 1
Flag to run the mongod in the background and maintain control of the terminal --fork  

The resulting command would resemble this:

sudo -u mongod mongod --port 27017 --dbpath /data/appdb \
  --logpath /data/appdb/mongodb.log \
  --wiredTigerCacheSizeGB 1 --fork
7

(Optional) Start the Ops Manager Backup Database mongod instance.

Start MongoDB as the mongod user, specifying:

Setting Command Option Value
Port --port 27018
Absolute path for MongoDB data files --dbpath /data/backup
Absolute file path for MongoDB logs --logpath /data/backup/mongodb.log
Amount of cache the WiredTiger storage engine uses for the application database. --wiredTigerCacheSizeGB 1
Flag to run the mongod in the background and maintain control of the terminal --fork  

The resulting command would resemble this:

sudo -u mongod mongod --port 27018 --dbpath /data/backup \
  --logpath /data/backup/mongodb.log \
  --wiredTigerCacheSizeGB 1 --fork
8

Download the Ops Manager package.

  1. Open your preferred browser to visit the MongoDB Download Center.
  2. Click the Tools tab and then click Ops Manager.
  3. From the Platforms drop-down menu, click Red Hat + CentOS 6, 7 / SUSE 12 / Amazon Linux.
  4. From the Packages drop-down menu, click RPM.
  5. Click Download.

Note

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

9

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. The default is locahost, port 27017, so no changes are necessary.

10

Start Ops Manager.

Issue the following command:

sudo service mongodb-mms start
11

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
12

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>:8080
    
  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.

13

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.

14

(Optional) Configure the backup capabilities.

  1. Create a directory to store the head databases.

    Important

    Do not use this directory for any other purpose:

    mkdir /data/backupDaemon
    
  2. Make the directory writable by the mongodb-mms user:

    sudo chown mongodb-mms:mongodb-mms /data/backupDaemon
    
  3. In Ops Manager, while logged in as the user you registered during installation, click the Admin link at the top right of the page.

  4. Click the Backup tab.

  5. Follow the prompts to configure the Backup storage. Ops Manager walks you through the configuration.

    For snapshot storage, select either the local filesystem or the backup database. If you use a File System Store, you still need a small MongoDB database for oplog storage. At the prompt to configure the connection string to the backup database, enter your local hostname and port:

    localhost:27018
    

    Ops Manager automatically prefixes connection strings with mongodb://. Your connection string should match the following:

    mongodb://localhost:27018
    
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.