System data migration method and device

Abstract

The invention belongs to the technical field of nuclear power, and particularly relates to a system data migration method and device. According to the system data migration method provided by the invention, aiming at two sets of PDM systems which are deployed in different environments, different in deployment architecture design and different in function, the problems that database design and historical data of the two sets of PDM systems are inconsistent, massive documents / CAD files processed by an algorithm are stored, the data structure is complex, multiple data bottom layer incidence relations exist, and deep coupling exists can be solved; data of the two PDM systems are rapidly and accurately migrated, and functions of the two PDM systems are combined. Therefore, file transmission is realized in a system deployment environment with strict limitation, and functions of two sets of systems with huge difference are combined quickly and accurately.

Description

Technical Field

[0001] The present invention belongs to the technical field of nuclear power, and in particular relates to a system data migration method and device. Background Art

[0002] PDM (Product Data Management) is used to manage all product-related information, including component information, configuration, documents, CAD / CAE / CAM files, structural information, permissions, etc.) and all product-related process information (including process definition and management). The PDM system is a type of industrial software platform software with complex data structure relationships. As an enterprise core system that carries the core design process of the model and manages the core design data of the model, it includes core functions such as data modeling and data management, unified data source, and maintaining data continuity. It plays a core supporting role in the construction of the enterprise's digital R&D system.

[0003] In the process of enterprise product updates or information system upgrades, it is usually necessary to migrate the functions and data of one PDM system to another PDM system, and the different functions of the two PDM systems need to be retained. Due to the complex design of the PDM system database, diverse data types, multiple underlying data relationships and deep coupling, extremely complex logic, and each system has historical data containing a large amount of entity data, how to improve the quality and efficiency of PDM system data migration has become an urgent problem to be solved. Summary of the invention

[0004] In order to overcome the problems existing in the related art, a system data migration method and device are provided.

[0005] According to one aspect of an embodiment of the present disclosure, a system data migration method is provided, the method comprising:

[0006] Step 10: Log in to the first system using an administrator account on any accessible terminal of the first system, and create target business data which is initially empty;

[0007] Step 11, use the SSH tool on the bastion host that can access the first system to remotely connect to the first system, switch to the MQL command environment on the bastion host after the connection, use the MQL command to call the Spinner tool to classify and store the data in the database of the first system into a specified folder in the first system, and bind it with the target business data; use the SSH tool to obtain the entity data of the first system and store it in a specified folder in the first system;

[0008] Step 12, log in to the first system with an administrator account on any network terminal that can access the first system and open the target business data, use the download function of the first system to download the data in the designated folder to the network terminal, and the network terminal can export the file to the Internet;

[0009] Step 13, according to the preset data categories, obtain data from the database of the second system and store them by category; obtain entity data of the second system;

[0010] Step 14, for each data category, compare the data in the first system database with the data in the second system database, delete, adjust or overwrite different data, and merge the entity data in the first system and the second system to form an integrated migration file.

[0011] In a possible implementation, the method also includes: step 15, writing a unified configuration modification script, a unified personnel import script, a file library import script, a file isolation rule configuration script, and a JPO compilation script for the integrated migration file, and storing them in a new empty storage medium after passing the inspection, and physically incorporating them into the first system hard disk group.

[0012] In a possible implementation, the method further includes: step 16, using a bastion host capable of accessing the first system to remotely connect to the first system server backend through SSH, and installing two sets of system difference software packages by controlling the imported migration data through SSH commands;

[0013] Step 17, using SSH commands in the bastion host to replace the first system database and entity data;

[0014] Step 18: Start MQL through SSH command in the bastion host, enable the super administrator command window in MQL, and use commands in conjunction with the Spinner tool to deploy the underlying management objects of the database;

[0015] Step 19, execute the unified configuration modification script, unified personnel import script, file library import script, file isolation rule configuration script, and JPO compilation script. If there are no errors in the script program after execution, exit MQL, restart all services in the first system, and perform the final test.

