User Migration
If you install a new 7.x DiveLine and want to populate the users from an earlier installation, you have a few alternatives.
Option 1: Use dicfg save/merge to import users.
The tasks are:
- Use 6.x dicfg.exe to export and save the users from the 6.x DiveLine.
- Update the licensing column for 7.x license levels.
- Use 7.x dicfg.exe to import and merge the users into the 7.x DiveLine.
- Set project access in Workbench for each user.
Option 2: Copy the atlcfg.cfg from your older installation, and overwrite the empty file in the 7.x instance.
Considerations:
- This creates the same set of users, as well as groups, aliases, and the Main configuration block which handles items like gateway_ips, the dlcgi URL to advertise to ProDiver users, and the default authentication scheme.
- Whether or not this is a reasonable option depends on what the current settings are and if you want to preserve the existing settings.
- If you use this approach, an automatic user license migration will occur, which might require some adjustments, but will certainly save you time.
- You also need to set project access in Workbench for each user.
Option 3: Copy just the users out of atlcfg.cfg, either adding to or replacing what is the new 7.x instance.
NOTE:
- All the copied users will need to have user categories for licensing assigned. This can be done using Workbench, dicfg.exe, or with a text editor.
- You also need to set project access in Workbench for each user.
Access control data to let users see a project is stored in a text file called project-access-config.sdl. This configuration file, which is in SDL format, is stored at <dataroot>\config\projects\<projectname>\. For example:
project-access { allow-user "dave" allow-user "mpp" allow-group "Managers" ... }
or, if everyone's allowed:
project-access { allow-all-users
}
Such a file could be created using Integrator or another tool if there is a need to set the access for numerous users as part of a conversion effort.
See also: