Given the following properties file that is saved as <server-root>/bin/ 
bindDN=cn=Directory\ Manager 
The Directory Proxy Server locates a command-line option in a specific priority order.
  1. All options presented with the tool on the command line take precedence over any options in any properties file. In the following example, the client request is run with the options specified on the command line (port and baseDN). The command uses the bindDN and bindPassword arguments specified in the properties file.
    $ bin/ldapsearch --port 2389 --baseDN ou=People,dc=example,dc=com \ 
      --propertiesFilePath bin/ “(objectclass=*)”
  2. Next, if you specify the properties file using the --propertiesFilePath option and no other command-line options, the Directory Proxy Server uses the specified properties file as follows:
    $ bin/ldapsearch --propertiesFilePath bin/ \ 
  3. If no options are presented with the tool on the command line and the --noPropertiesFile option is not present, the Directory Proxy Server attempts to locate any default file in the following location:
    Assume that you move your file from <server-root>/bin to the <server-root>/config directory. You can then run your tools as follows:
    $ bin/ldapsearch "(objectclass=*)"

    The Directory Proxy Server can be configured so that it does not search for a properties file by using the --noPropertiesFile option. This options tells the Directory Proxy Server to use only those options specified on the command line. The --propertiesFilePath and --noPropertiesFile options are mutually exclusive and cannot be used together.

  4. If no default file is found and no options are specified with the command-line tool, then the tool generates an error for any missing arguments.