Configuring Environment Isolation for a Workspace in Enterprise Mode

Prerequisites

• Before configuring environment isolation for DLI, ensure that you have created a DLI data connection.

(Optional) Configuring DLI Environment Isolation

Environment isolation needs to be configured only for a serverless service (that is, DLI).

1. On the DataArts Studio console, locate a workspace and click Management Center.
   Figure 1 Management Center
   

2. In the left navigation pane on the Management Center page, choose Data Source Resource Mapping Configuration.
   Figure 2 Data Source Resource Mapping Configuration
   

3. Click the DB Configuration tab and then Add. Set the database names for the development and production environments respectively and click Save. You can click and to edit and delete records.
   The database names must be the names of created databases. It is recommended that the database name for the development environment be the same as that for the production environment, and that suffix _dev be added to the database name for the development environment so that it can be distinguished from the database name for the production environment.

   Figure 3 DB Configuration
   

4. Click the DLI Queue Configuration tab and then Add. Set the queue names for the development and production environments respectively and click Save. You can use and to edit and delete records.
   The queue names must be the names of created DLI queues. It is recommended that the queue name for the development environment be the same as that for the production environment, and that suffix _dev be added to the queue name for the development environment so that it can be distinguished from the queue name for the production environment.

   Figure 4 DLI Queue Configuration
   

5. After the preceding operations are complete, DLI environment isolation configuration is complete.

DB Configuration

1. On the DataArts Studio console, locate a workspace and click Management Center.
2. In the left navigation pane on the Management Center page, choose Data Source Resource Mapping Configuration.
3. Click the DB Configuration tab and then Add. Set the database names for the development and production environments respectively and click Save. You can click and to edit and delete records.
   The database names must be the names of created databases. It is recommended that the database name for the development environment be the same as that for the production environment, and that suffix _dev be added to the database name for the development environment so that it can be distinguished from the database name for the production environment.

   

   For GaussDB(DWS), MRS Hive, and MRS Spark, if you select the same cluster when creating a data connection, you must configure database mapping on the Configure Data Source Resource Mapping page to isolate the development and production environments.

   Figure 5 DB Configuration