HP SIM V5.1 User Guide (356920-009, January 2007)

The include filter need not include all attributes allowed. If more than one attribute is included, the conditions
are logically AND'd together. 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
AND'd together. A tool with both operating system and hardware dependencies could 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 OR'd
together. A tool available on two different operating systems could 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 being filtered 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 will apply only for
Custom tools 303