Updated on 2026-11-12 GMT+08:00

DLI Connection Parameters

Table 1 DLI connection parameters

Parameter

Mandatory

Description

Data Connection Type

Yes

DLI is selected by default and cannot be changed.

Name

Yes

Name of the data connection to create. Data connection names can contain a maximum of 100 characters. They can contain only letters, digits, underscores (_), and hyphens (-).

Description

No

A description which can help identify the data connection more easily. It can contain a maximum of 100 characters.

Tag

No

Attribute of the data connection to create. Tags make management easier.
NOTE:

The tag name can contain only letters, digits, and underscores (_) and cannot start with an underscore (_) or contain more than 100 characters.

Applicable Modules

Yes

Select the modules for which this connection is available.

NOTE:
  • When offline or real-time data migration jobs are enabled, you can select the DataArts Migration module. Then you can select this data connection when creating a data migration job in DataArts Factory.
  • You can use offline or real-time data migration jobs only after you apply for the whitelist membership. To use this feature, contact customer service or technical support.
  • You cannot select both DataArts Migration and DataArts Factory. If you want to connect both DataArts Migration and DataArts Factory in the same workspace to DLI, you need to create two DLI data connections and select DataArts Migration and DataArts Factory for each of them.

Data Source Authentication and Other Function Configuration

Real-time Metadata Synchronization

Yes

When real-time metadata synchronization is enabled, the metadata of DLI is synchronized to the Data Map component in real time. You are advised to enable this function.

NOTE:

Whether real-time metadata synchronization is enabled depends on whether this function is enabled for the latest DLI connection in the DataArts Studio instance. That is, if real-time synchronization is disabled or enabled for a DLI connection, this function is also disabled or enabled for all DLI connections.

For example, if there is a DLI connection in a workspace of a DataArts Studio instance and another DLI connection in another workspace, and real-time metadata synchronization is enabled for the connection that is created first and disabled for the connection that is created later, then real-time metadata synchronization is disabled for DLI. If real-time metadata synchronization is disabled for the connection that is created first and enabled for the connection that is created later, then real-time metadata synchronization is enabled for DLI.

Metadata Collection Scope

No

Databases and data tables whose metadata will be synchronized in real time. If this parameter is not set, all metadata will be synchronized.

The value can be in either of the following formats:

  • database_name: databases whose names contain database_name
  • database_name.table_name: databases whose names contain database_name and data tables whose names contain table_name

Examples:

  • If you enter datatest, the metadata of the tables in the databases whose names contain datatest will be synchronized in real time.
  • If you enter datatest.table1, metadata of the tables whose names contain table1 in the databases whose names contain datatest will be synchronized in real time.

Network Connectivity Configuration

Project ID

Yes

This parameter is displayed when DataArts Migration is selected for Applicable Modules.

Project ID in the region where DLI resides

A project is a group of tenant resources, and an account ID corresponds to the current account. The IAM ID corresponds to the current user. You can view the project IDs, account IDs, and user IDs in different regions on the corresponding pages.
  1. Register with and log in to the management console.
  2. Hover the cursor on the username in the upper right corner and select My Credentials from the drop-down list.
  3. On the API Credentials page, obtain the account name, account ID, IAM username, and IAM user ID, and obtain the project and its ID from the project list.

Data Migration Configuration

AK

Yes

This parameter is displayed when DataArts Migration is selected for Applicable Modules.

AK/SK required for authentication during access to the DLI database.

You need to create an access key for the current account and obtain an AK/SK pair.

  1. Log in to the management console, move the cursor to the username in the upper right corner, and select My Credentials from the drop-down list.
  2. On the My Credentials page, choose Access Keys, and click Create Access Key. See Figure 1.
    Figure 1 Clicking Create Access Key

  3. Click OK and save the access key file as prompted. The access key file will be saved to your browser's configured download location. Open the credentials.csv file to view Access Key Id and Secret Access Key.
    NOTE:
    • Only two access keys can be added for each user.
    • To ensure access key security, the access key is automatically downloaded only when it is generated for the first time and cannot be obtained from the management console later. Keep them properly.

SK

Yes

KMS encryption key

Yes

KMS key used to encrypt and decrypt data source authentication information. Select a default or custom key.
NOTE:
  • When you use KMS encryption through DataArts Studio or Key Pair Service (KPS) for the first time, you will obtain the default key dlf/default or kps/default automatically generated. For more information about default keys, see What Is a Default Master Key?.
  • Only symmetric keys are supported. Asymmetric keys are not supported.

Agent

Yes

This parameter is displayed when DataArts Migration is selected for Applicable Modules.

DataArts Studio cannot directly connect to non-fully managed services. An agent is required for DataArts Studio to communicate with non-fully managed services. A CDM cluster can function as an agent. If no CDM cluster is available, create one by referring to Creating a CDM Cluster.

NOTE:

If a CDM cluster functions as the agent for a data connection in Management Center, the cluster supports a maximum of 200 concurrent active threads. If multiple data connections share an agent, a maximum of 200 SQL, Shell, and Python scripts submitted through the connections can run concurrently. Excess tasks will be queued. You are advised to plan multiple agents based on the workload.