Schneider Electric AVEVA System Platform Installation guide

Brand: Schneider Electric

Model: AVEVA System Platform

Category: Software manuals

Type: Installation guide

Version 2023

aveva.com

AVEVA™ System Platform

Installation Guide

No part of this documentaon shall be reproduced, stored in a retrieval system, or transmied by any means,

electronic, mechanical, photocopying, recording, or otherwise, without the prior wrien permission of AVEVA.

No liability is assumed with respect to the use of the informaon contained herein.

Although precauon has been taken in the preparaon of this documentaon, AVEVA assumes no responsibility

for errors or omissions. The informaon in this documentaon is subject to change without noce and does not

represent a commitment on the part of AVEVA. The soware described in this documentaon is furnished under

a license agreement. This soware may be used or copied only in accordance with the terms of such license

agreement.

ArchestrA, Avans, Citect, DYNSIM, eDNA, EYESIM, InBatch, InduSo, InStep, IntelaTrac, InTouch, OASyS,

PIPEPHASE, PRiSM, PRO/II, PROVISION, ROMeo, SIM4ME, SimCentral, SimSci, Skelta, SmartGlance, Spiral

Soware, WindowMaker, WindowViewer, and Wonderware are trademarks of AVEVA and/or its subsidiaries. An

extensive lisng of AVEVA trademarks can be found at: hps://sw.aveva.com/legal. All other brands may be

trademarks of their respecve owners.

Publicaon date: Wednesday, July 13, 2022

Publicaon ID: 853173

Contact Informaon

AVEVA Group plc

High Cross

Madingley Road

Cambridge

CB3 0HB. UK

hps://sw.aveva.com/

For informaon on how to contact sales and customer training, see hps://sw.aveva.com/contact.

For informaon on how to contact technical support, see hps://sw.aveva.com/support.

To access the AVEVA Knowledge and Support center, visit hps://sowaresupport.aveva.com.

Version 2023

Page 2

Contents

Chapter 1 Preparing for System Plaorm Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . 9

Important Noce for Highly Secured Environments (TLS 1.2 Exclusively). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

License Installaon and Acvaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

AVEVA System Monitor Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Selecng System Plaorm and System Plaorm Enterprise Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supported Operang Systems for System Plaorm 2023. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported InTouch Access Anywhere Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

System Sizing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Supported and Recommended Node Hardware Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Required Installaon Order of Addional Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Common Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Windows Network Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

System Plaorm Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SQL Server Requirements for System Plaorm Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Unsupported SQL Server Version Error Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Selecng a Type of Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

About Product-Based Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

About Role-Based Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Network Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

About Network Account Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 2 Installing System Plaorm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installing InTouch Access Anywhere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Install InTouch Access Anywhere Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Secure Gateway Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Conguring Ports for the InTouch Access Anywhere Secure Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Install the Secure Gateway and Authencaon Server Separately or Together. . . . . . . . . . . . . . . . . . . . . . . . 44

Install All Components on a Single Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 3 Conguring System Plaorm Components. . . . . . . . . . . . . . . . . . . . . . . . . 47

Using the Congurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Common Plaorm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

System Management Server Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

User Credenals for Conguring the System Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Version 2023

Page 3

Redundant SSO Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Advanced Conguraon Opons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Cercates Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Ports Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Communicaons Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Authencaon Provider Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Congure the AVEVA Identy Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

License Mode Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Designing a Robust SSO System with an External Authencaon Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Recommended SMS Architecture Ulizing an Authencaon Provider. . . . . . . . . . . . . . . . . . . . . . . . . 68

Simplied SMS Architecture Ulizing an Authencaon Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Minimum SMS Architecture Ulizing an Authencaon Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Industrial Graphic Server Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

AVEVA Historian Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Using HTTPS Instead of HTTP for Historian Client, Historian Client Web, and REST APIs. . . . . . . . . . . . . . . . . 77

Enabling Trust for a Self-Signed Cercate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Acquiring a Copy of the Self-Signed Cercate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Trusng a Self-Signed Cercate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

AVEVA Enterprise License Server Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

AVEVA System Monitor Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

System Monitor Manager Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Email Server Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Advanced System Monitor Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

System Restart aer Conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 4 Upgrading, Modifying, and Repairing System Plaorm. . . . . . . . . . . . . . . 93

AVEVA Applicaon Server Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

