Please, Dojo
is “Eventing” still supported in DataMiner 10.4?
Am I correct in thinking that gRPC is the recommendation but Eventing will still work, while Polling is just a “back-up” option since it creates overhead for the CUBE clients, as they’d have to poll alarms from the DMA rather than automatically receive them, forwarded by the server?
Found this in gitHub:
Looking for a way to move away from polling as clients seem to become very unresponsive when the amount of alarms to be “polled” is huge (~more than 2000).
.NET Remoting is still the default communication type in DataMiner 10.4 and will remain supported even in 10.5, but gRPC is indeed recommended.
.NET Remoting has 2 ways of operating:
– eventing, which requires establishing a connection from server to client on a random port, which is not always possible;
– polling, which should not introduce any overhead but rather a minor delay (the polling interval) in delivering events to the client.
We expect to change the default communication type to gRPC in the 10.5 lifecycle.
Out of the box, this will disable .NET Remoting on the server, and the “RemotingConnection” in ConnectionSettings.txt will be interpreted as “auto-detect gRPC”. To prepare your systems to keep using .NET Remoting as default, you can already specify LegacyRemotingConnection in ConnectionSettings.txt
and explicitly set EnableDotNetRemoting to true in MaintenanceSettings.xml.
Thank you very much for the helpful insight, Bert – marking this as solved.
P.S.: ref the random port, in most cases this is down to IT admins where DataMiner is deployed – the range of ports to be enabled is documented and depends on the OS version of the DMA – not a big deal as the range of ports is an ephemeral one ~ from 49152 to 65535 in most cases – and to be enabled only from known clients.