Analyzing the Scan Report
Viewing the Scan Report
- Click Software Porting Assessment from the navigation pane on the left. Historical reports are listed.
- In the historical report list, click the report name of the analysis task. The report details page is displayed, as shown in Figure 1.
The analysis reports are named by the report generation time.
Analyzing the Scan Result
The following uses the scan result of the Spark 2.3.0 .tar package as an example. Table 1 lists the dependencies to be ported and handling suggestions.
|
No. |
Dependency File |
Path |
Handling Suggestion |
|---|---|---|---|
|
1 |
spark-2.3.0-yarn-shuffle.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/yarn/spark-2.3.0-yarn-shuffle.jar |
Verify whether the package is compatible with the Kunpeng platform. If not, obtain a compatible version from the vendor or obtain the source code and compile a version that is compatible with the Kunpeng platform. |
|
2 |
leveldbjni-all-1.8.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/jars/leveldbjni-all-1.8.jar |
The .jar package is supported by the Kunpeng platform. You can click Download shown in Figure 1 to replace the package. |
|
3 |
scala-compiler-2.11.8.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/jars/scala-compiler-2.11.8.jar |
|
|
4 |
netty-all-4.1.17.Final.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/jars/netty-all-4.1.17.Final.jar |
|
|
5 |
commons-crypto-1.0.0.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/jars/commons-crypto-1.0.0.jar |
|
|
6 |
jline-2.12.1.jar |
/package/spark-2.3.0-bin-hadoop2.7.tar/spark-2.3.0-bin-hadoop2.7/jars/jline-2.12.1.jar |
- After downloading the JAR package supported by the Kunpeng platform, you need to check whether the name of the software package is the same as that of the software package to be replaced. If the software package name is the same, use the downloaded software package. If the software package name is changed, modify the package name in the configuration files in the RPM or DEB package.
- If the software package is not compatible with the Kunpeng platform and there is no substitute available, you need to compile the software package before the porting.
- For details about how to manage the reports, see Porting Advisor Feature Guide.