Configuration file overrides ​

For each of the main components in the grid (TSF Server and Register Service), there is our default configuration file bundled in the jar with defaults for each of the different parameters. There are 2 more configuration files that these components take as optional parameters when starting - another default, and an override. The process to get the overall configuration is to start with all of our default values that come with the framework. It will compare this with the default provided and override any parameters that were changed. It will do the same with that result and the override configuration file provided. If any of the configuration files are not provided, all of the parameters from the previous configuration file are used. Multiple examples of this process are shown below:

The actual parameters are not relevant, but rather important thing to note here is how the parameters flow through the override process to get in the final configuration file.

OurDefault.json

Note that these are the default values that are built into the jar - this actual file will not be visible to you.

{
   "intParameter": 2,
   "strParameter": "Hello",
   "doubleParameter": 1.1,
   "nestedParameter": {
     "subParameter1": 10,
     "subParameter2": 50,
     "subParameter3": 16,
     "subParameter4": 19
   }
 }

YourDefault.json

{
   "intParameter": 2000,
   "doubleParameter": 0.0,
   "nestedParameter": {
     "subParameter3": 0,
     "subParameter4": 0
   }
 }

YourOverride.json

{
   "doubleParameter": 2.2,
   "nestedParameter": {
     "subParameter3": 1000,
     "subParameter4": 5000
   }
 }

FinalConfiguration.json

{
   "intParameter": 2000,
   "strParameter": "Hello",
   "doubleParameter": 2.2,
   "nestedParameter": {
     "subParameter1": 10,
     "subParameter2": 50,
     "subParameter3": 1000,
     "subParameter4": 5000
   }
 }

This level of granularity allows for a lot of power and flexibility when configuring your TSF Servers. For example, an image can be created from our TSF image that includes your own personalized default json so that any common configurations (that override ours) can be bundled together - and if some TSF Servers behave differently, a specific override json as shown above can be passed to them externally at runtime.