Customize a Response File
- Last UpdatedFeb 05, 2024
- 3 minute read
To create a customized set of options for a silent installation of Plant SCADA, you should start by creating a copy of one of the provided response files. Four are available for use:
-
All.txt – installs all components (including all communication drivers)
-
DevelopmentWorkstation.txt – a typical set of components for a development workstation
-
RuntimeClient.txt – a typical set of components for a runtime client
-
Server.txt – a typical set of components for runtime server.
These are available from the following directory within the Plant SCADA installation media:
InstallFiles\ResponseFiles
You can then use the following set of properties to specify the settings for the forms normally seen when interacting with the Plant SCADA installer.
|
Form Name |
Properties |
Allowable Values |
|
ComputerRoleSelectionForm |
SelectedComputerRoleName |
One of the following values:
|
|
ServerRoleSelectionForm |
ServerRolesList |
Multiple server names separated by commas:
|
|
FeaturesForm |
SFeatureList |
ALL or multiple feature names separated by commas (see below). |
|
SecurityGroupForm |
AddUserToGroups True adds the current Windows user to created groups. |
True or False |
|
FirewallForm |
ModifyFireWall |
True or False |
|
CustomDestinationSelectionForm |
InstallDirPath |
A valid absolute folder path |
|
ProgramDataPath |
A valid absolute folder path |
Note: A response file needs to include an entry for each of the six forms it represents. If you remove any of the forms, installation will not succeed.
To specify the features that are installed via the FeaturesForm.SFeaturesList property, you can enter the following as a comma separated list.
|
Components |
Description |
SFeaturesList setting |
|
All components |
Includes all components listed below. |
ALL |
|
Runtime client |
Provides runtime client display and server level processing of I/O, trends, alarms, reports, and CtAPI. |
AVEVA Plant SCADA.Runtime |
|
Configuration Environment |
Plant SCADA Studio, graphics, Cicode Editor and other configuration tools for building your system. This option also requires the Runtime and Platform Common Services components. |
AVEVA Plant SCADA.Configuration |
|
Deployment Server |
Provides server functionality for managing the runtime versions of your system and deployment to runtime computers. |
AVEVA Plant SCADA.DeploymentServer |
|
Industrial Graphics Web Server |
Provides server functionality for managing the runtime versions of your system and deployment to runtime computers. |
AVEVA Plant SCADA.InTouchWebClient |
|
OPC UA Server |
Provides server functionality that allows OPC UA clients to browse and subscribe to Plant SCADA I/O data. |
AVEVA Plant SCADA.OpcUaServer |
|
Project DBF Add-in for Microsoft Excel |
Provides bulk editing of configuration databases in Microsoft Excel. |
Extensions.BinFiles |
|
Software Update by Schneider Electric |
Provides notification of updates, new versions and telemetry information. |
Extensions.SEP_Features |
|
AVEVA License Server |
Provides server functionality to acquire, store, maintain, and serve licenses to your installed AVEVA software. |
AVEVA Common Components.AELicenseServer |
|
AVEVA License Manager |
Browser-based client application for accessing and maintaining licenses for AVEVA Enterprise Software products. |
AVEVA Common Components.AELicenseManager |
|
Platform Common Services Note: You only need to include this component in a response file if you are setting up a computer as a standalone System Management Server. It will automatically be installed as a prerequisite for any other Plant SCADA components. |
Provides the following services: System Management Server Identity Management Service Data Storage Service Diagnostic Portal |
AVEVA Common Components.ASBRuntime |
|
Plant SCADA Communications Drivers These can include: ABCLX |
Installs software to enable communication with I/O devices using a specific protocol. |
AVEVA Plant SCADA Communication Drivers.<driverName>Driver For example: AVEVA Plant SCADA Communication Drivers.BACNETDriver |
Note: You can also specify Configurator settings within a response file. See Add Configurator Settings to a Response File.
Example
The following demonstrates the response file you could use to install a development workstation with all available features.
<responsefile>
<install>
ComputerRoleSelectionForm.SelectedComputerRoleName=DevelopmentWorkstation
FeaturesForm.SFeatureList=ALL
SecurityGroupForm.AddUserToGroups=true
FirewallForm.ModifyFireWall=true
CustomDestinationSelectionForm.InstallDirPath=C:\Program Files (x86)\AVEVA Plant SCADA
CustomDestinationSelectionForm.ProgramDataPath=C:\Program Data\AVEVA Plant SCADA 2023 R2 </install>
</responsefile>
Note: You can determine if the silent configuration of plugins has been successful at the
end of an installation using the XML log file located at:
C:\Program Files (x86)\Common Files\ArchestrA\SilentConfigurator