Navigation

Install a Simple Test Ops Manager Installation

On this page

Overview

To evaluate Ops Manager, you can install the Ops Manager Application and Ops Manager Application Database on a single server. 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 Backup Data 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 procedure installs the test deployment on servers running either RHEL 6+ or Amazon Linux.

Procedure

Warning

This setup is not suitable for a production deployment.

To install Ops Manager for evaluation:

1

Set up a RHEL 6+ or Amazon Linux server that meets the following requirements:

15 GB memory and 50 GB disk space:
The server must have 15 GB of memory and 50 GB of disk space for the root partition. You can meet the size requirements by using an Amazon Web Services EC2 m3.xlarge instance and changing the size of the root partition to 50 GB. When you log into the instance, execute df -h to verify the root partition has 50 GB of space.
Root access:
You must have root access to the server.
2

Configure the yum package management system to install the latest stable release of MongoDB.

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

echo "[mongodb-org-3.4]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/amazon/2013.03/mongodb-org/3.4/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-3.4.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 data directory for the Ops Manager Application Database.

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

Create the backup directory. (Optional)

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 MongoDB for the Application Database.

Start MongoDB as the mongod user, specifying:

  • Port 27017
  • The /data/appdb path for data files (--dbpath)
  • The /data/appdb/mongodb.log path for logs (--logpath)
  • The --fork option to run the process in the background and maintain control of the terminal.
  • The --wiredTigerCacheSizeGB option to minimize the amount of cache the WiredTiger storage engine uses for the application database.
sudo -u mongod mongod --port 27017 --dbpath /data/appdb --logpath /data/appdb/mongodb.log --wiredTigerCacheSizeGB 1 --fork
7

Start MongoDB for the backup database. (Optional)

Start MongoDB as the mongod user, specifying:

  • Port 27018
  • The /data/backup path for data files (--dbpath)
  • The /data/backup/mongodb.log path for logs (--logpath)
  • The --fork option to run the process in the background and maintain control of the terminal.
  • The --wiredTigerCacheSizeGB option to minimize the amount of cache the WiredTiger storage engine uses for the backup database.
sudo -u mongod mongod --port 27018 --dbpath /data/backup --logpath /data/backup/mongodb.log --wiredTigerCacheSizeGB 1 --fork
8

Download the Ops Manager package.

  1. In a browser, go to http://www.mongodb.com and click on the Download button.
  2. Complete the form.
  3. On the MongoDB Download Center page, click on the Ops Manager tab.
  4. Select RedHat 5+ / CentOS 5+ / SUSE 11+ / Amazon Linux from the Platforms drop-down menu.
  5. Select RPM from the Packages drop-down menu.
  6. 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 .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 server 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
11

Start Ops Manager.

Issue the following:

sudo service mongodb-mms start
12

Get your server’s 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=what%20is%20my%20IP%20address
13

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

  1. In a browser, enter the following URL using the server’s 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 group. 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.

15

If you will backup your instance, configure the backup capabilities. (Optional)

  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 the following:

    mongodb://localhost:27018
    
16

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 to deploy a MongoDB instance.