AVEVA Global

AVEVA Global WCF Configuration Guide

AVEVA Global

AVEVA Global can be used to enhance projects created in either the AVEVA Plant or AVEVA Marine group of products - henceforth known as the "base product" in this document.

References to paths and directory settings in this document are used from AVEVA Plant and should only be used as an example. Other base product paths and directory settings will be different.

The Global WCF Configuration Guide describes how to configure the Windows Communication Foundation (WCF) layer of security in AVEVA Global.

The user has the ability to use the WCF protocol in a Global project. The RPC protocol continues to be available to the user if required.

Important:

The Global Client of the base product (PDMS/Marine/Engineering) installs with RPC configured as default, AVEVA Everything3D ™ is configured with WCF by default.

Global has relied on RPC (Remote Procedure Call) for all inter-location communication. There are a number of limitations in using the RPC protocol such as a dependency on using port 135 for traffic and limited support of transport protocol bindings.

The main benefit of using WCF is that it can be fully customised. Through configuration files the administrator can decide what levels of security to apply (refer to Security Features). Global WCF Configuration Guide

The operation of a Global project does not change as a result of enabling WCF functionality. However the configuration of security has been abstracted from the software and is now fully customisable through new XML configuration files.

WCF is enabled and configured by modifying values within XML configuration files ,refer to Enable RPC Security.

The Global WCF Configuration Guide targets the IT administrator or Global Project Administrator. Knowledge of AVEVA Global will be helpful but is not essential.

The user must have the correct AVEVA license file before installing the AVEVA Global Server. The license file is called AVEVA Licensing System (ALS). Refer to the AVEVA Licensing System (ALS) guide for further information.

Global requires a license for Hub and Satellites. At the hub location each project daemon will take out a GLOBAL license entry. At each Satellite each project daemon will take out a GLOBALSAT license. A project daemon at a Satellite may use a spare Hub license (GLOBAL) if no satellite license (GLOBALSAT) is available.

It is assumed that the reader has already installed the base product and Global Server with the WCF functionality selected.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.