ENOVIA VPM V5 Prerequisites

This task describes the prerequisites that must be implemented before you can use Coexistence and Migration for ENOVIA VPM V5.

Important: The server batch mode is fully supported for the ENOVIA VPM V5 connector.

This page discusses:

Version Compatibility

The following table describes the versions of ENOVIA VPM V5 and ENOVIA 3DEXPERIENCE that are compatible with Coexistence and Migration.

3DEXPERIENCE ENOVIA VPM V5
3DEXPERIENCE R2019x

V5-6R2018 SP4+

V5-6R2019 GA+

3DEXPERIENCE R2020x

V5-6R2018 SP5+

V5-6R2019 SP3+

V5-6R2020 GA+

3DEXPERIENCE R2021x

V5-6R2019 SP4+

V5-6R2020 SP1+

3DEXPERIENCE R2022x

V5-6R2020 SP5+

V5-6R2021 SP3+

V5-6R2022 beta

Legend:

  • SPx+: fully functional for the specified level starting with SPx
  • GA+: fully functional for the specified GA level and all subsequent releases

Important: You can install a V5 compatible level as a frontal for a coexistence scenario.

Map V5 Objects to 3DEXPERIENCE

You must have the same metacontent implementation in both ENOVIA VPM V5 and 3DEXPERIENCE before you begin using Coexistence and Migration.

You must run the Resource Generator tool to ensure that the appropriate metadata and mapping files are generated correctly and put in the right place before starting any coexistence scenario. A default out-of-the-box customization of the 3DEXPERIENCE data model is delivered with the legacy source to support access to non-customized data. If data customization is required, an additional two-step mapping operation is necessary. For more information, see Resource Generator.