...
A * means either "oc" or "fss"
clientConfig.xml
...
file(s)
From Delft-FEWS 2018.02 onwards, the different clientConfig.xml files have an important place in the Delft-FEWS root configuration file. Different variants (for different components) of clientConfig.xml files exist and will be explained below.
The clientConfig.xml consist of the following elements:
title
Optional element for setting the title of your application/component
clientType
Required element for defining the type. Enumeration of options includes;
- Forecasting Shell
- Operator Client
- Stand Alone
otherRootConfigFiles
One or more A reference to the required root configuration files which should always be downloaded when an OC or FSS starts is a new element within this file.
.
connection
Optional element to define the connections to the Master Controller. Only required if you have more than 1 Master Controller connections (multi MC environments).
If there is only 1 Master Controller, the connection details are already within the shortcuts (TO DO: INSERT LINK TO EXPLANATION) you have created when deploying/installing the system.
databaseServer (+ url / user / password)
Required elements for setting the details of the database server if you want to specify those in the <connection>.
Example OC_clientConfig.xml
Minimum content for oc_clientConfig.xml + explanation + example
Recommended content for oc_clientConfig.xml + explanation + example
Full content/decription of oc_clientConfig.xml
FSS_clientConfig.xml
Recommendation for creating fss_clientConfig.xml per Operating System type
(fss_linux_clientConfig.xml, fss_windows_clientConfig.xml)
Minimum content for fss_clientConfig.xml + explanation + example
Recommended content for fss_clientConfig.xml + explanation + example
Full content/decription of fss_clientConfig.xml