System Properties and Environment Variables
You can use system properties and environment variables to configure many aspects of Management Center, from JMX to the home directory and feature flags. These properties give you the power to tweak settings at startup without having to configure anything in the UI.
If an environment variable isn’t available for a property and you start Management Center using any of the following methods, you can use the JAVA_OPTS
environment variable to set system properties:
-
Docker environments
You may also need to use other environment variables. For the Docker reference, see DockerHub. -
hz-mc conf
tool -
Start scripts included with Hazelcast Platform or Management Center such as
hz-mc start
.
You can use properties to configure both Management Center and Management Center’s client connection strategy on startup.
Management Center Configuration
If an environment variable is available, it is listed under the system property in the Property column.
Property | Description | Example |
---|---|---|
|
Whether a user can log into an account in Management Center on multiple devices in different locations at the same time. Default: |
|
|
Whether Management Center logs auditable events. See Audit Logging. Default: |
|
Full class name of a variable replacer to use. See Variable Replacers. |
|
|
Whether the
configuration loading process stops when a replacement value is missing. Default: |
|
|
|
Prefix of all URL paths in Management Center. Default: |
In this example, the URL for Management Center would be |
Timeout in milliseconds for Management Center operations that wait for a response from members. Default: 60000. |
|
|
Whether Management Center does not verify the hostname of signed TLS/SSL certificates. Default: |
|
|
|
Multiplier used for extending
the disabled login period in case the failed login attempts continue after the disabled login
period expires. Default: |
|
|
A comma separated list of cipher suites to be excluded from the list of supported ciphers in Management Center. Wildcards are supported. |
|
|
Path to an existing keystore. You do not have to set this property if you use a Hardware Security Module (HSM).
Default: |
|
|
Password for the keystore. You do not have to set this property if you use a Hardware Security Module (HSM) that provides another means to access the keystore.
Default: |
|
|
Type of the keystore.
Default: |
|
|
Provider of the keystore. If you use a Hardware Security Module (HSM), specify the class name of your HSM’s |
|
|
Number of failed
login attempts that Management Center allows before disabling logins. Default: |
|
|
Whether Management Center forces users to log out when other users try to log into the same account. Default: |
|
|
Whether Management Center reads |
|
|
Whether the |
In this example, the health check would be available at |
|
The port on which the |
|
|
Home directory where metrics, executed SQL queries, and configuration settings are saved. See Configuring Management Center. |
|
|
Network address that Management Center is reachable on. Default: |
|
|
HTTP port for Management Center. Default: |
In this example, the URL for Management Center would be |
|
A comma separated list of cipher suits to be included in the list of supported ciphers in Management Center. Wildcards are supported. |
|
|
Initial duration for the disabled
login period in seconds. Default: |
|
|
Whether the clustered JMX service is enabled. Default: |
|
|
Hostname/IP address of the JMX host machine. This is used by the JMX client to connect back into JMX, so the given host must be accessible from the host machine that runs the JMX client. Default: Server’s hostname. |
|
|
Whether mutual authentication is enabled for the JMX interface. Default: |
|
|
Port on which the clustered JMX service is exposed. Default: |
|
|
Port on which the Java process that you want to monitor listens for incoming connections from the client (Remote management applications) such as JConsole . For monitoring a local Java process, there is no need to specify the JMX RMI port number. Default: |
|
|
Whether TLS/SSL is enabled for communication between the JMX interface and JMX clients. Default: |
|
Path to a keystore. Default: |
|
|
Password for the keystore. Default: |
|
|
Path to a truststore. Default: |
|
|
Password for the truststore. Default: |
|
|
Type of the keystore. Default: |
|
|
|
Name of the algorithm based
on which the authentication keys are provided. You can find out the default by calling
the |
|
|
Timeout in milliseconds for Active Directory and LDAP search queries. Default: |
|
|
Enterprise license. When this property is set, the license takes precedence over one that is set in the user interface, and you cannot update the license in the UI. For more details about licenses, see See Enterprise Licenses. |
|
|
Whether the |
|
|
Maximum amount of time for the disable login period. By default, the disabled login period is unlimited. |
|
|
Whether Management Center persists metrics. Default: |
|
|
Time-to-Live (TTL) in ISO-8601-based durations format for each record in the metrics persistence. Default: |
|
|
Number of threads that are used to consume metrics from cluster members. Default: |
|
|
Whether Management Center generates a regular healthcheck report. Default: |
|
|
Whether Management Center sends usage data to the Hazelcast phone home server. Default: |
|
|
Whether to expose all metrics to the |
|
|
Metrics to include in the |
|
|
Metrics to exclude from the |
|
|
Port on which the |
In this example, the |
|
Enable clustered REST endpoints. Default: |
|
|
Minimum length that words in the dictionary must contain. Default: |
|
|
Path to a text file that contains words that cannot be included in user passwords. |
|
|
Number of seconds that a session can remain inactive before it is invalid and the user must log in again. Default |
|
|
Duration in milliseconds that Management Center waits before requesting metadata from a Hazelcast cluster. Metadata includes a list of all data structures and their configurations. Default: 1000. |
|
|
A comma separated list of TLS/SSL protocols to be excluded from the list of supported protocols in Management Center. |
|
|
Allow Management Center to use Google’s Conscrypt SSL that is built on their fork of OpenSSL, BoringSSL. Default: |
|
|
Whether TLS/SSL is enabled. Default: |
|
|
Path to a keystore. |
|
|
Password of the keystore in |
|
|
Path to a truststore. If the |
|
|
Password of the truststore. |
|
|
Whether the HTTP port in the |
|
|
Whether clients connected to Management Center are authenticated:
Default: |
|
|
Enables use of an existing keystore.
Default: |
|
Client Connection Strategy Configuration
Use the following properties to configure the connection strategy of the Management Center client.
These properties apply to all clients that are started by Management Center.
Property | Description | Example |
---|---|---|
Upper limit of the backoff in milliseconds. Default: |
|
|
Factor by which to multiply the backoff after
each failed retry. Default: |
|
|
Duration in milliseconds that Management Center waits after the first connection failure before retrying. Default: |
|