Identifying active nodes
In a multi-node system, multiple servers each hosting Pega Platform share one PegaRULES database.
Systems and Nodes report
Nodes have different meaning, depending on the environment:
- For on-premises systems, each server is known as a node and you can connect to a single node of a cluster, but Pega Platform can start and stop nodes independently.
- In Pega Cloud services environments, nodes run independently within each deployment tier. Pega Cloud services defines the parameters for the tiers and nodes running in your environments.
- For client-managed cloud environments, you associate nodes with Kubernetes pods. The tiers within the deployment manage the nodes that are defined in the tier configuration.
For on-premises systems, the Systems and Nodes report identifies all nodes participating in your system currently, or at any time in the last 90 days. To see this report, open and run the standard list view rule System-Status-Nodes.SystemNodeDetails.ALL.
Columns of the display present:
- A description, from this data instance
- The system name
- The node name
- The Short Description
- The number of hours since the node joined the system
- The number of minutes since the most recent system pulse
Instances of the System Node data class provides only a text description of a node. All other information on the Systems Node Detail display is derived and not part of the PegaRULES database.
Previous topic Updating the system node description in on-premises systems Next topic Setting application-specific configuration settings with configuration definitions and configuration bundles