Global now makes use of Microsoft Windows Communications Foundation (WCF) as provided by .NET 3 and above for more secure communications.
The question is: Does anyone here has already used the Global WCF release?
We are trying to make Global using WCF but getting lot of issues. We are unable to communicate HUB & SAT. But global is running on both HUB & SAT. Could you please send me any lesson learnt from your initial project setup?
Thanks
Hi dhasar
It is hard to say what is problem in your case but it is for us it has been usually because of it network e.g. firewalls. I didnt understand that what you mean that global is running but could not communicate. You have not managed to initialise?
When I run the Singleds in command window in HUB (Hub also a license server), it shows that Global Daemon startup. But I can't see the "Aveva Global Daemon" in Windows Services. Same message I get in SAT location. SAT has local windows Firewall and it has been disabled. But Hub is running Network Firewall setup. I doesn't have rights to check any issue in Neywrok Firewall.
for WCF
Check with IT if the vpn tunnel is set
Set the globalwcf config file to use protocol WCF and increase the timeout in adminwcf config file since the daemon takes more time to communicate.
set adminwcf.exe in the daemon file (in RPC we use admin.exe)
see that the port specified by for wcf connections is set (Normally 8000 port is used).
if timeout value is less it may prompt signal 11 trapped
if the daemon shows access denied error confirm that the user as access to the localhost site...else start the daemon as adiministrator...
