Skip to main content

Node types for on-premises environments

Suggest edit Updated on May 11, 2022

Pega Platform provides a set of node types which you can assign to a node in your system. You can associate these node types with resources in order to optimize performance.

If you do not assign a node type to a node, Pega Platform, by default, associates the node with four Pega-provided node types: "BackgroundProcessing,Search,Stream,WebUser".

Pega-provided node types

You can use the following Pega-provided node types to segregate work in your Pega application:

  • BackgroundProcessing – Performs background utility processing.
  • BIX – Performs Business Intelligence Exchange (BIX) data extractions for clients with BIX subscriptions.
  • Search – Performs search indexing using Elasticsearch.
  • Stream – Performs Kafka-based stream processing for queue processors in any Pega. application, as well as for Pega Customer Decision Hub and Pega Decision Strategy Management (DSM) subscriptions.
  • WebUser – Performs web application processing.
  • Universal – Performs processing for all of the job schedulers, queue processors, agents, and listeners on these nodes. As a best practice, avoid using the Universal node type in a production environment.
  • RunOnAllNodes – Associate this node type option with a work resource that you want to run on all the node types. This node type cannot start nodes.

Decision Strategy Manager node types

In Pega Decision Strategy Manager (DSM), you can use the following node types to further segregate DSM work in your Pega application:

  • ADM – Runs the Adaptive Decision Manager (ADM) service.
  • Batch – Runs DSM background processes.
  • DDS – Runs the Decision Data Store (DDS) service for Cassandra-related data processing.
  • RealTime – Runs realtime processes such as processing user requests in the context of DSM.
  • RTDG – Runs the Real Time Data Grid (RTDG) service.

Pega Customer Decision Hub and Pega Marketing node types

To use Pega Customer Decision Hub or Pega Marketing, you need to enable the following Custom node types for email and data flow services:

  • Custom1– used by the PegaMKTEmail decisioning dataflow service
  • Custom2 – used by the PegaMKTSMS decisioning dataflow serviceMarketing
  • Previous topic Node types for client-managed cloud environments
  • Next topic Assigning node types to nodes for on-premises environments
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us