You must compare the two policies
and merge the changes in the new policy to the existing policy, keeping
customizations if any.
You need to verify and merge the changes for the following files:
Note:
Note the following points.- If you have added attributes in baseline behavior environment, you must copy the existing attributes
located at <
V6R2018xLiveCollaborationServerFolder>\STAGING\ematrix\properties
> to <3DEXPERIENCE R2022xLiveCollaborationServerFolder>\STAGING\ematrix\properties
>. For more information, see Post Upgrade Instruction - Baseline Behavior Environment.
- If there are any custom admin entities present in the database that have been internationalized / localized by adding their names in the property files, then upon upgrade to another releases, the properties file entries related to these admin entities should be copied from the old properties files to the new properties files before running the war utility. These files are located at <
V6R2018xLiveCollaborationServerFolder>\STAGING\ematrix\properties
>. The relevant entries for custom admin types from these property files should be copied to the corresponding property files at <3DEXPERIENCE R2022xLiveCollaborationServerFolder>\STAGING\ematrix\properties
>. For more information about the properties files, see Internationalization and Localization
When you are migrating from version V6R2009x, V6R2010 or
V6R2010x to R2015x, the promote check trigger on all states of
existing policy must be corrected from MCADPolicyPromoteCheck to
PolicyMCADPolicyPromoteCheck.
Specifically for migration from V6R2009x or above to V6R2011,
the promote check trigger on all states of existing policy must be
corrected from MCADPolicyPromoteCheck to
PolicyMCADPolicyPromoteCheck.