Upgrading from a Previous EVT/EVP Installation to 3DEXPERIENCE R2022x

This section explains how to migrate from a previous EVT/EVP installation to 3DEXPERIENCE R2022x. EVT stands for “ENOVIA Team Multi-discipline Collaboration Platform”, which is included in EVP. EVT was a part f SMB/PLMExpress.


Before you begin: For a migration from V6R2014x to 3DEXPERIENCE R2022x GA, the minimum level of EVP V6R2014x is EVP V6R2014x HF2.
  1. Install 3DSpace as explained in Installing 3DSpace, in a new path.

    For example:

    C:\DassaultSystemes\R2022x\3DSpace

  2. Provide all necessary database information and PLM administrator username and password used in the original installation.
  3. If you performed baseline behavior parametrization of the previous release, perform upgrade operations for parametrization.

    Note: If you are upgrading from a V6R2012x or a newer release, steps 3a, 3b and 3c are not necessary and the mentioned files will not be found.

    1. Locate and recover the properties files generated by parameterization operations on the previous installation.

      The files are named PromotionChecks*.properties.

      Copy them from the previous location, for example if you previously installed V6R2012:

      C:\enoviaV6R2012\code\STAGING\ematrix\properties

      to:

      C:\DassaultSystemes\R2022x\3DSpace\STAGING\ematrix\properties

      In addition, copy the emxTeamSite.properties file from:

      C:\enoviaV6R2012\code\STAGING\ematrix\properties

      to:

      C:\DassaultSystemes\R2022x\3DSpace\STAGING\ematrix\WEB-INF\classes

      then redeploy the web application by running the warutil.bat command.

    2. Copy the files from C:\enoviaV6R[YourPreviousLevel]\server\distrib\enovia\WEB-INF\classes to a temporary folder, for example C:\Temp\STAGING\ematrix\properties.
    3. If they exist, copy the following files from the same location to the same temporary location:

      emxTeamSite.properties
      TeamAttributeCustomization_ENOSTProductReference_custom.properties 
      TeamAttributeCustomization_VPMEBOMPartReference_custom.properties
      TeamAttributeCustomization_ENOSTRepresentation_custom.properties
      TeamAttributeCustomization_ENOSTProductReference.properties 
      TeamAttributeCustomization_VPMEBOMPartReference.properties 
      TeamAttributeCustomization_ENOSTRepresentation.properties

    4. In the new installation, start MQL in command line mode as follows: C:\DassaultSystemes\R2022x\3DSpace\win_b64\code\bin\mql.exe
    5. If the administrator logged onto the parametrization console in 3DEXPERIENCE R2022x(or before), even if parameters were neither changed nor deployed, type:

      MQL<1> set context user creator vault vplm; 
      MQL<2> set env TEXT_Previous_Path C:\Temp ; 
      MQL<3> set env VPLMCentralAdminUser admin_platform ;
      MQL<4> set env VPLMCentralAdminPwd admin_platform ;
      MQL<5>

      where C:\Temp\ is the location of the properties files (containing the STAGING folder mentioned above), and where admin_platform is the name of the administrator, and admin_platform is the password.

    6. If the administrator logged onto the parametrization console in 3DEXPERIENCER2022x (or before), even if parameters were neither changed nor deployed, type:

      MQL<5> run C:\enoviaV6R2013x\EVP\win_b64\reffiles\MQLFamilies\mql\VPLMXPMainUpgrade-Execution-Wrapper-R213.mql ;

      The same procedure applies to Linux with the corresponding paths.

  4. Reinstall any original web apps and redeploy the app.