Enabling a Development Instance
Before you can enable a development instance:
- The development path and development area path must be defined for the development instance, or for the parent development, or for the development server.
- The parent development must have at least one tool suite for the development type defined.
- The parent development must have at least one development setting defined.
- If Allow External Development Areas is Yes, or Default, and the Default is Yes, the external path must be defined for this development instance or for the parent development.
You can enable a development instance:
- When you create the development instance
- On the list page of development instances for a specific development
- On the properties page for the development instance
- On the lifecycle page for the development instance (by promoting it to the Enabled state)
When you enable a development instance in Defect Management and Collaboration or enable a development in DesignSync, if the associated module does not already exist, it is automatically created in the DesignSync repository server. If a vault folder is specified instead of a DesignSync module, the vault folder is automatically created. The first time that you enable a development instance, the DesignSync development server creates the entire development directory structure and fetches data into the data replication root so that files and static modules are present before they are needed, that is, before development areas are created.
The DesignSync server uses this format to name a development instance:
<DevelopmentName>_<DevelopmentRevision>
If a development instance with this name already exists, then the server appends _<DevelopmentInstanceName>
to the development name.
When you enable a development instance in , Enterprise DesignSync Administration passes information from the 3DEXPERIENCE platform to the DesignSync server and the development instance or development settings are updated on the server based on that data. Such data could include the physical development path being resolved, or creating or copying development settings branches.
You might need to disable the development instance and then enable it again. For example, you would disable it if you need to connect to an updated development settings module. In this case, any updated data is populated on the DesignSync server for the development instance.