About Upgrading Applicaon Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Upgradeable Applicaon Server Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Windows Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

SQL Server Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Issues with Legacy Common Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Basic Upgrade Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Upgrading a Galaxy Repository Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Upgrading an IDE-only Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Migrang the Galaxy Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Upgrading Run-Time Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Upgrading Redundant Pairs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Upgrade Consideraons for Mul-Galaxy Communicaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Modifying an Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Repairing an Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 5 Uninstalling AVEVA System Plaorm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Uninstall a System Plaorm Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Uninstall All Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Version 2023

Page 4

AVEVA™ System Plaorm Installaon Guide

Contents

Chapter 6 Security and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Enhanced Security for Connecng to a Galaxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Modifying the Network Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Change the Network Account from the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

SQL Server Rights Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Seng the SQL Server Security Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Restoring Required SQL Server Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Seng the FIPS Security Policy Opon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Chapter 7 Conguring SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

SQL Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Working with SQL Server Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

SQL Server not found on node: small conguraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

SQL Server not found on node: medium and larger conguraons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Compable version of SQL Server already installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

New version of SQL Server already installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Incompable version of SQL Server already installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Using a Non-Default Port for SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Seng a Windows Firewall Excepon for the SQL Server Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Chapter 8 AVEVA InTouch HMI Requirements and Prerequisites. . . . . . . . . . . . . . . 126

Installing OI Gateway and Upgrading from FS Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Compability with Exisng FS Gateway Applicaons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

OI Gateway Installaon Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 9 AVEVA Historian Server Requirements and Recommendaons. . . . . . . . 131

Server Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

High Availability Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Requirements for Historian Management Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Remote IDAS Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Security Consideraons for a Remote IDAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Disk Sizing and Data Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

General Hardware Recommendaons for Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Planning for Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Disk Space Requirements for Database Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Disk Space Requirements for Historical Data Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Storage and Network Transmission Sizes for Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Disk Space Esmaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Bandwidth Esmaon for Streaming Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Bandwidth Esmaon for Store-and-Forward Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Time Esmaon for Store-and-Forward Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

About Data Compression and the Buer Age Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Performance Consideraons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Version 2023

Page 5

AVEVA™ System Plaorm Installaon Guide

Contents

Server Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

IDAS Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Tiered Historians. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Storage Subsystem Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Networking Recommendaons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Client Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Support for Non-English Operang Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Integraon with Other AVEVA Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

System Sizing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Process Historian Sizing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Server 1 (Non-Tiered): 2.4 GHz Single Processor Quad-Core CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Server 2 (Non-Tiered): Four Dual-Core 2.7 GHz CPUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Server 3 (Non-Tiered): Four Dual-Core 3.4 GHz CPUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Server 4 (Tier-2): Eight Dual-Core 2.67 GHz CPUs (Hyper Threaded). . . . . . . . . . . . . . . . . . . . . . . . . . . 150

SCADA (Tiered) Historian Sizing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Topology 1: Centralized Tiered Historian Topology on a Slow/Intermient Network. . . . . . . . . . . . . . 151

Topology 2: Centralized Tiered Historian Topology for a Single Physical Locaon. . . . . . . . . . . . . . . . 153

Topology 3: Simple Tiered Historian Topology for a Modem Conguraon. . . . . . . . . . . . . . . . . . . . . 155

Chapter 10 AVEVA Historian Server Installaon and Conguraon. . . . . . . . . . . . . 158

Preparing for the Historian Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Microso SQL Server Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Historian Installaon Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

About Historian Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Tesng the Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Anvirus Soware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Historian Menu Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Repairing the Historian. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Modifying the Historian Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Uninstalling the Historian. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Upgrading from a Previous Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

