Populate all ops manager hosts with the necessary mongodb binaries and archives
If you run Ops Manager with high availability , you must repeat the previous steps on each Ops Manager server. If you run Ops Manager with high availability, you must repeat the last step on each Ops Manager server.
Navigation This version of the manual is no longer supported. If the servers running Automation Agents or Backup Daemons do not have internet access, you must: If you run in Local Mode , you must: Store the archived MongoDB binaries for each version, edition and platform you need to support for Automation in this directory on each of your Ops Manager servers.
The versions directory must also store the extracted MongoDB binaries for each version, edition and platform you need to support for Backup. Grant the mongodb-mms user permission to read the contents of this directory. The version manifest must be downloaded and its contents copied and pasted into each Ops Manager server. You must update the version manifest as MongoDB, Inc. The mongodb-mms user needs permission to read the contents of the versions directory Before configuring Ops Manager to run in Local Mode , you must meet the prerequisites described here.
You need binaries for each MongoDB version that you: Have in each existing deployment to be imported into Ops Manager. May use to create new deployments through Ops Manager Automation. May use during an intermediary step in an upgrade. Example If you import an existing deployment of MongoDB 2. Important Each MongoDB edition supports a range of versions of a given operating system. Set Ops Manager to Local Mode.
Click the General tab. Click Ops Manager Config. Click the Miscellaneous button at the top of the page. Select Local as the Version Manifest Source setting. Note the directory specified in Versions Directory. Note Automation uses the archived binaries, but Backup uses the extracted binaries. Grant the mongodb-mms user read permissions to the versions directory. Example On a Linux platform, you should issue the chown command to change ownership for all files in the directory to mongodb-mms: If you installed using a tar.
By default, this is C: The Backup Daemon uses the conf-daemon. For configuration settings that store credentials, you can either store the credentials in plain text or use the Ops Manager credentialstool to encrypt the credentials, as described in Encrypt MongoDB User Credentials. If you choose to store credentials in plain text, reduce the permissions on the configuration file.
If you wish to use a port other than , Change the Ops Manager Ports describes how to change the ports that Ops Manager uses. You must set mms. When you specify mms. If you change this default, change the ports specified in the mms. Required if the PEM file contains an encrypted private key. Specify the password for PEM file. You can encrypt the specified password using the Ops Manager credentialstool.
The following email address settings are mandatory. You must define them before the Monitoring instance will start. The email address used for sending the general emails, such as Ops Manager alerts. You can include an alias with the email address. The email address to send messages from the Ops Manager admin. The email address to send messages or replies to the Ops Manager admin. The email address to send bounce messages, i. The email interface to use. AwsEmailDao , as in:. For JavaEmailDao, specify com.
JavaEmailDao , as in:. Transfer protocol smtp or smtps as specified by your email provider. To receive alert notifications via SMS, you must have a Twilio account and specify your Twilio account information in the configuration file. The connection string used to access the backing MongoDB instance.
The following example specifies connection to a replica set:. If you omit the port number, Ops Manager uses the default port for all hosts. For a backing MongoDB instance with access control , the connection string must include authentication credentials. If the database is a sharded cluster, the clusterAdmin role is required instead of clusterMonitor. The following examples show the formats to use for the different authentication mechanisms.
The client certificate is contained in the PEM file you specify in the mongodb. Once you have created the user, prefix the host specified in mongo. You must escape the user principal, replacing symbols with the URL encoded representation. To enable Kerberos authentication between the Ops Manager Application and the backup-database , see Kerberos Settings. The following settings in conf-mms. The name of the PEM file that contains the X certificate and private key. For more information on the option, see net.
Add this property and set it to true if mongo. You must encrypt the username and password in mongo. You can use the same email address throughout, or specify a different address for each field. The first user receives Global Owner permissions for the test install.
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 Monitoring, Ops Manager prompts you to download only the Monitoring Agent to the server. If you installed the Backup Daemon, do the following to enable Backup: You must have root access to the server. Configure the yum package management system to install the latest stable release of MongoDB.
Create the data directory for the Ops Manager Application database. Download the Ops Manager Application package. Fill out and submit the subscription form. Open a system prompt.