Associating an agent with a node type in a locked ruleset

Use Admin Studio to add a new association with a node type to an agent in a locked ruleset.

Note: When you add a node type to an agent in this way, the association is not created in the Agent definition.
  1. In the navigation panel of Admin Studio, click Resources > Node classification.
  2. Click New association for the agent to which you want to add a node type.
  3. Select a node type from the list. The agent runs for all the nodes that are started with the node types associated with the agent, including the node type that you added.
    Note: The following list contains the node types that Pega Platform provides by default. If you create your configurable node types, you can see only these configurable node types in the list.
    • Search – The agent runs on a search node for search jobs.
    • WebUser – The agent runs on a web user node for web user jobs.
    • BIX – The agent runs on a BIX node for BIX jobs.
    • BackgroundProcessing – The agent runs on a background node.
    • Custom1, Custom2, Custom3, Custom4, Custom5 – The agent runs on the selected custom node.
    • RunOnAllNodes – The agent runs on all the nodes in the cluster that are started with any node type, regardless of the node classification.
    After you add a new node type to the agent, the corresponding agent schedule is updated. To make this change permanent, enable the agent on the Agent definition in Dev Studio.
The agent runs for all the nodes that are started with that node type configuration or for all nodes in the cluster that are started with any node type in the case of RunOnAllNodes type.
Note: If an agent is enabled on the RunOnAllNodes node type and also on other node types, the agent-specific settings such as Pattern, Interval, Access group, and Bypass activity authentication are considered from other node types instead of the RunOnAllNodes node type. For example, if an agent is enabled on the Web User node type and the RunOnAllNodes node type, and the node started with Web User node type, the agent-specific settings are considered from the Web User node type instead of the RunOnAllNodes node type.
To edit an association, click the node type. The system opens the agent rule in Dev Studio.