About Database Migraon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Upgrading the Historian Version (Microso SQL Server 32-bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Upgrading the Historian Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Migraon of History Data Stored in SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Chapter 11 AVEVA Historian Client Informaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

About the Historian Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Historian Client Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Desktop Applicaons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Microso Oce Add-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

AcveX and .NET Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Requirements and Recommendaons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Version 2023

Page 6

AVEVA™ System Plaorm Installaon Guide

Contents

Support for Operang System Language Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Chapter 12 AVEVA Historian Client Installaon and Conguraon. . . . . . . . . . . . . . 167

About Historian Client Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Using Historian Client Soware with Roaming Proles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Repairing the Historian Client Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Uninstalling Historian Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Upgrading from a Previous Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Appendix A Using Silent Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Starng Silent Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Using Response Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Creang a Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Response File Entry to Acknowledge Installaon Change Informaon (Redistributable Libraries). . . . . . . . 174

Response File Entry to Acknowledge Compability Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Response File Entries to Congure the Common Plaorm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Response File Entries to Congure the Industrial Graphic Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Response File Entries to Congure the Historian. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Response File Entries to Congure the License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Response File Entries to Congure the System Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Response File Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Role-Based Response Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Product-Based Response Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Appendix B Single Product Installaon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Guidelines for Creang a Compact Installaon Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Upgrading from a Previous Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Preparaon for Installing a Single Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Oponal Folder for Historian. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Creang the Installaon Source and Installing the Selected Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Appendix C Ports Used by System Plaorm Products. . . . . . . . . . . . . . . . . . . . . . . . 187

System Plaorm Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Appendix D Common System Plaorm Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . 192

AVEVA System Plaorm Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Appendix E User Accounts and Groups Created by System Plaorm Installaon. . 194

Applicaon Server OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

InTouch HMI OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

InTouch Web Client OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Version 2023

Page 7

AVEVA™ System Plaorm Installaon Guide

Contents

Historian Server OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Plaorm Common Services Accounts and OS Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

AVEVA License Manager OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

System Monitor OS Groups and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Version 2023

Page 8

AVEVA™ System Plaorm Installaon Guide

Contents

Preparing for System Platform

Installation

This guide describes how to install AVEVA™ System Plaorm and System Plaorm Enterprise. System Plaorm

Enterprise provides addional cloud-based capabilies and is supplied separately, on a dierent DVD. Unless

otherwise noted, all informaon in this guide applies to both products.

You can use the System Plaorm installaon program to install the enre suite of products, or any of the

component products.

Before you begin the installaon program, you need to prepare your system, and you should plan your

installaon according to the two installaon types available to you, product-based and role-based. See Selecng

a Type of Installaon for addional informaon.

Your installaon planning should also include selecon of System Plaorm or System Plaorm Enterprise

components. See Selecng System Plaorm and System Plaorm Enterprise Components for more informaon.

Make sure that your computer meets or exceeds the hardware and soware requirements. System Plaorm

2023 is not supported on 32-bit operang systems or 32-bit versions of SQL Server. If the installed SQL Server

version is not compable for any reason, installaon stops and an error message is displayed. For more

informaon, see Unsupported SQL Server Version Error Message.

Important Notice for Highly Secured Environments (TLS 1.2

Exclusively)

Aected Systems

This informaon is applicable to a small subset of highly secured environments, in which operang systems and

supporng networks have been congured to enable TLS 1.2 and where TLS 1.0 and 1.1 have been purposefully

disabled. In these rare instances, some addional conguraon is required to ensure that System Plaorm will

work as expected.

System Plaorm 2023 includes various measures to strengthen security, including the ability to leverage the

latest version of transport layer security (TLS 1.2), provided that TLS 1.2 has been enabled and congured in the

host operang system.

As of the System Plaorm 2023 release date, Microso Windows Server 2016 does not support TLS 1.2 by

default. You must enable it by applying Microso updates and several manual edits to the system registry. The

tasks of applying all Microso updates and eding the system registry must be completed before you install

Version 2023

Page 9

Chapter 1

System Plaorm 2023. These instrucons also apply to any other soware products that support TLS 1.2. Follow

the instrucons listed below.

If you are required to enable TLS 1.2 and disable TLS 1.0 and TLS 1.1:

1. Before installing System Plaorm 2023 on a Windows Server 2016 computer, make sure that your computer1.

is up to date by downloading and installing all applicable Microso updates.

2. If required by the updates, restart your computer.2.

3. Edit the system registry. The .REG le shown below sets registry keys to their safest values.3.

For addional informaon about these registry changes, see hps://docs.microso.com/en-us/dotnet/

framework/network-programming/tls#conguring-security-via-the-windows-registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions"=dword:00000001

"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]

"SystemDefaultTlsVersions"=dword:00000001

"SchUseStrongCrypto"=dword:00000001

4. Restart your computer to ensure that all changes take eect.4.

5. Install System Plaorm 2023.5.

License Installation and Activation

A valid product license is required to enable product funconality. The AVEVA Enterprise License Server and

Enterprise License Manager are automacally selected when you select Applicaon Server or InTouch, or any

role (see About Role-Based Installaon) that includes the Applicaon Server Galaxy Repository. In some cases,

such as when you install a Runme Client, the Galaxy Repository is installed "silently" (without any noce it is

being installed).

While the Applicaon Server Galaxy Repository is selected for installaon, you cannot deselect the Enterprise

License components. The License Server and License Manager are installed on the Galaxy Repository node by

default.

Note: If you are using a workgroup, the License Manager and License Server must be installed on the same node.

You will need to congure the License Server and acvate your product licenses before using the products you

install. For detailed informaon about product licensing and acvaon, refer to the AVEVA Enterprise Licensing

Guide (AELicenseManagerGuide.pdf). You can access it aer installaon is complete from the AVEVA Enterprise

License Manager node, under the AVEVA start directory.

AVEVA Enterprise Licensing

The AVEVA Enterprise License Server acquires, stores, and serves licenses for all installed AVEVA soware,

including all System Plaorm products. The AVEVA Enterprise License Server and Manager work together to

provide centralized management of all your product licenses.

Version 2023

Page 10

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

For products and roles that do not install the License Server on the same node, you will have to provide the

locaon (node name) of the License Server.

The basic product installaon and license acvaon workow is:

1. Install System Products, along with the AVEVA Enterprise License Server and License Manager. See Installing1.

System Plaorm.

2. Congure the AVEVA Enterprise License Server (and Historian, if installed). See AVEVA Enterprise License2.

Server Conguraon.

3. Start the License Manager. The License Manager is browser-based, and is located in the AVEVA folder (Start >3.

AVEVA > Enterprise License Manager). The License Manager uses the following URL:

hp://localhost/AELicenseManager

Note: If you are running the License Manager from a remote node (not the License Server/Galaxy Repository

node), substute the node name for localhost.

The License Manager opens in your browser.

4. If a License Server is displayed, click on it to select it. If no License Servers are displayed, click the Add Server

buon, and then enter the computer name of the License Server, or select the computer name from the

drop down.

5. Refer to the AVEVA Enterprise Licensing Help for opons and procedures to acvate licenses.5.

Note: Changes to licensing, such as switching license servers or acvang a new license, should not be done

for a product that is already running. Depending on the product, it may take up to 30 minutes to acquire a

new or changed license. To immediately acquire a license, restart the aected product. However, product

interdependencies may require you to restart the node to force the immediate acquision of the license.

AVEVA System Monitor Installation

The AVEVA System Monitor constantly checks the License Server to ensure that it is accessible. In the event that

the soware on a node is unable to acquire a license, the System Monitor sends a warning so you can quickly x

licensing acquision issues to ensure that operaons are not interrupted.

The AVEVA System Monitor consists of the following components:

Version 2023

Page 11

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

•System Monitor Agent: The System Monitor Agent maintains the manifest of user-dened rules, handles•

monitoring of the machine to detect unhealthy condions, and securely communicates with the System

Monitor Manager to report those condions. The System Monitor Agent is installed by the System Monitor

Agent Install Manager on every System Plaorm node, including the System Monitor Manager node.

The System Monitor Agent communicates with the System Monitor to monitor the license acquision from

the node to the license server.

•System Monitor Manager: The System Monitor is automacally selected for installaon whenever the•

Galaxy Repository feature is selected. Note that you can use the Customize Installaon opon to deselect the

System Monitor, and then select for installaon on a dierent node. The System Monitor also has an SMTP

server that can send email nocaons if a process it is monitoring requires aenon.

For each System Plaorm node, conguraon of the System Monitor is required aer installaon. The System

Monitor Agent on each System Plaorm node must be congured to point to the System Monitor node. The

System Monitor node must be congured to point to itself (the System Monitor Manager Name is the node

name). The System Monitor Manager node also requires conguraon of its SMTP server and email addresses

for nocaons. See Advanced System Monitor Conguraon for addional informaon.

In addion to the license monitoring funconality that the System Monitor provides by default, your System

Plaorm licenses include the ability to congure System Monitor on a single node to monitor and manage the

performance and availability of the core AVEVA soware, the engineered soware applicaon(s), and the related

hardware and network infrastructure. To congure this addional funconality, see the AVEVA System Monitor

User Guide.

Important: If you have a System Monitor license and are running a full version of SQL Server (not Express), you

can congure System Monitor Reports. This feature is only available for fully-licensed System Monitor

installaons, not basic mode, and is not available if you are running SQL Server Express. If your System Monitor

installaon will be fully licensed, the SQL Server Reporng Services (SSRS) server should be congured and the

services started before iniang installaon of the System Monitor Manager. This will enable deployment of

System Monitor Reports. If SSRS is not congured before installaon of the System Monitor Manager, reports will

have to be manually deployed. See the AVEVA System Monitor User Guide for addional informaon.

Selecting System Platform and System Platform Enterprise

Components

This guide describes how to install AVEVA™ System Plaorm and System Plaorm Enterprise. System Plaorm

Enterprise provides addional cloud-based capabilies and is installed from its own separate DVD. Unless

otherwise noted, all informaon in this guide applies to both products.

The following tables list the System Plaorm and System Plaorm Enterprise components available for

installaon. Most components are common to both, while some widgets, apps, and other components are

available for installaon to only one.

AVEVA Applicaon Server and OMI Components System

Plaorm

System

Plaorm

Enterprise

System Plaorm IDE Yes Yes

Applicaon Server Galaxy Repository Yes Yes

Version 2023

Page 12

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

AVEVA Applicaon Server and OMI Components System

Plaorm

System

Plaorm

Enterprise

Applicaon Server Plaorm (runme) Yes Yes

Operaons Management Interface (OMI) ViewApp (runme) Yes Yes

OMI Web Server No Yes

OMI Workspaces No Yes

AVEVA OMI Apps System

Plaorm

System

Plaorm

Enterprise

OMI Content Presenter App Yes Yes

OMI Map App Yes Yes

OMI Standard Apps (included with System Plaorm 2020 R2

SP1)

Yes Yes

OMI Power BI App No Yes

OMI PI Vision App No Yes

OMI Sankey App No Yes

AVEVA OMI Widgets System

Plaorm

System

Plaorm

Enterprise

Grid View Widget Yes Yes

Carousel Widget Yes Yes

QRCode Scanner Widget Yes Yes

Web Browser Widget Yes Yes

Teamwork Widget Yes Yes

OMI ScaerChart Widget No Yes

OMI Breadcrumb Widget No Yes

OMI Graphic Repeater Widget No Yes

OMI Hamburger Widget No Yes

OMI Map App Widget No Yes

OMI Navigaon Tree Widget No Yes

Version 2023

Page 13

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

AVEVA OMI Widgets System

Plaorm

System

Plaorm

Enterprise

OMI Title Bar Widget No Yes

AVEVA InTouch HMI and InTouch Access Anywhere

Components

System

Plaorm

System

Plaorm

Enterprise

InTouch WindowMaker Yes No

InTouch WindowViewer Yes No

InTouch Web Server (Web Client) Yes No

InTouch Workspaces Yes No

InTouch Access Anywhere Server Yes Yes

InTouch Access Anywhere Secure Gateway Yes Yes

AVEVA Historian System

Plaorm

System

Plaorm

Enterprise

Historian Server (Desktop/Server) Yes Yes

Historian Client Web (Insight Local) Yes Yes

Historian Client Desktop Yes Yes

Insight Publisher Yes Yes

AVEVA Common Services System

Plaorm

System

Plaorm

Enterprise

Communicaon Driver Pack Yes Yes

Common Services Framework Yes Yes

AVEVA Enterprise Licensing Yes Yes

System Monitor Yes Yes

Supported Operating Systems for System Platform 2023

Important! System Plaorm 2023 is supported on 64-bit operang systems only.

System Plaorm 2023 is supported on the following Windows client and server operang systems (64-bit only).

This list was compiled at the release of System Plaorm 2023. Check the web site for the latest informaon.

Version 2023

Page 14

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Semi-Annual Channel Releases:

• Windows 10 20H1 SAC Professional, Enterprise, and IoT Enterprise•

• Windows 10 20H2 SAC Professional, Enterprise, and IoT Enterprise•

• Windows 11 20H1 SAC Professional, Enterprise, and IoT Enterprise•

• Windows 11 20H2 SAC Professional, Enterprise, and IoT Enterprise•

Long Term Service Channel Releases:

• Windows 10 LTSC Enterprise, IoT Enterprise 2019 (1809)•

•Windows 10 LTSC Enterprise, IoT Enterprise 2021 (21H2)

•

•Windows 11 LTSC Professional, Enterprise, and IoT Enterprise

•

•Windows Server 2016 LTSC Standard and Datacenter

•

•Windows Server 2019 LTSC Datacenter, Essenals, Standard

•

•Windows Server IoT 2016 LTSC

•

•Windows Server IoT 2019 LTSC

•

•Windows Server 2022 LTSC Standard and Datacenter

•

Note: System Plaorm is no longer supported on any version of Windows 8.1, or Windows Server versions

prior to 2016.

Supported InTouch Access Anywhere Clients

InTouch Access Anywhere has been tested in the following HTML5-capable browsers:

•Google Chrome version 98.0.4758.80 and newer

•

•Firefox version 96.03 ESR and newer

•

•Microso Edge Non-Chromium•

•Microso Edge Chromium 97.0.1072.76 and newer•

•Safari version 15.2 and newer (Mac and iOS only) (Not Windows)

•

•Opera version 83.0.4254.16 and newer

•

System Sizing Guidelines

The following table provides guidelines for hardware conguraons suitable for System Plaorm 2023, based on

applicaon size. These guidelines are subject to the limitaons of your Windows operang system, and if

applicable, to the SQL Server edion (Express, Standard, or Enterprise). See the Technology Matrix on the AVEVA

Global Customer Support website for supported versions of Windows operang systems and SQL Server.

•An HD display is recommended for engineering tools such as the System Plaorm IDE.

•

•A 64-bit operang system is required, regardless of system size.

•

•A Windows Server operang system is required for large installaons.

•

Version 2023

Page 15

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

• SQL Server Express is supported only for small systems, that is, installaons with less than 25,000 I/O per•

node.

•Pagele.sys, the Windows paging le (also called the swap le or virtual memory le), must be enabled. The•

Windows default seng is enabled.

Denions

In the table below, hardware guidelines for dierent types of System Plaorm are listed. Denions for the

terminology used in the table are:

Level (Minimum and Recommended)

Minimum level describes the baseline hardware conguraon that will provide at least minimally acceptable

performance for the role. Recommended level describes an expanded hardware set that provides improved

performance.

Applicaon Server Node

Applicaon Server nodes, also called IDE nodes, are engineering workstaons. These are used for creang,

eding, and deploying objects.

Galaxy Repository Node

Galaxy Repository nodes, also called GR nodes, host the galaxy database once it has been deployed from an

Applicaon Server node.

Historian Server Node

Historian Server nodes host the AVEVA Historian. At its core, the Historian is essenally a Microso SQL

database server.

Thin Client

Thin clients include include smart phones and tablets. In the context of System Plaorm, thin clients are

plaorms for web browsers and remote desktop sessions (for example, InTouch Access Anywhere clients).

Client

In the context of System Plaorm, clients are computers that can be used for development applicaons, such

as remote IDE workstaons, as well as for run-me applicaons like WindowViewer, AVEVA OMI ViewApps,

and Historian Insight.

The following guidelines are provided for reference only. The system conguraon required for your applicaon

will depend on mulple factors, including but not limited to the size and complexity of the applicaon, and the

features and components used.

Applicaon Level Logical

Processors 1RAM 3Free Disk

Space 2, 3 Network Speed

Applicaon Server Nodes 5

Small Applicaon

(1 - 25,000 I/O per Node)

Minimum 4 2 GB 100 GB 100 Mbps

Recommended 8 4 GB 200 GB 1 Gbps

Medium Applicaon

(25,000- 50,000 I/O per Node)

Minimum 8 8 GB 200 GB 1 Gbps

Recommended 16 12 GB 500 GB 1 Gbps

Large Applicaon

(> 50,000 I/O per Node)

Minimum 16 16 GB 500 GB 1 Gbps

Recommended 32 24 GB 1 TB Dual 1 Gbps

Version 2023

Page 16

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Applicaon Level Logical

Processors 1RAM 3Free Disk

Space 2, 3 Network Speed

Galaxy Repository Nodes

Small Galaxy

(1 - 50,000 I/O per Node)

Minimum 4 2 GB 100 GB 100 Mbps

Recommended 8 4 GB 200 GB 1 Gbps

Medium Galaxy

(50,000 - 200,000 I/O per Node)

Minimum 8 8 GB 200 GB 1 Gbps

Recommended 16 12 GB 500 GB 1 Gbps

Large Galaxy

(> 200,000 I/O per Node)

Minimum 16 16 GB 500 GB 1 Gbps

Recommended 32 24 GB 1 TB Dual 1 Gbps

Historian Server Nodes

Small Historian

(1 - 50,000 Historized Tags per Node)

Minimum 4 2 GB 100 GB 100 Mbps

Recommended 8 4 GB 200 GB 1 Gbps

Medium Applicaon

(50,000 - 200,000 Historized Tags per

Node)

Minimum 8 8 GB 200 GB 1 Gbps

Recommended 16 12 GB 500 GB 1 Gbps

Large Applicaon

(> 200,000 Historized Tags per Node)

Minimum 16 16 GB 500 GB 1 Gbps

Recommended 32 24 GB 1 TB Dual 1 Gbps

Thin Client Node

RDP clients, InTouch Access Anywhere

browsers, mobile devices

Minimum 2 512 MB N/A 100 Mbps

Recommended 4 2 GB N/A 100 Mbps

Client Node

WindowViewer, ViewApp, Historian

Client, Remote IDE

Minimum 4 1 GB 100 GB 100 Mbps

Recommended 8 4 GB 200 GB 1 Gbps

Remote Desktop Server Nodes

Basic RDS, InTouch Access Anywhere

Server

Supports up to 15 concurrent remote

sessions

Minimum 8 8 GB 200 GB 1 Gbps

Recommended 16 12 GB 500 GB 1 Gbps

Large RDS, InTouch Access Anywhere

Server

Supports up to 30 concurrent remote

sessions

Minimum 16 16 GB 500 GB 1 Gbps

Recommended 32 24 GB 1 TB Dual 1 Gbps

All-In-One Node 4 (all products on a single node)

Small Applicaon:

1,000 I/O max

Minimum 8 8 GB 200 GB 100 Mbps

Recommended 12 12 GB 500 GB 1 Gbps

Version 2023

Page 17

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Applicaon Level Logical

Processors 1RAM 3Free Disk

Space 2, 3 Network Speed

Medium Applicaon:

20,000 I/O max

Minimum 12 16 GB 500 GB 1 Gpbs

Recommended 16 32 GB 1 TB 1 Gbps

Large Applicaon 6

100,000 I/O max

Minimum 20 32 GB 2 TB 1Gbps

Recommended 24 64 GB 4 TB 1 Gbps

1) To calculate the number of logical processors: mulply the number of physical cores by the number of threads each core can run. A four