[0016] In a possible implementation, step 11 includes: step 110, remotely connecting to the first system through an SSH tool on a bastion host that can access the first system, and using SSH instructions to aggregate system files scattered throughout the first system into the designated folder;

[0017] Step 111, in the bastion host, using the SSH tool to use the MQL command to call the Spinner tool on the first system, and classify the data in the database of the first system into the designated folder according to the preset data category, and use the built-in file check-in command of MQL to bind the data in the designated folder with the target business data;

[0018] In a possible implementation, in step 111, the Spinner tool is called using the MQL command to abstractly classify the business data and management data in the database, and sort out the following: data type - type, management policy - policy, management menu - menu, management button - command, custom code - JPO, management attribute - attribute, management relationship - relationship, file library - Store, classification repository - vault, business data - businessobject, dynamic configuration - config, form - form, license - license, page framework - portal, page subframe - channel, transaction control - transaction, user - user, role - role, index - index, person instance - person, table - table file.

[0019] In a possible implementation, step 14 includes: using a folder and code comparison analysis tool to compare the data of the first system database with the data of the second system database for each data category;

[0020] If the data of the first system differs from the data of the second system only in the code file, the difference file is directly overwritten into the corresponding data of the first system. This method is suitable for the second system to have simple functions that are purely newly added compared to the first system and is not affected by the unique functions of the first system.

[0021] If there is a difference between the function codes of the first system and the second system, and the proportion of logical impact is less than the preset threshold, the difference code is modified in the first system data for the logical business and an overwriting operation is performed;

[0022] If there are differences in the function codes of the first system and the second system, and the proportion of logical impact exceeds the preset threshold, it means that the content control business functions of the two systems are highly overlapping, and the two systems have unique business requirements. In this case, based on the business needs of the first and second systems, current user needs and data statistics scripts, the code is redesigned to perform overwriting operations in the first system data.

[0023] In a possible implementation, step 14 also includes: deduplicating and merging the Store containers of the entity data of the first system and the second system, adding new environment configuration information and storage paths to form a new Store container, merging the entity data of the first system and the second system to form new entity data, and binding the new Store container to the new entity data.

[0024] According to another aspect of an embodiment of the present disclosure, a system data migration device is provided, the device comprising:

[0025] The first module is used to log in to the first system using an administrator account on any accessible terminal of the first system and create target business data which is initially empty;

[0026] The second module is used to use the SSH tool on the bastion host that can access the first system to remotely connect to the first system, switch to the MQL command environment on the bastion host after the connection, use the MQL command to call the Spinner tool to classify and store the data in the database of the first system into a specified folder in the first system, and bind it with the target business data; use the SSH tool to obtain the entity data of the first system and store it in a specified folder in the first system;

[0027] The third module is used to log in to the first system through an administrator account on any network terminal that can access the first system and open the target business data, and use the download function of the first system to download the data in the specified folder to the network terminal, and the network terminal can export the file to the Internet;

[0028] The fourth module is used to obtain data from the database of the second system and store it in categories according to preset data categories; obtain entity data of the second system;

[0029] The fifth module is used to compare the data of the first system and the second system database for each data category, delete, adjust or overwrite different data, and merge the entity data of the first system and the second system to form an integrated migration file.

[0030] According to another aspect of an embodiment of the present disclosure, a system data migration device is provided, the device comprising:

[0031] processor;

[0032] a memory for storing processor-executable instructions;

[0033] Wherein, the processor is configured to execute the above method.

[0034] According to another aspect of an embodiment of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, and the computer program instructions implement the above method when executed by a processor.

[0035] The beneficial effects of the present disclosure are as follows: the system data migration method provided by the present disclosure can overcome the problems of inconsistent database design, historical data, storage of massive documents / CAD files processed by algorithms, complex data structure, multiple underlying data associations and deep coupling, etc. for two PDM systems deployed in different environments, with different deployment architecture designs and different functions, and can quickly and accurately migrate the data of the two PDM systems and merge the functions of the two. In this way, file transfer can be achieved in a system deployment environment with strict restrictions, and the functions of the two systems with huge differences can be quickly and accurately merged. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a schematic diagram of a system data migration method shown in the present disclosure.

