Oracle Fusion Middleware Administration Guide for Oracle Directory Server Enterprise Edition

ProcedureTo Configure a Join Data View

You cannot use DSCC to perform this task. Use the command line, as described in this procedure.

  1. View the properties of a join data view.

    $ dpconf get-join-data-view-prop -h host -p port view-name

    The default properties of a join data view are as follows:

    allow-heuristic-search                      :  true  
    allow-partial-search                        :  false  
    alternate-search-base-dn                    :  -  
    attr-name-mappings                          :  none  
    base-dn                                     :  suffixDN  
    contains-shared-entries                     :  false  
    custom-distribution-algorithm               :  none  
    description                                 :  -  
    distribution-algorithm                      :  none  
    dn-join-rule                                :  none  
    dn-mapping-attrs                            :  none  
    dn-mapping-source-base-dn                   :  none  
    excluded-subtrees                           :  -  
    filter-join-rule                            :  none  
    is-enabled                                  :  true  
    is-read-only                                :  false  
    is-routable                                 :  true  
    join-rule-control-enabled                   :  false  
    lexicographic-attrs                         :  all  
    lexicographic-lower-bound                   :  none  
    lexicographic-upper-bound                   :  none  
    non-viewable-attr                           :  none  
    non-writable-attr                           :  none  
    numeric-attrs                               :  all  
    numeric-default-data-view                   :  false  
    numeric-lower-bound                         :  none  
    numeric-upper-bound                         :  none  
    pattern-matching-base-dn-regular-expression :  all  
    pattern-matching-base-object-search-filter  :  all  
    pattern-matching-dn-regular-expression      :  all  
    pattern-matching-one-level-search-filter    :  all  
    pattern-matching-subtree-search-filter      :  all  
    primary-view                                :  primary-view  
    process-bind                                :  -  
    replication-role                            :  master  
    request-grouping-size                       :  5
    secondary-view                              :  secondary-view  
    viewable-attr                               :  all except non-viewable-attr  
    vlv-control-enabled                         :  false  
    vlv-control-page-size                       :  1k  
    vlv-control-sorting-attr                    :  objectclass  
    writable-attr                               :  all except non-writable-attr  
  2. Change one or more of the properties that are listed in Step 1.

    $ dpconf set-join-data-view-prop -h host -p port view-name property:value \
     [property:value ... ]

    For example, to change the primary data view of a data source to myLDAPDataView, use the following command:

    $ dpconf set-join-data-view-prop -h host1 -p 1389 -D cn="Proxy Manager" \
     myJoinDataView primary-view:myLDAPDataView

    If vlv-control-enabled is set to true, Directory Proxy Server uses VLV control in search requests when it contacts the primary data view.

  3. When a join data view is configured, set viewable-attr and writable-attr properties on primary data view and secondary data view.

    Setting of these properties helps in splitting the search filters appropriately on primary and secondary data views. Otherwise, there might be discrepancies in search results when search filter contains attributes from secondary data view.

  4. If necessary, restart the instance of Directory Proxy Server for the changes to take effect.

    For information about restarting Directory Proxy Server, see To Restart Directory Proxy Server.