WCF Endpoint

AVEVA Global WCF Configuration Guide

As a service the Global Daemon exposes endpoints. The term ‘Endpoint’ is used to describe an address that can be specified where the Service will listen for incoming communications. This address is used by the base product and Daemon clients to establish a communication connection for transferring of messages.

An Endpoint consists of:


Address	Location on the Internet/Intranet where the Daemon Service can be reached.
Binding	what transport protocol the communication should occur on.
Contract	What the Service does.

Baseaddress:

The user must configure the baseaddress key in both the GlobalWCFClient.config file and the AdmindWCF.exe.config file.

</appSettings>

In the above example the HTTP protocol is used. Depending on the requirement the protocol can be changed to HTTPS or NET.TCP (this must be consistent with the chosen Binding).

The value localhost can be replaced with the name of the computer running the daemon (if on a different machine).

Note:

Better performance can be achieved if using localhost than the hostname of the local machine if on the same machine.

The value 8000 determines the port number used for WCF communication. The value can be set to any port number, although the administrator must make sure that the port is not blocked by a firewall (refer to Firewall Configuration).

The Design_Time_Addresses will be automatically replaced at run time with the UUID (Universally Unique Identifier) as specified in the base product project.

The remainder of the baseaddress must be left unchanged.

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 (i.e. Hub to Sat and Sat to Sat).

Note:

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

Binding:

The binding determines the transfer protocol for the communication. The user must edit the Client binding in the GlobalWCFClient.config file and the Service binding in the AdmindWCF.exe.config file.

Open the GlobalWCFClient.config file and locate the following Client code block:

      <endpoint address="" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IGlobalWcfService" contract="IGlobalWcfService_11_1_201011" name="WSHttpBinding_IGlobalWcfService">

</endpoint>

</client>

Edit the binding attribute to one of the following supported Binding values:

•

BasicHTTP –raw HTTP such as a Web page.

•

wsHTTP –secured HTTP such as a Banking web page.

•

netTCP –TCP such as RPC communications.

Important:

Other than the Binding the user must leave the parameters unchanged.

Open the AdmindWCF.exe.config file and locate the following code Services block:

      <service behaviorConfiguration="GlobalWcfServiceBehavior" name="GlobalWcfServiceLib.GlobalWcfService">

<endpoint address=""

                  binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IGlobalWcfService" contract="GlobalWcfServiceLib.IGlobalWcfService_11_1_201011" behaviorConfiguration="ValidationBehavior">

</endpoint>

        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

</service>

</services>

Edit the service binding in the same way described for the client binding.

Note:

The settings made in the GlobalWCFClient.config and AdmindWCF.exe.config files must be consistent.