AVEVA (formerly Wonderware) System Platform
versiondog supports the management of AVEVA System Platform galaxies and enables the automatic creation of backups and the cyclical monitoring of galaxies.
Info
AVEVA used to be called Wonderware. For technical reasons, the original name is still used in versiondog. There are two component types: Aveva System Platform and Wonderware System Platform. Depending on your version, you can use either component type.
Supported versions
AVEVA (formerly Wonderware) System Platform | 2012 R2 | 2014 R2 SP1 | 2017 SP1 Update3 | 2017 SP3 | 2020 R2 |
---|---|---|---|---|---|
versiondog 6.0.0 | ✓ | ✓ | |||
versiondog 7.0.0 | ✓ | ✓ | ✓ | ||
versiondog 8.0.0 | ✓ | ✓ | ✓ | ✓ | |
versiondog 9.0.0 | ✓ | ✓ | ✓ | ✓ | ✓* |
*Currently, it is not possible to perform a SmartCompare for version 2020 R2. Instead, a binary comparison is performed automatically. Uploads and corresponding disaster recovery can be performed in full.
Requirements
-
To carry out uploads and comparisons, a compatible version of the editor must be installed on the same computer where the server or an agent is running.
-
Complete backup (CAB)
- Consists of one file containing all objects. Example:
{Galaxy name}.cab
. - Backup and full restoration (disaster recovery) of the complete Galaxy are possible.
- An MS SQL Server is required for a comparison. The MS SQL Server must be the same version as the one used by the GRNode.
- To execute a job, both Bootstrap and Archestra IDE must be installed and licensed.
- The IDE (including GRAccess) is required for the upload.
- Consists of one file containing all objects. Example:
-
Exported objects (AAPKG)
- Only selected objects are included.
- Comparison is possible, but no upload can be configured.
- No additional software is required for comparisons.
- The IDE (including GRAccess) is required for automatic exports during versioning.
Integration features
- Custom component types
- Integrated AVEVA (formerly Wonderware) System Platform project tree
- Consistent change history
- Automatic export of existing aaPKG and CAB files
- SmartCompare for Galaxies (server version <-> backup detailed comparison)
- Automated monitoring of differences between the automatically created backup and the current version of the Galaxy on the server (server version <-> backup detailed comparison)
Configuration
To get the basic workflow for intergrating the device, open General workflow.
Device-specific settings for this device, such as job configuration, can be found on the following pages:
- Configuring the comparison
- Integrating a Galaxy
- Configuring an SQL Server for comparison
- Configuring jobs
- Integrating exported objects
Related topics