Role-based installation
- Last UpdatedMar 17, 2025
- 3 minute read
Role-based installation provides a combination of features specific to a node. If you are uncertain about the specific products or components you need, but you know what role your computer will play, you can opt for a role-based installation. For example, if your computer is a run-time node or a development node, you can select those roles in the role-based installation program. The System Platform installation program will install all components required for the roles that you have selected. It is recommended that you define the node you are installing and select the appropriate role before starting the installation program. During the installation, you can select a role to see its description, as described in Install System Platform.
Important: Role-based installation includes an option to install an InTouch Access Anywhere Secure Gateway node. The Secure Gateway can only be installed on a computer running a supported version of the Windows Server operating system (minimum: Windows Server 2016). To ensure security, no other System Platform components should be installed on the node.
Note: In some cases, you can still deselect a product category to remove all components under it, even if components are marked as required. For example, if you are installing a System Platform Development Server, and will be using the AVEVA OMI run time only, you can deselect the InTouch HMI category to remove all the components listed under it, including components that are marked as required. As another example, if you are installing Security Server, it is possible to deselect the System Management Server, but the resulting installed product will not be a Security Server.
Role-based installation automatically selects the product combinations required to support the specified role or roles on a node.
To modify the products selected by the role you have selected, choose the Customize Installation option when it is displayed. Role-based installation options are as follows:
|
Run-time client |
Installs InTouch HMI, OMI, OMI Web visualization run-time components, and Historian Client components for viewing historization data and trends. |
|
Remote AVEVA System Platform development client |
Installs the components, including the System Platform IDE, InTouch WindowMaker and InTouch WindowViewer, needed to develop and test both InTouch HMI and AVEVA System Platform View Apps. This option does not include the galaxy repository by default. |
|
AVEVA System Platform development server |
Installs the components, including the System Platform IDE, InTouch WindowMaker and InTouch WindowViewer, needed to develop and test both InTouch HMI and AVEVA System Platform View Apps. This option includes the galaxy repository by default. The galaxy repository requires SQL Server. |
|
AVEVA Historian Server node |
Installs everything needed to host a Historian Server and store historical data. |
|
AVEVA InTouch Access Anywhere Secure Gateway node |
Installs the components needed to access access AVEVA InTouch HMI applications hosted on an RDP session host via HTML5 compatible web browsers. It is used in combination with the InTouch Access Anywhere Server. No other System Platform components should be installed on a computer with this option. |
|
AVEVA Enterprise License Server node |
Installs the AVEVA Enterprise License Server to support the licensing infrastructure on this computer. |
|
System Monitor Manager node |
Installs the AVEVA System Monitor to proactively monitors the health of System Platform software products and the machines that host those products. The System Monitor Manager should be installed on the same machine as the Galaxy Repository. |
|
All-in-one node |
Installs all AVEVA System Platform products except AVEVA InTouch Access Anywhere on a single node. |
|
Custom |
The custom option lets you individually select which products, components, and features to install on the node. All other selected options are ignored when this is selected. |