Service system migration processing method and system for localization transformation

Abstract

The invention provides a business system migration processing method and system for localization transformation, and belongs to the technical field of data processing, and the method specifically comprises the steps: carrying out the migration processing of different business systems according to a migration processing sequence to obtain a processing result, and combining the call data of the different business systems after the migration processing to obtain a processing result; when it is determined that the running state after migration processing meets the requirement, calling data of different service systems after migration processing are obtained, migration test depths of the different service systems are determined through the calling data, and the calling similar situation of the service system to be migrated and the service system after migration is completed is obtained; and whether the service data of the service system to be migrated needs to be backed up or not is determined in combination with the migration test depths of different service systems, so that the reliability of migration processing is improved.

Description

Technical Field

[0001] The present invention belongs to the field of data processing technology, and in particular relates to a business system migration processing method and system for domestic transformation. Background Art

[0002] With the localization transformation of hardware systems, energy and power companies are facing an increasing demand for information system migration and transformation. However, at the same time, various problems are inevitable in the process of migration and transformation. In serious cases, it may even cause disruption to the operation of the original information system, and even lead to the loss of historical data of the information system and other abnormal situations.

[0003] In response to the above technical problems, the present invention provides a business system migration processing method and system for localization transformation. Summary of the invention

[0004] To achieve the purpose of the present invention, the present invention adopts the following technical solutions: According to one aspect of the present invention, a business system migration processing method for localization transformation is provided.

[0005] A business system migration processing method for localization transformation, specifically comprising: S1 determines the historical call data of different business systems based on the data processing conditions of different business systems, and determines the migration processing order of different business systems based on the data volume of the business systems; S2 performs migration processing of different business systems according to the migration processing sequence to obtain processing results, and combines the call data of different business systems after the migration processing to determine that the running status after the migration processing meets the requirements, and then proceeds to the next step; S3 obtains call data of different business systems after the migration process, and uses the call data to determine the migration test depth of different business systems; S4 obtains the call similarity between the business system to be migrated and the business system after the migration is completed, and determines whether the business data of the business system to be migrated needs to be backed up based on the migration test depth of different business systems.

[0006] The beneficial effects of the present invention are: Whether the running status after the migration process meets the requirements is determined based on the processing results of the migration process of different business systems and the call data after the migration process. This not only takes into account the impact of the abnormal situation of the processing results of the business system after the migration process on the abnormal situation of the running status after the migration process, but also takes into account the difference in the test depth of different business systems caused by the call data of the business system after the migration process. It realizes accurate evaluation of whether the running status after the migration process meets the requirements from multiple angles, and also lays the foundation for determining differentiated backup processing strategies for business data to be migrated.

[0007] Whether the business data of the business system to be migrated needs to be backed up is determined based on the similarity of calls between the business system to be migrated and the business system after migration, and the depth of migration test. This takes into account both the difference in test depth of the information system after localization transformation caused by the migration test depth of the business system after migration, and the similarity of calls between the business system to be migrated and the business system after migration. This reduces the need for unnecessary memory space for alternative processing, and also realizes the backup of business data of the business system to be migrated that is at risk of data loss.

[0008] A further technical solution is that the historical call data of the business system includes the historical call times of the business system and the call durations of different historical call times.

[0009] A further technical solution is that the data volume of the business system is determined based on the analysis results of the storage data of the business system on the server.

[0010] A further technical solution is that the method for determining the migration processing order of the business system is: Determine the historical call times of the business system based on the historical call data of the business system, and determine the abnormal impact coefficient of the business system based on the historical call times; Determining a data loss risk factor of the business system based on the data volume of the business system; The call processing priority value of the business system is determined according to the abnormal impact coefficient and the call frequency coefficient of the business system, and the migration processing order of the business system is determined based on the call processing priority value.

[0011] A further technical solution is that the abnormal impact coefficient of the business system is determined according to the product of the historical call times and a preset proportional coefficient.

[0012] A further technical solution is that the call processing priority value of the business system is determined according to an average value of a data loss risk coefficient and a call frequency coefficient of the business system.

