Scribd
Upload
15 views6 pages

aveva_system_platform_deployment_system_platform_and_application_server_2024-10-07-14-30-47

Uploaded by

Jan Kowalski
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views6 pages

aveva_system_platform_deployment_system_platform_and_application_server_2024-10-07-14-30-47

Uploaded by

Jan Kowalski
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

AVEVA™ System Platform Deployment

© 2015-2024 AVEVA Group Limited and its subsidiaries. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means,
mechanical, photocopying, recording, or otherwise, without the prior written permission of AVEVA Group Limited. No
liability is assumed with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this documentation, AVEVA assumes no responsibility for
errors or omissions. The information in this documentation is subject to change without notice and does not represent a
commitment on the part of AVEVA. The software described in this documentation is furnished under a license
agreement. This software may be used or copied only in accordance with the terms of such license agreement. AVEVA,
the AVEVA logo and logotype, OSIsoft, the OSIsoft logo and logotype, ArchestrA, Avantis, Citect, DYNSIM, eDNA, EYESIM,
InBatch, InduSoft, InStep, IntelaTrac, InTouch, Managed PI, OASyS, OSIsoft Advanced Services, OSIsoft Cloud Services,
OSIsoft Connected Services, OSIsoft EDS, PIPEPHASE, PI ACE, PI Advanced Computing Engine, PI AF SDK, PI API, PI Asset
Framework, PI Audit Viewer, PI Builder, PI Cloud Connect, PI Connectors, PI Data Archive, PI DataLink, PI DataLink Server,
PI Developers Club, PI Integrator for Business Analytics, PI Interfaces, PI JDBC Driver, PI Manual Logger, PI Notifications, PI
ODBC Driver, PI OLEDB Enterprise, PI OLEDB Provider, PI OPC DA Server, PI OPC HDA Server, PI ProcessBook, PI SDK, PI
Server, PI Square, PI System, PI System Access, PI Vision, PI Visualization Suite, PI Web API, PI WebParts, PI Web Services,
PRiSM, PRO/II, PROVISION, ROMeo, RLINK, RtReports, SIM4ME, SimCentral, SimSci, Skelta, SmartGlance, Spiral Software,
WindowMaker, WindowViewer, and Wonderware are trademarks of AVEVA and/or its subsidiaries. All other brands may
be trademarks of their respective owners.
U.S. GOVERNMENT RIGHTS
Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the license agreement with
AVEVA Group Limited or its subsidiaries and as provided in DFARS 227.7202, DFARS 252.227-7013, FAR 12-212, FAR
52.227-19, or their successors, as applicable.
AVEVA Legal Resources: https://www.aveva.com/en/legal/
AVEVA Third Party Software Notices and Licenses: https://www.aveva.com/en/legal/third-party-software-license/
AVEVA™ System Platform Deployment
Contents

Contents
System Platform and Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

© 2015-2024 AVEVA Group Limited and its subsidiaries. All rights reserved. Page 3
AVEVA™ System Platform Deployment
System Platform and Application Server

System Platform and Application Server


Application Server is a core component of System Platform. The Galaxy, stored in the Galaxy Repository (GR), is
the top level object in Application Server, and encompasses the whole supervisory control system. A Galaxy is
represented by a single logical namespace and a collection of Platforms, AppEngines, and application objects.
The Galaxy defines the namespace in which all components and objects reside.
Because of its distributed nature and common services, Application Server does not require expensive server-
class or fault-tolerant computers to enable a robust industrial application.
Application Server distributes objects throughout a distributed (networked) System Platform environment,
allowing a single application to be split into a number of different component objects, each of which can run on
a different computer.
Before exploring the following System Platform topologies, review the main components and how they will be
distributed based on requirements and functionality. The main components are:

• IDE: Application Server development node (Engineering workstation). The System Platform IDE runs on this
node. If you are using InTouch HMI for System Platform for visualization, WindowMaker can reside on this
node, in addition to the IDE.
• GR: Galaxy Repository. This is the configuration database. The GR uses a Microsoft SQL Server database.
• AOS: ApplicationObject Server (run time) nodes. Multiple sets of redundant AOS nodes can be implemented.
• OI: Operations Integration nodes contain the communication drivers that function as the interface to the
PLCs in the control network.
• Historian Server. This runs the Historian database and saves historical data. The Historian also uses a
Microsoft SQL Server database.
• Visualization nodes running AVEVA OMI ViewApps or InTouch WindowViewer. There are differences in how
InTouch HMI and AVEVA OMI handle different types of controls. Consider the following:
• ActiveX controls: Allowed by InTouch, but cannot be used with OMI.
• .NET controls: For InTouch, .NET controls can be embedded directly in an Industrial Graphic (the
Industrial Graphic functions as a container for the control). For OMI, .NET controls must be placed in
panes (one control per pane). If an Industrial Graphic used in OMI contains an embedded .NET control,
OMI will strip out the control before it displays the graphic. The only way that Industrial Graphics can
interact with .NET controls in OMI is through layout scripting. You must first build a layout that hosts
both the Industrial Graphic and the .NET control in separate panes, and embed that layout into a pane.
In this case, the layout with the .NET control and Industrial Graphic is the content that is embedded into
another layout.

Each System Platform and Application Server component can be installed on its own node, or a single node can
contain multiple components. In a small system, all Application Server components can exist on a single node.
The same principles and resource requirements apply to both physical environments and virtual environments
that leverage Hyper-V or VMware.
The following figure shows a multi-node System Platform topology, running the IDE, GR, Historian, System
Management Server, License Server, OI Server, and AOS Servers on separate nodes. The IDE, GR, OI Server, and
AOS Servers are components of Application Server.

© 2015-2024 AVEVA Group Limited and its subsidiaries. All rights reserved. Page 4
AVEVA™ System Platform Deployment
System Platform and Application Server

© 2015-2024 AVEVA Group Limited and its subsidiaries. All rights reserved. Page 5

You might also like