OVD 11g: How to Set Server Quota Enforcement Parameters Limits? How to Set OVD Server Capacity of Handling LDAP Requests Based on Hardware Specifications?
(Doc ID 1986852.1)
Last updated on MARCH 15, 2019
Applies to:Oracle Virtual Directory - Version 220.127.116.11 and later
Information in this document applies to any platform.
Using Oracle Virtual Directory (OVD) 11g with the default values regarding to the Server Quota Enforcement Parameters, i.e. Maximum Connections per Authenticated Subject, Maximum Connections per IP Address. (The defaults are Quota Enforcements Not enabled.)
There is an LDAP client (Peoplesoft in this case) connecting to the OVD server that keeps over 700 established connections. Not sure why that many connections (this is being investigated separately), but just would like to know the possibility to increase or decrease the OVD connection limit.
Is it possible to increase the value based on the server specification? If yes, how to formulate the new value based on the server specs?
Note: Not sure the parameter "Maximum Connections per IP Address" is even working, i.e., tested with a test java test client which keeps over 2000 established connections, and OVD server still seems ok.
Quota enforcement aside, interested in capacity planning based on the hardware limit. What is the maximum LDAP requests OVD can handle with its best tuned performance, with the only the limit from hardware?
In other words, based on the server hardware specs, what is the capacity that the OVD server can handle of LDAP requests? Or based on the server hardware specs, how many LDAP requests at maximum the OVD server can handle per minute or concurrently?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document