Migrate Old Data Sources to Version 3.2
- Last UpdatedJun 27, 2025
- 2 minute read
- Engineering
- Integration Service 3.2
- Integrators
Migrate Data Sources one AIS Server to Another Server
AVEVA Integration Service only displays the data sources created by this AIS Server not all the data sources available.
When creating Data sources, it is associated with Device ID which is the Product ID of the Server, can be found in System information.
To migrate the data sources created in AIS server to another or when Product ID of the Server is changed. You need move AISDatasources.DB file and update the Device ID information of Data source using AIS APIs.
Migrate Data Source, AIS 3.1.1 and later to 3.2
When you migrate from AIS 3.1.1 or later to 3.2 without Device ID being changed, Data source migration happens automatically when upgrade software to newer version.
Migration Hybrid integration AIS 3.1.1 and later to AIS on CONNECT
To facilitate a smooth transition for customers moving towards AIS CONNECT Service for integration, need to execute the Data Migration Tool/executable in command line to achieve this.
This tool available AIS 3.2 installation folder with name "AVEVA.AIS.Config.DatasourceMigration.exe".
The tool takes below input parameters
-
DBFile <DBFilePath> : File Path of AISDatasources.DB to be migrated.
-
DBPWD <DBPassword>: Password of AISDatasources.DB you have set for
-
SAT <ServiceAccessToken>: CONNECT Service Access Token of AIS created for role "Data source Admin" tool will use to interact with AIS CONNECT Service.
-
ConfigURL <ConfigAPIURL>: End point of AIS CONNECT Service Configuration API always https://eu.ais.connect.aveva.com/config.
-
DeviceId <DeviceId> : Product ID of the Server, update the Device ID information of Data sources.
Migrate Data Source AIS 3.1.1 and below
If you are on a version earlier than version 2.3.2, you can use the Migration Tool to migrate your data sources to version 3.0. This is available in AVEVA™ Integration Service 3.0.
Note: If you are on 3.0, start by upgrading to 3.1.2, and then 3.2. The installer service will automatically migrate from 3.1.2 to 3.2.
AVEVA™ Integration Service 3.0 enables administrators to to easily migrate their data sources through the use of AVEVA.IntegrationService.MigrationTool.exe available in the installation location of AVEVA™ Integration Service 3.0.