Data Integration provides four centralized configuration features — Authentication File Management, DDL message processing policies, Task Templates, and Public Alert Rules — that let you define settings once and reuse them across tasks and workspaces. This reduces repetitive setup and makes it easier to standardize team workflows.
Access the configuration page
Log on to the DataWorks console. In the top navigation bar, select the target region. In the left-side navigation pane, choose Data Integration > Data Integration. Select the target workspace from the drop-down list, then click Go to Data Integration.
In the navigation pane, under Configuration Options, click the module you want to configure: Authentication File Management, Processing Policy for DDL Messages in Real-time Sync, Task Template, or Public Alert Rule.
Authentication file management
Authentication File Management provides a unified interface for managing Kerberos configuration files uploaded when you configure a data source. Upload a file once and reuse it across multiple data sources without re-uploading.
For more information, see Third-party authentication file management.
DDL message processing policies for real-time sync
How it works
During real-time synchronization, schema changes — Data Definition Language (DDL) events such as adding a column or clearing a table — at the source must be handled at the destination. Each DDL event requires a decision: apply the change, ignore it, or stop the task. Without a predefined policy, you must configure DDL handling for each new task individually.
Processing Policy for DDL Messages in Real-time Sync lets you set a default DDL policy per destination type. When you create a new real-time sync task for an entire database, the saved policy loads automatically.
Set a DDL processing policy
From the Synchronize To drop-down list, select the destination data source type — for example, MaxCompute or Hologres.
For each type of DDL change message, select a processing method:
Policy What happens Normal treatment The DDL change is applied to the destination schema. Historical data is not backfilled into any new columns created this way. Ignore The DDL event is discarded. The destination schema remains unchanged. Error The real-time sync task stops immediately and its status is set to Error. Save the policy. It applies automatically when you create new real-time sync tasks for an entire database with this destination type.
To override the policy for a single task, click Advanced Configuration > DDL Capability Configuration in the upper-right corner of the task details page.
Usage notes
The following constraints apply to real-time synchronization from MySQL and PolarDB for MySQL sources.
Add new columns at the end of the table, not in the middle. If you must add a column in the middle of a source table, observe these constraints:
During full initialization: Do not add columns in the middle of a table. Doing so causes data anomalies in the subsequent real-time synchronization phase.
During real-time synchronization: Reset the synchronization offset to a point in time after the DDL event that added the column. Otherwise, data anomalies occur in subsequent synchronization.
If a data anomaly occurs, edit the task to remove the affected table, then reapply the update to recover the correct data.
Task templates
Some channels do not support Task Templates. Use the Clone feature instead.
Task Templates let you save a configured task as a reusable template. When creating a new task, import a template to skip repetitive configuration.
What you can do
Standardize development: Save common task configurations as shared templates for team reuse.
Speed up development: Modify an existing template to quickly complete a new task.
Preserve knowledge: Save complex or high-quality task implementations so the team can build on them.
Manage templates
On the Task Template page, you can:
View templates: See all available templates in the current project, including template IDs, names, and last update times.
Find a template: Use the search box to filter by task name, template ID, or data source information.
Delete a template: Click the delete action in the Operation column.
Public alert rules
Public Alert Rule lets you define a reusable alert rule once, then apply it across multiple tasks. When contacts change or thresholds need adjustment, update the rule once — all referencing tasks are updated automatically.
Create an alert rule
Click Create.
Enter an Alert Rule Name and select an Alert Reason — for example, business latency, dirty data, or failover.
Configure the Alert Notification Method: phone call, text message, email, DingTalk, webhook, or Lark.
(Optional) Set Configure Advanced Parameters for additional options.
Recovery notifications are supported for business latency, task status, and task resource utilization anomalies. Enable recovery notifications in the alert rule settings.
Webhook and Lark are available only in DataWorks Enterprise Edition.
For configuration guidance, see Best practices for configuring alerts for real-time sync tasks.
Apply and manage alert rules
Apply to multiple tasks: Click Task Reference to add the rule to multiple tasks or remove it from them. Enable or pause alerts across tasks in a single action.
Test an alert rule: Click Test to send a real alert notification and verify delivery to the specified recipients.
The Test action sends a live alert notification. Use it with care to avoid unexpected interruptions for your team.