Connect Kingdee K/3 WISE 15.0 or 15.1 to ApsaraDB RDS for SQL Server to run distributed transactions between your Elastic Compute Service (ECS) instance and RDS instance. This lets you migrate enterprise accounting workloads to the cloud while maintaining transactional consistency and isolation.
The connection process has three phases:
Restore data to the RDS instance — Upload a full backup of your Kingdee K/3 WISE set of books to an Object Storage Service (OSS) bucket, then restore it to the RDS instance.
Enable distributed transactions — Configure the RDS instance, ECS instance, and Windows operating system to open the required ports and establish hostname resolution, so that Microsoft Distributed Transaction Coordinator (MSDTC) can coordinate transactions across both machines.
Install the accounting data management tool and configure the database — Install the Kingdee K/3 WISE-compatible tool and connect it to the RDS instance endpoint.
Prerequisites
Before you begin, make sure that you have:
Completed a full backup of the Kingdee K/3 WISE set of books you want to migrate
A Windows ECS instance (this guide uses Windows Server 2016). For setup instructions, see Step 1. Create an ECS instance
An ApsaraDB RDS for SQL Server instance in the same region and virtual private cloud (VPC) as the ECS instance. For setup instructions, see VPCs and vSwitches and Create an instance
The RDS instance must meet all of the following requirements:
SQL Server edition: SQL Server 2022 EE (Always On), SQL Server 2019 EE (Always On), SQL Server 2017 EE (Always On), SQL Server 2016 EE, SQL Server 2012 EE, SQL Server 2022 SE, SQL Server 2019 SE, SQL Server 2017 SE, SQL Server 2016 SE, SQL Server 2012 SE, or SQL Server 2008 R2 with cloud disks
Instance family: General-purpose or dedicated. Shared instances are not supported
Billing method: Subscription or pay-as-you-go. Serverless instances are not supported
Restore data to the RDS instance
Step 1: Upload a full backup file to an OSS bucket
Log on to the OSS console.
In the left-side navigation pane, click Buckets, then click Create Bucket.
Configure the following parameters, keep all other parameters at their defaults, and click OK.
For more information about bucket creation, see Create buckets.
Parameter
Value
Bucket Name
Enter a name for the bucket.
Region
Select the same region as your ECS instance and RDS instance.
Storage Class
IA
Redundancy Type
LRS
ACL
Private
Versioning
Off
Encryption Method
None
Real-time Log Query
Not Activated
In the left-side navigation pane, click Buckets, then click the bucket you just created.
Choose Object Management > Objects, then click Upload Object.
Drag the full backup file to the Files to Upload area, or click Select Files and choose the file.
For more information, see Upload objects.

