To use DataArts Studio, create a cloud platform account, create a DataArts Studio instance, and authorize a user to use DataArts Studio.
+To use DataArts Studio, create a a cloud platform account, create a DataArts Studio instance, and authorize a user to use DataArts Studio.
For details about the preparations and operations, see later sections.
Creating an IAM User and Assigning DataArts Studio Permissions
-- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing DataArts Studio resources.
- Assign users only the permissions required to perform a task.
- Entrust a cloud platform account or cloud service to perform efficient O&M on your DataArts Studio resources.
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing DataArts Studio resources.
- Assign users only the permissions required to perform a task.
- Entrust a a cloud platform account or cloud service to perform efficient O&M on your DataArts Studio resources.
If you do not require individual IAM users for permissions management, skip this section.
Background
- Before assigning permissions to a user group, familiarize yourself with the DataArts Studio workspace role permissions that can be added to the user group and select permissions based on actual requirements.
Procedure
- Create a user group and assign permissions to it. Log in to the IAM console using a cloud platform account, create a user group, and grant permissions of a common user (for example, DAYU User) to the group.
For details, see "User Groups and Authorization" > "Creating a User Group and Assigning Permissions" in Identity and Access Management User Guide.
+Procedure
- Create a user group and assign permissions to it. Log in to the IAM console using a a cloud platform account, create a user group, and grant permissions of a common user (for example, DAYU User) to the group.
For details, see "User Groups and Authorization" > "Creating a User Group and Assigning Permissions" in Identity and Access Management User Guide.
- When configuring DataArts Studio permissions for a user group, enter DAYU in the search box to search for the permissions and select the permissions to be granted to the user group, for example, DAYU User.
- If an IAM user wants to create a workspace, you must assign the IAM user the DAYU Administrator policy. Users with the DAYU Administrator policy can perform all operations on DataArts Studio.
- DataArts Studio is a project-level service deployed in specific physical regions. If you select All resources for Scope, the permission takes effect in all projects of all regions. If you select Region-specific projects for Scope, the permission takes effect only for a specified project. When accessing DataArts Studio, the IAM user must switch to the region where they have been assigned the required permissions.
- Create a user and add the user to the user group. Create a user on the IAM console and add the user to the group created in 1.
For details, see "IAM Users" > "Creating an IAM User" in Identity and Access Management User Guide.
diff --git a/docs/dataartsstudio/umn/dataartsstudio_01_0021.html b/docs/dataartsstudio/umn/dataartsstudio_01_0021.html index 6f3c0820..27d1924d 100644 --- a/docs/dataartsstudio/umn/dataartsstudio_01_0021.html +++ b/docs/dataartsstudio/umn/dataartsstudio_01_0021.html @@ -3,7 +3,7 @@Viewing Basic Cluster Information and Modifying Cluster Configurations
Scenario
After creating a CDM cluster, you can view its basic information and modify its configurations.
- You can view the following basic cluster information:
- Cluster information: cluster version, creation time, project ID, instance ID, and cluster ID
- Instance configuration: cluster flavor, CPU, and memory
- Network configuration
- You can modify the following cluster configurations:
- Notification: If a CDM migration job (only table/file migration) fails or the EIP is abnormal, CDM sends an SMS or email notification to the user.
- User isolation: determines whether other users can operate the migration jobs or links in the cluster.
- If this function is enabled, migration jobs and links in the cluster are isolated. Other IAM users of the cloud platform account cannot operate the jobs and links.
- If this function is disabled, migration jobs and links in the cluster can be shared by users. All IAM users with the required permission in the cloud platform account can view and perform operations on the jobs and links in the cluster.
After disabling User Isolation, restart the cluster VM for the settings to take effect.
+ - You can modify the following cluster configurations:
- Notification: If a CDM migration job (only table/file migration) fails or the EIP is abnormal, CDM sends an SMS or email notification to the user.
- User isolation: determines whether other users can operate the migration jobs or links in the cluster.
- If this function is enabled, migration jobs and links in the cluster are isolated. Other IAM users of the a cloud platform account cannot operate the jobs and links.
- If this function is disabled, migration jobs and links in the cluster can be shared by users. All IAM users with the required permission in the a cloud platform account can view and perform operations on the jobs and links in the cluster.
After disabling User Isolation, restart the cluster VM for the settings to take effect.
Redis Server List
List of MongoDB server addresses. Enter each address in the format of IP address or domain name of the database server:port number, and separate the entered addresses with semicolons (;).
+List of Redis server addresses. Enter each address in the format of IP address or domain name of the database server:port number, and separate the entered addresses with semicolons (;).
192.168.0.1:7300;192.168.0.2:7301
To DDS
-If the destination link of a job is the Link to DDS, configure the destination job parameters based on Table 1. +If the destination link of a job is the Link to DDS, configure the destination job parameters based on Table 1.Table 1 Parameter description Parameter
Description
@@ -14,7 +14,7 @@Database to which data is to be imported
mongodb
+DB_dds
Collection Name
diff --git a/docs/dataartsstudio/umn/dataartsstudio_01_0115_0.html b/docs/dataartsstudio/umn/dataartsstudio_01_0115_0.html index 560cf616..98ca7d11 100644 --- a/docs/dataartsstudio/umn/dataartsstudio_01_0115_0.html +++ b/docs/dataartsstudio/umn/dataartsstudio_01_0115_0.html @@ -1,7 +1,7 @@Creating a DataArts Studio Basic Package
-Background
Only cloud platform account users with the DAYU Administrator or Tenant Administrator permissions can create DataArts Studio instances or DataArts Studio incremental packages.- Users with the Tenant Administrator permissions can perform all operations except IAM user management. For security purposes, you are not advised to grant the Tenant Administrator permissions to IAM users.
+diff --git a/docs/dataartsstudio/umn/dataartsstudio_01_0529.html b/docs/dataartsstudio/umn/dataartsstudio_01_0529.html index f2f3109f..95102991 100644 --- a/docs/dataartsstudio/umn/dataartsstudio_01_0529.html +++ b/docs/dataartsstudio/umn/dataartsstudio_01_0529.html @@ -105,9 +105,12 @@Background
Only a cloud platform account users with the DAYU Administrator or Tenant Administrator permissions can create DataArts Studio instances or DataArts Studio incremental packages. Users with the Tenant Administrator permissions can perform all operations except IAM user management. For security purposes, you are not advised to grant the Tenant Administrator permissions to IAM users.
- Click Test to test connectivity of the data connection. If the test passes, the data connection is created.
- After the test is successful, click OK. The system will create the data connection for you.
Developing a Python Script
- Choose DataArts Factory > Develop Script and create a Python script named python_test.
- Edit the Python statement in the editor, select the host connection, and click Submit and Unlock..
- This example defines a string template for saving company information and uses the template to output information about different companies.
template='No.:{:0>9s} \t CompanyName:{:s} \t Website:https://www.{:s}.com' -context1=template.format('1','CompanyXXX','companyxxx') -context2=template.format('2','CompanyYYY','companyyyy') +Developing a Python Script
- Choose DataArts Factory > Develop Script and create a Python script named python_test.
- Edit the Python statement in the editor, select the host connection, and click Submit and Unlock..
- This example defines a string template for saving company information and uses the template to output information about different companies.
import sys +Company_Name1=sys.argv[1] +Company_Name2=sys.argv[2] +template='No.:{:0>9s} \t CompanyName: {:s} \t Website: https://www.{:s}.com' +context1=template.format('1',Company_Name1,Company_Name1.lower()) +context2=template.format('2',Company_Name2,Company_Name2.lower()) print(context1) print(context2) - The script development area in Figure 4 is a temporary debugging area. After you close the script tab, the development area will be cleared.
- Connection: Select the data connection created in Creating an ECS Data Connection.
- This example defines a string template for saving company information and uses the template to output information about different companies.
- This example defines a string template for saving company information and uses the template to output information about different companies.
Field Mapping in Automatic Table Creation on DWS
Figure 1 describes the field mapping between DWS tables created by CDM and source tables. For example, if you use CDM to migrate the Oracle database to DWS, CDM automatically creates a table on DWS and maps the NUMBER(3,0) field of the Oracle database to the SMALLINT field of DWS.
- +diff --git a/docs/dataartsstudio/umn/dataartsstudio_07_013.html b/docs/dataartsstudio/umn/dataartsstudio_07_013.html index 7da6fa82..48dcd3de 100644 --- a/docs/dataartsstudio/umn/dataartsstudio_07_013.html +++ b/docs/dataartsstudio/umn/dataartsstudio_07_013.html @@ -3,7 +3,7 @@DataArts Studio Permissions
A workspace member can be assigned the role of admin, developer, operator, or viewer. This topic describes the permissions of each role.
- Admin: Users with this role have the permissions to perform all operations in a workspace. You are advised to assign this role to the project owner, development owner, and O&M administrator.
- Developer: Users with this role have the permissions to create and manage work items, but cannot perform operations on workspaces, clusters, and reviewers. You are advised to assign this tole to users who develop and process tasks.
- Operator: Users with this role have the permissions to perform operations such as O&M and scheduling, but cannot modify work items or configurations. You are advised to assign this role to users for O&M management and status monitoring.
- Viewer: Users with this role can only read data from DataArts Studio, but cannot perform operations on workspaces or modify work items or configurations. You are advised to assign this role to users who only want to view information in the workspace but do not perform any operation.
Accounts and users with the DAYU Administrator or Tenant Administrator role have all the permissions on cloud platform account, including permissions to createDataArts Studio instances and DataArts Studio incremental packages. By default, other users do not have the permissions to create DataArts Studio instances. If they want to create DataArts Studio instances, they must obtain the required permissions.
+ Accounts and users with the DAYU Administrator or Tenant Administrator role have all the permissions on a cloud platform account, including permissions to createDataArts Studio instances and DataArts Studio incremental packages. By default, other users do not have the permissions to create DataArts Studio instances. If they want to create DataArts Studio instances, they must obtain the required permissions.
Accounts and users with the Tenant Administrator role can perform all operations except IAM user management. For security purposes, you are not advised to assign this role to IAM users. Exercise caution when performing this operation.
Workspace
diff --git a/docs/dataartsstudio/umn/dataartsstudio_12_0006.html b/docs/dataartsstudio/umn/dataartsstudio_12_0006.html index 911a72f4..2abe57e1 100644 --- a/docs/dataartsstudio/umn/dataartsstudio_12_0006.html +++ b/docs/dataartsstudio/umn/dataartsstudio_12_0006.html @@ -8,7 +8,13 @@2023-04-30
+2024-03-01
+Update the following sections:
+ +2023-04-30
Update the following sections:
diff --git a/docs/dataartsstudio/umn/en-us_image_0000001322408176.png b/docs/dataartsstudio/umn/en-us_image_0000001322408176.png deleted file mode 100644 index 59dcc7f8..00000000 Binary files a/docs/dataartsstudio/umn/en-us_image_0000001322408176.png and /dev/null differ diff --git a/docs/dataartsstudio/umn/en-us_image_0000001694876605.png b/docs/dataartsstudio/umn/en-us_image_0000001694876605.png new file mode 100644 index 00000000..b935943e Binary files /dev/null and b/docs/dataartsstudio/umn/en-us_image_0000001694876605.png differ
- You can view the following basic cluster information:
- Create a user group and assign permissions to it. Log in to the IAM console using a a cloud platform account, create a user group, and grant permissions of a common user (for example, DAYU User) to the group.
