Get started with AVEVA Registers Gateway
- Last UpdatedJun 25, 2026
- 3 minute read
This section lists the hardware and software requirements and provides details about installing and running the Registers Gateway.
Hardware Requirements
Ensure the following hardware requirements are met prior to working with the Registers Gateway:
|
Component |
Minimum |
Recommended |
|
Memory |
8 GB |
32 GB |
|
Hard Disk Drive |
80 GB |
|
|
CPU |
Intel® Xeon® processor, 3 GHz, Dual core |
Intel® Xeon® processor, 3 GHz, Quad core |
Software Requirements
Ensure the following software requirements are met prior to working with the Registers Gateway:
|
Application |
Supported Version |
|
Microsoft .NET Framework |
.NET 10 |
|
.NET Runtime |
.NET 10 Runtime (10.0.1 or higher) |
|
Windows Server |
2022 (64-bit),2019 (64-bit) |
|
Information Standards Manager (ISM) |
2.2.3.0 or later |
Note: The Registers Gateway supports AIM 5.1.12 and later.
Data Formats
Register data may be updated from different formats. Multiple formats may be supplied in a single update transaction.
|
Format |
Description |
|---|---|
|
CSV Strict (RFC4180) |
CSV data is read using strict RFC4180 rules, optionally specifying an alternate separator, new line and quote strings (multi-character permitted). |
|
TAB Strict (RFC4180) |
Same as CSV Strict, with a TAB character separator. |
|
EXCEL |
XLS or XLSX files. |
|
CSV Relaxed |
CSV is read as Excel reads, which may in some cases read data incorrectly where quoting is incorrect. |
|
TAB Relaxed |
Same as CSV Relaxed, with a TAB character separator. |
|
EIWM XML |
AIM EIWM XML format, with root objects and datasets only. |
|
XML Simple |
XML is read with a simple XPath expression. |
|
JSON Simple |
JSON is read with a simple JPath expression. |
Security Guidelines
As the Registers Gateway processes and converts data from multiple data sources into a compatible file format that is loaded into AIM, it needs to read, write and modify files.
The following are the security best practice recommendations:
Use the principle of least privilege - Grant the user account that is used to run the Registers Gateway only read access. Grant write or update access only to the specific files and folders it needs to modify. For example, within a project folder, you can grant read only access to the Input folder, write access to the Log folder and modify access to the Output files.
Restrict the database user account with the read-only access to the databases (or the selected tables/views) from which information needs to be read as
lookup entries during transformation. It is required to avoid accidental addition, change or deletion of sensitive data.
If the Registers Gateway is configured to read data from an SQL Server database, for example, in a lookup, then to secure the data which is in transit, you can configure an SSL-encrypted connection between the Registers Gateway and the database.
You do not need to adjust your Firewall settings or User Account Control settings when you use the Registers Gateway.
The input-output files, Registers Gateway configuration and Registers Gateway exe are to be stored in a secure location accessible only to authorized users.
Note: If the security recommendations are not suitable for your environment, you must investigate what is the most suitable approach for your environment and apply those practices.
Running the Gateway
To run the Registers Gateway:
-
Download AVEVA.Registers.Gateway.zip, unzip the file and extract the setup files in a system location.
-
Navigate to the path using the command prompt and run the AVEVA.Registers.Gateway.exe by passing the configuration file as an input parameter.
Installation Guidelines
For the information relating to installation, refer to Configuration Options.