So, we have some services in a server outside the one that is holding Milestone, and when trying to connect using the same method the sample does to send new analytics events, we’ve found that when we point directly to the server everything goes fine. However, when going through the cluster, we can’t reach. Besides a probable error at cluster configuration, I wanted to clarify the following:
- Are there any guidelines for the use of socket connections that need to be followed in this type of case?
- Do we need to configure something in Milestone to make it available for clustering?
- Following the method used by the given sample is the way to address any socket related connection?
There are more than one way to submit Analytics Events, I assume you are using the analytics event the way “Trigger Analytics Event with XML” sample does it.
When you can do it going direct, you must have enabled Analytics Events in the Management Client, Tools, Options which is the first step.
Per default port 9090 on the Event Server is used. If you have configured it correctly you have either the Event Server in a setup where it failover but a cluster address is used and the Event Server is reached both in normal operation and in a failover situation, or alternatively the Event Server is a single server totally outside the server cluster.
Maybe you can test the general setup. Can you configure Alarms in the Management Client and can you see Alarms in the Smart Client even when in failover?
Failover management server - XProtect VMS products | Milestone Documentation 2024 R1 (milestonesys.com)