Migrating between Former Typing and Unified Typing

Before the 3DEXPERIENCE R2020x release, the 3DEXPERIENCE platform offered two typing modes:

  • Former Typing
  • Unified Typing.
Since the 3DEXPERIENCE R2020x release, the platform is operating in unified typing mode only. It is mandatory that you migrate any exiting data to unified typing.

There are three migration profiles, depending on whether you used former typing or unified typing in previous releases, and the baseline behavior or the Customer-Specific Environment in previous releases. As summarized in the following table, the objective is to migrate to Unified Typing permanently:

In the previous release, you used...As of 3DEXPERIENCE R2022x, you use...Do you need to implement any business process?
#A baseline behaviorFormer Typingbaseline behavior: content migration is mandatoryUnified Typing

No: if behaviors have been tuned using Manage P&O and Content.

If any specifics applied on top of baseline behavior, to be reconsidered.

#B Customer-Specific EnvironmentUnified Typing Customer-Specific Environment on top of baseline behavior: no content migration is required.Unified Typing

No: minor adjustments must be considered to reconnect implemented customer business processes.

For new apps, the customer will get baseline behavior.

#C Customer-Specific EnvironmentFormer TypingCustomer-Specific Environment customizations applied on top of baseline behavior: define and apply content migration of former types to unified types.

In this case, for example, you have used DMC to customize your system and/or you have used the DS samples (PLMProductDS).

Unified TypingYes: operating in unified typing mode requires a full re-engineering of customization for Customer-Specific Environment.

Note: if DMC has not been used, objects using DS sample types will be migrated automatically. Optionally, you can migrate them to a new customization.

Note: For more details about re-engineering of customization for Customer-Specific Environment, see the Customization section of the online documentation for a list of customization technologies (Mask, WebForm, Behaviors, Trigger EKL Rule/JPO, Policy, …).

This task shows you how to:

#A: Migrate from baseline behavior Former Typing to baseline behavior Unified Typing

Unified typing mode is mandatory for baseline behavior since 3DEXPERIENCE R2020x; former typing is obsolete and not supported. If your server was operated in the previous release in a baseline behavior environment (in former typing mode), you must migrate the content to support the default unified typing mode. Former typing objects must be imported into a 3DEXPERIENCE R2022x server in a baseline behavior environment as unified typing objects.

Complete content migration (via VPLMDataMigration) has to be performed before operating a 3DEXPERIENCE R2022x server in a baseline behavior environment and prior to the following scenario.

  1. Upgrade the server by installing the latest code.

    You must first upgrade the 3DSpace server. Once the server has been upgraded, migration must be performed before any end user connects to the server.

  2. Modify the deployed admin file STAGING/ematrix/WEB-INF/classes/vplm/environment/VPMAdminV6GA.adm as follows:
    1. Stop the application server.
    2. Copy the file VPLMAdminV6GA.adm to VPLMAdminV6GAOriginal.adm to preserve original content (if needed).
    3. Replace the content of VPLMAdminV6GA.adm by the content of VPLMAdminV6LA.adm.
    4. Launch the war_util command to rebuild the .war or .ear archive.
    5. Deploy the .war or .ear archive in the application server.
  3. Adapt data policy to new supported user processes.

    Certain specific baseline behavior app data is no longer supported with former user processes. The policy needs to be updated to support new user process (as they would now be created by users):

    • human and rendering data is migrated from definition to evaluation data (1)
    • piping line data is migrated from resource to definition data (1)
    • behavior data is migrated from evaluation data to definition data (2)
    • Frozen and Released VB macro data is migrated from evaluation data to resource data (2)
    • other VB Macro data is migrated to personal VB Macro data (*3).

    If the above types of data do not exist on your installation, nothing will change. If this is not the case:

    • case (1) and (2): the current state will be kept unchanged
    • case (2): the Administrator might need to assign the new related role to the users
    • case (3): only the Owner will keep access to the data.

    You must perform this policy migration before migrating content.

    To do so, on Windows:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>\Apps\VPMMultiDiscipline\V6R2016x\mql

      <3DSpace_Server_dir>\EVP\win_64b\reffiles\MQLFamilies\mql

    2. Run the following MQL scripts:
      VPLMxV1Types-UpgradeDeployment-R216.mql
VPLMxV1Types-UpgradeDeployment-R417.mql
VPLMxV1Types-UpgradeDeployment-R419.mql

    or on ‌Linux:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>/Apps/VPMMultiDiscipline/V6R2016x/mql

      <3DSpace_Server_dir>/EVP/linux_64a/reffiles/MQLFamilies/mql

    2. Run the MQL script:
      VPLMxV1Types-UpgradeDeployment-R216.mql
