AVEVA Product Feedback


Add a new idea Subscribe
Status Completed
Categories General
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

compatibility

the compatibility of products (e.g. Data Archive with PI AF) is not straightforward. e.g. regarding to documentation (release notes, Instal-guides) it's possible to combine Dataarchive 2012 with AF 2017-R2. and indeed it's possible to use it in combination, but the installation is requiring the following steps: - Install AF Server 2017 R2 - Install AF Client 2017 R2 on Dataarchive Server - Uninstall PI Network Subsystem on Dataarchive Server - Install PI Server 2012 (Dataarchive) - Install AF Client 2017 R2 on Dataarchive Server - Perform MDB to AF migration thats not straight forward and should be mentioned in the documentation (list the restrictions / requirements).
  • ADMIN RESPONSE
    Aug 20, 2022
    This is a case of forward/backwards compatibility. It's typically not possible to account for forward compatibility but as a general rule we provide backwards compatibility when possible. In this scenario, since AF 2017 R2 is newer than Data Archive 2012, you should first install Data Archive 2012 first, then install AF 2017 R2 and the backwards compatibility built into the upgrade process would take care of the PI Network Subsystem dependency.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    I'm actually not sure what problem you are trying to solve. Certainly there are quirks with installing a newer AF Server with an old PI Data Archive. Why are you bringing up PI Data Archive 2012 in the first place? Why not use PI Data Archive 2016 R2, largely considered the most stable version.
  • Guest
    Reply
    |     Aug 20, 2022
    In response to Gerhard Matzen, "I'm actually not sure what problem you a..." The background is as follows. we use our system in a regulated environment (pharmaceutical industrie). the effort to change the system is big. as the compatibility list showed it works, we planed to keep the actual version of the PI Dataarchive and update only PI AF (to use the good features in the new versions). the benefit of an compatibility list in my opinion is to find out what works and what doesn't. the installation of AF Client on the server side is not a big problem (as well i expect to see the requirement in the documentation). what i don't see as straight forward is to uninstall a component after this (PI Network Subsystem) and then reinstall this component.
  • Guest
    Reply
    |     Aug 20, 2022
    In response to Gerhard Matzen, "I'm actually not sure what problem you a..." The background is as follows. we use our system in a regulated environment (pharmaceutical industrie). the effort to change the system is big. as the compatibility list showed it works, we planed to keep the actual version of the PI Dataarchive and update only PI AF (to use the good features in the new versions). the benefit of an compatibility list in my opinion is to find out what works and what doesn't. the installation of AF Client on the server side is not a big problem (as well i expect to see the requirement in the documentation). what i don't see as straight forward is to uninstall a component after this (PI Network Subsystem) and then reinstall this component.