[0037] Figure 2 It is a block diagram of a system data migration device shown in the present disclosure. DETAILED DESCRIPTION

[0038] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0039] Figure 1 Schematic diagram of a system data migration method shown in the present disclosure. The method can be executed by a terminal device, wherein the terminal device can be a server or a desktop computer, etc. The embodiment of the present disclosure does not limit the type of the terminal device.

[0040] See also Figure 1 In the present disclosure, both the first system and the second system are PDM systems. The data export of the first system needs to go through a preset approval process. When the functions and data of the second system need to be migrated and merged into the first system, the following steps are adopted.

[0041] Step 10, use an administrator account to log in to the first system on any accessible terminal of the first system (for example, any http / hhtps accessible terminal of the first system), and after entering the first system, create initially empty target business data, which acts as a "bridge".

[0042] Step 11, use the SSH tool on the bastion host that can access the first system to remotely connect to the first system, switch to the MQL command environment on the bastion host after the connection, use the MQL command to call the Spinner tool to classify the data in the database of the first system and store it in a specified folder in the first system, and bind it with the target business data; use the SSH tool to obtain the entity data of the first system and store it in a specified folder in the first system.

[0043] As an example of this embodiment, step 11 may include: step 110, remotely connecting to the first system through the SSH tool on the bastion host that can access the first system, and using SSH instructions to aggregate system files scattered throughout the first system into the designated folder, wherein the system files may include application software packages, source code, configuration files (deployment configuration, service startup configuration, file isolation configuration, etc.), license files, key logs, deployment records, etc.

[0044] Step 111, in the bastion host, the SSH tool is used to use the MQL command to call the Spinner tool on the first system and classify the data in the database of the first system into the designated folder according to the preset data category, and the file check-in command built into the MQL is used to bind the data in the designated folder with the target business data. The folders corresponding to each data category can also be compressed and exported in pieces to improve the transmission speed.

[0045] In one possible implementation, the data in the database may include: PDM system support objects and business objects. PDM system support objects include personnel, roles, organizations, authority rules, life cycles, attributes, business types, etc.; business objects can be represented as objects generated by business activities, such as projects, tasks, processes, plans, parts, drawings, documents, meetings, etc.

[0046] In the related art, the MQL instruction itself can extract data such as permissions, roles, life cycles, business types, etc., but the extracted raw data is almost unreadable. The present disclosure uses the Spinner tool to expand the function of MQL. The two are used together to extract data, so that the extracted data format becomes easy to understand, standardized, and easy to modify and merge. Special management objects: PDM system support objects, such as personnel, roles, organizations, permission rules, life cycles, attributes, business types, etc.; business objects: objects generated by business activities, such as projects, tasks, processes, plans, parts, drawings, documents, meetings, etc.

[0047] For example, the MQL command is used to call the Spinner tool to abstractly classify the business data and management data in the database, and sort out the following files: data type - type, management strategy - policy, management menu - menu, management button - command, custom code - JPO, management attribute - attribute, management relationship - relationship, file library - Store, classification repository - vault, business data - businessobject, dynamic configuration - config, form - form, license - license, page framework - portal, page sub-frame - channel, transaction control - transaction, user - user, role - role, index - index, personnel instance - person, table - table and other files.

[0048] Examples of MQL built-in extraction commands are as follows:

[0049]

set context user creator;

[0050] [exec program emxExtractSchema.tcl program CNPROG_*;],

[0051] [exec program emxExtractSchema.tcl program CNPROG_*;],

[0052] [exec program emxExtractSchema.tcl webform CNPROG_*;],

[0053] [exec program emxExtractSchema.tcl command CNPROG_*;],

[0054] [exec program emxExtractSchema.tcl policy CNPROG_*;],

[0055] [exec program emxExtractSchema.tcl table CNPROG_*;],

[0056] [exec program emxExtractSchema.tcl channel CNPROG_*;],

[0057]

exec program emxExtractSchema.tcl portal CNPROG_*;

[0058]

