| Anchor |
|---|
| _Toc154574508 |
|---|
| _Toc154574508 |
|---|
|
Managing configurations
When the Configuration Manager is started, it is initialized with the information available in the local datastore. The datastore that is used is specified in the jpif file that needs to be provided with the executable file.
After startup the user may attempt can to connect to the Master Controller of the regionapplication. The details of which are obtained from the synchronization configuration files or the DDA (direct database access details) for that regionapplication. If a connection has been established successfully, the download and upload buttons will be activated. If a connection cannot be established, the buttons will remain inactive.
The file menu provides a command to create a connection to the master controller, to facilitate the possibility that a user has connected to the network after opening a Master Controller session.
Image Removed 
Image Added
After selecting Login the following window is shown (an example from the Southern wgrfc Configuration. If multiple master controllers are available, these will be shown also)
Image Removed 
Image Added
| Anchor |
|---|
| _Toc154574509 |
|---|
| _Toc154574509 |
|---|
|
Download a configuration from a Master Controller
The user must manually initiate a synchronization session with the master controller to download the latest configuration files. Seeing that the configuration manager works independent from FEWS, this is a required action to ensure that the local datastore is up to date. Only configuration files need to be synchronized.
| Wiki Markup |
|---|
Click on \ [Download\] to download all configuration files. The download button is only available if a connection has been established with a master controller.
Image Removed 
Image Added
In the screen above the download button is not available.
If no download can be performed, this does not mean that the manager cannot be used.
| Anchor |
|---|
| _Toc154574510 |
|---|
| _Toc154574510 |
|---|
|
Import configuration files
...
Three types of configuration files are handled by the configuration manager: XML, HTML and Binary files. The handling of each file type is slightly different, as is shown in the following table.
FileType | Handling |
XML | The file is stored in a readable form in the data store. The content of the xml file is validated before being imported. Invalid files will not be imported. |
HTML | The file is stored in a readable form in the data store. The content is not validated, as no schema will be available to validate against. |
Binary | Binary configuration files include all other configuration files. These may be xml configuration files, module data sets or module states. |
When a configuration file is imported, the user that has imported the file is registered.
How are configuration files displayed?
An active configuration is shown having a yellow background. A selected configuration file is shown having a blue background. An active selected configuration file is shown with a blue background, except for the ID which is shown with a yellow background. Below an example is given of two available Locations ManualForcastDisplay configuration files. The active file is selected.
Image Removed 
Image Added
| Anchor |
|---|
| _Toc154574511 |
|---|
| _Toc154574511 |
|---|
|
Make a selected configuration file the active file
| Wiki Markup |
|---|
Of any configuration file instance, only one can be the active file. After selecting a file, click on \ [Set Active\] to make the selected file the active file. Only one configuration file may be active at any moment.
\\
| Anchor |
|---|
| _Toc154574512 |
|---|
| _Toc154574512 |
|---|
|
Delete a configuration file
...
Configuration files may only be deleted in the following situation:
The configuration file ID is a local ID, ie it starts with the prefix "CM: ".
The configuration file is not the active configuration file, i.e. it is not referenced in the default tableunmigrated-wiki-markup
To delete a configuration file, select the file and click on \ [Delete\]
\\
| Anchor |
|---|
| _Toc154574513 |
|---|
| _Toc154574513 |
|---|
|
Export a configuration file
...
After exporting, the configuration manager will start up the application that has been associated with the specific file. This association must be configured in the configuration management configuration file.
| Anchor |
|---|
| _Toc154574514 |
|---|
| _Toc154574514 |
|---|
|
Upload to Master Controller
...
The procedure to follow when certain configuration file needs to be changed is simple. To do so, carry out the following steps:
| Wiki Markup |
|---|
Step 1: Select the configuration that needs to be changed
Step 2: Export the file by clicking on \ [Export\]. This will start the 'editor' that has been configured for the selected configuration file. If the editor does not allow editing, close the editor and open the configuration file in an appropriate editor
Step 3: Make the required changes and save the file. Give the configuration file an appropriate name, using the file naming convention given in paragraph 13.2.5
Step 4: Import the modified file. Note that the filename is now shown in the description field.
Step 5: Set the newly imported file Active
Step 6: Use the analysis section to verify that the configuration is still correct. Verify the relevant workflows.
Step 7: Upload the configuration to the master controller. Check that the file has indeed been uploaded by verifying that the ID has been changed from a Local ID to a Master Controller ID