Migrating the Source Package Only

Prerequisites

• You have logged in to the Kunpeng DevKit.
• The source component package to be migrated has been prepared.

Procedure

1. Click System Migration in the navigation tree on the left and then click to go to the New Project tab page.
   Figure 1 Basic Settings
   
2. Set Migration Project Name. A project name is automatically generated by default, which can be changed if needed.

   The name must meet the following requirements:

   • Can contain only letters, digits, and underscores (_).
   • 1 to 64 characters.
3. Select Source package migration only for Migration Scenario.
4. Select Source Code Porting services, which include SQL migration and configuration migration.
   • SQL migration: Extract SQL statements and associated statements from the source code, annotations, and Mybatis, assess SQL compatibility and convert SQL statements, and generate patches.
   • Configuration migration: Scan the configuration file for configuration items such as paths and drivers. Modify configuration items based on the suggestions.
5. Set Obtain Source Package to either of the following options:
   

   • Upload source package: The supported source package formats are tar, tar.bz, tar.bz2, tar.gz, tar.xz, tbz, tbz2, tgz, txz, and zip. You can upload multiple source packages at the same time. Each of the source packages must be less than or equal to 2048 MB.
   • For Dockerfile and Docker Compose files, the tool identifies the statements that do not support the Arm architecture and provides modification suggestions. For details about the file matching rules, see Dockerfile and Docker Compose Trustlist and Replacement List.
   • The tool detects the drivers, dependencies, Druid, and JPA configurations in the source code, and provides Quick Fix suggestions.
   • Upload source packages
     Figure 2 Upload source packages
     

     Click Upload and drag the source packages to the upload area. Alternatively, you can click Add File to select source packages and click Upload.

   • Obtain from node server
     Figure 3 Obtain from node server
     
     1. Set Migration Project Node. You can search for nodes by their IP addresses or names. If a node is not included on the list, you can click Add Node to add it for the migration project. For details, see Managing Agent.
        

        When migrating a source package, you can manually add a local node (that is, the current DevKit node) as a migration project node.

     2. Configure Paths to Scan. Scan source files in specified paths on the remote node. You can configure the node and file paths as needed.

        Click Add Path and enter the path to the source package to be scanned. To scan an SQL source package, you are advised to configure the data definition language (DDL) file. For details about how to obtain the DDL file, see Exporting a DDL File.

6. Complete the advanced settings for a more smooth migration.
   Figure 4 Advanced Settings
   

   Table 1 Advanced settings

   Parameter	Description
   Migration Source Database	Select the source database to improve the accuracy of migrating source code SQL statements. NOTE: During migration from MySQL to Vastbase, if Vastbase-transform.jar is not deployed in the current environment, you need to configure the related download information. SQL statement compatibility assessment and conversion will not be performed.
   Migration Target Database	Select the target database to improve the accuracy of migrating source code SQL statements.
   Origin of Tool Package	Where the tool package comes. Download from URL: Vastbase-transform.jar is automatically downloaded from the Kunpeng mirror site to the DevKit node. Upload tool package: Copy the tool package download link in the information below and obtain Vastbase-transform.jar.
   Upload Tool Package	Click Upload to upload the downloaded Vastbase-transform.jar. NOTE: This parameter is displayed when Origin of Tool Package is set to Upload tool package.
   DDL	You are advised to configure a DDL for each of the SQL source packages to be scanned. A DDL file records complete information about database tables and fields. DDL statements can improve the accuracy of SQL statement parsing. For details about how to obtain a DDL file, see Exporting a DDL File. NOTE: This parameter is displayed when Obtain Source Package is set to Upload source package.
   Migration Target Middleware Type	N/A BES migration strategy: The uploaded source package contains the built-in Tomcat configuration files and you need to migrate to the built-in BES files. TongTech migration strategy: The uploaded source package contains the built-in Tomcat configuration files and you need to migrate to the built-in TongTech files.

7. Click Start Migration.