On the Workspace Management page of a workspace, you can manage and configure the workspace.

Go to the Workspace Management page

  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Workspaces. On the Workspaces page that appears, go to the Workspace Management page of a workspace.
    You can go to the Workspace Management page in the following ways:
    • On the Workspaces page, find the target workspace and click Workspace Settings in the Actions column. In the Workspace Settings dialog box that appears, click More. The Workspace Management page appears.More
    • On the Workspaces page, find the target workspace and click Data Analytics in the Actions column. On the DataStudio page that appears, click the Workspace Manage icon in the upper-right corner to go to the Workspace Management page.Settings page
  3. On the Workspace Management page, configure the workspace as required in the General Information, Scheduling properties, Security Settings, and Compute Engine sections.

General Information section

General Information section
Parameter Description
Workspace ID The ID of the workspace.
Workspace Name The name of the workspace. The name must start with a letter and can contain only letters and digits. It is case-insensitive. It uniquely identifies the workspace and cannot be changed after the workspace is created.
Status The status of the workspace. Valid values: Normal, Deleted, Initialize, Initialization Failed, Manual Disable, Deleting, Deletion Failed, Suspended (Overdue), Updating, and Update Failed.
Note
  • If a workspace fails to be created, it enters the Initialization Failed state. In this case, you can create the workspace again.
  • A workspace in the Normal state can be disabled by the workspace administrator. After a workspace is disabled, all features of the workspace become unavailable. However, the data of the workspace is retained, and nodes that have been committed can run properly.
  • The workspace administrator can click Enable in the Actions column to restore the disabled workspace to normal.
Display Name The display name of the workspace. You can change the display name as required. The display name is used to identify the workspace and can contain only letters and digits.
Created At The time when the workspace was created, which cannot be changed.
Mode The mode of the workspace. Valid values: Basic Mode and Standard Mode.
Note This topic uses a workspace in standard mode as an example.
Owner The owner of the workspace, who has permissions to delete and disable the workspace. The owner of the workspace cannot be changed.
Description The descriptive information about the workspace, which provides comments on the workspace. You can modify the description as required. The description can be up to 128 characters in length and can contain letters, special characters, and digits.

Scheduling properties section

In the Scheduling properties section, you can specify whether to enable the recurrence feature for the current workspace. Recurring nodes can be run in this workspace only if you turn on this switch.Scheduling properties section

Security Settings section

  • Download SELECT Query Result

    You can specify whether to allow workspace members to download the results queried in DataStudio. If you turn on this switch, workspace members can download the query results returned by SELECT statements in DataStudio.

  • Allow sub-accounts to change their node responsible person

    You can specify whether to allow Resource Access Management (RAM) users to change the owner for their nodes.

  • Sandbox Whitelist (adds IP addresses and domains that can be accessed by Shell nodes)
    To allow a Shell node that is run on the default resource group to access a specified IP address or domain name and add the IP address or domain name to the whitelist.
    1. Click Add sandbox whitelist.
    2. In the Add to Sandbox Whitelist dialog box that appears, enter an IP address and port in the IP Address and Port fields respectively.
    3. Click OK.
    Note You must specify public IP addresses or domain names that can be accessed. For internal services in your enterprise, we recommend that you use exclusive resource groups to guarantee network accessibility. For more information, see Exclusive resource mode.

Compute Engine section

