Identify the Exchange Channel

The coexistence context enables to identify an exchange channel between two systems. To maintain the history of previous exchanges of the same object, it is advised not to change the context value as long as the corresponding exchange channel is maintained.

This page discusses:

Identify The Exchange Channel

Adapter for X-PDM is using a single name(X-PDM Site ID) to identify the exchange channel.

  • For event exchange, the Site IDs must be configured in both the Gateway Servers as described in Configuring Gateway Server.

  • For the Site IDs to be available in XPDMImportExportBatch UI and to execute or run the XPDMImportExportBatch successfully, it is necessary to associate a database type coexistence Mapping context to the Site IDs.

    • The created database type context must be of type XPDM and must use the Site ID name in the Site Id parameter.
    • When we create the database type context, it is recommended to use Site ID name as the context name.

    For more information about the creation of coexistence database type context, see 3DEXPERIENCE Platform - Administration 's Guide :User Preferences | General | File-based Design Import | Setting Up Coexistence Mapping Context

Setting-up Projects In baseline behavior

In an baseline behavior setup, it is recommended to use a dedicated project gathering the data created by import from X-PDM.

The downstream usage of the imported data as reference for new designs is easier if the import project is declared as public.

For more information related to creating Project , refer People & Organizations and Content Guide: Authoring P and O Data Using the Configure My ENOVIA Command | Managing Collaborative Spaces

The data in the Import project is handled by the system as 3DEXPERIENCE platform secondary data whereas data sent to X-PDM from other projects is 3DEXPERIENCE platform primary data. 3DEXPERIENCE platform secondary objects’ attributes are governed by the X-PDM system. For example:

  • The first time an object is imported in 3DEXPERIENCE platform, it can be in an advanced maturity status such as Release.
  • If the project name attribute is present in the XPDMXML file, its value is used to set the 3DEXPERIENCE platform project name of the object. The project name must correspond to the correct Team project. If this cannot be guaranteed, a BL can be defined to override default project name mapping.

Note: The strict locking and strict ownership options should not be active during the transfer from X-PDM to 3DEXPERIENCE platform.