Hi Dojo,
I'm reviewing the "ConnectionSettings" over a number of DMAs belonging to different clusters, with the aim of reverting to the default condition and use Eventing whenever the related ports are allowed.
Question 1: if I can use different DMAs to access the same DMS, shall I replicate the "Eventing" config line on all the DMAs? Or will there be a sync once one DMA is reverted to "Eventing" by default?
Question 2: are there any other settings (in the DMA or in the CUBE app) that can overrule the Eventing config line in ConnectionSettings?
----
Based on this page, the settings to use eventing by default were in the folder
C:\Skyline DataMiner\Webpages\
Does it mean that the settings in C:\Skyline DataMiner\Webpages\ConnectionSettings.txt can be ignored or overruled when connecting through the CUBE desktop client (not a webpage)?
Asking as I have a specific subset of agents where changing the above line doesn't change the behaviour found at connection with CUBE (an old server in staging) - on other servers, instead, the config line in ConnectionSettings.txt has a valid polling interval, e.g. 2000ms, but clients can connect in Eventing - so I'm figuring out if any other server side config can be present, outside of the above file, or if specific user-groups on the CUBE side may overrule server configs - any steer will be helpful.
- The ConnectionSettings.txt file is unique per agent in the cluster and does not get synced automatically.
- When the connection type is set to "auto" in Cube, it will retrieve the ConnectionSettings.txt file to autodetect the recommended connection setting for connecting to this agent. However, any Cube can ignore this by appling manual connection settings for .NET Remoting. Using gRPC can only be done through the "auto" setting as it already requires HTTPS port 443 to be accessible.

Thanks for the additional info on the gRPC too