Process for Importing Configurations

Instead of manually configuring an enviroment, you can configure a system by importing a configuration from another environment where it has been defined and tested.

The file used to import a configuration must be exported from a valid environment. Do not edit this file in any way. The export performs consistency and validity verifications that are not performed by the import process. Any modifications made to this file are not supported and could result in configuration problems and data inconsistencies.

Important: Only import a configuration to an environment that has not been configured and where no other configurations have been imported. Import the configuration before any content has been created and before inviting any users to the 3DEXPERIENCE platform. After making configuration changes, you can import a configuration, but the process must be strictly followed to maintain data integrity. If you choose to import a configuration to an environment that has already had any configurations made, keep these issues in mind:
  • The import does not clear any existing configurations; it adds to them. For example, if attributes have been added to types and the imported configuration also adds attributes to the same types, the existing attributes are retained and the imported attributes are added to the type. The import does not replace any previous customizations.
  • Depending on the number of objects that exist, it could be time-consuming to propagate attribute changes. Active users may experience slower response time.
  • On the cloud: When adding or removing attributes to or from existing objects, users might see discrepancies in the navigation panes and search results could show empty values. The properties for the object show the accurate values for those attributes. This discrepancy will only be resolved when the cloud platform is upgraded.

This page discusses:

Preferred Import Process: Best Practice

The best practice for importing a configuration is to do so before any content is created, and before any users are invited to the 3DEXPERIENCE platform.

An Administrator follows these steps to import a configuration before any content is created or inviting any users to the 3DEXPERIENCE platform:

  1. Do not change any settings in the Collaborative Spaces Configuration Center.
  2. Import a configuration that was exported from a system that has already been defined and tested. For more information, see Importing Configurations.
  3. If the configuration included custom attributes on type, test the customization by creating a few objects.
  4. Evaluate the results to ensure that the configuration is defined as expected.
  5. Delete all test objects.
  6. Invite users to the 3DEXPERIENCE platform.
  7. Do not add or remove attributes after content has been created in the 3DEXPERIENCE platform.

Important: Do not reimport a configuration to pick up additional configuration changes. If you need to make additional configuration changes, use the Collaborative Spaces Configuration Center.

If Any Configurations Have Been Made

If you made any configuration changes, such as adding attributes or editing maturity graphs, or users have created content in the 3DEXPERIENCE platform, you can still import a configuration if absolutely required, however, follow these guidelines to maintain data integrity.

An Administrator follows these steps to import a configuration:

  1. Stop production of all apps to prevent any creation or modification of content.
  2. Import a configuration that was exported from a system that has already been defined and tested. For more information, see Importing Configurations.
  3. If the configuration included custom attributes on type, test the customization by creating a few objects.
  4. Evaluate the results to ensure that the configuration is defined as expected.
  5. Delete all of the test objects.
  6. Propagate the attributes to existing objects.
    Note: This process can be time-consuming.
  7. Restart production for all apps.
  8. Do not add or remove attributes after content has been created in the 3DEXPERIENCE platform.