System Migration Functions

The System Migration tool collects information about installed software including software packages, middleware, and databases in an application system, and analyzes the dependency compatibility in the POM file of a Maven project.

This tool supports three types of installation packages: the standalone System Migration packages (.tar.gz and .rpm) and the full DevKit package.

The standalone System Migration packages provide a lightweight tool installation. If you only need to use the System Migration function, you can choose a standalone package to prevent unnecessary components from occupying resources.
The full DevKit tool package not only contains the System Migration function, but also provides the Porting Advisor, Affinity Analyzer, and System Profiler. If you need to use other functions, choose the full installation package.

Prerequisites

You have installed the System Migration tool. For details, see Installing the Tool.
If you have installed the tool using a compressed package, decompress the package and switch to the tool directory. Then run the command in ./ mode on Linux, for example, ./devkit sys-mig -v. If you have installed the tool using an RPM package, run devkit sys-mig -v. This section uses an RPM package as an example.

Command Function

Displays the help information about System Migration tasks.

Syntax

Linux:
1
devkit sys-mig -h

Windows:
1
sys-mig.exe -h
Before running the command, go to the directory where sys-mig.exe is stored after decompressing the software package.

Example

The following uses the Linux environment as an example. Run the following command to query the parameter descriptions of all commands:

1	devkit sys-mig -h

Use the -c option to specify the information collection mode. For details, see Table 1.

**Table 1** Information collection modes
Mode	Description
stmt	stmt (statement) collects ledger information. It scans the system to collect information such as the node IP address, node name, current platform, data volume, number of servers, memory, system architecture, middleware, database type, service OS, and development language. It generates a CSV report. Ledger Information Collection Functions provides examples.
sbom	sbom (software bill of materials) collects component information. It scans all subdirectories or files in the target directory, parses the initial software component information, and determines the compatibility with the Kunpeng platform. The information includes the software component name, type, version, vendor, quantity, size, architecture type, standard, source, and checkout path. It generates an HTML or JSON report. System Component Information Collection Functions provides examples.
mvn_analyse	It analyzes the source code porting of a Maven project to generate an HTML report. Maven Project Source Code Porting Analysis Functions provides examples.

By default, the application information listed in Table 2 can be collected. You can also use Scan Rule File Usage Example to extend the application information.

**Table 2** Software that can be detected
Category	Software Name
JDK	Oracle JDK IBM JDK OpenJDK
Middleware	Tomcat Nginx WebLogic TongWeb BES Kafka Apusic WebSphere Elasticsearch Filebeat Nacos RabbitMQ SeatServer ZooKeeper Redis Apollo K8s MinIO ActiveMQ Kibana Logstash RocketMQ Apache Spark Memcached Python Apache HTTP Server Docker Consul
Database	MySQL Oracle Dameng GaussDB Vastbase G100 MongoDB PostgreSQL SQL Server DB2 IIS 10.0 GoldenDB KingbaseES

Parent topic: System Migration