[0013] A further technical solution is to determine whether the business data of the business system to be migrated needs to be backed up, which specifically includes: Based on the similarity of calls between the business system to be migrated and the business system after migration, determine the similarity of call modules of different business functions between the business system to be migrated and the business system after migration, and determine the similarity coefficient between the business system to be migrated and the business system after migration according to the similarity of call modules of different business functions; Determine the weight coefficients of different business systems based on the similarity coefficients, and determine the correction test depth of the business system to be migrated in combination with the migration test depths of different migrated business systems; Whether the business data of the business system to be migrated needs to be backed up is determined according to the correction test depth of the business system to be migrated.

[0014] A further technical solution is to determine whether the business data of the business system to be migrated needs to be backed up according to the correction test depth of the business system to be migrated, which specifically includes: When the correction test depth of the business system to be migrated is greater than the preset test depth, it is determined that the business data of the business system to be migrated does not need to be backed up.

[0015] In a second aspect, the present invention provides a computer system comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the above-mentioned business system migration processing method for domestic transformation when running the computer program.

[0016] Other features and advantages will be described in the following description, and partly become apparent from the description, or understood by practicing the invention. The purpose and other advantages of the invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0017] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0019] Figure 1 It is a flow chart of a business system migration processing method for localization transformation; Figure 2 It is a flow chart of a method for determining a migration processing sequence of a business system; Figure 3 It is a flow chart to determine whether the operation status after the migration process meets the requirements; Figure 4 It is a flowchart of a method for determining the migration test depth of a business system. DETAILED DESCRIPTION

[0020] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present invention will be comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar structures, and thus their detailed description will be omitted.

[0021] The terms "a", "an", "the", and "said" are used to indicate the presence of one or more elements / components / etc.; the terms "comprising" and "having" are used to express an open-ended inclusive meaning and mean that additional elements / components / etc. may be present in addition to the listed elements / components / etc.

[0022] Example 1 To solve the above problems, according to one aspect of the present invention, Figure 1 According to one aspect of the present invention, a method for migrating a business system for localization transformation is provided, which specifically includes: S1 determines the historical call data of different business systems based on the data processing conditions of different business systems, and determines the migration processing order of different business systems based on the data volume of the business systems; S2 performs migration processing of different business systems according to the migration processing sequence to obtain processing results, and combines the call data of different business systems after the migration processing to determine that the running status after the migration processing meets the requirements, and then proceeds to the next step; S3 obtains call data of different business systems after the migration process, and uses the call data to determine the migration test depth of different business systems; S4 obtains the call similarity between the business system to be migrated and the business system after the migration is completed, and determines whether the business data of the business system to be migrated needs to be backed up based on the migration test depth of different business systems.

[0023] Furthermore, the historical call data of the business system includes the historical call times of the business system and the call durations of different historical call times.

[0024] Specifically, the data volume of the business system is determined according to the analysis result of the storage data of the business system on the server.

[0025] Specifically, Figure 2 As shown, the method for determining the migration processing order of the business system is: Determine the historical call times of the business system based on the historical call data of the business system, and determine the abnormal impact coefficient of the business system based on the historical call times; Determining a data loss risk factor of the business system based on the data volume of the business system; The call processing priority value of the business system is determined according to the abnormal impact coefficient and the call frequency coefficient of the business system, and the migration processing order of the business system is determined based on the call processing priority value.

[0026] Optionally, the abnormal impact coefficient of the business system is determined according to the product of the historical call times and a preset proportional coefficient.

[0027] It should be noted that the call processing priority value of the business system is determined according to the average value of the data loss risk coefficient and the call frequency coefficient of the business system.

[0028] Further, determining the migration processing order of the business system based on the call processing priority value specifically includes: The migration processing order of different business systems is determined based on the call processing priority values ​​of different business systems from large to small.

