Performing Common Migration Tasks

All migration scripts listed in this section also mention the release for which they are essential. Only the migration steps that are specific to the release you are upgrading from should be run. For example., if you are upgrading from V6R2009 to V6R2011,then the scripts specific to V6R2009x, V6R2010, V6R2010x and V6R2011 should be run in that order.

For every migration script, there are additional notes given which indicate if the script is to be run on upgrade from an Apparel Accelerator for Design and Development stack or an Apparel Accelerator for Design and Development with Apparel Accelerator for Sourcing and Production stack.

During migration, Matrix history will be on and the changes done will be reflected in the history. This is applicable to upgrade from any given release to any higher release.

Before you begin:

Before proceeding with any migration/post-upgrade script, make below changes to Person 'Test Everything' in ENOVIA > Business

*Give 'Business Admin' and 'System Admin' privileges

*Give 'Administrative Access' to all Admin types

Once all migration/post-upgrade scripts are run, revert the changes done to Person 'Test Everything' earlier.

Update the value of key MX_CLASSPATH in file enovia.ini to refer to <WEB_APPLICATION_HOME>/WEB-INF/classes directory.

This file has to be updated at both the locations:

<ENOVIA_HOME>/studio/<CUR_OS>/code/bin

<ENOVIA_HOME>/server/<CUR_OS>/code/bin

Where CUR_OS for 64 bit Windows would be win_b64, for 32 bit windows will be intel_a

Execute the below common steps at the beginning of every migration/post-upgrade script applicable for the release you are upgrading from.

If the same MQL session is used to run multiple scripts, then you do not have to run the common steps each time.

Do not run the same script multiple times. If any script fails in the first run (error will be displayed at the MQL prompt), contact the support team.

  1. In file emxApparelAccelerator.properties, specify the value for the key emxApparelAccelerator.Migration.LogFolder the location where in the logs needs to be generated.

  2. Update below entries in emxApparelAccelerator.properties as below:

    emxApparelAccelerator.Migration.Log.QualityControlInformation=<Server_HOME>/managed/properties/QCMigration.properties

    emxApparelAccelerator.Migration.Log.ProductTypesInformation=<Server_HOME>/managed/properties/ProductTypeMigration.properties

    In these key-value pairs, replace

    <Server_HOME>/managed/properties/

  3. Start the mql interface.

  4. Run the command set context user "Test Everything" vault "eService Production".

    Note: Where CUR_OS - Current Operating System.

    Note: Where SERVER_HOME - Refers to location where ENOVIA Server is Installed.

    Note: Where WEB_APPLICATION_HOME - Referes to Deployment Directory.