How the MMT Batch Works
Each PLMEntity with a non-null V_StreamDescriptor is checked for correct store assignment of it's files. If a PLMEntity’s file breaks one store assignment rule, it is moved to the proper store following store rules set up in the PLMPolicyChooser.xml file.
Rules depending on parameters such as $role and $user are not supported. Parameters supported for migration rules are:
- $org
- $project
- $type.
These parameters will be checked against migrated PLMEntity attributes values:
- V_project
- V_organization
- and its PLM type.
Multi-store migration can be performed in several steps since MMT progression is recorded in a log file. Starting the MMT tool with a log file containing previously run data will enable the migration to continue where it was stopped.
Multi-store migration must be executed on the central server site. The migration can be pushed onto other sites using the FCS synchronization server tool or manual MQL sync store commands.
Before pushing migration onto distant sites, make sure that each store that is replicated on a site has one (and only one) location on this site.