Previous | XML Configuration Files | Next |
The domains directory under the OpenFusion installation directory contains the XML files that record the current configuration of the OpenFusion installation. The domains directory structure maps directly to the Object Hierarchy in the Administration Manager, so a directory exists for each domain, node, Service, Singleton, and Java Object. The directory must have exactly the same name as the domain, node, Service, Singleton, or Java Object it represents.
For example, the localhost node in the Administration Manager's default Object Hierarchy is represented by the following directory structure:
<INSTALL>/domains/OpenFusion/localhost
where <INSTALL> is the OpenFusion installation directory.
If the Object Hierarchy is altered or added to through the Administration Manager (see Extending the Object Hierarchy), new directories and XML files are created to reflect the new structure.
The following figure shows the correlation between the Object Hierarchy and the domains directory structure (the illustration is from Windows NT, however the same structure is used on UNIX)..
The normal installation of OpenFusion CORBA Services creates minimal XML configuration files in the domains directory structure. These files only contain configuration information for properties which differ from the default values. To fully populate these XML files with property information, you must run the Administration Manager and save the configuration.
As an alternative to running the Administration Manager GUI, the configuration can be completed using the Administration Manager command line tool, described in Administration Manager Tool.
This must be performed before any Services can be started from the command line using the server -start script (as described in Starting Servers from the Command Line).
Configuration information is stored in XML files at each level of the directory tree.
Each domain and node directory must contain a single file, <name>.xml, where <name> is the name of the domain or node.
The domain and node files list all the children of that domain or node. They also show whether the Object Hierarchy has been locked at that level (see Locking Nodes).
These files are located and named as follows:
<INSTALL>/domains/<domain>/<domain>.xml
<INSTALL>/domains/<domain>/<node>/<node>.xml
where <INSTALL> is the OpenFusion installation directory, <domain> is the name of the domain, and <node> is the name of the node.
For example, the localhost node in the Administration Manager's Object Hierarchy is defined in the following XML file:
<INSTALL>/domains/OpenFusion/localhost/localhost.xml
The XML file also records whether or not the node is locked (see Locking Nodes).
The format of the XML files for domains and nodes is defined in the following DTD files:
<INSTALL>/xml/schema/Domain.dtd
<INSTALL>/xml/schema/Node.dtd
Each Service directory must contain a single file, <service>.xml, where <service> is the name of the Service.
The service file lists the Singletons and Java Objects under that Service. They also show whether the Object Hierarchy has been locked at that level (see Locking Nodes) and store any run time properties for the service.
These files are located as follows:
<INSTALL>/domains/<domain>/<node>/<service>/<service>.xml
where <INSTALL> is the OpenFusion installation directory, <domain> is the name of the domain, <node> is the name of the node, and <service> is the name of the Service.
For example, the NameService node in the Administration Manager's Object Hierarchy is defined in the following XML file:
<INSTALL>/domains/OpenFusion/localhost/NameService/NameService.xml
The XML file also records the current value and locking status of each property belonging to the Service. See Common Configuration Properties for details of Service properties.
The format of the XML files for Services is defined in the following DTD file:
<INSTALL>/xml/schema/Service.dtd
Each Singleton directory must contain a file, <singleton>.xml, where <singleton> is the name of the Singleton. The directory also contains the Singleton's IOR file (after the Service has been started).
These files are located as follows:
<INSTALL>/domains/<domain>/<node>/<service>/<singleton>/<singleton>.xml
<INSTALL>/domains/<domain>/<node>/<service>/<singleton>/<singleton>.ior
where <INSTALL> is the OpenFusion installation directory, <domain> is the name of the domain, <node> is the name of the node, and <service> is the name of the Service that contains the Singleton.
For example, the NameSingleton Singleton in the Administration Manager's Object Hierarchy is represented by the following XML file:
<INSTALL>/domains/OpenFusion/localhost/NameService/NameSingleton/ NameSingleton.xml
The XML file records the current value and locking status of each property belonging to the Singleton. See Common Configuration Properties for details of properties.
The format of the XML files for Singletons is defined in the following DTD file:
<INSTALL>/xml/schema/Singleton.dtd
Each Java Object directory must contain a file, <javaobject>.xml, where <javaobject> is the name of the Java Object.
This file is located as follows:
<INSTALL>/domains/<domain>/<node>/<service>/<javaobject>/<javaobject>.xml
where <INSTALL> is the OpenFusion installation directory, <domain> is the name of the domain, <node> is the name of the node, and <service> is the name of the Service that contains the Java Object.
For example, the ChannelConfiguratorObject Java Object in the Administration Manager's Object Hierarchy is represented by the following XML file:
<INSTALL>/domains/OpenFusion/localhost/NotificationService/ ChannelConfiguratorObject/ChannelConfiguratorObject.xml
The XML file records the current value and locking status of each property belonging to the Java Object. See Common Configuration Properties for details of properties.
The format of the XML files for Java Objects is defined in the following DTD file:
<INSTALL>/xml/schema/JavaObject.dtd
See , for details of how to create and configure Java Objects.
Previous | XML Configuration Files | Next |