Register a data source via Edge during migration

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

Before you can migrate Schema assets that were registered via Jobserver to Edge, you need to register your data source via the Edge connection. This creates a Database asset which is needed to synchronize, profile and classify the data via Edge.

Before you begin

Steps

  1. On the main toolbar, click Products icon, and then click Catalog.
    The Catalog Home opens.
  2. In the tab bar, click Integrations.
    The Integrations page opens.
  3. Click the Data Source Registration tab.
  4. On the main toolbar, click .The Create dialog box appears.
  5. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
    The Register contentIntegration Configuration tab page opens.
  6. In the row of the data source that you want to register, click AddRegister.
    The Add Database pageRegister a Data Source dialog box opens.
    Note You can register multiple databases via the same JDBC connection. If a database is already registered, the name of the Database asset is shown in the Data sources column.
  7. Enter the required information.
    FieldDescription
    CommunityThe name of the parent community in which the assets will be created.

    System

    The name of the System asset.

    After you have registered the database, a relation of the type Technology Asset groups / is grouped by Technology Asset is created between this System asset and the newly created Database asset.

    Important 

    A Database asset should have only one relation of the type 'Technology asset groups / is grouped by Technology asset' to a System asset.

    Owner

    Tip By default, this field is called Owner, referencing the out-of-the-box Owner resource role. If you change the name of this out-of-the-box resource role, the updated name will be displayed instead.

    After the registration, a new domain and Database asset will be created specifically for this database in the community that you have specified. The user you select in this field will receive the responsibility for the domain. This ownership is then inherited by the Database asset.

    By default, the current user is selected.

    Note  An owner must be associated with the Database asset for synchronizations to run. The owner can be changed later on, but should not be removed.

    Database name

    Select the name of the database that you want to register via the JDBC connection. The drop-down menu automatically shows which databases exist in your data source. You can refresh the list by clicking next to the drop-down menu.

    Note 
    • Some data sources allow you to use one Edge connection to register multiple databases. In that case, the drop-down will show more than one name.
    • We map Project ID in Google Bigquery, and Data Source in AWS Athena and AWS Glue to Database.
    • Sometimes you can also see CDATA as an option, for example CSV. For information on changing the name, go to Customizing the database name for database-less data sources.

    The name will also be the name of the Database asset that is created as a result of registering the data source via Edge.

    Important 

    If you rename a database in the data source, the Edge synchronization process will consider it a new database. We don’t detect the renaming of a database at this moment.

    Description

    A description of the data source.

  8. Click Register.
    A Physical Data Dictionary domain containing a Database asset is created.
    The Database name is the name you added in the Database name field.
    A relation of the type "Technology asset groups / is grouped by Technology asset " is created between the Database asset and the System asset.
    The Database asset page opens.
    A list of available schemas in the database is generated.

What's next?

Migrate a schema to Edge