exec program emxExtractSchema.tcl trigger CNPROG_*;

[0059]

exec program emxExtractSchema.tcl rule CNPROG_*;

[0060]

exec program emxExtractSchema.tcl Store CNPROG_*;

[0061]

exec program emxExtractSchema.tcl transaction CNPROG_*;

[0062]

exec program emxExtractSchema.tcl user CNPROG_*;

[0063]

exec program emxExtractSchema.tcl connection CNPROG_*;

[0064]

exec program emxExtractSchema.tcl format CNPROG_*;

[0065]

exec program emxExtractSchema.tcl person CNPROG_*;

[0066]

exec program emxExtractSchema.tcl relationship CNPROG_*;

[0067]

exec program emxExtractSchema.tcl typa CNPROG_*;

[0068]

exec program emxExtractSchema.tcl attribute CNPROG_*;

[0069] [exec program emxExtractSchema.tcl context CNPROG_*;],

[0070]

exec program emxExtractSchema.tcl group CNPROG_*;

[0071] An example of an MQL file check-in command is as follows:

[0072]

checkin businessobj objid filedir / tmp / XXX;

[0073] Step 12, log in to the first system with an administrator account on any network terminal that can access the first system and open the target business data, use the download function of the first system to download the data in the designated folder to the network terminal, and the network terminal can export the file to the Internet.

[0074] Step 13: According to preset data categories, data files are obtained from the database of the second system and stored in categories; and entity data of the second system is obtained.

[0075] Step 14, for each data category, compare the data in the first system database with the data in the second system database, delete, adjust or overwrite different data, and merge the entity data in the first system and the second system to form an integrated migration file.

[0076] As an example of this embodiment, step 14 may include: using a folder and code comparison analysis tool to compare the data of the first system database with the data of the second system database for each data category.

[0077] If the data of the first system differs from the data of the second system only in the code file, the difference file will be directly overwritten into the corresponding data of the first system. This method is suitable for simple functions that are purely newly added to the second system compared to the first system and is not affected by the unique functions of the first system.

[0078] If there is a difference between the function codes of the first system and the second system, and the proportion of logical impact is less than a preset threshold, the difference code is modified for the logical business and an overwriting operation is performed in the first system data.

[0079] If there are differences in the function codes of the first system and the second system, and the proportion of logical impact exceeds the preset threshold, it means that the content control business functions of the two systems are highly overlapping, and the two systems have unique business requirements. In this case, based on the business needs of the first and second systems, current user needs and data statistics scripts, the code is redesigned to perform overwriting operations in the first system data.

[0080] As an example of this embodiment, step 14 may also include: deduplicating and merging the Store containers of the entity data of the first system and the second system, adding new environment configuration information and storage paths to form a new Store container, merging the entity data of the first system and the second system to form new entity data, and binding the new Store container to the new entity data.

[0081] CAD and other physical data are attachments uploaded and generated in the PDM system. After being processed by the algorithm, they are directly stored in the hard disk, not in the database, and belong to the scope of data migration. The Store container is a special management object in the PDM system, which can be used to manage CAD, ordinary drawings, word, pdf, excel and other physical data.

[0082] Since physical data such as CAD has been processed by specific algorithm encoding, it is unreadable and unparseable during the migration process. After using the method disclosed in the present invention, the abstractly classified Store container is bound to the file library such as CAD. Only the Store container file needs to be modified to merge the files. The Store container is readable, parseable, easy to operate, and easy to merge. If this method is not used, thousands (hundreds of thousands or even millions) of database data will have to be merged manually. After using this solution, the data is converted into a Spinner format file, the data is classified and archived, and the format is readable and easy to process. Only the files that need to be merged need to be operated, and the efficiency and accuracy are significantly improved.

[0083] In a possible implementation, the method further includes: step 15, writing a configuration unified modification script, a personnel unified import script, a file library import script, a file isolation rule configuration script, a JPO compilation script, etc. for the integrated migration file, and then directly storing these contents in a brand new empty storage medium after checking them with professional management software, and directly physically merging them into the first system hard disk group, so as to realize risk-free and ultra-high-speed import of migration data.

