Creating a data source definition

Prerequisite

Cloud Pak for Data common core services must be installed. The common core services are automatically installed by services that rely on them. If you don't see the Connectivity page, it's because none of the services that are installed in your environment rely on the common core services. You access the Connectivity page from the navigation menu at Data > Connectivity.

Requirements

• The ability to create, edit, deactivate, or delete a data source definition requires specific roles, permissions, and asset privacy settings. The permissions must be assigned to a role in advance. See Roles and asset privacy settings for data source definitions.
• Data source definitions must be unique. You cannot create two data source definitions that contain the same endpoint or set of endpoints.
• By default, data source definitions are private assets. After you create a data source definition, you can add other users to the asset or make the asset public. For information, see Controlling access to an asset in a catalog.
• Only certain data source types can be used for data source definitions. See Connectors that support data source definitions.
• As part of creating a data source definition, you select a protection solution. Certain protection solutions must be set up in advance. See Protection solutions for data source definitions.

Connection credentials

Because deep enforcement is performed based on the credentials that the user provides for the connection, ensure that the connection's credentials match the logged-in user of the platform. Therefore, it is advised to use personal credentials instead of shared credentials when you create a connection that will be associated with a data source definition. For information about personal and shared credentials, see Adding connections to data sources in a project.