Viewing the current configuration settings of a node or the whole cluster

On the Configuration Settings landing page, you can view a list of the current configuration settings for your system. You can view the settings for a specific node, current or remote, or for the whole cluster, to verify that the settings are configured as expected. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings.

For example, if a started agent does not run, you can check if agents are enabled on your system; or if you noticed that some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.

The Configuration Settings landing page displays configuration settings from the following sources:

  • Dynamic System Settings

  • prconfig.xml file

  • JVM command line arguments. For more information, see the PDN article JVM configuration best practices.

  • JNDI

  • Engine API

Note: From the Configuration Settings landing page you can only review the configuration settings; you cannot modify individual settings.

To access the Configuration Settings landing page, view the list of settings, and download the prconfig.xml file, you must have the pzSystemOperationsObserver privilege.

  1. Click Designer Studio > System > Operations > Configuration settings .
  2. In the Select node / All nodes field, select a node:
    • Select All Nodes to list the current configuration settings for all the nodes in the cluster.
    • Select a specific node (either the current node or a remote node) to list the current configuration settings only for this node.

    In addition to viewing configuration settings from Configuration Settings as described below , you can also view the configuration settings for a node or cluster by using REST APIs. For more details, see Pega API.