[0084] In a possible implementation, the method also includes: Step 16: Use a bastion host that can access the first system to perform SSH remote connection to the first system server backend, and use SSH commands to control the imported migration data to install two sets of system difference software packages (signature service software packages, etc.). This step completes the preparation of the basic hardware and software environment of the first system.

[0085] Step 17, use SSH commands in the bastion host to replace the first system database and jsp, xml, js, properties, and CAD format files. This step completes the migration of the first system's basic data, basic operating programs, and a large number of documents and CAD files.

[0086] Step 18, start MQL through SSH command in the bastion host, enable the super administrator command window in MQL, and use the command to deploy the database underlying management objects in combination with the Spinner tool:

[0087] The following is an example of a deployment command:

[0088]

set context user creator;

[0089] [tcl;cd / tmp / deployfolder / XXX exit],

[0090] [exec program emxSpinnerAgent.tcl force update;],

[0091]

compile program PROG_XXX*force

[0092] Step 19, execute the unified configuration modification script, unified personnel import script, file library import script, file isolation rule configuration script, JPO compilation script, etc. If there is no error in the script after execution, exit MQL, restart all services in the first system, and perform the final test.

[0093] The following are examples of executing commands:

[0094]

run person.mql;

[0095] [run jpo.mql;]

[0096] [run config.mql;]

[0097]

run sign.mql;

[0098] The present invention discloses a technical means of directly operating the server to upload data to the business database through a special method, and the client directly accesses the business system to download data, thereby achieving the technical effect of data transmission between different deployment environments.

[0099] Through MQL+Spinner, we abstract, classify and integrate the structured objects in the database, bind CAD and other entity data with Store objects, and then use technical means such as file comparison, code analysis, and demand redevelopment and design to achieve the technical effect of migrating business functions and data between different PDM systems with conflicting functions and complex data structures.

[0100] The description of the above-mentioned device has been explained in detail in the description of the above-mentioned method, and will not be repeated here.

[0101] Figure 2 1900 is a block diagram of a system data migration device shown in the present disclosure. For example, the device 1900 can be provided as a server. Figure 2 , the apparatus 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions, such as an application, that can be executed by the processing component 1922. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above method.

[0102] The device 1900 may also include a power supply component 1926 configured to perform power management of the device 1900, a wired or wireless network interface 1950 configured to connect the device 1900 to a network, and an input / output (I / O) interface 1958. The device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, MacOS X™, Unix™, Linux™, FreeBSD™, or the like.

[0103] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions, which can be executed by the processing component 1922 of the device 1900 to perform the above method.

[0104] The present disclosure may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0105] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.

[0106] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0107] The computer program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0108] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0109] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0110] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0111] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.

[0112] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A system data migration method, characterized in that: The method comprises: Step 10: Log in to the first system using an administrator account on any accessible terminal of the first system, and create target business data which is initially empty; Step 11, use the SSH tool on the bastion host that can access the first system to remotely connect to the first system, switch to the MQL command environment on the bastion host after the connection, use the MQL command to call the Spinner tool to classify and store the data in the database of the first system into a specified folder in the first system, and bind it with the target business data; use the SSH tool to obtain the entity data of the first system and store it in a specified folder in the first system; Step 12, log in to the first system with an administrator account on any network terminal that can access the first system and open the target business data, use the download function of the first system to download the data in the designated folder to the network terminal, and the network terminal can export the file to the Internet; Step 13, according to the preset data categories, obtain data from the database of the second system and store them by category; obtain entity data of the second system; Step 14, for each data category, compare the data in the first system database with the data in the second system database, delete, adjust or overwrite different data, and merge the entity data in the first system and the second system to form an integrated migration file.

2. The method according to claim 1, characterized in that: The method also includes: step 15, writing a unified configuration modification script, a unified personnel import script, a file library import script, a file isolation rule configuration script, and a JPO compilation script for the integrated migration file, storing them in a new empty storage medium after passing the inspection, and physically incorporating them into the first system hard disk group.

