Mapping agents to node types

To effectively use node classifications, you must map agents to node types. When you start a node with a specific node type, the node runs only the agents that are associated with that node type.

To map agents to node types in an open ruleset, complete the following steps:

  1. Open an agent rule form in one of the following ways:
    • From the Node Classification landing page
      1. Click Designer Studio > System > Operations > Node Classification.
      2. On the Agents tab, click the name of an agent in the Associated node types column to open its rule form.
    • From the Explorer panel
      1. Click Records > SysAdmin > Agents.
      2. Click the name of an agent in the list to open its rule form.
  2. On the Schedule tab, click the Gear icon in the Associated with Node type column to open the condition builder for the agent.
  3. Select the check box next to each node type that you want to map to the agent. Only the allowed node types are shown. The agent runs for all the nodes that are started with the node type or types that you select.
    • 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.
    Note: By default, an agent is mapped to the background node type.
  4. Optional: Clear the check box next to each node type that you no longer want to be associated with the agent.
  5. Click Submit.
  6. Ensure that the Enabled check box that corresponds to the agent that you want to map to the node type is selected.
  7. Click Save.
    Note: The agent schedule is created during the node startup, if it does not exist.
  8. Optional: Create an agent schedule if you need to customize it and the agent schedule is not created yet.
    On the Node Classification landing page, on the Agents tab, in the Agent schedule column, click +Create for the node type that is associated with the agent for which you want to create an agent schedule.

    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:
    • You can associate an agent with a node type in a locked ruleset, by adding a new association directly on the Node Classification landing page.
    • 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.