Server User Manual
Mapping the Connection Pool Conguration
Directory Proxy Server 5 can be congured to reuse existing connections to the backend LDAP
servers. This can provide a signicant performance gain if the backend servers are on a Wide
Area Network (WAN). In Directory Proxy Server 6.0, this functionality is provided with
connection pools that are congured in the backend server itself. For more information, see
Chapter 20, “LDAP Data Sources and Data Source Pools,” in Sun Java System Directory Server
Enterprise Edition 6.0 Administration Guide.
In Iplanet Directory Access Router 5.0 (IDAR) these conguration attributes are stored under
ids-proxy-con-Config-Name=name,ou=global,ou=pd2,ou=iDAR,o=services. In Directory
Proxy Server 5.2, these conguration attributes are stored under
ids-proxy-con-Config-Name=user-dened-name,ou=system,ou=dar-config,o=netscaperoot.
The following table provides a mapping between Directory Proxy Server 5 connection
conguration attributes and the corresponding Directory Proxy Server 6.0 properties.
TABLE 6–3 Mapping of Connection Pool Attributes
Directory Proxy Server 5 Attribute Directory Proxy Server 6.0 Property
ids-proxy-con-connection-pool No equivalent
ids-proxy-con-connection-pool-interval The connection pool grows automatically to a
congured maximum. The maximum is congured
by setting the following properties of an LDAP data
source:
num-bind-init
num-bin-incr
num-bind-limit
num-read-init
num-read-incr
num-read-limit
num-write-init
num-write-incr
num-write-limit
For information about setting LDAP data source
properties, see “To Congure an LDAP Data Source”
in Sun Java System Directory Server Enterprise
Edition 6.0 Administration Guide.
ids-proxy-con-connection-pool-timeout backendMaxReadWaitTimeInMilliSec
Mapping the Connection Pool Conguration
Chapter 6 • Migrating Directory Proxy Server 87
Sun Condential: Registered