core CPU that runs two threads per core provides eight logical processors. The terms "Hyper-Threading and "simultaneous

multhreading" (SMT) are also used to describe logical processors.

2) SSD drives are highly recommended.

3) In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource ulizaon.

4) For opmal performance of all-in-one nodes, a high clock speed (>2.8 GHz) is recommended.

5) For Applicaon Server plaorm nodes, it is recommended that you deploy no more than two AppEngines per logical processor

(typically one primary AppEngine and one backup).

6) For large applicaons on all-in-one nodes, dual XEON processors are recommended.

Supported and Recommended Node Hardware Types

Product Server Node Thin Client-

Server Node

Client Node Thin Client All-In-One

Applicaon Server

Galaxy Repository Preferred Supported Supported No Supported

Applicaon Engine Preferred Supported Supported No Supported

IDE Preferred Supported Supported RDP Supported

AVEVA OMI ViewApp Runme Supported Supported Preferred ITAA/RDP Supported

InTouch Standalone

WindowMaker (No Modern Apps) Supported Supported Preferred RDP Supported

WindowMaker (with Modern Apps) Preferred Supported Supported RDP Supported

WindowViewer / InTouch ViewApp (runme

only)

Supported Supported Preferred ITAA/RDP Supported

InTouch for System Plaorm

