Filtering allows to select interesting parts of topology data by assigning a context to these CIs. This context allows to selectively apply mapping rules to CIs of the same context. All CIs that have no context attached will not be synchronized.
Note: The <Rules>
tag for filter mapping rules must not contain the Context attribute.
<Context>[Context Name]</Context>
In the following example, all CIs that are assigned to the type exch_spi_std_server_role
and that are below a CI with a type exch_spi_std_server
are assigned to the exchange
context.
Example:
<Mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../mapping.xsd"> <Rules> <Rule name="Exchange Server Role Filter"> <Condition> <And> <Exists> <XPathResult>ancestor::ci[omType='exch_spi_std_server'] </XPathResult> </Exists> <Equals> <OMType/> <Value>exch_spi_std_server_role</Value> </Equals> </And> </Condition> <MapTo> <Context>exchange</Context> </MapTo> </Rule> </Rules> </Mapping>