$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#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 > Subnode configuration IBM Tivoli Monitoring, Version 6.3


Subnode configuration overrides

Use Subnode Configuration Overrides to override agent configuration properties with subnode-specific properties.

The example in (Configure a subnode) describes how to manage subnode configuration for automatically generated properties. Managing custom configuration properties is similar. Any custom configuration properties that are defined are displayed in the Subnode Configuration Overrides window.

Figure 1. Overriding custom configuration

When you copy or move a custom property from the subnode level to the agent-level, you are prompted for the section to place the property in. As shown in the (Figure 2). You can select an existing custom section, or enter the name of a new custom section.

Figure 2. Select Configuration Section window


Selecting subnode configuration properties

Without subnodes, all instances of a data source type share the configuration parameters. For example, all SNMP attribute groups connect to the same host using the same community name. With subnodes, each instance of a subnode can connect to a different host if the SNMP_HOST property is placed at the subnode level.

Selecting properties to be overridden at the subnode level is an important consideration when you are developing an agent. If too many properties are selected, the subnode configuration section becomes cluttered and difficult to manage. If too few properties are selected, then the agent functions might be limited when someone wants to vary a property from one subnode to the next.

The following properties cannot be copied to the subnode level. (All attribute groups in all subnodes and in the base agent must use the same SNMP version and JMX connection type):


Parent topic:

Subnode configuration

+

Search Tips   |   Advanced Search