When you have specified the information described in "Initial Configuration Properties", you have a server with a default configuration. It has the following characteristics:
|
|
Port used for Lightweight Directory Access Protocol (LDAP) communications is 389 |
|
|
Port used by the LDAP/HTTP gateway is 1760 |
|
|
Searches are limited to 5000 entries or 3600 seconds (one hour). A search stops when the first of these limits is reached |
|
|
Schema is checked for each directory operation. |
|
|
Data store is in /var/opt/SUNWconn/ldap/dbm |
|
|
Log files are stored in /var/opt/SUNWconn/ldap/log |
|
|
1000 entries are cached. A cache file of 100,000 bytes is created for each data store. |
|
|
Default indexing is used, as described in "idxgen" |
|
|
Passwords are stored in encrypted format |
|
|
Alias dereferencing on bind operation is enabled |
|
|
Directory contains no entries (the name and password for the administrator are stored in the configuration file) |
|
|
Default access control is used, as described in the table located in the following section "Configuring Access Control." |
|
|
No knowledge references apply to other servers |
IMTA is distributed with a default job controller configuration that is suitable for most sites. This default configuration defines a single queue named DEFAULT with a job limit of 4 and a capacity of 200. As the first queue in the file, DEFAULT is used by all IMTA channels that do not specify a queue using the queue channel keyword. (In the default configuration, the queue DEFAULT is actually the only queue.) In addition, the supplied job controller configuration file includes channel definitions for all of the supplied and supported IMTA channels.
The job controller configuration file is required. If it is not present or its contents are incorrect, the job controller does not start. There is no need to modify the configuration file unless you choose to add queues, modify queue parameters, or add processing information for locally developed channels.