Skip to main content

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

Classifying nodes

Updated on July 8, 2022

Node classification is the process of separating nodes by purpose, predefining their behavior by assigning node types. When you associate a work resource with a specific node type,you optimize work performance in your Pega application.

During the onboarding process, Pega helps you to determine what node types you need. The method of node assignment depends on your deployment:

  • In on-premises environments, you and your support team determine which node types you need. You assign the node types to nodes when you start the nodes.

    For details on assigning nodes with node types on-premises, see Assigning node types to nodes for on-premises environments.

  • In Pega Cloud environments, Pega Cloud services assigns nodes with node types during provisioning.
  • In client-managed environments, the node type is determined by the configuration settings of your deployment. In each tier, the node type is set using the nodeType parameter. For details, seeTiers of a Pega deployment.

You can associate the following work resources with one or more node types:

  • Job Schedulers
  • Queue Processors
  • Agents
  • Listeners

For example, to avoid performance issues caused by intensive background processing on the same node, you can dedicate a node type for user requests, and disable background jobs on that node type.

Job Schedulers and Queue Processors require an association with a node type when you create these resources. For more information, see Creating a job scheduler rule and Creating a queue processor rule.

  • Previous topic Updating dynamic system settings by using Java methods
  • Next topic Node types for Pega Cloud services environments

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