Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Reference 11 g Release 1 (11.1.1.5.0) |
1. Directory Server Enterprise Edition File Reference
Software Layout for Directory Server Enterprise Edition
Directory Proxy Server Instance Default Layout
Part I Directory Server Reference
4. Directory Server LDIF and Search Filters
6. Directory Server Monitoring
7. Directory Server Replication
8. Directory Server Data Caching
11. Directory Server Groups and Roles
12. Directory Server Class of Service
14. Directory Server Internationalization Support
Part II Directory Proxy Server Reference
15. Directory Proxy Server Overview
16. Directory Proxy Server Load Balancing and Client Affinity
17. Directory Proxy Server Distribution
18. Directory Proxy Server Virtualization
19. Connections Between Directory Proxy Server and Backend LDAP Servers
20. Connections Between Clients and Directory Proxy Server
21. Directory Proxy Server Client Authentication
22. Security in Directory Proxy Server
23. Directory Proxy Server Logging
This section describes the file layout you find after creating a Directory Server instance. The instance-path is the file system path where you created the instance.
NSS certificate mapping configuration file.
Default data backup directory.
Each directory database backup is held in its own file system directory. The name of the backup directory corresponds to the time and date of the backup.
Server configuration file, not intended to be edited directly.
LDAP schema configuration files. See dirserv(5dssd).
Default server database files directory. When a suffix has been created, the following database files are stored in this file system directory.
Files used internally by the database. Do not move, delete, or modify these files.
File that identifies the version of the database.
File used to store information about the state of the database, used to determine whether database recovery is required.
Files used to store the database transaction logs.
Files that store your directory suffix information. The directory name is derived from the suffix name, such that the database for a suffix identified by DN dc=example,dc=com is stored in a file system directory named example.
For every index defined in the database, the suffix directory contains a file with a name of the form suffix_indexedAttr.db3, such that an index of CNs for dc=example,dc=com has file name example_cn.db3.
Suffix directories also contain a file named suffix_id2entry.db3. The suffix_id2entry.db3 file contains the directory database entries.
If necessary, all index files can be rebuild from the suffix_id2entry.db3 file. To recreate the index files, reindex the suffix.
Lock files stored here in subdirectories exports/, imports/, and server/ prevent simultaneous operations from conflicting with each other. The lock mechanisms allow one server instance to run at a time. The lock mechanisms also permit only one dsadm import (offline import) operation at a time. As a result, no export or server instance operations can be run during import.
The lock restriction does not however apply to dsconf import (online import) operations. Multiple online imports can run at the same time.
Default server logs directory. The following files are stored here.
This file records information about client access to Directory Server. For detail about access logs, see Access Logs.
This file records information about modifications to Directory Server data. For detail about audit logs, see Audit Logs.
By default, server core files are dumped here during a crash.
This file records errors, warnings, and informational messages logged during Directory Server operation. For detail about errors logs, see Error Logs.
This file holds the process identifier of the running server.
DSMLv2 schema file.
SOAP schema location for DSMLv2.
Default dictionary file used for strong password checks.
Plug-in signatures directory, not intended to be used directly.
Server runtime files directory, not intended to be used directly.