WindowMaker (with Managed Apps) Preferred Supported Supported RDP Supported

WindowViewer / InTouch ViewApp (runme

only)

Supported Supported Preferred ITAA/RDP Supported

InTouch Access Anywhere

InTouch Access Anywhere Server Supported Preferred No No Supported

InTouch Access Anywhere Client (HTML5

Browser)

Browser Browser Browser Browser Browser

Version 2023

Page 18

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Product Server Node Thin Client-

Server Node

Client Node Thin Client All-In-One

InTouch Access Anywhere Secure Gateway Supported No No No No

Historian

Historian Server Preferred Supported Supported No Supported

AVEVA Insight Browser Browser Browser Browser Browser

Historian Client Supported Supported Preferred RDP Supported

Support Components

OI Gateway Preferred Supported Supported No Supported

AVEVA Enterprise License Server Preferred Supported Supported No Supported

AVEVA Enterprise License Manager Preferred Supported Supported No Supported

AVEVA Enterprise License Manager Client Browser Browser Browser Browser Browser

Required Installation Order of Additional Products

Some AVEVA products released prior to System Plaorm 2023 must be installed before you install System

Plaorm. These are:

•Alarm Adviser (2014 R2 SP1 and prior versions)

•

•Intelligence (2017 SP1 and prior versions)

