Importing a configuration
Importing a repository configuration loads the settings from a repository that was previously exported as described in Exporting the configuration.
Importing a configuration is useful for several purposes:
- To restore the system's configuration to a known point in time, such as before major changes were made.
- To rebuild a repository configuration after a disaster.
- To duplicate the configuration of another Meridian Explorer repository.
The following table lists the configuration items that can be imported and describes how the items are imported.
Item | Description |
---|---|
Property definitions (document, tag, project) |
If an item already exists in the repository, it is skipped. |
Object types (document, tag, project) |
|
Reference types (document, tag) |
|
Filters (document, tag, project) |
|
Security settings
|
All security settings will be removed and replaced by the settings in the configuration file. If a user or group is missing, it will be ignored. This can happen when importing a configuration that was exported from a server with different users and groups. The memberships are applied to all projects. If a group already has global permissions, they are skipped. If a role is applied to a hierarchy value, the value is created so that the security will apply as expected when the value is used later. The value must not already exist. |
To import a configuration:
- In Meridian Enterprise Server Administration Console, in the Repositories group, click the name of the repository that you want to import. The repository overview page appears.
- In the app bar, click IMPORT. The IMPORTING REPOSITORY CONFIGURATION dialog box appears to prompt you for the location of the file to import.
- Click the folder icon
. The Open dialog box appears.
- Navigate to and select a local compressed archive file (the default is <RepositoryName>.zip) that you want to import and then click Open. The filename appears in the Configuration field.
- Click UPLOAD. A confirmation dialog box appears.
- Click YES. A background task is started and you can continue working.
When the process has completed, the changes are effective immediately.