# Ops Manager Application > Source-anchored research for Ops Manager Application. Run status: COMPLETED. Parent: [MongoDB Ops Manager and Cloud Manager](https://llms-explorer.com/tree/mongodb-ops-manager-and-cloud-manager/) · 2 facets · 16 facts · page: https://llms-explorer.com/tree/ops-manager-application/ ## Comparisons and alternatives - The dbi services installation guide explicitly uses a single instance for testing and proof of concept. Its standalone backing-database and HTTP examples should be read as historical lab instructions rather than a production deployment recommendation. (medium confidence) — [source](https://www.dbi-services.com/blog/mongodb-ops-manager/) ## Facts and statements - The Ops Manager Application supplies the administrator web interface and HTTP services used by MongoDB Agents to exchange data; its web interface includes user management, host monitoring and backup management. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/core/system-overview.md) - The application needs its own MongoDB database for operational information; install and start that database before starting the application. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/core/system-overview.md) - mms.centralUrl identifies the application's access URL; installation walkthroughs configure it in conf/conf-mms.properties. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/reference/config/ui-settings.md) - For a conventional host installation, the documented initial browser address is http://:8080 and first access prompts user registration. The dbi services walkthrough demonstrates that sequence for a historical test installation. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/tutorial/start-and-stop-application.md) - The mongodb-mms script starts the application; the official init.d examples use /etc/init.d/mongodb-mms start and stop. Archive installations require the documented init.d symlink. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/tutorial/start-and-stop-application.md) - Changing the application HTTP port on a host installation requires updating mms.centralUrl in conf-mms.properties, changing BASE_PORT in mms.conf, and restarting the application. Merely changing an advertised URL does not complete the documented port-change procedure. (low confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/tutorial/start-and-stop-application.md) - The application writes startup output under each host’s logs directory to mms#-startup.log, where # is a zero-based instance index. These logs retain startup history subject to the configured rotation policy. (low confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/tutorial/start-and-stop-application.md) - HTTPS configuration uses a PEM file containing a valid certificate and private key. The documented HTTPS port is 8443; changing it also requires changing the access URL. (low confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/reference/config/ui-settings.md) - Creationline's 2023 evaluation of Ops Manager 6.0.13 observed roughly five minutes between systemctl reporting the service active and the web interface becoming accessible; this is one test observation, not a universal startup-time guarantee. (low confidence) — [source](https://www.creationline.com/tech-blog/data-management/mongodb/61890) - The dbi services 4.0.2 walkthrough and Creationline 6.0.13 walkthrough explicitly describe evaluation environments. Their single-instance or colocated setup examples should be read within that scope. (high confidence) — [source](https://www.dbi-services.com/blog/mongodb-ops-manager/) - The application requires a MongoDB application database to retain operational information. MongoDB documents a dedicated replica set for this state; independent installation walkthroughs also configure a backing database before using the application. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/core/system-overview.md) - Ops Manager stores global configuration in the application database. Local conf-mms.properties settings override global values, so changing a value in the Admin UI may not change effective behavior on a server with a local override. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/reference/configuration.md) - Each application server needs its application-database connection and authentication configuration in conf-mms.properties. The mongo.mongoUri property identifies that connection; mms.centralUrl identifies the application access URL. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/reference/configuration.md) - Bypassing the initial setup wizard requires mms.ignoreInitialUiSetup=true plus the required application configuration. The flag alone does not bypass pre-flight validation; missing required settings can prevent startup. (high confidence) — [source](https://www.mongodb.com/docs/ops-manager/current/reference/configuration.md) - The Kubernetes Operator can deploy and maintain Ops Manager as a Kubernetes resource. Its application configuration can be supplied through spec.configuration, and externalConnectivity settings can request a service for access to the application. (high confidence) — [source](https://www.mongodb.com/docs/kubernetes/current/tutorial/configure-om-resource.md)