../pvss.htm menu.gif basics.gif

Requirements and installation

Requirements

  • Correct installed WinCC OA version 3.0 or higher.

  • A license for redundancy has to exist.

  • At least two computers with the same operating system.

note.gifnote

It is not supported to mix one server being 32-bit and one server being 64-bit to form a hot-standby redundancy server pair. For productive use both Hot-Standby redundancy partners must be identical and must be 64-bit as the 32-bit server can only be operated as an engineering server. Please refer to software-requirements.

  • 2 network cards per computer for the redundant LAN connection.

  • The same WinCC OA version has to be installed on both computers.

  • The WinCC OA projects of the both redundant systems have to be saved with the same name in the same directory.

  • Under Windows the project directory has to be released for swapping out/in (Release name = Project name) and you have to set writing/reading rights to the directory; under Linux mountpoints have to exist for the computers - under /nfs/HOST.

note.gifNOTE

Note the restriction for the following connect and query functions regarding the usage with multiple systems: dpConnect(), dpQuery(), dpQueryConnectAll(), dpQueryConnectSingle(), isAnswer() as well as isRefresh().

caution.gifCaution

Note that the entry for the local host, 127.0.0.1 localhost, always has to exist in the host file.
Drivers, CTRL and all other managers, which should establish a connection to the local Data/Event manager, convert it to "localhost". Thereby, it is not necessary to configure "-data localhost" in a non-redundant project. In a redundant project, it is intended that the managers establish a connection to the local and to the redundant Data/Event manager. Thus, the manager must be started with the option -connectToRedundantHosts or the config entry connectToRedundantHosts = 1 must be set in the specific manager section.

caution.gifCAUTION

If the active server is stopped under Solaris and the system overview panel is not used, the color of all objects might be set to inactive for few seconds. To avoid this, use the function getLastError() in the work function when using the function dpConnect().

Installation

A normal installation of WinCC OA version 3.0 or higher is sufficient for using the redundancy. See chapter Installation for more information on installing WinCC OA. The configuration of a redundant system with WinCC OA is described in detail in the chapter creating a redundant system.

 

For instruction how to perform a WinCC OA version/patch/service pack upgrade in a redundant system, see WinCC OA Upgrade in a redundant system.

 

note.gifNote

When using redundancy for a WinCC OA project under Solaris, it is necessary to deactivate the possibility to call the TCP service by the Network Information Service (NIS). Otherwise a loss of the network connection would lead to the service being blocked. To apply the necessary changes the line "services  files nis" inside the file /etc/nsswitch.conf must be changed to "services  files".

 

page_top.gif

V 3.11 SP1

Copyright ETM professional control GmbH 2013 All Rights Reserved