Windows Communication Foundation Configuration Files

Global Windows Communication Foundation (WCF) makes use of configuration files to load runtime settings for connecting to remote locations and to determine the security settings applied to Global communications.

Constructor Module Configuration files are configuration files used by any base product module that supports Global operation either directly or through data extracts (for example Admin, Design or Draft).

All Constructor Module Configuration files reference the GlobalWCFClient.config file (described later) for WCF configuration data. If GlobalWCFClient.config is absent, or not referenced from adm.exe.config or Constructor module config files, then Global will default back to using RPC communication.

In most cases the administrator will not need to modify the content of the Constructor Module Configuration files.

A complete list of Constructor Module configuration files is listed below.

In addition to the Constructor Module configuration files the following configuration files are provided:

The Global daemon is a client/server application. The server will listen to inbound communication by using a service with exposed Endpoints (discussed later in section WCF Endpoint). Outbound communication is handled by the client. The configuration of client and service are maintained in separate files:

The figure below illustrates the use of the configuration files when multiple nodes are present.

On the base product workstation the constructor module adm.exe.config is shown to reference the GlobalWCFClient.config file stored locally on that node. The copy of the Globalwcfclient.config file on the base product work station contains all of the WCF client configuration settings for being able to communicate with Global at a different location.

The base product machine is a client therefore there is no requirement for the AdmindWCF.exe.config (which is required only for service configuration).

The Cambridge node has its own AdmindWCF.exe.config and GlobalWCFClient.config file.

Referring to the illustration above, the base product configuration files will be located in the folder in which the base product was installed. Refer to the relevant installation guide.

For PDMS, an example default installation path would be:

C:\AVEVA\Plant\PDMS12.1.xx (where xx = <version number>)

For AVEVA Everything 3D™, an example default installation path would be:

C:\Program Files (x86)\AVEVA\Plant\E3Dx.xx. (where x.xx = <version number>)

Each of the Global Server nodes will have an instance of the Global Server files installed to the following path:

C:\AVEVA\GlobalServer (PDMS)

or

C:\Program Files (x86)\AVEVA\Global Server (AVEVA Everything 3D™)

Important:
Only edit XML configuration files inside a plain text ANSI editor to avoid file corruption. Do not open the configuration files inside a text editor that uses Rich Text such as Microsoft WordPad. AVEVA recommend editing the files inside Microsoft Notepad unless a suitable XML editor is available.

Sets of sample configuration files are available for different Protocols and Security options. These are available in a sub folder of the Global installed product. For example

C:\Program Files (x86)\AVEVA\Global Server\GlobalWCF_SampleConfigFiles

The supplied configuration files are example only.

For more complex configurations containing multiple endpoints, refer to AVEVA Support.

Updates to Configuration files and those for previous versions will be made available through the Knowledge base for the Global product on the AVEVA Helpdesk.

On the Knowledge Base, the files are supplied in a version specific ZIP file attached to the relevant Knowledge base item. The contents of the GlobalWCF_SampleConfigFiles folder file must be extracted to a folder before they can be viewed or edited.

The GlobalWCF_SampleConfigFiles folder is situated below the Global Installed folder, for example:

C:\AVEVA\GlobalServer3.xx (where xx = <version number>)

Or

C:\Program Files (x86)\AVEVA\GlobalServer3.xx (where xx = <version number>)

Each folder contains 2 files:

• admindWCF.exe.config

• GlobalWCFClient.config

The following sub-folders will be created below the GlobalWCF_SampleConfigFiles folder for each different sample configuration:

• MessageSecurityCertificateAuthentication\basicHttp

• MessageSecurityWindowsAuthentication\netTcp

• MessageSecurityWindowsAuthentication\wsHttp

• NoSecurity\basicHttp

• NoSecurity\netTcp

• NoSecurity\wsHttp

• TransportSecurityCertificateAuthentication\basicHttp

• TransportSecurityCertificateAuthentication\netTcp

• TransportSecurityCertificateAuthentication\wsHttp

• TransportSecurityWindowsAuthentication\basicHttp

• TransportSecurityWindowsAuthentication\netTcp

• TransportSecurityWindowsAuthentication\wsHttp

  Important:
  The globalWCFClient.config file used by the Global client in the base product (PDMS, AVEVA Everything3D™ and related products) must be consistent with the config files used by the Global daemon. The file admindWCF.exe.config must contain a suitable endpoint to receive communications from the base product.

Open the AdmindWCF.exe.config or GlobalWCFClient.config file in an XML or text editor.

Important:
AVEVA recommend editing the files inside Microsoft Notepad if an XML editor is not available. Only edit XML configuration files inside a plain text ANSI editor to avoid file corruption. Do not open the configuration files inside a text editor that uses Rich Text such as Microsoft WordPad.

Note: Sets of sample configuration files are supplied as part of the Global Server installation in the sub-folder GlobalWCF_SampleConfigFiles. Config files must be deployed consistently for both Global Server and Global Client throughout a Global project. The appropriate GlobalWCFClient.config file must be deployed to all Base products which use Global.

Sample Configuration files are supplied for different Security settings and Bindings.