Configuration Files

The configuration file (Config) run by a server is a composite XML document in which AssemblyLines, connectors and so forth are all part of the same document. In the IBM Tivoli Directory Integrator Eclipse CE each of these components are allocated their own physical file. These files only contain one configuration object.

One of the reasons for splitting the configuration file into separate files during solution development was to make sharing of components easier. Also, having each component in its own file lends itself nicely to source control systems like CVS and also to multiuser development where different people work on different parts of the solution at the same time.

Configurations prior to this version can be imported using an import wizard. The imported configuration splits into individual configuration files as a result of this process. Another way is to use the option...

File > Open Directory Integrator Configuration File

...which will import the pre-7.0 configuration into a new project. Be aware though that this option also set the auto update back to the source file.

Runtime Configuration File

Hidden from normal view is the runtime configuration file. This is the file that TDI servers use to run the solution and also the file that previous versions (pre-7.0) would work directly on. Whenever we save a configuration file in the CE, it will cause an update to the runtime configuration file as well. This file is also the one that is transferred to a TDI server for execution. This file is maintained by the Project Builder and should not be modified by the end user.

We can configure the project to export the runtime configuration file automatically when it changes. Use the project properties panel to configure the file the project is linked to.

Whenever the runtime configuration is updated it is also copied to the file specified in the TDI properties section of the project. The linked file is automatically set when we use the command...

File > Open Directory Integrator Configuration

Parent topic: The Project Model