Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Unified Engineering - Spectrum

Background Information for AVEVA Edge Connector Installation

Background Information for AVEVA Edge Connector Installation

  • Last UpdatedDec 05, 2025
  • 1 minute read

When the Edge Connector installation completes, the following configuration has been prepared:

  • The windows registry is updated with configuration for the installation.

  • An entry is added to the list of programs for uninstallation.

  • A shared folder is created (named “cloudstore”) during the installation for use by the File Sync Service.

    Note: By default, and for security reasons, no permissions are setup. Configure access for the cloud store folder (per project). Do not grant access to the db folder.

  • An encrypted JSON configuration file is created and stored on disk, to be read by the services.

    Note: Do not directly modify, move or delete the configuration file.

  • Edge Connector services are downloaded from the AVEVA Unified Engineering - Spectrum Service and registered as Windows services

  • A Windows scheduled task is registered, running between 3am and 4am local time, which updates the services if available.

The following communication ports are used between:

  • Edge Connector and CONNECT: HTTPS, TLS, port 443.

  • AVEVA Unified Engineering product component and Edge Connector: TCP/IP, TLS, ports 5005, 5006 (default).

Security Catalog

During Edge Connector installation for each edge service, a third-party component catalog (called a Security Catalog) is automatically downloaded. This catalog is downloaded and stored under the services directory, followed by the specific service name (for example, spectrum.filesyncservice), and then within the corresponding version folder.

The catalog file is created with the name:

AVEVA-[service name]-[version number].cat

Example:

AVEVA-spectrum.site.claimsservice-2.0.51.cat

This file lists all third-party components to help ensure transparency and traceability of components used during installation.

TitleResults for “How to create a CRG?”Also Available in