•

• Recipe Manager Plus (2017 Update 1 and prior versions)•

• Skelta BPM (2017 R2 Update 1 and prior versions)•

If any of the above products will be installed on the same system as System Plaorm 2023:

1. Install the product (Alarm Adviser, Intelligence, etc.) rst.

2. Then, install System Plaorm 2023.2.

InBatch 2017 or prior versions must installed aer installing System Plaorm 2023.

1. Install System Plaorm 2023.1.

2. Then, install InBatch.

Common Components

System Plaorm 2023 includes several shared modules that are needed for the products to operate. You will see

some or all of the following common components listed under Programs and Features in the Windows Control

Panel aer installaon is complete, depending on your installaon selecons for the node:

Version 2023

Page 19

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Component Version Required/

Oponal

AVEVA Communicaon Drivers Pack 2023 7.4.0 Required

AVEVA Plaorm Common Services 7.0 7.022168.5 Required

AVEVA Help 1.0.0 Oponal

AVEVA Enterprise License Manager 3.7.002 Required

AVEVA Enterprise License Server 3.7.002 Oponal (see

note)

AVEVA Enterprise Licensing Plaorm

AVEVA Enterprise Licensing Plaorm (x86)

3.7.002

Required

Operaons Control Logger 22.1.000 Required

Operaons Control Management Console 22.1.000 Required