[0029] Optionally, the method for determining the migration processing order of the business system is: The data volume of the business system is obtained. When the data volume of the business system is greater than a preset data volume: The migration processing priority of the business system is set as the first priority, and the migration processing order of the business system is determined according to the data volume of the business system; When the data volume of the business system is not greater than the preset data volume: When the data volume of the business system is within the preset data volume range: The historical call times of the business system are determined based on the historical call data of the business system. When the historical call times of the business system are greater than the preset call times: Determine historical calling users of the business system by using historical calling data of the business system, and when the number of historical calling users of the business system does not meet the requirement, use the migration processing priority of the business system as the second priority, and determine the migration processing order of the business system according to the number of historical calling users; When the number of historical callers of the business system meets the requirement: The migration processing priority of the business system is taken as the third priority, the user call frequency coefficients of different historical call users are determined by using the historical call times of different historical call times and the call durations of different historical call times, and the call frequency coefficients of the business system are determined according to the user call frequency coefficients of different historical call users, and the migration processing order of the business system is determined according to the call frequency coefficients of the business system; When the data volume of the business system is not within the preset data volume range or the historical call times of the business system is not greater than the preset call times: Determine the historical call times of the business system based on the historical call data of the business system, and determine the abnormal impact coefficient of the business system based on the historical call times; Determining a data loss risk factor of the business system based on the data volume of the business system; The migration processing priority of the business system is taken as the fourth priority, the call processing priority value of the business system is determined according to the abnormal impact coefficient and the call frequency coefficient of the business system, and the migration processing order of the business system is determined based on the call processing priority value.

[0030] Furthermore, the processing result includes the number of occurrences of different types of compatibility anomalies corresponding to the business system.

[0031] Specifically, Figure 3 As shown in the figure, it is determined that the running status after the migration process meets the requirements, including: Determine the call times of different business systems based on the call data of different business systems after the migration process, and determine the trusted business systems among the business systems based on the call times; Determining the number of occurrences of compatibility anomalies of the trusted business system according to the processing result of the trusted business system; By averaging the number of occurrences of compatibility anomalies in different trusted business systems, it is determined whether the operating status after the migration process meets the requirements.

[0032] Furthermore, the trusted business system is a business system whose call times are greater than a preset call times.

[0033] It should also be noted that when the average number of occurrences of compatibility anomalies of different trusted business systems is not within a preset number range, it is determined that the operating status after the migration process does not meet the requirements.

[0034] Furthermore, when the running status after the migration process does not meet the requirements, it is determined that the business data of the business system to be migrated needs to be backed up.

[0035] Optionally, determine whether the running status after the migration process meets the requirements, including: S21, according to the processing result of the business system, determining the number of occurrences of the compatibility anomaly problem of the business system, and determining the compatibility anomaly coefficients of different business systems by using the number of occurrences of the compatibility anomaly problems of different business systems; S22 determines the call times of different business systems based on the call data of different business systems after the migration process, and determines the call weight coefficients of different business systems based on the call times of different calling users; S23 determines a comprehensive abnormality coefficient through the compatibility abnormality coefficients and call weight coefficients of different business systems, and uses the comprehensive abnormality coefficient to determine whether the operating status after the migration process meets the requirements.

[0036] Specifically, the comprehensive abnormality coefficient is determined according to the sum of compatibility abnormality coefficients of different business systems and call weight coefficients.

[0037] It should also be noted that when the comprehensive abnormality coefficient is greater than a preset abnormality coefficient threshold, it is determined that the operating state after the migration process does not meet the requirements.

