- Install Ops Manager >
- Install Ops Manager >
- Install Ops Manager on Windows
Install Ops Manager on Windows¶
On this page
Overview¶
This tutorial describes how to install the Ops Manager Application, which monitors MongoDB deployments, and the optional Backup Daemon, which creates and stores deployment snapshots. This tutorial installs to Windows servers.
Ops Manager supports Monitoring and Backup on Windows but does not support Automation on Windows.
Prerequisites¶
Prior to installation you must:
- Configure Windows servers that meet the hardware and software requirements. Configure as many servers as needed for your deployment. For deployment diagrams, see Example Installation Diagrams.
- Deploy the dedicated MongoDB instances that store the Ops Manager Application Database and Backup Blockstore Database. Do not use MongoDB instances that store other data. Ensure that firewall rules allow access to the ports the instances runs on. See Deploy Backing MongoDB Replica Sets.
- Optionally install an SMTP email server.
Procedures¶
You must have administrative access on the machines to which you install.
Install and Start the Ops Manager Application¶
Download Monitoring.¶
- In a browser, go to http://www.mongodb.com/download.
- 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, click the “Monitoring and Core” MSI link.
Install the Ops Manager Application.¶
Right-click on the mongodb-mms-<version>.msi
file and select
Install. Follow the instructions in the Setup Wizard.
During setup, the Configuration/Log Folder screen prompts you to specify a folder for configuration and log files. The installation restricts access to the folder to administrators only.
Configure the Ops Manager Application.¶
In the folder you selected for configuration and log files, navigate to
\Server\Config
. For example, if you chose C:\MMSData
for
configuration and log files, navigate to C:\MMSData\Server\Config
.
Open the conf-mms.properties
file and configure the required settings
below, as well as any additional settings your deployment uses, such as
authentication settings. For descriptions of all settings, see
Ops Manager Configuration Files.
Set mms.centralUrl
and mms.backupCentralUrl
as
follows, where <host>
is the fully qualified domain name of
the server running the Ops Manager Application.
Set the following Email Address Settings as appropriate. Each can be the same or different values.
Set the mongo.mongoUri
option to the servers and ports
hosting the Ops Manager Application database. For example:
Start the MongoDB Ops Manager HTTP Service
.¶
Before starting the service, make sure the MongoDB instances that store the Ops Manager Application Database are running and that they are reachable from the Ops Manager Application’s host machine. Ensure that firewall rules allow access to the ports the MongoDB instances runs on.
To start the service, open Control Panel
, then System and Security
,
then Administrative Tools
, and then Services
.
In the Services
list, right-click on the MongoDB Ops Manager HTTP Service
and select
Start
.
If you will also run MMS Backup, start the two Backup services.¶
In the Services
list, right-click on the following services and select Start
:
MMS Backup HTTP Service
MMS Backup Alert Service
Open the Ops Manager home page and register the first user.¶
To open the home page, enter the following URL in a browser,
where <host>
is the fully
qualified domain name of the server:
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. When you finish, you are logged into the Ops Manager Application as the new user. For more information on creating and managing users, see Manage Ops Manager Users.
At the Welcome page, follow the prompts to set up Monitoring.¶
Ops Manager prompts you to download only the Monitoring Agent.
Install the Backup Daemon (Optional)¶
If you use Backup, install the Backup Daemon.
Download the Backup Daemon package.¶
- In a browser, go to http://www.mongodb.com/download.
- 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 “Backup” MSI link.
Install the Backup Daemon.¶
Right-click on the mongodb-mms-backup-daemon-<version>.msi
file
and select Install. Follow the instructions in the Setup
Wizard.
During setup, the Daemon Paths screen prompts you to specify the following folders. The installer will restrict access to these folders to administrators only:
- Configuration/Log Path. The location of the Backup Daemon’s configuration and log files.
- Backup Data Root Path. The path where the Backup Daemon stores the local copies of the backed-up databases. This location must have enough storage to hold a full copy of each database being backed up.
- MongoDB Releases Path. The location of the MongoDB software releases required to replicate the backed up databases. These releases will be downloaded from
mongodb.org
by default.
Configure the Backup Daemon.¶
In the folder you selected for storing configuration and log files,
navigate to \BackupDaemon\Config
. For example, if you chose
C:\MMSData
, navigate to C:\MMSData\BackupDaemon\Config
.
Open the conf-daemon.properties
file and configure the
mongo.mongoUri
property to point the Backup Daemon to the
servers and ports hosting the Ops Manager Application database. For example:
Copy the gen-key
file from the Ops Manager Application server to the Backup Daemon server.¶
Important: You must copy the file as a whole. Do not open the file and copy its content.
Copy the gen.key
file from the C:\MMSData\Secrets
folder on the
Ops Manager Application server to the empty C:\MMSData\Secrets
folder on the
Backup Daemon server.
If you have not already done so, start the Backup services on the Ops Manager Application server.¶
On the Ops Manager Application server, open Control Panel
, then System and
Security
, then Administrative Tools
, and then Services
.
Right-click on the following services and select Start
:
MMS Backup HTTP Service
MMS Backup Alert Service
Start the Backup Daemon.¶
On the Backup Daemon server, open Control Panel
, then System and
Security
, then Administrative Tools
, and then Services
.
Right-click on the MMS Backup Daemon Service
and select Start
.
Open Ops Manager and access the Backup configuration page.¶
Open the Ops Manager home page and log in as the user you registered when installing the Ops Manager Application. Then click the Admin link at the top right of the page. Then click the Backup tab.
Enter configuration information for the Backup database.¶
Enter the configuration information described here, and then click Save. Ops Manager uses this information to create the connection string URI used to connect to the database.
<hostname>:<port>: Enter a comma-separated list of the fully qualified domain names and port numbers for all replica set members for the Backup database. For test deployments, you can use a standalone MongoDB instance for the database.
MongoDD Auth Username and MongoDB Auth Password: Enter the user credentials if the database uses authentication.
Encrypted Credentials: Check this if the user credentials use
the Ops Manager credentialstool
. For more information, see
Encrypt MongoDB User Credentials.
Use SSL: Check this if the MongoDB database uses SSL. If you select this, you must configure SSL settings for both the Ops Manager Application and Backup Daemon. See Ops Manager Configuration Files.
Connection Options: To add additional connection options, enter them using the MongoDB Connection String URI Format.
Next Step¶
Set up security for your Ops Manager servers, Ops Manager agents, and MongoDB deployments.
Note
To set up a deployment for a test environment, see Test Ops Manager Monitoring. The tutorial populates the replica set with test data, registers a user, and installs the Monitoring and Backup Agents on a client machine in order to monitor the test replica set.