File layout
DS software installs and creates the following files and directories. The following table is not meant to be exhaustive.
File or directory | Description |
---|---|
|
Directory intended for local backup data. |
|
Windows command-line tools. |
|
Linux command-line tools. |
|
Backend for replication changelog data. |
|
Directory added to the server classpath, permitting individual classes to be patched. |
|
(Optionally) immutable server configuration files. |
|
Templates for configuring external Common Audit event handlers. |
|
LDIF representation of current DS server configuration. |
|
Keystore and password ( |
|
Templates for use with the |
|
Default directory for backend database files. For details, refer to Data storage. |
|
Directory for additional .jar files used by your custom plugins. If the instance path is not the same as the binaries,
copy additional files into the |
|
Working directory used when importing LDIF data. |
|
Directory for saving LDIF export files. |
|
License information. |
|
Scripts and libraries shipped with DS servers. |
|
Directory for custom plugins. |
|
Lock files that prevent more than one process from using the same backend. |
|
Access, errors, and audit logs. |
|
Contains the process ID for a running server. |
|
DS splash logo. |
|
About DS servers. |
|
Samples for use with DS servers, such as:
|
|
Linux setup tool. |
|
Windows setup tool. |
|
SNMP support files. |
|
Templates for setting up a server instance. |
|
Profile scripts to configure directory servers for specific use cases. |
|
Linux upgrade tool. |
|
Windows upgrade tool. |
|
Files the DS server writes to during operation. Do not modify or move files in the |
|
Snapshots of the main server configuration file, The server writes a compressed snapshot file when the configuration is changed. |
|
The most recent version of the main server configuration file that the server successfully started with. |
(1) The samples are provided on an "as is" basis. ForgeRock does not guarantee the individual success developers may have in implementing the samples on their development platforms or in production configurations.
For details about how to try the samples, refer to the accompanying README.md
files.