DataWorks provides the connection isolation feature for workspaces in standard mode. This way, data of the development environment can be isolated from data of the production environment.

Background information

If a connection is configured in both the development and production environments, you can use the connection isolation feature to isolate the connection in the development environment from that in the production environment.
Note Only workspaces in standard mode support the connection isolation feature.

When you configure a sync node, the connection in the development environment is used. After you commit the sync node to the production environment for running, the connection in the production environment is used. To commit a sync node to the production environment for running, you must configure connections in both the development and production environments. The connections must have the same name in the development and production environments. For more information about the supported data stores for batch synchronization, see Supported data sources, readers, and writers.

The connection isolation feature has the following impacts on workspaces:
  • Workspaces in basic mode: The features and configuration dialog boxes of connections are the same as those before the connection isolation feature is added.
  • Workspaces in standard mode: The Environment parameter is added to the configuration dialog boxes of connections.
  • Workspaces upgraded from the basic mode to the standard mode: During the upgrade, you are prompted to upgrade connections. After the upgrade, the connections in the development environment are isolated from those in the production environment.

Procedure

  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Workspaces.
  3. In the top navigation bar, select the region where your workspace resides. Find your workspace and click Data Integration in the Actions column.
  4. On the page that appears, click Connection in the left-side navigation pane. The Data Source page appears.
    Data Source page
    GUI element Description
    Batch add data source You can create only multiple MySQL, SQL Server, or Oracle connections at a time.

    DataWorks provides templates for you to create multiple connections at a time. To create multiple connections of a specific type at a time, download the corresponding template, enter connection information in the template, and then upload the template. The progress and result of creating connections are displayed in the Batch add data source dialog box. You must configure the following information for each connection in the template: connection type, connection name, description, URL, and applicable environment. When you specify the applicable environment, the value 0 indicates the development environment and the value 1 indicates the production environment.

    New data source
    • Connections in the development environment: You can select such a connection when you create a sync node, and then run the sync node in the development environment. You cannot commit the sync node to the production environment for running.
    • Connections in the production environment: You can use such a connection only in the production environment. You cannot select such a connection when you create a sync node.
    Note The same connection must have the same name in the development and production environments.
    Environment This parameter is not displayed for a workspace in basic mode.
    Operation
    • New: This button is displayed if no connection is configured for the corresponding environment. Click the button to create a connection for the environment.
    • Edit and Delete: These buttons are displayed if a connection is configured for the corresponding environment. You can click Edit to modify the connection or Delete to delete the connection.
      • Before you delete a connection from both the development and production environments, check whether the connection is used by any sync node in the production environment. The delete operation cannot be rolled back. After the connection is deleted, you cannot select it when you configure a sync node in the development environment.

        If a sync node in the production environment uses this connection, the sync node cannot be run after the connection is deleted. Delete the sync node before you delete the connection.

      • Before you delete a connection from the development environment, check whether the connection is used by any sync node in the production environment. The delete operation cannot be rolled back. After the connection is deleted, you cannot select it when you configure a sync node in the development environment.

        If a sync node in the production environment uses this connection, you cannot obtain metadata when you edit the sync node after the connection is deleted. However, the sync node can be run in the production environment.

      • Before you delete a connection from the production environment, check whether the connection is used by any sync node in the production environment. If you select this connection when you configure a sync node in the development environment, you cannot commit the sync node to the production environment after the connection is deleted.

        If a sync node in the production environment uses this connection, the sync node cannot be run after the connection is deleted.

    Select You can select multiple connections to test the connectivity of the connections or delete them at a time.