Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Reference 11 g Release 1 (11.1.1.5.0) |
1. Directory Server Enterprise Edition File Reference
Software Layout for Directory Server Enterprise Edition
Directory Server Instance Default Layout
Directory Proxy Server Instance Default Layout
Part I Directory Server Reference
4. Directory Server LDIF and Search Filters
6. Directory Server Monitoring
7. Directory Server Replication
8. Directory Server Data Caching
11. Directory Server Groups and Roles
12. Directory Server Class of Service
14. Directory Server Internationalization Support
Part II Directory Proxy Server Reference
15. Directory Proxy Server Overview
16. Directory Proxy Server Load Balancing and Client Affinity
17. Directory Proxy Server Distribution
18. Directory Proxy Server Virtualization
19. Connections Between Directory Proxy Server and Backend LDAP Servers
Connections Between Directory Proxy Server and Backend LDAP Servers
Opening and Closing Connections Between Directory Proxy Server and Backend LDAP Servers
Connection Pools Between Directory Proxy Server and Backend LDAP Servers
Forwarding Request From Directory Proxy Server to Backend LDAP Servers
Directory Proxy Server Configured for BIND Replay
Directory Proxy Server Configured for Proxy Authorization
Connections When Directory Proxy Server Is Configured for Proxy Authorization
Security Issues When Directory Proxy Server Is Configured for Proxy Authorization
Directory Proxy Server Configured to Forward Requests Without the Client Identity
Directory Proxy Server Configured to Forward Requests As an Alternate User
20. Connections Between Clients and Directory Proxy Server
21. Directory Proxy Server Client Authentication
22. Security in Directory Proxy Server
23. Directory Proxy Server Logging
This section describes how connections between Directory Proxy Server and backend LDAP servers are opened and closed. It also describes the use of connection pools for multiple client requests.
At startup, Directory Proxy Server opens a connection to each data source that is configured, and enabled.
When an error is detected on a connection, Directory Proxy Server closes the connection and tries to reestablish it immediately. If Directory Proxy Server cannot connect to a data source, the data source is considered unavailable. For more information about how Directory Proxy Server responds to failed connections, see Responding to the Failure of a Data Source.
Connections between Directory Proxy Server and backend LDAP servers are pooled for use with multiple client requests. Each data source can have one pool of SSL connections and one pool of non-SSL connections. The ssl-policy property of the data source and the is-ssl-mandatory property of the connection handler determine whether SSL is used when contacting the data source.
The number of connections that can be opened to a data source can be configured independently for BIND, READ, and WRITE operations. The same limit applies to SSL connections and to non-SSL connections.
The following properties can be configured for each data source and for each type of operation:
The initial number of connections made to the data source
If more than the initial number of connections are requested, the number of new connections made
The maximum number of connections that can be made to the data source
When BIND replay is configured, Directory Proxy Server attempts to reuse connections that have already been opened, to optimize performance. If a client opens an authenticated connection, the connection is taken from the BIND pool. Therefore, when BIND replay is used, the connection pool for BIND operations is used more than the connection pools for READ or WRITE operations. For more information about BIND replay, see Directory Proxy Server Configured for BIND Replay.
When a connection to a data source is not used for 5 minutes, the connection is removed from the pool.