Navigation

This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.

Ops Manager Introduction >
Install a Simple Test Ops Manager Installation

Install a Simple Test Ops Manager Installation¶

On this page

Overview
Procedure

Overview¶

To evaluate Ops Manager, you can quickly create a test installation by installing 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. This is not a production setup.

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 install Ops Manager Backup, in which case you would install the Backup Daemon and Backup Blockstore database on the same server as the other Ops Manager components. The Backup Blockstore 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:¶

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 from 8 GB to 50 GB. When you log into the instance, execute “df -h” to verify the root partition has 50 GB of space.
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]
name=MongoDB Repository
baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64
gpgcheck=0
enabled=1" | 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/db
sudo chown -R mongod:mongod /data

OPTIONAL: To also install the Backup feature, issue following additional commands for the Backup Blockstore database:

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

5

Start the MongoDB backing instance for the Ops Manager Application database.¶

Issue the following command to start MongoDB as the mongod user. Start MongoDB on port 27017 and specify the /data/db for both data files and logs. Include the --fork option to run the process in the background and maintain control of the terminal.

sudo -u mongod mongod --port 27017 --dbpath /data/db --logpath /data/db/mongodb.log --fork

OPTIONAL: To also install the Backup feature, issue following command to start a MongoDB instance similar to the other but on port 27018 and with the data directory and log path of the Backup Blockstore database:

sudo -u mongod mongod --port 27018 --dbpath /data/backup --logpath /data/backup/mongodb.log --fork

6

Download the Ops Manager Application package.¶

In a browser, go to http://www.mongodb.com/download.
Fill out and submit the subscription form.
On the MongoDB Enterprise Downloads page, go to the MongoDB Ops Manager section and click the here link.
On the Ops Manager Download page, acknowledge the recommendation to contact MongoDB for production installs.
On the MongoDB Ops Manager Downloads page, copy the link address of the RPM link for Monitoring, Automation and Core. OPTIONAL: If you will install Backup, copy the link address of the RPM link for Backup as well.
Open a system prompt.
Download the Ops Manager Application package by issuing a curl command that uses the link address copied for the RPM for Monitoring, Automation and Core:
copy
```
curl -OL <link-address-for-monitoring-automation-core-rpm>
```
OPTIONAL: Download the Backup Daemon package by issuing a curl command that uses the link address copied for the Backup RPM:
copy
```
curl -OL <link-address-for-backup-rpm>
```

7

Install the Ops Manager Application.¶

Install the Monitoring, Automation and Core RPM package that you downloaded. Issue the rpm --install command with root privileges and specify the package name:

sudo rpm --install <rpm-package-for-monitoring-automation-core>

OPTIONAL: To also install Backup, issue the rpm --install command with root privileges and specify the Backup RPM package:

sudo rpm --install <rpm-package-for-backup>

8

Get your server’s public IP address.¶

If you are using an EC2 instance, this is available on the instance’s Description tab.

Alternately, you can get the public IP address by issuing the following:

curl -s http://whatismijnip.nl |cut -d " " -f 5

9

Configure the Ops Manager Application.¶

Edit /opt/mongodb/mms/conf/conf-mms.properties with root privileges and set the following options. For detailed information on each option, see Ops Manager Configuration Files.

Set mms.centralUrl and mms.backupCentralUrl as follows, where <ip_address> is the IP address of the server running the Ops Manager Application.

mms.centralUrl=http://<ip_address>:8080
mms.backupCentralUrl=http://<ip_address>:8081

Set the following Email Address Settings as appropriate. You can use the same email address throughout, or specify a different address for each field.

mms.fromEmailAddr=<email_address>
mms.replyToEmailAddr=<email_address>
mms.adminFromEmailAddr=<email_address>
mms.adminEmailAddr=<email_address>
mms.bounceEmailAddr=<email_address>

Set the mongo.mongoUri option to the port hosting the Ops Manager Application database:

mongo.mongoUri=mongodb://localhost:27017

OPTIONAL: If you installed the Backup Daemon, edit /opt/mongodb/mms-backup-daemon/conf/conf-daemon.properties with root privileges and set the mongo.mongoUri value to the port hosting the Ops Manager Application database:

mongo.mongoUri=mongodb://localhost:27017

10

Start the Ops Manager Application.¶

To start the Ops Manager Application, issue the following:

sudo service mongodb-mms start

OPTIONAL: To start the Backup Daemon, issue the following:

sudo service mongodb-mms-backup-daemon start

11

Open the Ops Manager home page.¶

In a browser, enter the following URL, where <ip_address> is the IP address of the server:

http://<ip_address>:8080

12

To begin testing Ops Manager, click Register and follow the prompts to create the first user and group.¶

The first user receives Global Owner permissions for the test install.

13

At the Welcome page, follow the prompts to set up Automation or Monitoring.¶

Automation lets you define a MongoDB deployment through the Ops Manager interface and rely on the Automation Agent to construct the deployment. If you select Automation, Ops Manager prompts you to download the Automation Agent and Monitoring Agent to the server.

Monitoring lets you manage a MongoDB deployment through the Ops Manager interface. If you select Monitoring, Ops Manager prompts you to download only the Monitoring Agent to the server.

OPTIONAL: If you installed the Backup Daemon, do the following to enable Backup: click the Admin link in at the top right of the Ops Manager page and click the Backup tab. In the <hostname>:<port> field, enter localhost:27018 and click Save.

← Ops Manager Components Install Ops Manager →