Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Deploying Hazelcast Management Center

Updated on November 9, 2021

This content applies only to On-premises and Client-managed cloud environments

If you are using the client-server model for Hazelcast on Pega Platform™, you can use the Hazelcast Management Center to gain insight into the client-server clusters. Management Center offers information about resource usage, topology, and a variety of distributed objects such as queues, topics, and maps.

    For more information about the client-server mode of the Hazelcast service, see Configuring client-server mode for Hazelcast on Pega Platform.

    This topic provides supporting information about deploying Management Center specifically for Pega Platform. To deploy and start the Hazelcast Management Center for Pega Platform, follow the instructions for your version of Management Center in the manual provided on the Hazelcast website.

    Deploying Management Center for Pega Platform involves the following tasks:

    1. Configuring the Pega application server to point to Management Center 
    2. Setting up and using optional features    

    Configuring the Pega application server to point to Management Center

    When installing Management Center, you must configure the Pega application server to point to Management Center.

    1. On the application server, navigate to the prweb/WEB-INF/classes directory, and then open the prconfig.xml configuration file.
    2. Add the following line to the file:  <env name="cluster/hazelcast/managementconsole/url" value="http://<mancenter host IP>:8080/hazelcast-mancenter/" />
    3. Save and close the configuration file.

      Note: When logging in to Management Center for the first time, you create a user that has administrative privileges. This user has abilities that are beyond those of basic monitoring needs, such as running garbage collection or viewing data in a distributed map, which can contain consumer information protected under HIPAA.. Pega recommends that you create new users with the Metrics Only privilege. This privilege level does not have the ability to view sensitive data in the Hazelcast cluster. For more information about creating users for Management Center, see the user manual for your version of Management Center on the Hazelcast website.

    Setting up and using optional features

    The following table provides information about setting up and using optional features in Management Center with Pega Platform. For more information about these features, see the documentation for your version of Management Center on the Hazelcast website.

    Client Monitoring

    You can use Management Center to monitor all of the clients that connect to your Hazelcast cluster.

    By default, Management Center only shows basic information for clients, such as client instance name, address, type, and labels. To see more advanced information, enable client statistics before starting your clients by setting the hazelcast.client.statistics.enabled Hazelcast system property to true on the Hazelcast server.


    If you are using encryption with the Management Center, perform the following steps:

    1. Set the cluster truststore as the default Java truststore by passing the following argument when starting the Hazelcast server.
    2. Enable encryption by passing the following arguments when starting Management Center.

      •<password for truststore> 

      •<path to keys>/cluster-truststore.jks 

      •<keystore password>

      •<path to keys>/cluster-keystore.jks 

    3. Make sure that your browser trusts the certificate provided to Management Center. When encryption is enabled, Management Center starts with the following URL: http://<mancenter host IP>:8443/hazelcast-mancenter/.
    Time Travel

    Pega recommends that you enable the Time Travel feature. When this feature is enabled, Management Center records statistics about the cluster, such as CPU usage, garbage collector, and heap usage.

    Hazelcast Diagnostic Logging

    Hazelcast diagnostic logging is enabled by default for servers and is disabled for clients. The log file pega_hazelcast-diagnostics-<IP>-<timestamp>-<ID> provides information about the state of the Hazelcast cluster and is located in the same directory as your other Pega logs. Hazelcast uses a rolling file strategy to limit the size of the diagnostic logs. By default, Pega provides for a maximum of three files with a size of up to 50 MB each.

    You can change thesdefault settings for your Hazelcast instance by configuring the following properties for Hazelcast logging in the prconfig.xml configuration file:

    • hazelcast/diagnostics/enabled – Logging is enabled on the server by default. To disable logging at the server level, change the value of the setting to false.

    • hazelcast/diagnostics/client/enabled – Logging is disabled for clients by default. To enable logging at the client level, change the value of the setting to true.

    • hazelcast/diagnostics/metric/level – The level of information saved in the log file is set to info by default. To change the level of information saved in the log file, change the value of the setting to the level that you want to use.

    • hazelcast/diagnostics/file/sizeMaximum – The maximum size of each diagnostic file is 50MB. To change the maximum size, change the value of the setting to the size that you want to use.

    • hazelcast/diagnostics/file/count – The maximum number of diagnostic files that the systemp keeps by default is 3. To change the maximum number of log files, change the value to the number of files that you want to keep. When the system reaches that limit, the oldest file is replaced. 

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us