NAME | Description | Attributes | See Also
Syntax |
boolean |
Default value |
false |
Must be set |
No |
Is modifiable |
Yes |
Is multivalued |
No |
Requires restart |
No |
This property determines what should be done if an entry in a secondary data view is used by more than one entry in a primary data view.
This property is applicable to secondary data views only.
If it is set to TRUE, the secondary data view entry is deleted when the virtual entry is deleted. If the entry does not exist in the secondary data view, it is created when the virtual entry is created.
This property is true or false.
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