| 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 ini file that needs to be provided with the executable file (before 2014.02 this was a jpif file).
After startup the user may attempt to connect to the Master Controller of the region. The details of which are obtained from the synchronization configuration files for that region. 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.
...
After selecting Login the following window is shown (an example from the Southern Configuration. If multiple master controllers are available, these will be shown also)
| Anchor |
|---|
| _Toc154574509 |
|---|
| _Toc154574509 |
|---|
|
Download a configuration from a Master Controller
...
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 configuration files. The active file is selected.
| Anchor |
|---|
| _Toc154574511 |
|---|
| _Toc154574511 |
|---|
|
Make a selected configuration file the active file
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
...
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 uploading of configuration files is carried out in a transaction, enabling the complete transaction to be rolled back if an error occurs.
| Anchor |
|---|
| _Toc154574515 |
|---|
| _Toc154574515 |
|---|
|
Changing an existing configuration file
...