HP Systems Insight Manager 7.2 Technical Reference Guide

operator="ge" value="7.2" />
</include-filter>
The include filter does not need to include all attributes allowed. If more than one attribute is
included, the conditions are logically concatenated using the AND operator. An attribute cannot
appear in an include filter more than once, except that an attribute having a version number value
can appear twice if one operator is lt and the other operator is ge. For example:
<include-filter type="protocol">
<node-filter name="WBEM"
operator="lt" value="2.6" />
<node-filter name="WBEM"
operator="ge" value="2.4" />
</include-filter>
This would specify that the tool should be shown for any collection of systems supporting the WBEM
protocol version 2.4 or higher, but less than 2.6.
If a tool contains more than one include filter of different types, the conditions of the filters are
logically concatenated using the AND operator. A tool with both operating system and hardware
dependencies can use the filter:
<include-filter type="os">
<node-filter name="OSName"
operator="eq" value="LINUX" />
</include-filter>
<include-filter type="hardware">
<node-filter name="DeviceSubType"
operator="eq" value="HPVectra" />
</include-filter>
If a tool contains more than one include filter of the same type, the conditions of the filters are
logically separated using the OR operator. A tool available on two different operating systems can
specify:
<include-filter type="os">
<node-filter name="OSName"
operator="eq" value="LINUX" />
</include-filter>
<include-filter type="os">
<node-filter name="OSName"
operator="eq" value="HPUX" />
</include-filter>
This tool could be launched on any collection of systems using Linux or HP-UX.
Tool filtering depends on the attributes having a value defined on the systems selected. For the os
filter type, if any attribute being filtered on is not defined for a system, the system is assumed to
have the value required by the filter. Thus, a system with none of the os attributes specified by a
tool filter are assumed capable of running the tool. For the hardware filter type, the above statement
is true in the case of the Model attribute. But for the DeviceType and DeviceSubType attributes, the
tool filter applies only for known values on the selected systems. The protocol filter type requires
that the protocol must exist on the system before the operators can be applied. This means that the
neq and nct operators also depend on the system to have that protocol. The other filter also works
like the protocol filter such that the attribute being filtered upon must exist on the system before the
operators can be applied. If a tool uses the other and/or protocol filters, then at least one system
must contain the filterable attributes for the tool to appear in the GUI.
Custom tools reference 473