Heterogeneous daemon communications
- Last UpdatedJun 09, 2026
- 2 minute read
The default Global setup uses a single endpoint defined in the admindWCF.exe.config and globalWCFclient.config files. These configuration files support only one endpoint. See Default WCF configuration for more information.
The default configuration from 3.11.3 includes one endpoint with configuration BasicHttp_Transport_None (HTTPS).
Customers can use the single default endpoint, combine the default endpoint with HGS (Heterogeneous setup) endpoints, or configure only HGS endpoints and remove the default endpoint. The differences among these options are explained in the following table.
|
Configuration |
Resulting endpoints |
|---|---|
|
Default |
One single endpoint defined in admindWCF.exe.config file |
|
Default + HGS |
Default endpoint plus additional endpoints defined in HGS. Keep the connection name in the bindings form empty or set it to Default for the location you wish to use the default endpoint. |
|
HGS only |
Set the following environment variable in the global batch file to remove the default endpoint: set REMOVE_DEFAULT_ENDPOINT = true Only HGS endpoints are available. |
Heterogeneous daemon communication configuration
With Global 3.3 it is now possible for a location daemon to run different communication protocols and ports to its neighboring locations. This extends to other project daemons running from the same server or desktop machine.
This is achieved through a shared GlobalCommsSetting.config file which defines user connections. Because multiple products use Global, you must also edit the globalWCFClient.config file for each product. In addition, set the same globalConfigurationFilePath value in the admindWCF.exe configuration file located in the Global product installation folder. Refer to each product’s release notes for compatibility.
The following table shows configuration file locations:
|
Application |
Configuration files |
Folder location |
|---|---|---|
|
Global |
admindWCF.exe.config and globalWCFClient.config |
Global install directory |
|
Administration |
globalWCFClient.config |
C:\Users\<user>\AppData\Local\Aveva\AVEVA Administration\ClientConfigurationFiles |
|
Unified Engineering/ E3D Design (required only if UE/E3D needs to communicate with Global Daemon) |
globalWCFClient.config |
UE - C:\Users\<user>\AppData\Local\Aveva\AVEVA Unified Engineering\ClientConfigurationFiles E3D - E3D install directory |
For detailed instructions on editing the files and setting up heterogeneous daemon communications, see Initiate heterogeneous daemon communications.
Port sharing
Port numbers cannot be shared across connections with different binding configurations. If connections have different binding configurations, assign a unique port to each one.
Note: When using binding configurations that involve certificates with remote service validation enabled, separate connections must be used for each location. This is because the remote service validation value differs. In this case, the same port number can be shared across the connections.