[0038] Optionally, the above step S21 includes the following contents: S211 determines the number of occurrences of the compatibility anomaly problem of the business system according to the processing result of the business system. When the total number of occurrences of the compatibility anomaly problems of different business systems does not meet the requirement, it is determined that the running state after the migration processing does not meet the requirement. When the total number of occurrences of the compatibility anomaly problems of different business systems meets the requirement, the process proceeds to step S212; S212 obtains business systems with compatibility anomalies. When the proportion of business systems with compatibility anomalies is less than the preset proportion, the process proceeds to step S213. When the proportion of business systems with compatibility anomalies is not less than the preset proportion, the process proceeds to step S2124. S213 determines the compatibility anomaly coefficients of different business systems according to the number of occurrences of compatibility anomaly problems of different business systems. If there is a business system whose compatibility anomaly coefficient does not meet the requirements, the process proceeds to step S214. If there is no business system whose compatibility anomaly coefficient does not meet the requirements, it is determined that the running state after the migration process does not meet the requirements. S214: When the number of business systems whose compatibility anomaly coefficients do not meet the requirements is greater than the preset number of business systems, it is determined that the operation status after the migration process does not meet the requirements; when the number of business systems whose compatibility anomaly coefficients do not meet the requirements is not greater than the preset number of business systems, the process proceeds to step S215; S215 determines the compatibility coefficient abnormal value based on the compatibility coefficient of the business system whose different compatibility coefficient abnormal value does not meet the requirements. When the compatibility coefficient abnormal value does not meet the requirements, it is determined that the operating state after the migration processing does not meet the requirements. When the compatibility coefficient abnormal value meets the requirements, it goes to step S22.

[0039] Optionally, the above step S22 includes the following contents: S221 determines the call times of different business systems based on the call data of different business systems after the migration process, and determines the trusted business systems in the business systems based on the call times. When the total number of occurrences of the compatibility anomaly problems of the trusted business systems does not meet the requirement, the process proceeds to step S222. When the total number of occurrences of the compatibility anomaly problems of the trusted business systems meets the requirement, the process proceeds to step S223. S222: obtaining the number of trusted business systems with compatibility anomalies. When the number of trusted business systems with compatibility anomalies does not meet the requirement, determining that the running state after the migration process does not meet the requirement. When the number of trusted business systems with compatibility anomalies meets the requirement, proceeding to step S223. S223 determines the call weight coefficients of different business systems according to the number of calls by different calling users, and determines the corrected exception coefficients of different business systems in combination with the compatibility exception coefficients of different business systems. When the corrected exception coefficients do not meet the requirements and the number of business systems does not meet the requirements, it is determined that the operating status after the migration process does not meet the requirements. When the corrected exception coefficients do not meet the requirements and the number of business systems meets the requirements, proceed to step S23.

[0040] Specifically, Figure 4 As shown, the method for determining the migration test depth of the business system is: Determine the number of calling users of the business system after the migration process based on the calling data of different business systems after the migration process; Determine the calling times of different calling users and the calling durations of different calling times according to the calling data of the calling users after the migration processing of the business system, and determine the calling test depths of different calling users by using the calling times of different calling users and the calling durations of different calling times; The migration test depth of the business system is determined based on the call test depths of different calling users.

[0041] Further, the migration test depth of the business system has a value range of 0 to 1, wherein the greater the migration test depth of the business system, the higher the migration test depth of the business system.

[0042] Optionally, determining whether the business data of the business system to be migrated needs to be backed up specifically includes: Based on the similarity of calls between the business system to be migrated and the business system after migration, determine the similarity of call modules of different business functions between the business system to be migrated and the business system after migration, and determine the similarity coefficient between the business system to be migrated and the business system after migration according to the similarity of call modules of different business functions; Determine the weight coefficients of different business systems based on the similarity coefficients, and determine the correction test depth of the business system to be migrated in combination with the migration test depths of different migrated business systems; Whether the business data of the business system to be migrated needs to be backed up is determined according to the correction test depth of the business system to be migrated.

[0043] Further, determining whether the business data of the business system to be migrated needs to be backed up according to the correction test depth of the business system to be migrated specifically includes: When the correction test depth of the business system to be migrated is greater than the preset test depth, it is determined that the business data of the business system to be migrated does not need to be backed up.

