Why Mongo Ops Manager (MMS) cannot find page???

[janerim oh]

Hi All,

I am really struggling to understand mongoDB documentations. 

But that is difficult for me. :(

I'm trying to setup Mongo Ops Manager (MMS) with windows.

I follow  mongoDB documentations.(https://docs.opsmanager.mongodb.com/v1.6/tutorial/install-on-prem-windows/)

when IoOpen the Ops Manager home page (http://localhost:8080), there is an error in 404.

I do not understand what configuration parameter is required in Ops Manager configuration file conf-mms.properties

Here my conf-mms.properties files ( C:\MMSData\Server\Config\conf-mms.properties )

#

# Ops Manager Configuration File

#

# #####################################

# Ops Manager MongoDB storage settings

#

# The following MongoURI parameters are for configuring the MongoDB storage

# that backs the Ops Manager server's functionality. By default. the Ops Manager server is

# configured to expect a local standalone instance of MongoDB running on

# the default port 27017.

#

# For more advanced configurations of the backing MongoDB store, such as

# running with replication or authentication, please refer to the

# documentation at http://mms.mongodb.com/help-hosted.

# ####################################

mongo.mongoUri=mongodb://127.0.0.1:27017/?maxPoolSize=150

mongo.ssl=false

mms.centralUrl=http://localhost:8080

mms.backupCentralUrl=http://localhost:8081

# #####################################

# MongoDB SSL Settings (Optional)

#

# The following parameters are for configuring the SSL certificates to be

# used by the Ops Manager server to connect to its MongoDB backing stores. These

# settings are only applied to the mongoUri connection above when

# `mongo.ssl` is set to true.

# CAFile - the certificate of the CA that issued the MongoDB server certificate(s)

# PEMKeyFile - a client certificate containing a certificate and private key

# (needed when MongoDB is running with --sslCAFile)

# PEMKeyFilePassword - required if the `PEMKeyFile` contains an encrypted private key

# ####################################

mongodb.ssl.CAFile=

mongodb.ssl.PEMKeyFile=

mongodb.ssl.PEMKeyFilePassword=

# #####################################

# Kerberos Module (Optional)

#

# The following parameters are for configuring Ops Manager to use Kerberos to connection

# to its MongoDB backing stores.

#

# jvm.java.security.krb5.conf: This should be the path to the Kerberos conf file. The value will be set to JVM's

# java.security.krb5.conf.

#

# jvm.java.security.krb5.kdc: This should be the IP/FQDN of the KDC server. The value will be set to JVM's

# java.security.krb5.kdc.

#

# jvm.java.security.krb5.realm: This is the default REALM for Kerberos. It is being used for JVM's

# java.security.krb5.realm.

#

# mms.kerberos.principal: The principal we used to authenticate with MongoDB. This should be the exact same user

# on the mongoUri above.

#

# mms.kerberos.keyTab: The absolute path to the keytab file for the principal.

#

# mms.kerberos.debug: The debug flag to output more information on Kerberos authentication process.

#

# Please note, all the parameters are required for Kerberos authentication, except jvm.java.security.krb5.conf and

# mms.kerberos.debug. The mechanism will not be functioning if any of the setting value is missing.

#

# Assume your kdc server FQDN is kdc.example.com, your Kerberos default realm is: EXAMPLE.COM,

# the host running Ops Manager is mmsweb.example.com, the Kerberos for Ops Manager is mms/mmsweb.ex...@EXAMPLE.com,

# And you have a keytab file for mms/mmsweb.ex...@EXAMPLE.COM located at /path/to/mms.keytab, then the

# configurations would be:

# jvm.java.security.krb5.kdc=kdc.example.com

# jvm.java.security.krb5.realm=EXAMPLE.COM

# mms.kerberos.principal=mms/mmsweb.ex...@EXAMPLE.COM

# mms.kerberos.keyTab=/path/to/mms.keytab

# mms.kerberos.debug=false

#

# ####################################

jvm.java.security.krb5.conf=

jvm.java.security.krb5.kdc=

jvm.java.security.krb5.realm=

mms.kerberos.principal=

mms.kerberos.keyTab=

mms.kerberos.debug=

# #####################################

# Instance Parameter Overrides

#

# In this section include any parameters to be used on this instance

# of Ops Manager. These parameters will override any global configuration

# stored in the Ops Manager database.

#

# See https://docs.opsmanager.mongodb.com/current/reference/configuration/

# for additional information

#

# #####################################

Thaks,

[Wan Bachtiar]

I’m trying to setup Mongo Ops Manager (MMS) with windows.

Hi Janerim,

Please note that OpsManager Application is part of the MongoDB Enterprise edition, which is a commercially supported product.

If your company/organisation already has a commercial subscription and you have further questions about running OpsManager, you should open a case in the Commercial Support Portal.

Alternatively if you are evaluating MongoDB Enterprise and interested, send me a private message with your contact details and I can request a MongoDB Account Executive to contact you.

Kind regards,
Wan.

​