Step 2: Create a privileged account for the RDS instance
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region of your RDS instance, then click the instance ID.
In the left-side navigation pane, click Accounts.
Click Create Account and configure the following parameters.
Parameter
Description
Database Account
Enter an account name: up to 50 characters, using lowercase letters, digits, and underscores (_). Must start with a lowercase letter and end with a lowercase letter or digit.
Account Type
Select Privileged Account. For permission details, see Account permissions in an ApsaraDB RDS for SQL Server instance.
New Password
8–32 characters, containing at least three of: uppercase letters, lowercase letters, digits, and special characters (
! @ # $ % ^ & * ( ) _ + - =).Confirm Password
Re-enter the password.
Description
(Optional) Enter a description to identify the account.
Click OK.
Step 3: Restore the full backup file to the RDS instance
The AliyunServiceRoleForDBS service-linked role is created automatically the first time you use the backup feature of ApsaraDB RDS. For more information, see How do I create a service-linked role for Data Disaster Recovery?Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region of your RDS instance, then click the instance ID.
In the left-side navigation pane, click Backup and Restoration, then click Migrate OSS Backup Data to RDS.
If the button is not visible, check that your RDS instance meets the SQL Server edition and instance family requirements listed in Prerequisites.
Click Next twice to reach the Import Data step.
Configure the following parameters.
If this is your first time migrating backup data from OSS to ApsaraDB RDS, you will be prompted to authorize access. Click Authorize, then Confirm Authorization Policy.
Parameter
Description
Database Name
Enter the name for the destination database on the RDS instance.
OSS Bucket
Select the OSS bucket that contains the full backup file.
OSS File
Select the backup file. Enter a prefix in the search box and click the search icon to find it. The list shows each file's name, size, and update time.
Cloud Migration Method
Select Immediate Access (Full Backup).
Consistency Check Mode
Select Synchronous DBCC.

Click OK and wait for the import to complete. To check progress, click Databases in the left-side navigation pane and verify the status of the destination database.
Enable distributed transactions
Step 1: Configure the RDS instance
Configure a whitelist
Add the ECS instance's IP address to the RDS instance whitelist so that the ECS instance can connect to the RDS instance.
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region of your RDS instance, then click the instance ID.
In the left-side navigation pane, click Whitelist and SecGroup.
On the Whitelist Settings tab, click Modify next to the
defaultwhitelist and add the ECS instance's IP address.- If the ECS instance and RDS instance are in the same VPC, enter the private IP address of the ECS instance. - If they are in different VPCs, enter the public IP address of the ECS instance and apply for a public endpoint for the RDS instance. For more information, see Apply for or release a public endpoint. - To find the ECS instance's IP addresses, go to the Instance Details page of the ECS instance. For more information, see View IP addresses.

Click OK.
Configure a distributed transaction whitelist
Add the ECS instance to the distributed transaction whitelist so that the RDS instance recognizes it as a trusted participant in distributed transactions.
In the left-side navigation pane, click Data Security, then click the Distributed Transaction Whitelist tab.
Click Create Whitelist and configure the following parameters.
Parameter
Description
Whitelist Name
2–32 characters, using digits, lowercase letters, and underscores (_). Must start with a lowercase letter and end with a lowercase letter or digit.
IP Addresses
Enter one entry per line in the format
<ECS IP address>,<Windows computer name>. For example:192.168.1.100,k3ecstest. To find the computer name, open Control Panel and choose System and Security > System.Click OK.
Step 2: Configure the ECS instance
Open the ports that MSDTC requires on the ECS instance's security group. You need two inbound rules: one for the Remote Procedure Call (RPC) endpoint mapper (port 135) and one for the dynamic RPC port range (1024–65535).
Log on to the ECS console.
Choose Instances & Images > Instances.
In the top navigation bar, select the region of the ECS instance.
Click the ECS instance ID.
Click Security Groups in the top navigation bar.
Find the security group and click Manage Rules in the Actions column.
On the Inbound tab, click Add Rule and configure the following parameters for the first rule.
Parameter
Value
Action
Allow
Priority
1
Protocol Type
Custom TCP
Port Range
135
Source
The two IP addresses shown under Data Security > Distributed Transaction Whitelist in the RDS console. You can also call the DescribeDBInstanceIpHostname API operation to retrieve them.
Description
Enter a description (2–256 characters, cannot start with
http://orhttps://).
Click Save.
Add a second inbound rule with the same parameters, but set Port Range to 1024/65535.
Step 3: Configure the Windows operating system
Configure the ECS instance's Windows operating system to allow MSDTC to resolve the RDS instance by hostname and to participate in distributed transactions.
Log on to the ECS instance (this guide uses Windows Server 2016).
Open the hosts file at
C:\Windows\System32\drivers\etc\hosts.At the end of the file, add the internal IP address and hostname of the ECS instance on which the RDS instance runs. Find this information on the Distributed Transaction Whitelist tab under Data Security in the ApsaraDB RDS console.
You can also call the DescribeDBInstanceIpHostname API operation to retrieve the internal IP address and hostname.


Save the hosts file.
Open Control Panel, choose System and Security > Administrative Tools, then double-click Component Services.
Navigate to Component Services > Computer > My Computer > Distributed Transaction Coordinator.
Right-click Local DTC and select Properties.
Click the Security tab and configure the DTC security settings.

Click OK. When the MSDTC Service dialog appears, click Yes and wait for the MSDTC service to restart.
Install the accounting data management tool and configure the database
Log on to the ECS instance.
Download the accounting data management tool for your Kingdee K/3 WISE version:
Only versions 15.0 and 15.1 are supported. Use the tool that matches your installed version.
Extract the package and copy all files to the Kingdee K/3 WISE installation directory:
K3ERP\KDSYSTEM\KDCOM.Open Kingdee K/3 WISE. In the dialog that appears, configure the identity verification settings and set the data server to the internal endpoint of the RDS instance. For more information, see View and change the endpoints and port numbers.
Configure the preset connection.
Register the set of books.
Select the target database and click All.
Log on to Kingdee K/3 WISE
After completing all the steps, log on to Kingdee K/3 WISE. Distributed transactions between the ECS instance and RDS instance are now enabled, providing transactional consistency and isolation for your accounting data.