Global Daemon Node Communication

The Global daemon operates in two parts, a client and service. This architecture gives the administrator the opportunity to configure the way that the service listens and how data is transmitted through the client.

The client and service have their own configuration files that are maintained separately. The AdmindWCF.exe.config file controls configuration of the service and the GlobalWCFClient.config file controls configuration of the client.

The nature of these configuration files is described in detail in section Configure Security. The following describes the theory behind how the administrator should configure settings between computer nodes hosting Global daemons. The binding used must be consistent across all nodes/trust boundaries.

In the illustration above each circle represents a different physical computer node. Each node is running an instance of the Global daemon. Each node will have its own AdmindWCF.exe.config and GlobalWCFClient.config file.

The left and right Satellite nodes are configured to use wsHTTP for client and service. The central Hub node is able to communicate with both by having an endpoint exposed for wsHTTP.Endpoints are discussed further in section WCF Endpoint.

Note: Multiple end points are not currently supported, therefore a Global project must use the same protocol, transport mechanism and security (NetTCP, HTTP or wsHTTP) across all daemon nodes for the project (for example, Hub to Sat and Sat to Sat).

Different projects can use different configurations by having a separate copy of the Global server installation (and therefore configuration files) for each project.