3. The method according to claim 1, characterized in that The method further includes: step 16, using a bastion host capable of accessing the first system to remotely connect to the first system server backend through SSH, and installing two sets of system difference software packages by controlling the imported migration data through SSH commands; Step 17, replace the first system database and entity data through SSH commands in the bastion host; Step 18: Start MQL through SSH command in the bastion host, enable the super administrator command window in MQL, and use commands in conjunction with the Spinner tool to deploy the underlying management objects of the database; Step 19, execute the unified configuration modification script, unified personnel import script, file library import script, file isolation rule configuration script, and JPO compilation script. If there are no errors in the script program after execution, exit MQL, restart all services in the first system, and perform the final test.

4. The method according to claim 1, characterized in that: Step 11 includes: step 110, remotely connecting to the first system through an SSH tool on a bastion host that can access the first system, and using SSH instructions to aggregate system files scattered throughout the first system into the designated folder; Step 111, in the bastion host, the SSH tool is used to use the MQL command to call the Spinner tool on the first system and the data in the database of the first system is classified into the designated folder according to the preset data category, and the file check-in command built into the MQL is used to bind the data in the designated folder with the target business data.

5. The method according to claim 4, characterized in that In step 111, the Spinner tool is called using the MQL command to abstractly classify the business data and management data in the database, and sort out the following: data type - type, management strategy - policy, management menu - menu, management button - command, custom code - JPO, management attribute - attribute, management relationship - relationship, file library - Store, classification repository - vault, business data - businessobject, dynamic configuration - config, form - form, license - license, page framework - portal, page subframe - channel, transaction control - transaction, user - user, role - role, index - index, person instance - person, table - table file.

6. The method according to claim 1, characterized in that Step 14 includes: using a folder and code comparison analysis tool to compare the data of the first system database with the data of the second system database for each data category; If the data of the first system differs from the data of the second system only in the code file, the difference file is directly overwritten into the corresponding data of the first system. This method is suitable for the second system to have simple functions that are purely newly added compared to the first system and is not affected by the unique functions of the first system. If there is a difference between the function codes of the first system and the second system, and the proportion of logical impact is less than the preset threshold, the difference code is modified in the first system data for the logical business and an overwriting operation is performed; If there are differences in the function codes of the first system and the second system, and the proportion of logical impact exceeds the preset threshold, it means that the content control business functions of the two systems are highly overlapping, and the two systems have unique business requirements. In this case, based on the business needs of the first and second systems, current user needs and data statistics scripts, the code is redesigned to perform overwriting operations in the first system data.

7. The method according to claim 1, characterized in that Step 14 also includes: deduplicating and merging the Store containers of the entity data of the first system and the second system, adding new environment configuration information and storage path to form a new Store container, merging the entity data of the first system and the second system to form new entity data, and binding the new Store container to the new entity data.

8. A system data migration device, characterized in that: The device comprises: The first module is used to log in to the first system using an administrator account on any accessible terminal of the first system and create target business data which is initially empty; The second module is used to use the SSH tool on the bastion host that can access the first system to remotely connect to the first system, switch to the MQL command environment on the bastion host after the connection, use the MQL command to call the Spinner tool to classify and store the data in the database of the first system into a specified folder in the first system, and bind it with the target business data; use the SSH tool to obtain the entity data of the first system and store it in a specified folder in the first system; The third module is used to log in to the first system through an administrator account on any network terminal that can access the first system and open the target business data, and use the download function of the first system to download the data in the specified folder to the network terminal, and the network terminal can export the file to the Internet; The fourth module is used to obtain data from the database of the second system and store it in categories according to preset data categories; obtain entity data of the second system; The fifth module is used to compare the data of the first system and the second system database for each data category, delete, adjust or overwrite different data, and merge the entity data of the first system and the second system to form an integrated migration file.

9. A system data migration device, characterized in that: The device comprises: processor; a memory for storing processor-executable instructions; The processor is configured to execute the method according to any one of claims 1 to 7.

10. A non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images