This chapter contains important, product-specific information available at the time of release of Directory Server Resource Kit.
This chapter includes the following sections:
This section provides an overview of Directory Server Resource Kit components.
Directory Server Resource Kit gives you tools for working with directory services in the laboratory, during deployment, and in the data center.
Use the ldapsubtdel(1) tool to delete an entire directory subtree over LDAP with one command.
Use the following tools to test directory access through DSML v2 when designing, developing, and testing web applications:
The dsmlmodify(1) command to add, delete, modify, rename, and move entries
The dsmlsearch(1) command to find and read entries
Use the following tools to measure bind, read, and write performance when accessing the directory over LDAP:
The authrate(1) command to measure LDAP bind performance
The modrate(1) command to measure LDAP write performance
The searchrate(1) command to measure LDAP read performance
Use the following tools to generate sample LDIF for sizing and tuning. Use the tools also to transform, sort, and filter LDIF for interoperability:
The ldifxform(1) command to transform, sort, and filter LDIF
The makeldif(1) command to generate sample LDIF
Use the logconv(1) command to examine how clients use directory services and to generate recommendations for indexing.
You can decide to set up and run Directory Server Resource Kit tools on the same system as your directory server, or on another system. The decision depends on your work environment. The decision also depends on the stage of deployment you have reached. The following questions and answers help you decide where to use Directory Server Resource Kit.
Question:Are you working to evaluate or to demonstrate directory technology prior to developing directory services?
Answer:For convenience, install and use Directory Server Resource Kit on the same system as your directory.
Question:Are you working to develop directory client applications or plug-ins?
Answer:For convenience, install and use Directory Server Resource Kit on the same system as your directory.
Question:Are you working to test directory performance characteristics?
Answer:The only command that you must run on the system that provides directory services is the idsktune command, which generates system-specific tuning recommendations.
Answer:Avoid perturbing the system that you measure by installing Directory Server Resource Kit and running commands, except for idsktune, on other systems.
Get accurate directory performance measurements by running clients such as authrate, modrate, and searchrate on separate systems. You can improve accuracy by carefully controlling the processes that run on the system you measure. You can also improve accuracy by controlling the sample data that you store in the directory. You can generate controlled data with makeldif.
Question:Have you already deployed your directory into the data center?
Answer:Avoid perturbing the deployed system by installing Directory Server Resource Kit and running commands on other systems.
Run analysis with logconv, LDIF conversions with ldifxform, and other operations from other systems as well.
This section lists the bugs fixed since the last release of Directory Server Resource Kit.
The searchrate command should have an option to specify a timeout.
Fix usage for authrate.
Fix usage for searchrate.
Fix usage for modrate.
The ldifxform command does not properly convert when used with to=cs.
The ldapsubtdel command should allow a password to be read from a file.
The authrate command should signal bind errors.
The dsmlsearch command should handle LDAP filter string syntax.
Fix usage for dsmlmodify.
The ldifxform command crashes on Windows systems when using the -c to=ascii option.
The logconv -d option generates a divide by zero error.
This section lists known problems and limitations at the time of release.
searchrate crashes on Windows systems when using multiple threads.
modrate crashes on Windows systems when using multiple threads.
authrate crashes on Windows systems when using multiple threads.
The dsmlsearch command -D option takes an HTTP user ID rather than a bind DN.
To work around this issue, provide the user ID that is mapped to a DN in Directory Server.
NameFinder has been seen to fail to deploy in Application Server on Windows systems.
NameFinder has been seen to throw a page not found error after deployment.
To work around this issue, rename nsDSRK/nf to nsDSRK/NF.
Cannot add more than two users to My Selections list in NameFinder.
NameFinder search should fetch entries for values other than Last Name, First Name, Email, and Given Name.
NameFinder search should allow searches for groups.
Killing modrate and searchrate launcher does not kill actual modrate and searchrate processes respectively.