You can configure CA Directory using commands in text files. The text files contain commands that define how the DSA works. These commands are identical to the commands that can be entered from a DSA console.
Note: If you have DXmanager installed, use it to define the knowledge. It stores the knowledge in an XML file. Do not edit this file yourself: use DXmanager instead.
The different types of CA Directory configuration files are as follows. The file extensions for the text files are a convention to help people recognize the file types, and they are not mandatory.
|
File Type |
Extension |
Location |
How Many? |
What the File Contains |
How to Edit the File |
|---|---|---|---|---|---|
|
DSA Initialization files |
.dxi |
DXHOME/config/servers/ |
One for each DSA |
Contains the source commands that initialize a DSA. These commands to refer to .dxg and .dxc files in other config subdirectories. The name of the initialization file must be the same as the DSA name. When a DSA starts, it uses an initialization file named dsaname.dxi. |
In a text editor |
|
DSA configuration files |
.dxc |
|
As many as required |
Contain one or more commands that set configuration parameters. The knowledge file is one type of configuration file. |
In a text editor |
|
Group files |
.dxg |
|
As many as required |
Contain a series of source commands to group one or more .dxc files in the current directory. |
In a text editor |
|
Script files |
.dxs |
|
As many as required |
Contain commands supported by a DSA console. You usually use script files for testing. |
In a text editor |
|
DXmanager configuration file |
.xml |
|
One for each directory backbone |
Contains the topology and namespace partitions of the whole backbone, plus some configuration of each DSA. DXmanager uses this instead of knowledge files. This information is shared by all DSAs that are configured in DXmanager. |
This file is created by DXmanager. Never edit this file yourself: use DXmanager instead.
|
|
Copyright © 2013 CA.
All rights reserved.
|
|