ENOVIA SmarTeam V5 Prerequisites

This section describes the prerequisites that must be implemented before you use ENOVIA SmarTeam V5 Coexistence and Migration.

Important:
  • Connecting to a SmarTeam server and running along CATBatchStarter.exe consumes two LAA licenses.
  • The server batch mode is fully supported for the ENOVIA SmarTeam V5 connector.

This page discusses:

Version Compatibility

3DEXPERIENCE SmarTeam
3DEXPERIENCE R2017x V5-6R2015 or higher
3DEXPERIENCE R2018x V5-6R2015 or higher
3DEXPERIENCE R2019x V5-6R2016 or higher
3DEXPERIENCE R2020x V5-6R2017 or higher
3DEXPERIENCE R2021x V5-6R2019 or higher

Methodology for Migration

Methodology for migration.

Before starting a migration, you are advised to have all required data released in the SmarTeam database.

Note: Check-in is also supported but will break the versioning process. New or checked-out data may be modified again and this modification could not be sent to 3DEXPERIENCE as we address here the migration procedure.
Warning: Data must not contain special characters otherwise the transfer will not work as expected. To avoid this issue, you must select the Allow double escaping checkbox in the IIS Manager tool. For more information about IIS data settings, refer to the IIS documentation.

Migrating the data:

  • Support both global migration and incremental migration.
  • 3DEXPERIENCE has a corresponding table (containing mapping between V5 objects & 3DEXPERIENCE objects)
  • Previously sent V5 objects are automatically recognized. Migration will not take place on those objects. Depending on the migration options, the user will be either explicitly notified through an error message when running a Global Migration or data will be ignored during the migration process when running an incremental migration.
  • Modifications of already migrated V5 data should be prevented on the V5 side. Note that data that has been migrated cannot be migrated a second time. This does not apply to Coexistence scenarios.