Configure Deployment to Have Limited Internet Access

Set the source for Ops Manager and MongoDB Agents to install binaries to the Ops Manager Application Server.

1. Click Admin in the upper right corner to open system administration.

2. From the General tab, click Ops Manager Config.

3. Click the Miscellaneous tab at the top of the page.

4. In the MongoDB Version Management section, select the following settings:

   Option	Action
   Installer Download Source	Select remote. All necessary installers are downloaded over the internet from MongoDB, Inc. or from another HTTP or HTTPS endpoint that the hosts can access.
   Base URL	HTTP endpoint to fetch MongoDB binaries from. If the endpoint uses HTTPS, Ops Manager validates the certificate using the Certificate Authority file set in httpsCAFile. If unset, Ops Manager downloads MongoDB binaries from the remote URLs of mongodb.com and fastdl.mongodb.org. Ops Manager Application hosts require an internet connection.
   Versions Directory	Accept the platform default value unless you need to change it to meet a requirement for your environment. The default locations for the Versions Directory depend on your Ops Manager host platform: Platform Versions Directory Default Path RHEL, Ubuntu /opt/mongodb/mms/mongodb-releases Linux Archive <userSelected>/mongodb-releases Windows C:\MMSData\MongoDBReleases The Ops Manager Application expects the MongoDB binaries to be stored in this directory on every Ops Manager host.
   Backup Versions Auto Download	Select true if your Backup Daemon and Ops Manager Application run on the same platform (chip architectures, operating systems, or operating system versions). If they run on separate platforms, select false.
   Backup Versions Auto Download Enterprise Builds	Select true if you want the Backup Daemon to download MongoDB Enterprise builds as well as MongoDB Community builds. Queryable Backups require MongoDB Enterprise.
   Required Module for Backup	Select which build of MongoDB you want the Backup Daemon to use for the head database. Select Enterprise Required if you want the Backup Daemon to download only MongoDB Enterprise builds. FCV 4.2 and later use backup cursors instead of head databases. For more information, see Backup Daemon Service.

Review and approve your changes.

Ops Manager displays your proposed changes.

1. If you are satisfied, click Confirm & Deploy.

2. Otherwise, click Cancel and you can make additional changes.

Set the source for Ops Manager and MongoDB Agents to install binaries to the Ops Manager Application Server.

1. Click Admin in the upper right corner to open system administration.

2. From the General tab, click Ops Manager Config.

3. Click the Miscellaneous tab at the top of the page.

4. In the MongoDB Version Management section, select the following settings:

   Option	Action
   Installer Download Source	Select hybrid. All necessary installers are downloaded from Ops Manager Application hosts. MongoDB Agent hosts do not need an internet connection.
   Base URL	HTTP endpoint to fetch MongoDB binaries from. If the endpoint uses HTTPS, Ops Manager validates the certificate using the Certificate Authority file set in httpsCAFile. If unset, Ops Manager downloads MongoDB binaries from the remote URLs of mongodb.com and fastdl.mongodb.org. Ops Manager Application hosts require an internet connection.
   Versions Directory	Accept the platform default value unless you need to change it to meet a requirement for your environment. The default locations for the Versions Directory depend on your Ops Manager host platform: Platform Versions Directory Default Path RHEL, Ubuntu /opt/mongodb/mms/mongodb-releases Linux Archive <userSelected>/mongodb-releases Windows C:\MMSData\MongoDBReleases The Ops Manager Application expects the MongoDB binaries to be stored in this directory on every Ops Manager host.
   Backup Versions Auto Download	Select true if your Backup Daemon and Ops Manager Application run on the same platform (chip architectures, operating systems, or operating system versions). If they run on separate platforms, select false.
   Backup Versions Auto Download Enterprise Builds	Select true if you want the Backup Daemon to download MongoDB Enterprise builds as well as MongoDB Community builds. Queryable Backups require MongoDB Enterprise.
   Required Module for Backup	Select which build of MongoDB you want the Backup Daemon to use for the head database. Select Enterprise Required if you want the Backup Daemon to download only MongoDB Enterprise builds. FCV 4.2 and later use backup cursors instead of head databases. For more information, see Backup Daemon Service.

Review and approve your changes.

Ops Manager displays your proposed changes.

1. If you are satisfied, click Confirm & Deploy.

2. Otherwise, click Cancel and you can make additional changes.

Set the source for Backup Daemons and MongoDB Agents to install binaries to the Ops Manager Application Server.

1. Click Admin in the upper right corner to open system administration.

2. From the General tab, click Ops Manager Config.

3. Click the Miscellaneous tab at the top of the page.

4. In the MongoDB Version Management section, select the following settings:

   Option	Action
   Installer Download Source	Select local. All necessary installers are downloaded from Ops Manager Application Servers. MongoDB Agent hosts do not need an internet connection. An Ops Manager administrator provides installers from the MongoDB Download Center into the Versions Directory. Ops Manager serves them to MongoDB Agent hosts. The Version Manifest must be updated manually. No hosts in the deployment require an internet connection.
   Versions Directory	Accept the plaform default value unless you need to change it to meet a requirement for your environment. The default locations for the Versions Directory depend on your Ops Manager host platform: Platform Versions Directory Default Path RHEL, Ubuntu /opt/mongodb/mms/mongodb-releases Linux Archive <userSelected>/mongodb-releases Windows C:\MMSData\MongoDBReleases The Ops Manager Application expects the MongoDB binaries to be stored in this directory on every Ops Manager host.
   Backup Versions Auto Download	Select true unless your Backup Daemon and Ops Manager Application run on different platforms (chip architectures, operating systems, or operating system versions). If they run on separate platforms, select false.
   Backup Versions Auto Download Enterprise Builds	Select true if you want the Backup Daemon to download MongoDB Enterprise builds as well as MongoDB Community builds.
   Required Module for Backup	Select which build of MongoDB you want the Backup Daemon to use for the head database. Select Enterprise Required if you want the Backup Daemon to download only MongoDB Enterprise builds. FCV 4.2 and later use backup cursors instead of head databases. For more information, see Backup Daemon Service.

