Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. 1.2
  4. User Sync Client
  5. Configure the data integration file
  6. Data adapter configuration
  7. LDAP Hierarchy-based configuration—<hierarchyConfig>

LDAP Hierarchy-based configuration—<hierarchyConfig>

The <hierarchyConfig> node contains search filter definitions to create search filters for LDAP searches and transform definitions that direct the LDAP data adapter to transform the resulting hierarchy tree. The following XML segment shows an example hierarchy configuration: 
<!-- Hierarchy-based configuration example -->
   <hierarchyConfig>
      <filters>
        <filter type="xxx" inheritable="true">…</filter>
        <filter type="xxx" inheritable="false">…</filter>
        <filter type="xxx" inheritable="true">…</filter>
      </filters>
      <transforms>
        <transform type="xxx" inheritable="true">…</transform>
        <transform type="xxx" inheritable="false">…</transform>
      </transforms>
      <node name="IT Department">
        <filters>
          <filter type="xxx" inheritable="false">…</filter>
        </filters>
        <transforms>
          <transform type="xxx" inheritable="true">…</transform>
        </transforms>
        <node name="Web Team">
          <filters>
            <filter type="xxx" inheritable="false">…</filter>
          </filters>
          <transforms>
            <transform type="xxx" inheritable="true">…</transform>
          </transforms>
        </node>
      </node>
    </hierarchyConfig>
<hierarchyConfig>
: The <hierarchyConfig> node corresponds to the hierarchy root entry that is specified in the <adParameters> section. Each <node name="xxx"> corresponds to one of the LDAP root entry’s descendants whose common name is “xxx.” The hierarchy relationship between these nodes is defined by their relative position in the XML. The "name" attribute of each node should be the same as the common name of the corresponding LDAP entry. Tree branches can be missing, but if any child node appears in this hierarchy configuration, the tree path to the root node should be complete and the same as it is in the LDAP directory.
Each node can have its own filter and transform definitions which are placed in the tags <filters> and <transforms>. Do not copy the entire LDAP tree into this configuration section and define specific filters and transforms for all nodes. This configuration section is inheritance-based. By setting the appropriate attribute value, any filter or transform defined in any node can be inherited by its child nodes, and they take effect if they are applicable for a specific child node.
You should define non-inheritable, node-specific <filters> and <transforms> but define common <filters> and <transforms> in a high-level node and apply them throughout its sub-tree.