User profile analysis (MaxCompute simplified version)

1. Activate services

This tutorial uses the China (Shanghai) region as an example. Prepare the environment based on the services you have activated in the China (Shanghai) region.

2. Enable public network access for the resource group

DataWorks provides the raw data for this case study and its public network access address. To access this raw test data in DataWorks and ensure the case study runs smoothly, you must make sure your Serverless resource group has public network access.

The General-purpose Serverless resource group created when you activate DataWorks in Step 1 or created manually does not have public network access by default. You need to use an Internet NAT gateway to associate an Elastic IP Address (EIP) with the VPC bound to the resource group. This gives the resource group public network access. Follow the steps below.

1. Log on to the VPC - Internet NAT Gateway console. In the top menu bar, switch to the China (Shanghai) region and click Create Internet NAT Gateway. Configure the parameters as shown in the table below.

   Note

   Keep the default values for parameters not mentioned in the table.

   Parameter	Value
   Region	China (Shanghai).
   Network and Zone	Select the VPC and vSwitch bound to the resource group. You can go to the DataWorks resource group list page, switch to the China (Shanghai) region, find the created resource group, and click Network Settings in the Operation column. In the Data Scheduling & Data Integration area, view the Bound VPC and vSwitch. For more information about VPCs and vSwitches, see What is a VPC?. Note If the current resource group is bound to multiple VPCs and vSwitches, make sure to configure and use the VPC and vSwitch from the first row of the list.
   Network Type	Internet NAT gateway.
   Elastic IP Address	Purchase New EIP.
   Service-linked Role Creation	When creating a NAT Gateway for the first time, you need to create a service-linked role. Click Create Service-linked Role.

2. Click Buy Now and complete the payment to create the NAT Gateway instance.

   

3. After the NAT Gateway instance is purchased, click to return to the console and create an SNAT entry for the new instance.

   Note

   Only after an SNAT entry is configured can the resource group using this VPC access the public network.

   1. Click the Manage button in the operation column of the new instance to go to the management page of the target NAT Gateway instance. Switch to the SNAT Management tab.

   2. Under the SNAT Entry List, click the Create SNAT Entry button to create an SNAT entry. Key configurations are as follows:

      Parameter	Value
      SNAT Entry Granularity	Select VPC Granularity to ensure that all resource groups within the NAT Gateway's VPC can access the public network through the configured EIP.
      Select EIP Address	Configure the EIP address bound to the current NAT Gateway instance.

      After configuring the SNAT entry parameters, click the Confirm button to create the SNAT entry.

   Under the SNAT Entry List, when the Status of the newly created SNAT entry changes to Available, it means the VPC bound to the resource group has public network access.

3. Create a workspace

A workspace is the basic unit in DataWorks for task development, member permission management, and collaborative development. All development work in DataWorks is done within a workspace. Follow these steps to create a DataWorks standard mode workspace (with isolated development and production environments) for this case study.

1. Go to the workspace list page.

   Go to the Workspace List. At the top of the page, switch the region to China (Shanghai), and then click Create Workspace.

2. Create the workspace. The following are the key parameters for this tutorial. Keep the default values for other parameters.

   • Workspace Name: Customize the workspace name. It cannot be changed after creation.

     Important

     DataWorks workspace names must be unique across the entire network. You can customize the name or add a unique suffix to avoid naming conflicts.

   • Isolate Development and Production Environments: Enable this switch to specify the workspace mode as Standard Mode Workspace.

   • Use the new version of DataStudio: This tutorial works whether this is enabled or not. It indicates whether to use the new DataStudio features (recommended). If you do not see this option, it is enabled by default.

     Note

     • The new version of DataStudio provides capabilities for collaborative data development across multiple engines, visual workflow orchestration, and data catalog management. It supports interactive data exploration and analysis linked with AI using Notebooks. For more information about the new version of DataStudio, see DataStudio (New Version).

     • For a detailed comparison of core features and interface layouts between the new and old versions of DataStudio, see the DataStudio Upgrade Guide.

   • Workspace Template: Select All Capabilities.

   • Default Resource Group Configuration for DataWorks Workspace: Set this to the Serverless resource group created in Step 1.

3. Click Create Workspace.

   Note

   If you selected Use the new version of DataStudio when creating the workspace, you will be guided to the Bind Computing Resource page. You can skip this for now by clicking Done or Close.

4. Bind MaxCompute as a computing resource

1. Flow design

The website user behavior analysis case uses the offline synchronization capability of the DataWorks Data Integration module to sync business data to MaxCompute. Then, it uses the MaxCompute SQL node in the DataWorks Data Development module to process the user profile data. The final processed result is written to the ads_user_info_1d table. The business data includes:

• Basic user information stored in MySQL (ods_user_info_d). This is provided by the platform by default, so no activation is needed. You can access this data in your workspace by configuring its access information as a data source.

• Website access log data stored in OSS (user_log.txt). This is provided by the platform by default, so no activation is needed. You can access this data in your workspace by configuring its access information as a data source.

2. Task development

Based on the Flow design, develop the workflow tasks in DataWorks. DataWorks provides the relevant code for this tutorial. You can quickly experience this case by importing it with one click. Later, you can also follow the User profile analysis (MaxCompute version) for a step-by-step hands-on experience.

