The mongodb-enterprise package includes various control scripts, including the init script /etc/rc.d/init.d/mongod.

The package configures MongoDB using the /etc/mongod.conf file in
conjunction with the control scripts. See
the Configuration File
reference for documentation of settings available in the configuration file.

As of version 2.6.12, there are no control scripts for
mongos. The mongos process is used only in
sharding. You can use the mongod init script
to derive your own mongos control script.

The default /etc/mongod.conf configuration file supplied by the
2.6 series packages has bind_ip` set to
127.0.0.1 by default. Modify this setting as needed for your
environment before initializing a replica set.

Changed in version 2.6: The package structure and names have changed as of version 2.6. For
instructions on installation of an older release, please refer to the
documentation for the appropriate version.

Use the following repository to install only versions of
MongoDB for the 2.6 release. If you’d like to install
MongoDB Enterprise packages from a particular release
series, such as 2.4 or 2.6, you can
specify the release series in the repository configuration. For
example, to restrict your system to the 2.6 release series,
create a /etc/yum.repos.d/mongodb-enterprise-2.6.repo file
to hold the following configuration information for the MongoDB
Enterprise 2.6 repository:

.repo files for each release can also be found in the repository itself.
Remember that odd-numbered minor release versions (e.g. 2.5) are development versions and are unsuitable
for production deployment.

Although you can specify any available version of MongoDB
Enterprise, yum will upgrade the packages when a newer
version becomes available. To prevent unintended upgrades, pin
the package. To pin a package, add the following exclude
directive to your /etc/yum.conf file:

You can use setenforce to change to permissive mode; this
method does not require a reboot but is not persistent.

Enable access to the relevant ports (e.g. 27017) for SELinux if in
enforcing mode. See Default MongoDB Port for
more information on MongoDB’s default ports. For default settings,
this can be accomplished by running

On RHEL 7.0, if you change the data path, the default SELinux
policies will prevent mongod from having write access on
the new data path if you do not change the security context.

You may alternatively choose not to install the SELinux packages when you are
installing your Linux operating system, or choose to remove the relevant
packages. This option is the most invasive and is not recommended.

On RHEL 7.0, if you change the data path, the default SELinux
policies will prevent mongod from having write access on
the new data path if you do not change the security context.

The MongoDB instance stores its data files in /var/lib/mongo
and its log files in /var/log/mongodb by default,
and runs using the mongod
user account. You can specify alternate log and data file
directories in /etc/mongod.conf. See systemLog.path
and storage.dbPath for additional information.

If you change the user that runs the MongoDB process, you
must modify the access control rights to the /var/lib/mongo and
/var/log/mongodb directories to give this user access to these
directories.

To completely remove MongoDB from a system, you must remove the MongoDB
applications themselves, the configuration files, and any directories containing
data and logs. The following section guides you through the necessary steps.

Warning

This process will completely remove MongoDB, its configuration, and all
databases. This process is not reversible, so ensure that all of your
configuration and data is backed up before proceeding.