Dynamic Configuration in 2K

Dynamic Configuration is pervasive in 2K. It is supported by three major elements: the ComponentConfigurator, the DynamicConfigurator, and the Automatic Configuration Service. In the following links you can find detailed information about each of them.

The ComponentConfigurator is an object that stores the runtime dependencies of a certain component and is able to transport configuration events from one component to their dependent ones and vice versa. It can be extended so that customized subclasses can handle the events in application-specific ways. We have implementations of it in C++, Java, and CORBA/C++.

DynamicConfigurator is the dynamicTAO reconfiguration IDL interface. By using it, one can inspect the state and reconfigure an instance of dynamicTAO and the applications that are running on it.

The Automatic Configuration Service is a 2K service that is able to process the prerequisite specification of a certain 2K component, resolving all the required dependencies.

Back to the 2K Home Page

Last modified: Wed Sep 1 15:44:05 CDT 1999