Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Administration Guide 11g Release 1 (11.1.1.5.0) |
Part I Directory Server Administration
2. Directory Server Instances and Suffixes
3. Directory Server Configuration
6. Directory Server Access Control
7. Directory Server Password Policy
8. Directory Server Backup and Restore
9. Directory Server Groups, Roles, and CoS
10. Directory Server Replication
13. Directory Server Attribute Value Uniqueness
15. Directory Server Monitoring
Part II Directory Proxy Server Administration
16. Directory Proxy Server Tools
17. Directory Proxy Server Instances
19. Directory Proxy Server Certificates
20. Directory Proxy Server Load Balancing and Client Affinity
21. Directory Proxy Server Distribution
22. Directory Proxy Server Virtualization
Creating and Configuring LDIF Data Views
To Configure an LDIF Data View
Defining Access Control on Virtual Data Views
To Define a New ACI Storage Repository
To Configure Virtual Access Controls
Defining Schema Checking on Virtual Data Views
Creating and Configuring Join Data Views
To Configure a Join Data View to Enable Referencing of a Data View by Multiple Join Data Views
To Configure the Secondary View of a Join View
Creating and Configuring JDBC Data Views
To Configure JDBC Tables, Attributes, and Object Classes
Defining Relationships Between JDBC Tables
Joining an LDAP Directory and a MySQL Database
Configuring and Testing the LDAP Data View
Configuring and Testing the JDBC Data View
Creating and Testing the Join Data View
Joining Multiple Disparate Data Sources
Client Application Requirements
Aggregate Data From the HR LDAP Directory and the Administration LDIF File
Add Data From Company 22 to Example.Com's DIT by Renaming the DN
Add Company 22's Data to the HR Data
Enable LDAP Clients to Access the Payroll Data in an SQL Database
23. Virtual Data Transformations
24. Connections Between Directory Proxy Server and Back-End LDAP Servers
25. Connections Between Clients and Directory Proxy Server
26. Directory Proxy Server Client Authentication
27. Directory Proxy Server Logging
28. Directory Proxy Server Monitoring and Alerts
Part III Directory Service Control Center Administration
The Coordinator data view has an ordered list of data views to coordinate. When the Coordinator data view receives a request, it sends the request to its coordinated data views in the right order, which is defined by the order used in the CLI to specify the coordinated data view. The Coordinator data view sends the request to coordinated data view as defined by the routing policy and in the end returns the result(s) to the client. For more information, see Coordinator Data Views in Oracle Directory Server Enterprise Edition Reference.
The Coordinator data view supports the following routing policies:
first-match: stops sending the request at first match
all-candidates: sends the request to all the coordinated data views
mirror: sends all the requests to first coordinated data view but the write requests are sent to all the coordinated data views.
Note - All the data views coordinated by a coordinator data view must have the same view base identical with the view base of the coordinator data view.
You cannot use DSCC to perform this task. Use the command line, as described in this procedure.
The data views must exist before the Coordinator data view can be created. The data views can be any type of data view, including an LDAP data view, LDIF data view, JDBC data view, or another join data view.
$ dpconf create-coordinator-data-view -h host -p port VIEW_NAME \ COORDINATED_VIEW [COORDINATED_VIEW...] SUFFIX_DN
The following command creates a Coordinator data view, view_com, using two data views.
$ dpconf create-coordinator-data-view -h host -p port view_com \ first_view second_view dc=com
$ dpconf list-coordinator-data-views -h host -p port
In this case, the above command displays view_com.
You cannot use DSCC to perform this task. Use the command line, as described in this procedure.
$ dpconf get-coordinator-data-view-prop -h host -p port VIEW_NAME
The default properties of a join data view are as follows:
alternate-search-base-dn : "" attr-name-mappings : none base-dn : "" contains-shared-entries : - coordinated-data-view : first_view coordinated-data-view : second_view 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 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-object-search-filter : all pattern-matching-dn-regular-expression : all pattern-matching-one-level-search-filter : all pattern-matching-subtree-search-filter : all process-bind : - replication-role : master routing-policy : all-candidates viewable-attr : all except non-viewable-attr writable-attr : all except non-writable-attr
For example, the following commands lists the coordinated-data-views property of the specified Coordinator data view.
$ dpconf get-coordinator-data-view-prop VIEW_NAME coordinated-data-view coordinated-data-view : first_view coordinated-data-view : second_view
$ dpconf set-coordinator-data-view-prop -h host -p port VIEW_NAME PROP:VAL \ [PROP:VAL...]
For example, add more coordinated data views to the Coordinator data view using the following command:
$ dpconf set-coordinator-data-view-prop -h host -p port view_com \ coordinated-data-view+:third_view coordinated-data-view+:fouth_view
As per the order of the coordinated data views specified in the above command, the coordinated data views are send in the following order:
$ dpconf get-coordinator-data-view-prop VIEW_NAME coordinated-data-view coordinated-data-view : first_view coordinated-data-view : second_view coordinated-data-view : third_view coordinated-data-view : fourth_view
$ dpconf set-coordinator-data-view-prop -h host -p port view_com \ routing-policy:first-match
For more information, see routing-policy(5dpconf).
For information about restarting Directory Proxy Server, see To Restart Directory Proxy Server.