DataWorks supports the following types of compute engines: MaxCompute, E-MapReduce, Realtime Compute, Hologres, GraphCompute, and AnalyticDB for PostgreSQL.
  • MaxCompute
    1. Click the MaxCompute tab in the Compute Engine section. On this tab, you can view the information about all available MaxCompute compute engines in the current workspace.
    2. Click Add instance. In the Add MaxCompute instance dialog box that appears, set the parameters as required.
      Parameter Description
      Instance display name The display name of the compute engine instance. The display name can be up to 27 characters in length. It can only start with a letter and can contain letters, underscores (_), and digits.
      Region The region where the compute engine instance resides.
      Payment mode The billing method of the compute engine instance. Valid values: Pay by volume, Annual package month, and Developer Edition.
      Note An instance of Developer Edition cannot be added if the current workspace is in standard mode.
      Quota group The quotas of computing resources and disk spaces for the compute engine instance.
      Production Environment The parameters in this section include Project name and Access identity.
      • Project name: the name of the MaxCompute project that serves as the production environment at the underlying layer of the DataWorks workspace.
      • Access identity: the type of the account used to access the MaxCompute project. Valid values: Alibaba Cloud primary account and Alibaba Cloud sub-account.
      Development Environment The parameters in this section include Project name and Access identity.
      • Project name: the name of the MaxCompute project that serves as the development environment at the underlying layer of the DataWorks workspace.
        Note This MaxCompute project provides computing and storage resources.
      • Access identity: the type of the account used to access the MaxCompute project. The default value is Task owner and cannot be changed.
    3. Click OK.

      After the compute engine instance is added, you can set it as the default instance.

  • E-MapReduce
    1. Click the E-MapReduce tab in the Compute Engine section. On this tab, you can view the information about all available E-MapReduce compute engines in the current workspace.
    2. Click Add instance. In the New EMR cluster dialog box that appears, set the parameters as required.
      Parameter Description
      Instance display name The display name of the compute engine instance.
      Region The region where the compute engine instance resides.
      Access ID The AccessKey ID of the account authorized to access the E-MapReduce cluster to be added as the compute engine instance.
      Access Key The AccessKey secret of the account authorized to access the E-MapReduce cluster.
      Cluster ID The ID of the E-MapReduce cluster.
      EmrUserID The ID of the user who created the E-MapReduce cluster.
      Project ID The ID of the project in the E-MapReduce cluster.
      YARN resource queue The name of the resource queue in the E-MapReduce cluster. Unless otherwise specified, set the value to default.
      Endpoint The endpoint of the E-MapReduce cluster. You can obtain the endpoint from the E-MapReduce console.
    3. Click OK.

      After the compute engine instance is added, you can set it as the default instance and modify the instance configuration as needed.

  • Realtime Compute
    Click the Realtime compute tab in the Compute Engine section. On this tab, you can view the information about all available Blink compute engines in the current workspace.
    Parameter Description
    Blink project name The name of the Blink project.
    Add people The name of the account used to add the Blink compute engine.
    Added At The time when the Blink compute engine was added.
    System Account The Alibaba Cloud account used to add the Blink compute engine.
    Blink engine name The name of the Blink compute engine.
    Blink cluster name The name of the cluster to which the Blink compute engine belongs.
    Blink Queue The queue of the Blink compute engine.
  • Hologres
    1. Click the Hologres tab in the Compute Engine section. On this tab, you can view the information about all available Hologres compute engines in the current workspace.
    2. Click Binding HologresDB. In the Binding HologresDB dialog box that appears, set the parameters as required.
      Parameter Description
      Instance display name The display name of the compute engine instance.
      Hologres instance name The name of the purchased Hologres instance to be added as the compute engine instance.
      Database name The name of the database that was created in SQL Console, for example, testdb.
      Server The endpoint of the purchased Hologres instance. The value is automatically generated after you select the target Hologres instance.
      Port The port of the purchased Hologres instance. The value is automatically generated after you select the target Hologres instance.
    3. Click Test connectivity.
    4. After the connectivity test is passed, click OK.
  • GraphCompute
    1. Click the GraphCompute tab in the Compute Engine section. On this tab, you can view the information about all available Graph Compute compute engines in the current workspace.
    2. Click Bind a GraphCompute instance. In the Bind a GraphCompute instance dialog box that appears, set the parameters as required.
      Parameter Description
      Instance display name The display name of the compute engine instance.
      GraphCompute instance name The name of the Graph Compute instance to be added as the compute engine instance.
      Note A Graph Compute instance can be bound to only one DataWorks workspace. After a Graph Compute instance is bound to a DataWorks workspace, the instance cannot be used in other DataWorks workspaces.
  • AnalyticDB for PostgreSQL
    1. Click the AnalyticDB for PostgreSQL tab in the Compute Engine section. On this tab, you can view the information about all available AnalyticDB for PostgreSQL compute engines in the current workspace.
    2. Click Add instance. In the Add an AnalyticDB for PostgreSQL instance dialog box that appears, set the parameters as required.
      Parameter Description
      Instance display name The display name of the compute engine instance. Specify a unique display name.
      InstanceName The name of the AnalyticDB for PostgreSQL instance to be added as the compute engine instance.
      DatabaseName The name of the database to be connected to under the AnalyticDB for PostgreSQL instance.
      Username The username used to log on to the database.
      Password The password used to log on to the database.
      Test connectivity AnalyticDB for PostgreSQL nodes must be run on an exclusive resource group. Specify an exclusive resource group for running these nodes. Click Test connectivity to test the connectivity between the specified exclusive resource group and AnalyticDB for PostgreSQL instance.
    3. After the connectivity test is passed, click OK.