Associating an agent with a node type in a locked ruleset

From the Node Classification landing page, you can add a new association with a node type to an agent that is in the 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. Click Designer Studio > System > Operations > Node Classification.

2. On the Agents tab, 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.

• RunOnAllNodes – The agent runs on all the nodes in the cluster that are started with any node type, regardless of the node classification.

• 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.

• Custom1, Custom2, Custom3, Custom4, Custom5 – The agent runs on the selected custom node.

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. For more details, see Mapping agents to node types.

4. Optional: Remove the new association by editing the Agent schedule rule.

   1. In the Associated node type column, click the name of the node type associated to the agent that you modified.

   2. In the Enabled? column, clear the check box corresponding to the agent for which you want to remove the association with the node type.

   3. Click Save.

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.

Open topic with navigation