04/29/2019
Hello Sir,
I have been trying to experiment a bit on the GDS sample provided in the .NET stack.
So the scenario currently is I have 2 hosts. HostA(Linux OS) has a LDS (mDNS enabled). Also, I have the .NET core global discovery Server running on the hostA.
Next, I have the HostB(Windows), which has its local discovery service running in the background, and also a prosys simulation server registered to it. I run the global discovery client here, and I connect to the GDS server running on hostA.
Now, the observation is that in the discovery section -> on the local machine-> I observe the prosys simulation server
on the local network-> I observe the LDS of hostA, and Prosys server(HostB)
on the global discovery-> empty
But on the global discovery, I expect it to show the above mentioned servers in the list. But it shows an empty list. I have checked a demo presentation where, it was mentioned that there is a background thread, which calls for findServersOnNetwork service and adds all the servers to the Global discovery section. But the observation is an empty list.
I tried attaching the screenshot here. but I could not
Also, in the video, you register a server config file to the GDS. Then the sample server is visible in the global discovery section. What is the purpose of having it done? Do you mean registering a server directly to the GDS without any LDS in the system? Like this Direct registration?
Or According to Overview is this the 2nd step?
Looking forward for your guidance.
Regards,
Rakshan
04/29/2019
Ohh, that is sad..
Anyway, in that video you register a sample xml file to the client(client Pull) and a sample xml file(server pull).
What are these steps actually doing? I am trying to correlate it with Link(Overview) and I am wondering if it is the 2nd step?
Also, in UnifiedAutomation document on GDS, they mention that the GDS registers to the LDS ME. But in Link(Overview),
it says LDS ME is registered to the GDS by the admin.
Please could you clarify which one is correct here
1 Guest(s)