Initiate heterogeneous daemon communications

Use the following procedures to configure a location daemon that communicates with neighboring locations using different protocols and ports.

See Heterogeneous daemon communications for additional information.

Edit the configuration files

This example demonstrates setup for Global and Administration configuration files.

1. Find the configuration files.

   The Global files admindWCF.exe.config and globalWCFClient.config are located in the Global install directory.

   The Administration file globalWCFClient.config is located in the user app data folder C:\Users\<user>\AppData\Local\Aveva\AVEVA Administration\ClientConfigurationFiles\globalWCFClient.config.

2. Use an editor with Administration privileges and edit the files as follows:

   Look for the line:

   <add key="globalConfigurationFilePath" value="Default"/>

   And change it to:

   <add key="globalConfigurationFilePath" value="c:\temp"/>

   In this example, folder temp on the local machine C drive is being used, but this can be any shared folder on any machine.

Initiate heterogeneous daemon communications

This example assumes a globalized project with the hub and one or more satellites has been initialized, and the files globalWCFClient.config and admindWCF.exe.config have been edited.

3. In Admin, on the Global Tools tab, in the Daemon Management group, select Global Binding Configuration.

   

   The Global Bindings window opens.

4. For a new installation, no configuration file exists. Browse to the folder shown in the Status field.

   Note: The folder can be on a shared server that is accessible by multiple E3D projects.

   The Current Location is that for the project selected when AVEVA Administration is run. In this example it is the HUB, but it could easily be a satellite location. The Neighboring Locations will be either parent or child locations within the topology of the project structure.

   In this example the HUB has eight satellites.

   

   Note: The Defaults are extracted from the globalWCFClient.config file and the values shown above are the installed values.

   Once the folder location has been specified, the Apply button becomes active.

5. Select Apply to create the file GlobalCommsSettings.config.

   

   

   All locations now have a yellow warning graphical indicator, this means that the default protocol and port will be used.

   

   To change to another port and protocol, enter a connection name or reference in the User Defined Connection field.

   

   Note: Remember that any project referencing the same GlobalCommsSettings.config file can make use of any user defined connection and so we recommend some formal or structured naming convention.

6. Once the name is entered, select Edit, select from the populated Binding list.

   

7. From the Binding Overrides window, enter the required port.

   

8. Select OK.

   The yellow warning symbol is now a green tick, indicating the changes have been set in the Global-CommsSettings.config file and a reference is set in the project system database.

   

   Once a user defined connection has been created, it becomes available for use by other locations.

   

9. To allow different Global and Service configurations, uncheck the Same Settings for Client and Service check box.

   

   Because the GlobalCommsSettings.config file can be shared between many projects and because administrators have read/write access to the file, if a red warning symbol appears it indicates that the user defined connection held in the project system database cannot be found in the config file.

   

10. Restart the global daemon to capture the new user-defined connections.

    The additional service endpoints defined are visible as part of the daemon output: