Reference Guide › File Structure and File Formats › File Structure

File Structure

After installation, the CA Directory files use the following directories:

DXHOME

|__ bin
|__ config 
|      |__ access
|      |__ autostart (UNIX only)
|      |__ knowledge
|      |__ limits
|      |__ logging
|      |__ replication
|      |__ schema
|      |__ servers
|      |__ settings
|      |__ ssld
|__ data
|__ install  (UNIX only)
|__ logs
|__ pid       
|__ samples
|__ uninstall  (UNIX only)

• bin

  Holds all binary executables and batch files for CA Directory.

• config

  Holds the current configuration files, and some Readme files for your reference. DSAs always start with the configuration information stored in this directory. We recommend that you give read-only permissions to files in these directories to prevent accidental overwriting.

  Each subdirectory contains the configuration file(s) that deal with a component of the configuration.

  • access

    Holds configuration files that specify access control rules.

  • autostart

    (UNIX only) Tracks the DSAs that must start at the same time as the operating system.

  • knowledge

    Holds the knowledge files for DSAs if DXmanager is not used.

  • limits

    Holds configuration files that specify administrative limits, such as size limits and time limits.

  • logging

    Holds configuration files that specify trace levels and log file names.

  • replication

    Holds configuration files that specify replication agreements.

  • schema

    Holds configuration files that specify schema definitions.

  • servers

    Holds initialization files that specify startup information. An initialization file must exist for each DXserver on the host computer.

  • settings

    Holds configuration files that specify operational settings and controls.

  • ssld

    Holds .pem certificates for trusted CA and server entities.

• data

  Holds the data store file (.db) for each DSA.

• install

  (UNIX, for CA Directory use only) Contains installation files and environment information.

• logs

  Holds all log output for CA Directory. You can specify another directory.

• pid

  (CA Directory use only) Contains information about currently running processes. The pid directory is empty immediately after an installation, but when the services are run, files are created in that directory.

• samples

  Contains demonstration utilities and test script files. Each sample has its own subdirectory and an associated Readme file.

• uninstall

  (UNIX only) Contains uninstallation scripts.