System Monitor Manager 1.4 1.4.0 Oponal

Note: The License Server is required on nodes with the Galaxy Repository.

Windows Network Configuration

If you are installing System Plaorm products on more than one node, we recommend that you use domain

based networking. Domain based (client-server) networks provide beer user account security and management

than workgroup based (peer to peer) networks.

System Plaorm does not support mixed Windows workgroup/domain environments. While workgroups are

supported, you cannot use workgroup nodes within a domain environment.

Note: Do not install the Galaxy Repository on a computer that is used as a domain controller or an Acve

Directory server.

Operaons that rely on inter-node communicaons may not funcon correctly in a workgroup based Applicaon

Server installaon. Examples of this type operaon include connecng to a remote IDE, or viewing the status of a

remote plaorm.

If you must use workgroup based networking, you can avoid communicaons issues by enabling "everyone

permissions" for anonymous users. To enable these permissions, go to:

Local Security Policy > Local Policies > Security Options > Network Access: Let everyone

permissions apply to anonymous.

Or, you can enter the following command from an administrator command prompt:

reg add HKLM\System\CurrentControlSet\Control\Lsa /v EveryoneIncludesAnonymous /t

REG_DWORD /d 0

Version 2023

Page 20

AVEVA™ System Plaorm Installaon Guide

Chapter 1 – Preparing for System Plaorm Installaon

Page is loading ...

Schneider Electric AVEVA System Platform Installation guide

Brand: Schneider Electric

Model: AVEVA System Platform

Category: Software manuals

Type: Installation guide

Download PDF

report

Schneider Electric AVEVA System Platform Installation guide

Schneider Electric AVEVA System Platform Installation guide

Other documents