1. Log on to the DataWorks console. In the navigation pane on the left, choose Getting Started > DataWorks Gallery. Then, in the Category section, select Workflow.

2. Load the case study.

   Click the Website User Profile Analysis card. On the case details page, click Load. Then, follow the on-screen instructions to load the case study.

   Key parameter descriptions:

   • Workspace: Select the target workspace for importing the workflow case. Set this to the workspace created in Step 3.

   • Computing Resource Name: Select the computing resource that provides computing and storage services for this tutorial. Set this to the MaxCompute computing resource created and bound in Step 4.

   • Scheduling Resource Group and Integration Resource Group: Select the resource groups for task synchronization and scheduling. Set these to the resource group created in Step 1.

   • Loading Method: Select the processing policy for when the nodes and resources in the case are loaded into the workspace. Keep the default setting.

   • Publishing Rule: Select whether to directly enter the production scheduling system for daily automatic scheduling after the task is imported. Keep the default setting. Deselecting this means it will only be used for testing in data development and will not be automatically scheduled. You can manually publish it later.

3. Confirm the loading result.

   On the Load Case page, click Confirm to start loading. You can view the Import Progress in the pop-up window. After all content is imported, you can click Go to View.

   Note

   Closing the Import Progress window will not affect the template import. You can go to the DataWorks - Workspace List page, click Quick Access > DataStudio or Quick Access > Data Development in the operation column of the target workspace to view the imported template content in the data development module.

4. View the case study.

   If you are using the new version of DataStudio, click in the navigation pane on the left, then click the imported user_profile_analysis case to open the corresponding workflow panel.

   You can double-click each node in the workflow to view the case background and the processing logic of each node.

   Note

   If you are using the old version of DataStudio, under Data Development > Business Flow, double-click experience_case_1_user_behavior_analysis to open the business flow canvas.

   You can double-click each node in the business flow on the canvas to view the case background and the processing logic of each node.

   Important

   Before the business flow is executed successfully for the first time, opening an offline sync task node () will report an error because the target MaxCompute table does not exist. You can first manually run the ancestor nodes (table_ddl_ods_raw_log_d and table_ddl_ods_user_info_d) to create the target tables, and then view the offline sync details.

   • Business data synchronization: The business data provided in this case study is simulated static test data. The offline sync task is responsible for syncing this test data to the specified date partition in MaxCompute daily.

   • Code parameter usage: In actual data synchronization and processing, you can use scheduling parameters for dynamic data handling. For example, by configuring the data timestamp parameter (format: yyyymmdd, usually the previous day's date), you can automatically identify and process data for the corresponding data timestamp and write it to the specified date partition of the target table. For more information, see Scheduling parameters.

     • In the new version of the DataStudio tutorial, each node's code uses ${workflow.var} to get the value of the var parameter defined in the workflow. This allows for dynamic value assignment at runtime. The var parameter is assigned the value $[yyyymmdd-1] to get the data timestamp (yesterday).

     • In the old version of the DataStudio tutorial, each node's code uses ${bizdate} to define a node-level parameter (this parameter name can be customized in actual development). The node then assigns a scheduling parameter to this parameter, enabling dynamic value assignment at runtime. The bizdate parameter is assigned the value $[yyyymmdd-1] to get the data timestamp (yesterday).

   • Dependency settings: For setting dependencies between task nodes, see Scheduling dependencies.

3. Run the task

After developing the task, you can run it to confirm that the code and flow meet expectations.

1. Run the user profile analysis flow: The imported case is a complete case. You can go to the workflow or business flow panel and click the Run button in the toolbar to run the workflow or business flow.

   • If you are using the new version of DataStudio, after clicking Run, the system will automatically read the var parameter in the workflow. On the Fill in Runtime Parameters page, you need to assign a constant value to the parameter for the Current Run Value (for example, set the parameter to 20250101).

   • If you are using the old version of DataStudio, after clicking Run, you do not need to manually assign a value to the bizdate parameter in the code. The system will automatically use the node parameter to assign a value to the bizdate parameter for this task execution.

     Important

     If the run fails with the error "function or view getregion cannot be resolved", check if the ip2region.jar resource and the getregion function used in the processing flow have been published successfully. For the solution, see FAQ.

2. View the business flow execution process: Wait patiently until all task nodes have run successfully (all statuses are ) before proceeding.

   Note

   To view the running details of a node, you can click the node in the successfully executed workflow or business flow to view its operational log and execution information.

   If you are using the new version of DataStudio, click Back at the top of the page to return to the workflow panel before proceeding.

3. Confirm the user profile data: Run the last task node individually to view the final user profile data.

   On the workflow or business flow page, double-click the last node in the flow to enter the node details page. Select the following SQL statement, modify the dt condition, and click Run at the top of the page to query the ads_user_info_1d table and get the final user profile data.

   SELECT * FROM ads_user_info_1d where dt = '20250101' LIMIT  10;

   • New version of DataStudio: The value for the dt condition in this query should match the Current Run Value you configured when running the workflow.

   • Old version of DataStudio: The value for the dt condition in this query should match the data timestamp parsed in the business flow node.

Task O&M