Skip to main content

Associating an agent with a node type in a locked ruleset

Suggest edit Updated on May 11, 2022

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 pane of Admin Studio, click ResourcesNode 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: For a description of the node types that you can choose from, see Node types for on-premises environments. In addition, the value RunOnAllNodes runs the agent on all nodes.
    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.
Result: 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. What to do next: To edit an association, click the node type. The system opens the agent rule in Dev Studio.
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