Data Management (DMS) allows DMS administrators to manage system configurations. If you are a DMS administrator, you can modify the system configuration items to flexibly meet your business requirements. This topic describes how to modify the system configuration items.

Prerequisites

You are a DMS administrator.

Procedure

  1. Log on to the DMS console.
  2. In the top navigation bar, move the pointer over the More icon and choose System > Configuration.
  3. On the Configuration tab, find the configuration item that you want to modify and click Change in the Actions column.
    Note For more information about configuration items, see Configuration items.
  4. In the Change Parameter Configuration dialog box, change the value as needed.
  5. Click Confirm Change.

Configuration items

Configuration item Description
Whether to enable access source IP control Specifies whether to enable the IP address whitelist feature for access control. Valid values:
  • Y: enables the IP address whitelist feature. To configure an IP address whitelist as a DMS administrator, choose System > Security > Access IP Whitelists. Only the access from the specified IP addresses or Classless Inter-Domain Routing (CIDR) blocks in the whitelist is allowed.
  • N: disables the IP address whitelist feature. In this case, the users within the current tenant account can access DMS from all IP addresses.
Whether to enable automatic synchronization of instance resources on the cloud Specifies whether to automatically register all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS. Valid values:
  • Y: automatically registers all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS.
  • N: does not automatically register all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS.
Whether to force rollback SQL to be entered when submitting a data change work order Specifies whether to require a user to enter executable SQL statements for rolling back the data change when the user is creating a data change ticket. Valid values:
  • Y: requires executable SQL statements for rolling back the data change.
  • N: does not require executable SQL statements for rolling back the data change.
The timeout period for the number of rows affected by data change verification The timeout period for calculating the number of rows to be affected. The value must be an integer. Before a data change is performed, DMS calculates the number of rows to be affected. The calculation takes a long time if the data volume is large. To ensure that the data change can be performed as required, specify a timeout period for the calculation in seconds. DMS automatically terminates the calculation after the specified timeout period.
Data Change reason classification The reason for a data change. The value must be a JSON string. For more information, see Appendix: Reasons for data changes.
How data changes are performed The method that is used to perform a data change after the ticket is approved. Valid values:
  • COMMITOR: The data change is performed by the user who submits the ticket.
  • AUTO: The data change is automatically performed after the ticket is approved.
  • LAST_AUDITOR: The data change is performed by the last user who approves the ticket.
Enable workflow approval to exceed your authority (DBA | administrator only) Specifies whether to allow a database administrator (DBA) or DMS administrator to act beyond its authority to approve or reject a ticket. Valid values:
  • Y: allows a DBA or DMS administrator to approve or reject a ticket if the previous approver, such as a database owner of the relevant resource, fails to perform the operation.
  • N: does not allow a DBA or DMS administrator to act beyond its authority to approve or reject a ticket.
Default value: Y
Allow OWNER to authorize users Specifies whether to allow a database owner to grant permissions on data resources to other users. The data resources may be database instances, databases, or tables. Valid values:
  • Y: allows a database owner to grant permissions on data resources to other users.
  • N: does not allow a database owner to grant permissions on data resources to other users.
Maximum number of queries for the day The maximum number of queries that each user is allowed to perform per day. The value must be an integer. After the number of queries that a user performs in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account.
Day query rows upper limit The maximum number of data rows that can be returned to each user per day. The value must be an integer. After the number of data rows that are returned to a user in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account.
DMS locale: ZH/EN/JA/ZT The language of the operations logs that are returned by DMS. Valid values:
  • ZH: simplified Chinese
  • EN: English
  • JA: Japanese
  • ZT: traditional Chinese

Appendix: Reasons for data changes

DMS provides the following default reasons for data changes, in the format of JSON strings: 

[{"key":"config_correct","value":"Modify Config"},
{"key":"project_init_data","value":"Init Project Data"},
{"key":"program_bug","value":"Program Bug"},
{"key":"require_deal_without_backend_function","value":"Requirements Without Backend Function"},
{"key":"history_data_clear","value":"History Data Clean"},
{"key":"test","value":"Test"},
{"key":"mis_operation","value":"Mis Operation"},
{"key":"others","value":"Others"}]

The following table describes the default reasons for data changes.

key value Description
config_correct Modify Config To modify configurations.
project_init_data Init Project Data To initialize the data for a project.
program_bug Program Bug To fix a bug.
require_deal_without_backend_function Requirements Without Backend Function To manage the data of an application that does not support backend management.
history_data_clear History Data Clean To clear historical data.
test Test To run a test.
mis_operation Mis Operation To restore data after a misoperation.
others Others To change data for other reasons.