Configuration Overview

iWD is configured through a thin-client GUI application that is called iWD Manager.

The configuration is stored and managed in a centralized database; however, runtime services work with a local configuration in XML files. In this way, the configuration that is performed in iWD Manager is offline and is propagated to runtime services via a deployment function.

Such an approach provides a more manageable environment (configuration changes are enabled in batches) . This also means that runtime services have fewer restrictions on physical distribution, as they do not have to read the configuration directly from a centralized location.

iWD Manager supports multi-tenancy and configurable security policies. In addition, any change that is made in the configuration (for example, who changed priority from 10 to 20 for this process) is logged at the attribute level and can be reviewed within a context at any given moment.

To configure iWD, you must configure each of the following sections:

See also User Profile.