This is a prerelease version.

View latest

Configuring Management Center

You can use various options to configure the Management Center instance as well as the client that Management Center uses to connect to and interact with Hazelcast clusters.

For example, you may want to configure the client to connect to certain Hazelcast members. You may also want to configure the home directory of the Management Center instance to customize where metrics and other configuration data is saved.

Where Management Center Saves Data

By default, Management Center saves the following data in the hazlecast-mc directory of the user’s home directory:

  • Configuration settings

  • Metrics

You can configure Management Center to save this data in a different location, using the hazelcast.mc.home property.

Ways to Configure Management Center

You can either configure Management Center in the UI while it’s running or preconfigure it in the terminal so that it starts with the settings you need.

Table 1. Configuration methods for Managment Center
Configuration method Use case

UI

Configure a running instance of Management Center. Use this method for the following:

  • Managing connections to clusters

  • Setting a security provider

  • Setting and updating license keys

  • Managing users in the local security provider

Configure any aspect of Management Center on start from the command line, including client configuration, feature flags, JMX, and home directory.

Preconfigure Management Center before starting it. Use this method for the following:

  • Managing connections to clusters

  • Setting and updating security providers

  • Managing users

  • Setting system properties

Configuring the Client

Because Management Center connects to Hazelcast clusters as a client, you can configure it, using the following methods:

However, Management Center does not allow you to override the following settings:

  • instance-name: Set to the name of the cluster.

  • connection-strategy.async-start: Set to true so that Management Center starts without waiting to get a cluster connection.

  • connection-strategy.cluster-connect-timeout-millis: Set to infinity so that Management Center never gives up trying to connect to the cluster.

  • network.smart-routing: Set to true so that Management Center will open connections to all members.

Member-Side Configuration

On a Hazelcast member, you can also use the management-center setting to enable or disable both scripting and the console as well as setting up trusted interfaces. See Management Center in the Platform documentation.

Providing an Extra Classpath

To start Management Center with an extra classpath entry, use the following command:

java -cp "hazelcast-management-center-5.1-BETA-1.jar:/path/to/an/extra.jar" com.hazelcast.webmonitor.Launcher

On Windows, use a semicolon instead of colon:

java -cp "hazelcast-management-center-5.1-BETA-1.jar;/path/to/an/extra.jar" com.hazelcast.webmonitor.Launcher