The Transition Journey

AVEVA Integration Service (WCF), is designed to facilitate integration within AVEVA Products. AVEVA Integration Service (WCF) is currently available for integration, and recent updates include the introduction of new services (AVEVA Integration Service Data API, AVEVA Integration Service Config API, AVEVA Integration Service REST API) to enhance the integration process. AVEVA Integration Service Data API, AVEVA Integration Service Config API is offered in two variants:

On-Premises Installation: Customers have the option to install AVEVA Integration Service Data API and AVEVA Integration Service Config API within their network and utilize it accordingly.

CONNECT Deployment as a Multi-Tenant Service: Alternatively, AVEVA Integration Service Data API and AVEVA Integration Service Config API are also deployed in CONNECT as a multi-tenant service. In this scenario, customers do not need to install AVEVA Integration Service Data API and AVEVA Integration Service Config API locally; they can leverage the CONNECT hosted AVEVA Integration Service Data API, AVEVA Integration Service Config API instead.

If you opt for CONNECT hosted AVEVA Integration Service Data API and AVEVA Integration Service Config API, the following steps are required:

• You must Install the AVEVA Integration Service (WCF) and AVEVA Integration Service REST API locally on your network.

• Use AVEVA Integration Service (WCF) and AVEVA Integration Service REST API to integrate with CONNECT Hosted AVEVA Integration Service Data API and AVEVA Integration Service Config API.

To facilitate a smooth transition for customers moving towards CONNECT hosted AVEVA Integration Service Data API and AVEVA Integration Service Config API, you can follow these steps:

• Install Service AVEVA Integration Service (WCF) and AVEVA Integration Service REST API locally on your network.

• Integrate AVEVA Integration Service (WCF) and AVEVA Integration Service REST API installed locally on your network with AVEVA Integration Service Data API and AVEVA Integration Service Config API in CONNECT.

• Your existing DataSources will not be migrated to CONNECT Hosted AVEVA Integration Service. Datasources need to be created manually.

This process ensures a seamless shift for customers from the local deployment of AVEVA Integration Service to its CONNECT-hosted counterpart, all while maintaining the necessary integration and Data source configuration settings.