Migrate System Default Files to the Configuration Database

The following procedure is necessary to migrate existing projects to AVEVA E3D Design 4.0 or later from a previous version of AVEVA E3D Design.

First ensure the desired configuration database(s) have been created and added to the MDBs in the project. Refer to Project Database Set up in AVEVA Administration for further information.

Some planning may be required before importing the existing dra-gen-system files for the project. If there is only one dra-gen-system file for the project, only the project level configuration needs importing. If any MDBs have their own dra-gen-system files, then the configuration for those MDBs will also need importing. Finally, if the project used additional dra-gen-system files to supply the needs of particular groups (for example, different disciplines), the administrator can create those groups in advance in the System Defaults window before starting the procedure.

1. Launch Draw with any MDB.

2. On the Admin tab, in the Settings group, click System Defaults to display the System Defaults window.

3. Select a configuration level to be imported to from an existing dra-gen-system or dra-gen-system.imp file. Start with the project level first, then any MDB level configurations, then any group level configurations. This is recommended as the project level supplies defaults to the levels above, default values at a particular level are only set if they are different from the level below.

   Note:
   To import a group, create and name an empty group. Select the group and choose Import. If no group is selected on the Group tab, the application assumes you are updating the project-level configuration.

4. Select Import and select Legacy Import from the drop-down menu to select the appropriate dra-gen-system or dra-gen-system.imp file from the file system. This applies the contents of the file to the current configuration, which can be edited further, if required.

   Note:
   Configuration database changes are applied immediately but require a save work once the System Defaults window is closed.

5. Repeat the previous step for as many dra-gen-system files as required in the project. The configurations are not limited by the historic dra-gen-system files, additional configurations can be added.

6. Once the dra-gen-system files have been imported into the project and a save work is done, they are no longer required by the application. AVEVA E3D Design 4.0 or later never looks at these files; they are only ever used for defining database configurations as described here.

   Note:
   Only the dra-gen-system files are no longer used by the application. Other default files, under AVEVA_DESIGN_DFLTS, are currently unaffected and remain in use.