...
Trebuchet populates it's application list and creates a listener for discovery data based on a JSON configuration file. On start up, the launcher looks for this file, called appConfiguration.json in the same folder as the Trebuchet executable. On first start up, a blank config file will be created and written to disk (the blank config should allow radar discovery on most systems).
If the app cannot parse the config file (usually due to a syntax error, or if the file is empty), no data will be displayed in the app:
...
The config file itself consists of two sections: ConnectionConfig and TrebuchetApps, which are the Radar Discovery Connection Details and the App Configuration respectively.
...
For example, a launcher used on a PC with a network IP address of 10.77.3.59the (auto generated) default config file:
| Code Block |
|---|
"ConnectionConfig": {
"DiscoveryIPAddress": "239.69.69.69",
"DiscoveryInterface": "100.770.30.590",
"DiscoveryPublishPeriod": 5000,
"Port": 6317
} |
...
Mutually exclusive parameter groups ensure that only one of these modes can be selected for a given instance. Within the configuration file, they are treated as a separate list to ParameterGroups:.
...
When viewed in the UI, mutually exclusive groups are represented by a drop-down menu:
...
Once a group is selected, its constituent parameters are displayed.:
...
Special Treatment of Ipaddress and Port Parameters
...