All Products
Search
Document Center

Configuration management

Last Updated: May 29, 2020

Data Management Service (DMS) supports configuration management for the system. DMS allows you to use a DMS administrator account to manage the system configuration items to flexibly meet your business requirements. This topic describes how to manage the system configuration items.

Prerequisites

You are a DMS administrator.

Configuration items

Configuration item Description
Whether to enable access source IP control Specifies whether to enable the IP address whitelist for access control. Valid values:
  • Y: Enable the whitelist. To set the whitelist, follow these steps: Log on to the DMS console. In the top navigation bar, choose System Management > Security > Access IP Whitelists. On the page that appears, click Create Whitelist. In the dialog box that appears, enter IP addresses as required. After the whitelist is set, only accesses from the specified IP addresses are allowed.
  • N: Disable the whitelist. If the whitelist feature is disabled, all users under the current tenant can access DMS from any IP address.
Whether to enable automatic synchronization of instance resources on the cloud Specifies whether to enable automatic registration of ApsaraDB for RDS instances to DMS. Valid values:
  • Y: Enable automatic registration of ApsaraDB for RDS instances.
  • N: Disable automatic registration of ApsaraDB for RDS instances.
Whether to force rollback SQL to be entered when submitting a data change work order Specifies whether to require a user to enter the executable SQL statements for rolling back the data change when the user submits a data change ticket. Valid values:
  • Y: Require the executable SQL statements for rolling back the data change.
  • N: Do not require the 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 of calculating the number of rows in which data will be affected. The value must be an integer.
Before a data change is executed, the system calculates the number of rows in which data will be affected. The calculation will take a long time if the data volume is large. To guarantee that the data change can be properly executed, you can specify a timeout period accurate to seconds for the calculation. The calculation stops when the time it takes exceeds the specified timeout period.
Data Change reason classification The type of a data change.
The value must be a JSON string. For more information, see Appendix: Types of data changes.
How data changes are performed The method of executing a data change after the corresponding ticket is approved. Valid values:
  • COMMITOR: The data change is executed by the user who submits the ticket.
  • AUTO: The data change is automatically executed.
  • LAST_AUDITOR: The data change is executed 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: Allow a DBA or DMS administrator to approve or reject a ticket if its previous approval node, such as a data owner for the target resource, fails to perform the operation.
  • N: Allow a DBA or DMS administrator to approve or reject a ticket only after its previous approval node approves or rejects the ticket.
Default value: Y.
Allow OWNER to authorize users Specifies whether a data owner for an instance, a database, or a table is allowed to grant permissions on the resource to other users. Valid values:
  • Y: Allow a data owner for a resource to grant permissions on the resource to other users.
  • N: Do not allow a data owner for a resource to grant permissions on the resource to other users.
Maximum number of queries for the day The maximum number of queries allowed per day. The value must be an integer.
When the number of queries sent within a day reaches the specified upper limit, no more queries are allowed on that day. This configuration item applies to all users of DMS.
Day query rows upper limit The maximum number of queried data rows that can be returned per day. The value must be an integer.
When the number of data rows returned within a day reaches the specified upper limit, no more queries are allowed on that day. This configuration item applies to all users of DMS.
DMS locale: ZH/EN/JA/ZT The language of the operational logs returned by DMS. Valid values:
  • ZH: simplified Chinese.
  • EN: English.
  • JA: Japanese.
  • ZT: traditional Chinese.

Procedure

  1. Log on to the DMS console.
  2. In the top navigation bar, choose System Management > Configuration.
  3. On the Configuration page that appears, find the target configuration item and click Change in the Actions column.

For more information about the configuration items, see Configuration items.

  1. In the Change Parameter Configuration dialog box that appears, specify a value as required.
  2. Click Confirm Change.

Appendix: Types of data changes

  • The system provides the following default types of data changes, in the format of JSON strings:
  1. [{"key":"config_correct","value":"Modify Config"},
  2. {"key":"project_init_data","value":"Init Project Data"},
  3. {"key":"program_bug","value":"Program Bug"},
  4. {"key":"require_deal_without_backend_function","value":"Requirements Without Backend Function"},
  5. {"key":"history_data_clear","value":"History Data Clean"},
  6. {"key":"test","value":"Test"},
  7. {"key":"mis_operation","value":"Mis Operation"},
  8. {"key":"others","value":"Others"}]

The following table describes the default types of data changes.

key value Description
config_correct Modify Config To change configurations.
project_init_data Init Project Data To initialize the data for a project.
program_bug Program Bug To clear a program error.
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 clean historical data.
test Test To run a test.
mis_operation Mis Operation To restore data due to a misoperation.
others Others Others.