Migrating Tracked Stores to Captured Stores

3DEXPERIENCE R2022x is the last release on which tracked stores will be supported. So you will need to migrate tracked stores to captured stores. To do so, a migration tool is provided.

A tracked store is a legacy store type that is no longer suitable for modern applications. A migration tool is provided to move the checked-in files from a tracked store to a captured store. The migrated files will be checked in to the captured store, while the business object modified dates, the file modified dates and the business object histories would be untouched. The tool does not delete the tracked store or remove references to it (i.e. policy). You must remove the tracked store manually and all the references to it.

We recommend that you do not run the migration tool on a 3DSpace environment currently in use as it will impact modifications and history related metadata.

  1. Start MQL as system administrator (user that is allowed to modify the corresponding business objects and files).
  2. Run the migration tool as follows, and specify the corresponding tracked store and captured store: 

    MQL<1>java com.matrixone.fcs.tools.migrateTrackedStore -fromStore tracked-store -toStore captured-store;
    For example, 
    MQL<3>java com.matrixone.fcs.tools.migrateTrackedStore -fromStore tracked-store -toStore file-store;
Migrating bus A22ACD5500001EBC5453D3AC0000001C format f file test_file.txt to store file-store
Migrating bus A22ACD5500001EBC5453D3AC00000014 format f file test_file.txt to store file-store
Migrating bus A22ACD5500001EBC5453D3AC00000014 format f file test_file2.txt to store file-store
3 files treated.

The migration tool will process one business object at a time and commit its changes. Therefore, in the event of an unexpected error, the previously processed business objects would not need to be reprocessed.

You can also run the tool in simulation mode using the -simul option to see the list of files that will be processed.

Note: Do not run the migration tool in parallel. In case of abnormal termination of the migration tool, it may be necessary to clean up the workspace directories which are temporary directories. The workspace directories can be found under the server install directory.