Initiate Heterogeneous Daemon Communications

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 via a common or shared GlobalCommsSetting.config file in which your user connections are defined. Since many products can make use of global an edit needs to be made to the globalWCFClient.config file for each of these products. See each products release note for compatibility.

In the installation folder for Global 3.3 (and above) and Admin 1.5 (and above) using a suitable editor and running with Administration privileges edit the file globalWCFclient.config.

Look for the line

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

And change this to:

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

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

The following example shows how to use heterogeneous daemon communications.

Assumption

A globalized project with the hub and one or more satellites has been initialized and the globalWCFClient.config files have been edited as detailed above.

1. In Admin module, from the main menu bar select Settings > Global Binding Configuration.

   

2. The Global Bindings window is displayed, on a new installation no configuration file will exist and so the first requirement is to browse to the folder as indicated by the Status field.

   Note:
   The folder could be on a shared server, accessible by many 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. Clicking the

Apply button will create a 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, click in the User Defined Connection field and type in a connection name or reference.

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.

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

From the Binding Overrides window, enter the required port.

Select OK and 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.

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.

Global Daemon Start-up

Once any user defined connection have been created, the global daemon will need to be restarted to capture the changes. The additional service endpoints defined will then be visible as part of the daemon output.

Note:
Multiple clients can share the same Bindings, but the server cannot support more than one Binding type on a given port number.