Migrating Repository Data Sources to Cross-Repository Data Sources

In the Management Center, repository data sources can be migrated to cross-repository data sources (see Data Sources), provided that the corresponding cross-repository data source is already defined.

During the migration process, all existing references to the original data source are reassigned to the new data source. The repository data source is then fully removed.

If the new cross-repository data source does not point to the exact same physical data source (or an identical clone), the reassigned references may produce incorrect results or even cause errors. Since the migration cannot be undone, exercising special care when specifying the correponding data source during migration as well as making a backup before the migration is strongly recommended.

Recommendations

We recommend defining as few RDBMS data sources as possible. Ideally, the main data source even is the only data source (containing the only CDS schema). So we also recommend storing data as much as possible into one RDBMS database with different schemas (the configured cross-repository login user must have sufficient privileges to access the different schemas).

Because structural changes are difficult to implement after migration, we strongly recommend thorough planning beforehand.

How to Migrate a Repository Data Source to a Cross-Repository Data Source

First, prepare the migration on the database and configuration level:

  1. Make sure the repository schema containing the affected repository data source is up-to-date (see Using the Database Migration Tool).

  2. Strongly recommended: Make a backup of the repository schema containing the affected repository data source.

  3. In datasources Configuration, configure the corresponding cross-repository data source:

    • This data source must point to the same physical data source (or an identical clone).

    • Since it is crucial that this data source can be identified in the migration dialog, it is recommended to use the same display name as for the original repository data source.

    • Credentials are mandatory.

Then, carry out the migration in the Management Center:

  1. Make sure you have the required permissions:

    • System privilege “Manage repository data sources”

    • System privilege “Manage cross-repository data sources”

    • Authorization level "Edit and manage" for the repository data source

    • Authorization level "Edit content" for its repository

  2. In the “Repository data sources” tab of the “Data sources” section, open the migration dialog:

    • For an invalid data source: In the error message in the data sources overview or on the detail page, select the button “Migrate data source”.

    • For both valid or invalid data sources: On the detail page in the three dots menu, select the menu item “Migrate data source”.

  3. In the dialog, select the corresponding cross-repository data source.

    The migration cannot be undone! Make sure to select the correct data source.

  4. Grant the authorization level “Create items” to users who need to be able to create new objecttypes or add layers based on the data source. For a RDBMS data source, the authorization is granted per schema. (Using objecttypes or layers is possible without authorization for the data source.)