'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Use of subnodes > Create subnodes IBM Tivoli Monitoring, Version 6.3
Subnode configuration
When a subnode type is defined, a single configuration section is defined specifically for that subnode.
There are several ways that a subnode configuration section differs from other configuration sections:
- The set of properties in a subnode section can be duplicated, so there are multiple sets of properties. Each set of properties forms its own section. The layout of all sections is identical, but different values can be entered in each section.
In contrast, the properties in other sections (which are referred to as agent-level sections) are shown only one time during runtime configuration. They do not form subsections and cannot be duplicated or removed.
See Subnode configuration example for GUI and command-line examples of configuring subnodes.
For each copy of a subnode section that is created at runtime configuration, the agent creates a separate subnode instance. All of those subnode instances are of the same type.
- The property names in subnode sections can be duplicates of property names in agent-level sections. When duplicate names occur, the subnode property value overrides the agent-level property value.
- In IBM Tivoli Monitoring V6.2.1 and later, a subnode section can have default property values that apply to all instances of subnodes of that type. This feature makes it possible to have a three-level lookup of a single property value as follows:
- The agent obtains the property value from the subnode instance subsection.
- If no value is configured at the subnode instance level, the property value is obtained from the subnode default level.
- If no value is configured at either of those two levels, then the property value is obtained from an agent-level section.
See Subnode configuration example for GUI and command-line examples of configuring subnodes.
- Configure a subnode
Use the Subnode Configuration Overrides page to configure a subnode data source.
- Subnode configuration overrides
Use Subnode Configuration Overrides to override agent configuration properties with subnode-specific properties.
- Advanced subnode configuration
Use advanced subnode configuration to override an agent configuration property in a subnode.
- Configure a subnode from the command line
You can also configure a subnode using the command line.
- Subnode configuration example
How to configure a sample agent with one defined subnode.
- Subnodes and Windows data sources
Choose to include Windows Remote Connection properties in the agent or not.
- Subnodes and Script data sources
Subnode instance configuration properties are accessed in subnode scripts just as they are in agent-level scripts.
Parent topic:
Create subnodes