On the Workspace Management page of a workspace, you can manage and configure the workspace. DataWorks supports a variety of compute engines, such as MaxCompute, E-MapReduce, Realtime Compute, Hologres, Graph Compute, and AnalyticDB for PostgreSQL.

Go to the Workspace Management page

  1. Log on to the DataWorks console.
  2. In the left-side navigation pane, click Workspaces.
  3. You can go to the Workspace Management page of a workspace from the Workspaces page.
    Go to the Workspace Management page by using the following methods:
    • On the Workspaces page, find the workspace that you want to configure and click Workspace Settings in the Actions column. In the Workspace Settings panel, click More. The Workspace Management page appears.More
    • On the Workspaces page, find the workspace that you want to configure and click Data Analytics in the Actions column. On the DataStudio page, click the Workspace Management page icon in the upper-right corner to go to the Workspace Management page.Workspace Settings panel
  4. On the Workspace Management page, you can configure the basic properties, scheduling properties, security settings, and compute engines of the workspace based on your actual needs.

Configure the basic properties

Basic properties 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 not case-sensitive. 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 that is used to identify the workspace. It can contain only letters and digits. You can change the display name as required.
Creation date The point in time when the workspace was created, which cannot be changed.
Mode The mode of the workspace. Valid values: Simple Mode and Standard mode.
Note In this example, a workspace in standard mode is used.
The head of 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.

Configure the scheduling properties

In the Scheduling properties section, you can enable periodic scheduling for the workspace. You can also set the default resource group for scheduling, default resource group for Data Integration, and default number of times and interval of automatic reruns after an error occurs.Scheduling properties section

Recurring nodes can be run in a workspace only after you turn on Enable periodic scheduling for the workspace.

Configure the security settings

Security Settings section
Section Description
Allow download of select results Specifies 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 own node owners Specifies whether to allow RAM users to change owners of their nodes.
Sandbox whitelist (configure IP addresses or domain names that Shell nodes can access) The IP addresses or domain names that can be accessed by a Shell node that runs on the default resource group.
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.

To add an IP address or a domain name to the whitelist, perform the following steps:

  1. In the Security Settings section, click Add sandbox whitelist.
  2. In the Add sandbox whitelist dialog box, enter an IP address or a domain name and a port number in the Address and Port fields.
  3. Click Confirm.

Bind a MaxCompute compute engine instance

  1. In the Computing Engine information section, click the MaxCompute tab. On this tab, you can view the information about all available MaxCompute compute engines in the current workspace.
  2. Click Add instances.
  3. In the Add a MaxCompute instance dialog box, set the parameters as required.
    Add a MaxCompute instance dialog box
    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 must start with a letter and can contain letters, underscores (_), and digits.
    Region The region of the workspace.
    Payment mode The billing method of the compute engine instance. Valid values: The pay-as-you-go billing method, Monthly package, and Developer version.
    Note An instance of the Developer version mode cannot be added if the current workspace is in standard mode.
    Quota group The quotas of computing resources and disk space 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.
  4. Click Confirm.
    After the compute engine instance is added, you can set it as the default instance.