[0044] In another embodiment, determining whether the business data of the business system to be migrated needs to be backed up specifically includes: Based on the similarity of calls between the business system to be migrated and the business system after migration, determine the similarity of call modules of different business functions between the business system to be migrated and the business system after migration, and determine the similarity coefficient between the business system to be migrated and the business system after migration according to the similarity of call modules of different business functions; When it is determined by using the similarity coefficient that the business system to be migrated does not have a similar business system after the migration is completed: It is determined that the business data of the business system to be migrated needs to be backed up; When the business system to be migrated has a similar business system that has been migrated: A migrated business system similar to the business system to be migrated is regarded as a similar business system, and when there is a similar business system whose number of occurrences of compatibility anomalies does not meet the requirement, it is determined that the business data of the business system to be migrated needs to be backed up; When there are no similar business systems where the number of occurrences of compatibility anomalies does not meet the requirements: Determine the abnormality coefficient of the compatibility abnormality problem of the similar business system according to the number of occurrences of the compatibility abnormality problem of different similar business systems; when the abnormality coefficient of the compatibility abnormality problem of the similar business system does not meet the requirement, determine that the business data of the business system to be migrated needs to be backed up; When the anomaly coefficient of the compatibility anomaly problem of the similar business system meets the requirements: Determine the weight coefficients of different business systems based on the similarity coefficients, and determine the correction test depth of the business system to be migrated in combination with the migration test depths of different migrated business systems; The backup requirement coefficient of the business system to be migrated is determined based on the correction test depth of the business system to be migrated and the abnormality coefficient of the compatibility abnormality problem of the similar business system, and the backup requirement coefficient is used to determine whether the business data of the business system to be migrated needs to be backed up.

[0045] Example 2 In a second aspect, the present invention provides a computer system comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the above-mentioned business system migration processing method for domestic transformation when running the computer program.

[0046] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0047] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0048] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A method for migrating a business system for localization transformation, characterized in that: Specifically include: Determine the historical call data of different business systems based on the data processing conditions of different business systems, and determine the migration processing sequence of different business systems based on the data volume of the business systems; Perform migration processing of different business systems in the migration processing sequence to obtain processing results, and combine the call data of different business systems after the migration processing to determine that the running status after the migration processing meets the requirements, and then proceed to the next step; Obtaining call data of different business systems after migration processing, and using the call data to determine the migration test depth of different business systems; Obtain the call similarity between the business system to be migrated and the business system after the migration is completed, and determine whether the business data of the business system to be migrated needs to be backed up based on the migration test depth of different business systems.

2. The method for migrating a business system for localization transformation according to claim 1, characterized in that: The historical call data of the business system includes the historical call times of the business system and the call durations of different historical call times.

3. The method for migrating a business system for localization transformation according to claim 1, characterized in that: The data volume of the business system is determined based on the analysis results of the storage data of the business system on the server.

4. The method for migrating a business system for localization transformation according to claim 1, characterized in that: The method for determining the migration processing order of the business system is: Determine the historical call times of the business system based on the historical call data of the business system, and determine the abnormal impact coefficient of the business system based on the historical call times; Determining a data loss risk factor of the business system based on the data volume of the business system; The call processing priority value of the business system is determined according to the abnormal impact coefficient and the call frequency coefficient of the business system, and the migration processing order of the business system is determined based on the call processing priority value.

5. The method for migrating a business system for localization transformation according to claim 4, characterized in that: The abnormal impact coefficient of the business system is determined according to the product of the historical call times and a preset proportional coefficient.

6. The method for migrating a business system for localization transformation according to claim 4, characterized in that: Determining the migration processing order of the business system based on the call processing priority value specifically includes: The migration processing order of different business systems is determined based on the call processing priority values ​​of different business systems from large to small.

7. The method for migrating a business system for localization transformation according to claim 1, characterized in that: The method for determining the migration test depth of the business system is: Determine the number of calling users of the business system after the migration process based on the calling data of different business systems after the migration process; Determine the calling times of different calling users and the calling durations of different calling times according to the calling data of the calling users after the migration processing of the business system, and determine the calling test depths of different calling users by using the calling times of different calling users and the calling durations of different calling times; The migration test depth of the business system is determined based on the call test depths of different calling users.

8. The method for migrating a business system for localization transformation according to claim 7, characterized in that: The migration test depth of the business system ranges from 0 to 1, wherein the greater the migration test depth of the business system, the higher the migration test depth of the business system.

9. A computer system comprising: A memory and a processor connected in communication, and a computer program stored in the memory and capable of running on the processor, characterized in that when the processor runs the computer program, a business system migration processing method for localization transformation as described in any one of claims 1-8 is executed.

Images