Service manual

149
Chapter 9
Managing Use of Other Resources
After optimizing cache size, attribute value indexing, and log management, it may
prove useful totune how Directory Server limits resources made available to client
applications, and how Directory Servermakesuse of system resources. Itmay also
prove useful to reconfigure and even disable some features offered as Directory
Server plug-ins.
Limiting Resources Available to Clients
Default configuration may allow client applications to use more Directory Server
resources than are actually required. This may leave the door open to accidentally
or intentionally abusive client applications negatively impacting server
performance, by opening many connections then leaving them idle or unused,
launching costly and unnecessary unindexed searches, or storing enormous and
unplanned for binary attribute values in the directory.
In some deployment situations, it is not advisable to modify the default
configuration. For deployments in which you opt not to change the configuration
attribute values mentioned in this section, consider using Sun ONE Directory
Proxy Server software to set limits externally, and to help protect against denial of
service attacks.
Insomedeploymentsituations, oneinstance of DirectoryServermust support both
directory-intensive client applications such as messaging servers and occasional
directory clients such as user mail applications. In such situations, consider using
bind DN-based resource limits as described in the Sun ONE Directory Server
Administration Guide to raise individual limits for directory-intensive applications.
The recommendations in Table 9-1 address settings for limiting resources available
to all client applications. These limits do not apply to the Directory Manager user,
so ensure client applications do not connect as the Directory Manager user.