Download the required binaries.

Review the list that you prepared, in the Determine the Binaries to Store Locally and Download section before this procedure, of the binaries that you need to store locally and download.

Using a computer connected to the Internet, go to the MongoDB Download Center and download the MongoDB binary archives for the appropriate platforms and versions.

Binaries are stored as compressed archives (.tgz for all platforms except Windows, and .zip for Windows).

1. Download the Community Server, Enterprise Server, or both.

   Community Server

   Enterprise Server

   To download MongoDB Community Server:

   1. Go to the MongoDB Download Center.

   2. Click Servers and then click MongoDB Community Server.

   3. In the Version dropdown menu, click the desired MongoDB version. By default, this menu displays the current release. This menu also provides the current version of all active release series and the current development series.

   4. In the OS dropdown menu, click the desired platform. By default, this menu displays the platform of the computer that is accessing this page.

   5. In the Package dropdown menu, click the desired packaging for the download. By default, this menu displays an archive file format: .zip for Windows, .tgz for all other platforms.

   6. Click Download.

   To download an older version of the Community Server:

   1. Click the All Version Binaries link to the right of the Download button.

   2. Download the archive file for each MongoDB host platform that Ops Manager manages.

   To download MongoDB Enterprise Server:

   1. Go to the MongoDB Download Center.

   2. Click Servers and then click MongoDB Enterprise Server.

   3. In the Version dropdown menu, click the desired MongoDB version. By default, this menu displays the current release. This menu also provides the current version of all active release series and the current development series.

   4. In the OS dropdown menu, click the desired platform. By default, this menu displays the platform of the computer that is accessing this page.

   5. In the Package dropdown menu, click the desired packaging for the download. By default, this menu displays an archive file format: .zip for Windows, .tgz for all other platforms.

   6. Click Download.

   To download an older version of the Enterprise Server:

   1. To download the older versions, click Archived Releases.

   2. For each platform and MongoDB version you want to download, click the link to the right of the Archive label.

2. Download the MongoDB Database Tools in the .tgz format.

3. (Optional) Download MongoDB Shell.

Populate all Ops Manager hosts with the necessary MongoDB binaries and archives.

On all your Ops Manager hosts, copy all of the archived binaries (in .tgz for all platforms other than Windows, or .zip for Windows) for MongoDB Server, MongoDB Database Tools, and MongoDB Shell into the Versions Directory. Include each platform and version of these binaries that you plan to support.

This directory stores all of the archived and extracted binaries. Ops Manager needs these binaries in the .tgz or .zip formats to install and upgrade MongoDB deployments and tools.

Optional: Ensure that the Ops Manager Linux user can read files in the Versions Directory. (Linux only)

On a Linux platform, the mongodb-mms user needs the read permissions to the Versions Directory.

1. Change ownership of all files and directories in the Versions Directory to mongodb-mms.

   sudo chown -R mongodb-mms:mongodb-mms <path-to-the-versions-directory>/*

2. Change permissions on all the files under the Versions Directory to allow the:

   • Owner to read and write them

   • Group to read them

   When you set these permissions, Ops Manager can read and extract the archived binaries. Do not remove the execute permission from any directories under the Versions Directory. If you did, the Backup Daemon cannot access any files inside those directories.

   sudo chmod -R 640 <path-to-the-versions-directory>/*.tgz \
     <path-to-the-versions-directory>/*.zip

If these steps were successful, the resulting list of the Versions Directory should look similar to the following example. This example may not reflect the list of currently supported versions.

-rw-r----- 1 mongodb-mms mongodb-mms 116513825 Apr 27 15:06 mongodb-linux-x86_64-2.6.9.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  51163601 May 22 10:05 mongodb-linux-x86_64-amazon-3.0.3.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50972165 May 22 10:06 mongodb-linux-x86_64-suse12-3.6.4.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  95800685 Apr 27 15:05 mongodb-linux-x86_64-enterprise-amzn64-2.6.9.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50594134 Apr 27 15:04 mongodb-linux-x86_64-enterprise-amzn64-3.0.2.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50438645 Apr 27 15:04 mongodb-linux-x86_64-enterprise-suse12-3.6.4.tgz
drwxrwx--- 1 mongodb-mms mongodb-mms      4096 Apr 27 15:04 mongodb-linux-x86_64-enterprise-suse12-3.6.4

Repeat these steps on each Ops Manager host.

Update the version manifest for Ops Manager on each Ops Manager host.

Ensure you have downloaded MongoDB binaries in your Versions Directory.

For the selected versions, ensure that you have downloaded and placed the archived binaries in the Versions Directory. Otherwise, Ops Manager fails a pre-flight check when starting in Local Mode.

Review and approve your changes.

Ops Manager displays your proposed changes.

1. If you are satisfied, click Confirm & Deploy.

2. Otherwise, click Cancel and you can make additional changes.