NAME | Description | Attributes | See Also
Syntax |
string |
Default value |
none |
Must be set |
No |
Is modifiable |
Yes |
Is multivalued |
No |
Requires restart |
No |
This property defines the relationship between the primary and secondary data views.
A filter join rule indicates how an entry should be retrieved from the secondary data view based on something in the primary data view.
For example, uid=\${primary-view-name.uid} is a valid property value.
To be taken in account by the server, this property must be set on join data view if the join-rule-control-enabled property for join data view is set to true; otherwise it must be set on secondary data views.
A filter join rule takes the form of an LDAP filter that is used to construct an attribute from one or more attributes from the primary data view.
The default behavior for this property is as follows: No filter join rule is applied
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 JDBC table is created for each relational database table that will be used in the JDBC data view. When you create a JDBC table you specify the name of the table in the relational database, and the name you want to assign to this table in the JDBC data view.
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