NAME | Description | Attributes | See Also
Syntax |
enumeration |
Default value |
none |
Must be set |
No |
Is modifiable |
Yes |
Is multivalued |
No |
Requires restart |
Yes |
This property specifies the built-in algorithm used to distribute operations to data views that have the same base DN.
This property can take the following values in addition to the default.
Requests are distributed to data views based on the match between the parameters of the requests and one or more patterns.
Requests are distributed to data views based on the lexicographic value of the RDN specified in the request. Lexicographic bounds are taken from the value of the first RDN beneath the base DN of the data view.
Requests are distributed to data views based on the numeric value of the RDN specified in the request. The numeric value is taken from the value of the first RDN beneath the base DN of the data view.
Requests are distributed to data views based on the role of the data view in replication. The algorithm forces all write operations to be sent to all data sources in the data source pool, and all read operations to be sent to a single data source.
The default behavior for this property is as follows: No distribution algorithm is enabled
This property is used to configure the following features:
A JDBC data view enables you to make a relational database accessible to LDAP client applications.
A join data view is an aggregation of multiple data views. The current release of Directory Proxy Server supports the aggregation of two data views into one join data view.
An LDAP data view exposes data in an LDAP server to a client request and specifies the data source pool that responds to the request.
An LDIF data view allows data in an LDIF file to be present to LDAP applications as if it were LDAP data.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE |
ATTRIBUTE VALUE |
---|---|
Availability |
SUNWldap-proxy |
Stability Level |
Evolving |
dpconf(1M)
NAME | Description | Attributes | See Also