Custom configuration files

[OzFenric]

For various of our issues we've made custom changes to our configuration files on VBO and proxy machines (i.e. config.xml and proxy.xml files). However our configuration creates new proxy servers as required. Will new proxies inherit the same config and proxy files as on the VBO server or do we need to build in a way to update/replace these files? TIA.

[Mildur]

Hi OzFenric

No, each proxy server has its own config.xml and proxy.xml files.
You should not replace the files because proxy.xml contains, for example, the information about the backup repositories and their path. If you simply replace the files with the same template, important information will be overwritten.

Thanks
Fabian

[OzFenric]

Thanks Fabian. We'll obviously need to build the config file update/replacement into the proxy generation method so our custom configurations are installed before repositories start getting put on them.

[Mildur]

I don't have experience with PowerShell and xml, but there should be a method to add a single configuration line (node) without overwriting the entire file.

[OzFenric]

Wondering if this situation has changed at all. We now have dozens of remote proxies and generating more 2-3 per week and would like to standardise the config settings (e.g. WCF timeout). There must be a template config.xml and proxy.xml file somewhere that gets copied as part of deploying a new proxy (before there's any job information on it). If we could set parameters in those template files all newly deployed proxies would start with the same config, otherwise we need to manually log into each new proxy and update their configs (or replace them with our own default config).

[Mildur]

Hello OzFenric

In our upcoming version 8 we plan to include a new PowerShell cmdlet which will allow you to deploy XML configurations from the VB365 server to the proxies. I believe this will solve your use case.

Best,
Fabian