VPLMxV1Types-UpgradeDeployment-R417.mql
VPLMxV1Types-UpgradeDeployment-R419.mql

  4. Migrate the content.

    For full details, perform the procedure described in the following section of the online documentation: Installation and Setup - Customize - Data Model - Unified Typing Migration Tool..

    References to former customization types are replaced by references to unified types.

  5. Modify the deployed admin file STAGING/ematrix/WEB-INF/classes/vplm/environment/VPMAdminV6GA.adm as follows:
    1. Stop the application server.
    2. Replace the content of the file VPLMAdminV6GA.adm with the content of the file VPLMAdminV6GAOriginal.adm you saved earlier in the process.
    3. Launch the war_util command to rebuild the .war or .ear archive.
    4. Deploy the .war or .ear archive in the application server.
  6. Hide former types.

    On Windows:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>\Apps\VPMMultiDiscipline\V6R2016x\mql

      <3DSpace_Server_dir>\EVP\win_64b\reffiles\MQLFamilies\mql

    2. Run the MQL script to hide former types:
      VPLMxV1Types-Hide-R216.mql

    On Linux:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>/Apps/VPMMultiDiscipline/V6R2016x/mql

      <3DSpace_Server_dir>/EVP/linux_64a/reffiles/MQLFamilies/mql

    2. Run the MQL script:
      VPLMxV1Types-Hide-R216.mql
VPLMxV1Types-UpgradeDeployment-R417.mql

  7. Unhide unified types.

    Go the location specified above on each operating system, and run the MQL script:

    VPLMxV2Types-Unhide-R214.mql
    Note: In the script names, V1 refers to former typing and V2 refers to unified typing.

  8. If you have migrated your former types (Former Typing) to the new types (Unified Typing) created by the Specialize Data Model, you must implement a specific opening.

    The opening is described in the following user assistance section: Installation and Setup | Customize | 3DEXPERIENCE Platform | Behavior | Data Setup | List of Resource Set IDs | Infrastructure Business Logics | PLM Business Logic to Support Data Upgrade: Unified Typing Migration Type and Attributes Mapping (INFRA_UnifiedTypingMigration).

Once migration has been performed, the use of the former typing mode is prohibited.

#B: Migrate from Customer-Specific Environment Unified Typing to Customer-Specific Environment on Top of baseline behavior Unified Typing

  1. Upgrade the server by installing the latest code.
  2. No content migration is required.
  3. No business process needs to be implemented.

    Minor adjustments have to be considered to reconnect implemented customer business processes. For new apps, the customer will get baseline behavior.

    Note: If you encountered any issues with PVS object, and to ensure that these objects will be upgraded on the fly, we recommend that you replace the following file on the server side: STAGING/ematrix/WEB-INF/classes/vplm/environment/VPMAdminV6GA.adm by the file produced by the DMC tool.

#C: Migrate from Customer-Specific Environment Former Typing to Customer-Specific Environment with Customizations Applied on Top of baseline behavior Unified Typing

In this case, for example, you have used DMC to customize your system or the DS sample types.

In this case, unified typing mode is also mandatory and you must migrate the existing Former Typing data to Unified Typing.

  1. Upgrade the server by installing the latest code.

    Make sure that you have run the VPLMDataMigration command. When applicable, make sure DMC migration has been done. For more information, see Installation and Setup: Customize: Legacy Tools: VPM Data Model Configuration: Working with Migrations.

  2. Modify the deployed admin file STAGING/ematrix/WEB-INF/classes/vplm/environment/VPMAdminV6GA.adm as follows:
    1. Stop the application server.
    2. Copy the file VPLMAdminV6GA.adm to VPLMAdminV6GAOriginal.adm to preserve original content (if needed).
    3. If you did NOT use DMC, replace the content of VPLMAdminV6GA.adm by the content of VPLMAdminV6LA.adm. If you DID use DMC, use the VPLMAdminV6GA.adm file generated by DMC.

      If you used DS sample types, replace the content of VPLMAdminV6GA.adm by the content of VPLMAdminV6LA.adm.

    4. Launch the war_util command to rebuild the .war or .ear archive.
    5. Deploy the .war or .ear archive in the application server.
  3. Perform a full re-engineering of Customer-Specific Environment customizations.

    Operating in unified typing mode requires a full re-engineering of customizations developed with the Customer-Specific Environment.

    You have to migrate the former content to a new customization on top of unified typing to remove former content; the procedure for content migration will be customer defined. See the Unified Typing Migration Tool guide because you need to execute the migration tool.

  4. Run the migration.
  5. Hide former types (when no former content exists anymore).

    On Windows:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>\Apps\VPMMultiDiscipline\V6R2016x\mql

      <3DSpace_Server_dir>\EVP\win_64b\reffiles\MQLFamilies\mql

    2. Run the MQL script to hide former types:
      VPLMxV1Types-Hide-R216.mql

    On Linux:

    1. Go to one of the following folders containing MQL scripts:

      <3DSpace_Server_dir>/Apps/VPMMultiDiscipline/V6R2016x/mql

      <3DSpace_Server_dir>/EVP/linux_64a/reffiles/MQLFamilies/mql

    2. Run the MQL script:
      VPLMxV1Types-Hide-R216.mql

  6. Unhide unified types.

    Given that unhiding of unified types is performed at installation, this step might not be required. However, it depends on whether you decided to continue to operate in Customer-Specific Environment former typing for a while, in which case you need to perform this step.

    Go the location specified above on each operating system, and run the MQL script:

    VPLMxV2Types-Unhide-R214.mql