...
| Info |
|---|
Note that in multi-Master Controller environments, the configuration needs only to be updated in the primary Master Controller. The secondary and other Master Controllers will normally receive the configuration by means of synchronisation. |
Importing new files from root
Select root and click the <Import> button
...
For new files this means they will get a new version and synchLevel 11 and they will be officially part of the active config revision.
Import changed files from root
When there already is an active config revision and an import from root is done, the import dialog will show in the first tab all new and changed files
...
When the user tries to close the config manager and there are changes in memory that are not processed by <Save all> the user gets a message and a question whether het is sure he wants to exit.
Single file changes
Besides changing the config revision by import there are also options to activate, deactivate or delete config file versions. These changes will also be kept in memory and only made final after <Save all> is pressed and a new revision is created.
Set active
When an inactive config file version is selected it can be made active by clicking the <Set Active> button
...
Afterwards, the activated version will be highlighted in yellow to show it belongs to the new config revision the user is working on. The change however will only be made final after <Save all> is clicked and a new revision is created.
Set Inactive
When an active config file version is selected it can be made inactive by clicking the <Set Inactive> button
...
Afterwards, the deactivated version will not be highlighted in yellow anymore because it will not belong to the new config revision the user is working on. The change however will only be made final after <Save all> is clicked and a new revision is created.
Delete
When an inactive config file version is selected it can be deleted by clicking the <Delete> button
...
Deleting older versions needs to be done with care if it will be desired to restore older config revisions later on.
Exiting without "Save all"
When the user made config changes and tries to exit Delft-FEWS without having pressed <Save all> a popup will show with a warning.
Restoring old revision
In the Version Management tab a table with all revisions stored in the database is shown.
...
If the user clicks yes, the deleted file will be removed from the revision. So after "Save All" has been pressed the old revision is restored but the deleted file is removed from it.
Group By
The Group By button will group module config files by their module when selected.
...
When activated the module config files will be grouped by module (like generalAdapterRun, timeseriesImportRun or transformationModule):
Using the ConfigManager for a Master Controller synchronization pool
The ConfigManager will always operate on a single Master Controller database, also in a multi Master Controller environment. When multiple Master Controllers are always kept in synch, in theory it should not matter which Master Controller database the ConfigManager operates on. In practice however, it is best practice to upload new configuration to one and the same Master Controller of the synchronization pool. Most commonly the database where the upload takes place is referred to as the primary Master Controller. Changes uploaded are then automatically shared among the synchronizing Master Controllers that synchronize the uploaded configuration from that central database.
| Info |
|---|
Always upload new configuration to one and the same Master Controller of the synchronization pool. If by mistake the Config Manager was used to upload a single patch.jar to the secondary Master Controller, this can lead to the secondary MC not seeing al the configuration. In such a case it is advised to use the ConfigManager to upload a minor change (e.g. comment) in the primary MC to make all config files visible again to the secondary Master Controller. This will work if only a single patch.jar has been oploaded to the secondary MC and no other config files or actions like "delete inactive config" have been done. |
Using the ConfigManager in a non-standard Master Controller synchronization pool
A non-standard Master Controller synchronisation pool is for instance when there is an external synchronizing Master Controller (for instance in another geography / organization) that is also allowed to synchronize from the primary Master Controller database, but is not synchronizing back. In this case it strongly forbidden to upload configuration in the external Master Controller database. Any subsequent upload into the primary Master Controller could conflict with the externally uploaded configuration.
...