-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Ops Manager
-
Labels:
-
Environment:
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-application-high-availability/#multiple-application-servers
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/CS-32073
*Screen Resolution*: 1680 x 1050
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-application-high-availability/#multiple-application-servers *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/CS-32073 *Screen Resolution*: 1680 x 1050
This page should be updated for Ops Manager 2.0.x regarding the configuration parameters (mms.centralUrl, mms.remoteIp.header) that now should be set using the Ops Manager Web UI ( "Admin" -> "Ops Manager Configuration" page) instead of editing the conf-mms.properties file on each server.
- links to