Bind an E-MapReduce compute engine instance

  1. In the Compute Engine information section, click the E-MapReduce tab. On this tab, you can view the information about all available E-MapReduce compute engines in the current workspace.
  2. Click Add instances.
  3. In the New EMR cluster dialog box, set the parameters as required.
    New EMR cluster dialog box
    Parameter Description
    Instance display name The display name of the E-MapReduce cluster to bind.
    Region The region of the current workspace, which cannot be modified.
    Access Mode The access mode of the E-MapReduce cluster to bind. Valid values: Shortcut mode and Security mode.
    Note In this example, bind an E-MapReduce cluster in Shortcut mode.
    Scheduling access identity The identity that is used to deliver the code of an EMR node to the E-MapReduce cluster after the node is committed to the scheduling system of DataWorks in the production environment. Valid values: Alibaba Cloud primary account and Alibaba Cloud sub-account.
    Note If you select Alibaba Cloud sub-account, you must specify a RAM user to which the AliyunEMRDevelopAccess policy is attached.
    Access identity The identity that is used to deliver the code of an EMR node in the development environment to the E-MapReduce cluster. Default value: Task owner.
    Note This parameter is available only when the workspace is in standard mode.
    Cluster ID The ID of the E-MapReduce cluster to bind. Select an ID from the drop-down list. The selected E-MapReduce cluster is used as the runtime environment of EMR nodes.
    Project ID The ID of the E-MapReduce project to bind. Select an ID from the drop-down list. The selected E-MapReduce project is used as the runtime environment of EMR nodes.
    Note E-MapReduce projects in Security mode are unavailable.
    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 E-MapReduce, which cannot be modified.
  4. Click Confirm.
    After the compute engine instance is added, you can set it as the default instance and modify the instance configuration as needed.

Bind a Realtime Compute compute engine instance

  1. In the Compute Engine information section, click the Real-time computing tab. On this tab, you can view the information about all available Realtime Compute compute engines in the current workspace.
  2. Click Add instances.
  3. In the Add a real-time computing instance dialog box, set the parameters as required.
    Add a real-time computing instance dialog box
    Parameter Description
    Instance display name The display name of the compute engine instance.
    Region The region of the current workspace.
    Select project The Realtime Compute project to be bound to the workspace. Select a project from the drop-down list. If you need to create a project, click Real-time calculation control platform.
  4. Click Confirm.
    After the compute engine instance is added, you can set it as the default instance and modify the instance configuration as needed.

Bind a Hologres compute engine instance

  1. In the Compute Engine information section, click the Hologres tab. On this tab, you can view the information about all available Hologres compute engines in the current workspace.
  2. Click Binding HologresDB.
  3. In the Binding HologresDB dialog box, set the parameters as required.
    Hologres
    Parameter Description
    Instance display name The display name of the compute engine instance.
    Access identity The identity used to run the code of committed nodes in Hologres. Valid values: Alibaba Cloud primary account and Alibaba Cloud sub-account.
    Hologres instance name The name of the Hologres instance to be bound to the workspace.
    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 Hologres instance.
    Port The port of the purchased Hologres instance. The value is automatically generated after you select the Hologres instance.
  4. Click Test connectivity.
  5. After the connectivity test is passed, click Confirm.

Bind a Graph Compute compute engine instance

  1. In the Compute Engine information section, click the GraphCompute tab.
  2. Click Bind a GraphCompute instance.
    Notice 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.
  3. In the Bind a GraphCompute instance dialog box, set the parameters as required.
    GraphCompute
    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.
    Create an instance If you do not have a Graph Compute instance, click Create an instance to purchase a Graph Compute instance.
    Notice By default, each Alibaba Cloud account can purchase only one Graph Compute instance.
  4. Click Binding.

Bind an AnalyticDB for PostgreSQL compute engine instance

Notice You can use the AnalyticDB for PostgreSQL compute engine only in DataWorks Standard Edition or a more advanced edition. Therefore, the AnalyticDB for PostgreSQL tab is available only in DataWorks Standard Edition or a more advanced edition.
  1. In the Compute Engine information section, click the AnalyticDB for PostgreSQL tab.
  2. Click Add instances.
  3. In the Add an AnalyticDB for PostgreSQL instance dialog box, set the parameters as required.
    ADB
    Parameter Description
    Instance display name The display name of the compute engine instance, which must be unique.
    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 of the account that you can use to access the database.
    Password The password of the account that you can use to access the database.
    Test connectivity AnalyticDB for PostgreSQL nodes must be run on exclusive resource groups. Specify an exclusive resource group for running these nodes. For more information, see Exclusive resource mode.

    Click Test connectivity to test the connectivity between the specified exclusive resource group and AnalyticDB for PostgreSQL instance.

  4. After the connectivity test is passed, click Confirm.