Porting with Source Code

You can view a migration report on the migration result page and perform necessary operations as instructed to verify or complete the migration.

You can drag the sliding frame on the left of the Guidance Suggestion area to adjust the area size. You can also click a file in the file list on the navigation pane to quickly locate the first suggestion.
Click View Details. The number of suggestions (excluding compatible SQL statements and modified system content) contained in the file is displayed in the list on the left of the Guidance Suggestion area.
On the upper part of the Migration Result page, you can click New Project to return to the New Project page, where you can modify the information of the components to be migrated and restart the migration.
The button indicates that the data in the column supports search, and you can click the button to search for data. The button indicates that the data in the column supports filtering, and you can click the button to filter data. The button indicates that the data in the column supports sorting, and you can click the button to sort data in ascending or descending order. The button indicates the columns presented in the table, and you can click the button to set what columns to display.

Prerequisites

You have logged in to the Kunpeng DevKit.
You have created a system migration project and completed the migration.

Migration Report

Go to the Migration Result page and view the migration report. If SQL statements exist, the Download Non-Source-Code SQL File button is displayed. You can click this button to download the file.

Figure 1 Migration Report

**Table 1** Parameters in the migration report
Parameter	Description
Source Component Name	Name of the migrated source component.
Source Node	Source node of the component. Filtering is supported.
Target Node	Target node for the component. Filtering is supported.
Component Belonging	Ownership of a component. Filtering is supported.
Origin of Source Component	Where the component comes.
Target Component Name	Name of the target component.
Status	Migration status of the component, which is Migrated, To be migrated, or Masked.
Guidance	Click View Details to view the guidance details.
Status Source	Where the component comes. It is hidden by default and you can click to display it. It defaults to a migration handled by the tool. If you want to modify the component status, the status source will change to Customized.
Remarks	Supplementary information.
Updated	Time when the migration status is displayed. It is hidden by default and you can click to display it.
Operation	You can modify the migration status and add remarks.

Click View Details in the Guidance column, and you will see the guidance details on the right.
- Migrated: Verify system functions based on the verification method provided in Guidance Suggestion. The following uses a migration from Tomcat to TongWeb as an example.
  Figure 2 Guidance Suggestion
- To be migrated: Perform a manual migration and verify system functions based on Guidance Suggestion. The following uses a Nginx migration as an example.
  Figure 3 Guidance Suggestion
  
  You can click Edit and Remigrate under the guidance suggestion to return to the New Project page, edit the component information, and click Restart to retry the migration.
- Java application migration: Java application packages can be automatically converted to JAR packages that can run on the Kunpeng platform.
  Figure 4 Java application conversion
  - For dependencies that fail to be replaced, run a script to obtain related dependencies or required files according to Migration Guide.
    1. Click script for downloading dependency files, decompress the downloaded package, and run the script.
```
sh dependency_download.sh
```
      See the following example. If the information in bold is displayed, the dependency has been successfully downloaded:
```
Start downloading: DmDialect-for-hibernate5.6-8.1.3.140.jar
Start downloading: DmJdbcDriver18-8.1.3.140.jar
Download failed: 
DmDialect-for-hibernate5.6-8.1.3.140.jar       100%[====================================================================================================>]  49.62K   203KB/s    in 0.2s    
Downloaded: DmDialect-for-hibernate5.6-8.1.3.140.jar
DmJdbcDriver18-8.1.3.140.jar                   100%[====================================================================================================>]   1.31M  92.7KB/s    in 8.3s    
Downloaded: DmJdbcDriver18-8.1.3.140.jar
All files have been downloaded.
```
      The script execution requires Internet connection. For details, refer to Configuring a Proxy for Wget.
      
      After the download is successful, a download folder that stores the dependencies is generated in the same directory as the script.
    2. For architecture-related dependencies, replace the dependencies that fail to be converted one by one using replacement package paths. For database-related dependencies, refer to the handling suggestions.
    3. Use the prepared test cases to check whether the application is successfully migrated in the Kunpeng environment.
  - For the dependencies that are successfully replaced, perform operations based on the migration guide. These dependencies can be rolled back when needed. After the rollback, in the case of architecture-related dependencies, the converted software package is replaced by the original software package; in the case of database-related dependencies, dependency files added to the application package are deleted.
After the migration is complete, you can close the right sliding frame. Click Edit in the Operation column, select a state from the drop-down list, and click Save.

You can select multiple components and click Batch Edit to edit the selected components at the same time. Click OK to save the modification.
You can click Source Code Porting in the lower left corner of the page to port the source code.

Parent topic: Viewing the Migration Result