About the Data Source Registration tab page and Register a Data Source dialog box

Data Source Registration tab page

The Data Source Registration tab page is located in the Catalog Integrations submenu. It allows you to create a Database or File System asset from which you can start the synchronization of a data source. Use this tab page for JDBC, S3, GCS, and ADLS integrations via Edge.

Column Description
Connection Name The name of the connection to the data source.
Description The description of the connection to the data source.

Connection Type

The type of connection. For example, JDBC.

Data Sources

The name of the database that is already registered in Data Catalog. If the column is empty, the connection doesn't have registered assets yet.

Tip If you click the name of the asset, you are automatically redirected to the asset page. If the name of the asset is grayed out, you don't have permission to go to the asset's page.

Action

Click Register to register the data source for JDBC, S3, GCS, and ADLS integrations.

Register a Data Source dialog box

In the Register a Data Source dialog box you can select a community, a System asset, the database from your data source that you want to register and the owner of the data.

Field Description
Community

The name of the parent community in which you want to add the Database asset.
After you have registered the database, a new domain will be created in the community that you have specified.

System

The name of the System asset to which you want to link the Database asset.
After you have registered the database, a 'Technology Asset groups / is grouped by Technology Asset' relation will be created between this System asset and the newly created Database asset.

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 shown here instead.

The name of the owner of the new domain and Database asset. By default, the current user is selected.
After you have registered the database, a new domain and Database asset will be created specifically for the 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.

A Database asset must have an owner for synchronizations to run. The owner can be changed later on, but shouldn't be removed.

Database

Select the name of the database that you want to register via the JDBC connection. The drop-down list automatically shows one or more databases that exist in your data source.
You can refresh the list by clicking .
After you have registered the database, the name visible in the drop-down list will be the name of the Database asset.

Important considerations:

  • Some data sources allow you to use one connection to register multiple databases. In that case, the drop-down list shows more than one name.
  • Collibra maps Project ID in Google Bigquery, and Data Source in AWS Athena and AWS Glue to Database.
  • For some data sources, such as CSV, you can see CDATA as an option. For information on changing the name, go to Customizing the database name for database-less data sources.
  • If scalable ingestion is active in your environment, Collibra prevents you from registering a database that is already registered through a different Edge connection. In this case, the database name is grayed out in the drop-down list. To register the database again, first delete the existing Database asset.
  • If you rename a database in the data source, the Edge synchronization process treats it as a new database. The existing Database asset is marked with the Missing from source status. You must create a new Database asset through a new data source registration.
Description

A description of the data source.

What's next

Register a data source via Edge
About synchronizing schemas