- Security >
- Manage Ops Manager Hostname and Ports
Manage Ops Manager Hostname and Ports¶
On this page
- Ubuntu/Debian
- RHEL/CentOS/SLES/AMZ
- Linux
Ops Manager must provide a consistent hostname and consistent ports. Follow these procedures to:
- Override the default hostname for Ops Manager
- Change the default ports for Ops Manager
- Enable the health-check endpoints
Note
All of these procedures are optional. You shouldn’t need to change these settings unless your Ops Manager Backup Daemons or Ops Manager Application doesn’t appear with the correct hostname, or you need to change ports to meet local security concerns.
Override the Ops Manager Hostname¶
Ops Manager tries to detect its host’s FQDN. There might be times when the Ops Manager hosts select the wrong hostname. If you need to override the hostname that Ops Manager selected, you can set Ops Manager to use a hostname that you specify.
Important
If Ops Manager works as expected from the URL you wanted, you can skip this procedure.
To set the hostname on Ubuntu or Debian hosts:
Log in to the host running Ops Manager.¶
Open mms.conf
for editing.¶
Navigate to the
<install_dir>/conf/
directory.Open the
mms.conf
file asroot
in your preferred text editor.Example
Set the hostname values to the FQDN for the Ops Manager Application and Backup Daemon.¶
Add two options with the mms.system.hostname
value:
JAVA_MMS_UI_OPTS
for the Ops Manager ApplicationJAVA_DAEMON_OPTS
for the Backup Daemon
Example
These Java options should look similar to this example:
You can use environment variables on Linux systems to set this value:
Update the Ops Manager URL.¶
In the Ops Manager Application, click the Admin link in the upper right corner of the page.
Click the General tab and then click Ops Manager Config.
Update the URL to Access Ops Manager field to use the value you specified in the Java Options registry value.
Example
Click Save.
Restart Ops Manager.¶
Invoke the following command:
You can access the Ops Manager Application from the new URL after Ops Manager restarts.
Change the Default Port¶
Ops Manager uses the ports and health-check endpoints described in
Firewall Configuration. The endpoints default to
disabled
.
To change the ports on Ubuntu or Debian hosts:
Log in to the host running Ops Manager.¶
Open mms.conf
for editing.¶
Navigate to the
<install_dir>/conf/
directory.Open the
mms.conf
file asroot
in your preferred text editor.Example
Set the BASE_PORT
value to the desired Ops Manager port.¶
When changing the port, ensure that the chosen port is available for use.
By default, Ops Manager uses port 8080
. Change the BASE_PORT
value to the desired port number.
If you want to change the port for Ops Manager connections over TLS,
update BASE_SSL_PORT
.
Update the Ops Manager URL.¶
In the Ops Manager Application, click the Admin link in the upper right corner of the page.
Click the General tab and then click Ops Manager Config.
Update the URL to Access Ops Manager field to use the value you specified in the Java Options registry value.
Example
Click Save.
Restart Ops Manager.¶
Invoke the following command:
You can access the Ops Manager Application from the new URL after Ops Manager restarts.
Enable the Health Check Endpoint¶
Ops Manager provides an HTTP health-check endpoint. This endpoint is
accessed on port 8090
and is disabled by default. Before you enable
the endpoint, make sure that another application or process isn’t using
port 8090
.
To enable the endpoint:
Open mms.conf
for editing.¶
Open the mms.conf
file with root access. mms.conf
is located in the
<install_dir>/conf/
directory.
Uncomment DEBUG.PORT
.¶
To enable the endoint, remove the #
symbol so that the line
reads:
Important
This port is only accessible from localhost
(or
127.0.0.1
). The port number can be changed from 8090
to
another value.