3DEXPERIENCE to ENOVIA VPM V5 Coexistence Variables

This section describes how to use variables facilitating coexistence from 3DEXPERIENCE to ENOVIA VPM V5.

Variable Use
V6R2012x_V6V5Coex_PartInstanceCreation

This variable is set on the server side and can therefore be used only for one Product Root Class (PRC) at a time.

Example: V6R2012x_V6V5Coex_PartInstanceCreation=PCName

where "PCName" is the name of the existing PC under which the data is to be instantiated.

You cannot use this variable if you want to instantiate multiple 3DEXPERIENCE structured data under multiple V5 PRCs simultaneously. To do that you must use the variable V55_PRC_FOR_COEX described below.

V55_PRC_FOR_COEX

This variable must be set on the client side from where the 3DEXPERIENCE to ENOVIA VPM V5 coexistence data transfer is launched. It enables you to instantiate multiple 3DEXPERIENCE structured data under existing multiple V5 Product Root Classes (PRCs) simultaneously.

Example: V55_PRC_FOR_COEX=PRCName

where "PRCName" is the name of the PRC under which the data is to be instantiated.

Important: If both of these variables are set on the server and client sides simultaneously, the V55_PRC_FOR_COEX variable takes precedence over the server variable and instantiation is done under the PRC you specify.
V6R2012x_V6V5Coex_RetainLock

By default, once the 3DEXPERIENCE to ENOVIA VPM V5 transfer is completed, objects created in V5 are not locked, but if the environment variable (on the server side) is set as follows:

V6R2012x_V6V5Coex_RetainLock=1

the lock is retained on created objects and the lock owner remains the V5 user running the transfer.

Important: This variable is MANDATORY for a successful transfer from 3DEXPERIENCE to ENOVIA VPM V5.