Single object migration configuration method applied to pharmaceutical enterprise data

Abstract

The invention relates to the technical field of data migration configuration, and discloses a single-object migration configuration method applied to pharmaceutical enterprise data, which comprises the following steps of: 1, importing a project needing to be configured into a first environment, and modifying the content of the project in the first environment; 2, creating an outbound configuration package for the modified configuration content, adding related components needing to be exported into the outbound configuration package, and generating an outbound configuration file; in the second step, dependency and related data of the components added into the outbound configuration packet are added into the outbound configuration packet; 3, importing the outbound configuration file generated in the step 2 into a verification environment for verification; and 4, auditing the outbound configuration file which passes verification in the step 3, and deploying the related components configured in the outbound configuration file to a second environment after the auditing is passed. The method has the advantages of being high in migration efficiency and good in migration configuration environment adaptation degree.

Description

Technical Field

[0001] The present invention relates to the technical field of data migration configuration, and in particular to a single object migration configuration method applied to pharmaceutical enterprise data. Background Art

[0002] The production process of pharmaceutical companies usually involves the development and implementation of multiple projects. When these projects are implemented for the first time or when the business logic of existing projects needs to be adjusted, it is usually necessary to configure the parameters and other information of these projects. In order to avoid the modification and adjustment of the configuration information of the project during the project configuration process, causing the existing running projects to affect or interfere with the normal operation of other projects, it is usually necessary to adjust the configuration of the project in a specific configuration environment, and after the adjusted configuration is tested and verified, the configuration content will be updated in the actual production environment. In order to ensure that the content of the project configuration can be synchronized between the actual production environment and the configuration environment, and to ensure data consistency and security, it is usually necessary to synchronize the configuration content in different environments through configuration migration.

[0003] For example, the patent document with publication number CN117459389A discloses a configuration migration method, device, computer equipment and storage medium. The method includes: a message conversion step, which performs message conversion of the old decision system; a migration step, which creates a decision version of the new decision system through the content after message conversion; a comparison step, which uses the input of the old decision system as the input of the new decision system to obtain the execution result of the new decision system, and compares the execution result of the new decision system with the execution result of the old decision system; a verification step, which performs business empty run and grayscale verification on the new decision system that passes the comparison in the comparison step, and puts the new decision system that passes the business empty run and grayscale verification online. Accidents caused by human errors can be avoided by designing the migration status and operation during the decision migration process.

[0004] Although the above technical solution can realize the migration of decision-making configurations and avoid accidents caused by mistakes during the migration process; however, during the configuration migration process, some functions after the project configuration usually have historical data. When these configurations are migrated to the actual production environment, in order to ensure that these functions after the configuration can be normally enabled and run, it is usually necessary to synchronize these historical data when the configuration is performed; when migrating the configuration, the above technical solution only migrates the decision content of the project, resulting in some historical data in the configuration cannot be synchronized migration, resulting in some functions after the project configuration cannot be enabled or run normally in the new environment after the project configuration is migrated. Summary of the invention

[0005] The present invention aims to provide a single-object migration configuration method applied to pharmaceutical enterprise data to solve the technical problems in the prior art that some historical data in the configuration cannot be migrated synchronously, and some functions after project configuration cannot be enabled or run normally in the new environment.

[0006] To achieve the above object, the present invention adopts the following technical solution: a single object migration configuration method applied to pharmaceutical enterprise data, comprising the following steps: Step 1: Import the project to be configured into the first environment, and modify the project content in the first environment; Step 2: Create an outbound configuration package with the modified configuration content, add the relevant components that need to be exported to the outbound configuration package and generate an outbound configuration file; In step 2, a component list of the project configuration content is also generated, and the component list is used to display all component information of the configuration and dependency information of each component; when adding a component to the outbound configuration package, the dependency of the component added to the outbound configuration package is added to the outbound configuration package according to the dependency information in the component list; The outbound configuration package also includes a data set, which is used to store data information required by the components in the outbound configuration package for synchronous migration; Step 3: Import the outbound configuration file generated in step 2 into the verification environment for verification; Step 4: Review the outbound configuration file that has passed the verification in step 3, and deploy the relevant components configured in the outbound configuration file to the second environment after the review is passed.

[0007] In this solution, when migrating the project configuration, the component information of the components that need to be migrated is displayed in the form of a list, so that when migrating the outbound configuration package of the configuration migration, the dependent content of the components that need to be migrated can be migrated synchronously, ensuring the integrity of the content contained in the outbound configuration package, avoiding the lack of necessary dependent content in the components in the configured outbound configuration package, resulting in some components not being able to run normally after being migrated to the target environment. In addition, the data sets required by each component are added to the outbound configuration package, so that after the migration of each component, the historical data required for the operation of the component can be migrated together, ensuring the consistency of the supporting data of the components when running in different environments, ensuring the uniformity of the operating effects of each component in different environments, avoiding different operating effects or non-operating due to different data in different environments, and increasing the difficulty of component configuration modification and debugging.

[0008] Preferably, as an improvement, in step 1, before importing the project into the first environment, the configuration of the first environment is also compared with the configuration of the second environment, and a comparison result of the configuration of the first environment and the configuration of the second environment is generated. This ensures that when configuring the project content, the consistency of the configuration of the test environment deployed by the project and the configuration of the production environment can be ensured, and that after the project is configured in the test environment, it can be directly migrated to the production environment for operation, avoiding the inconsistency between the configuration of the test environment configured by the project and the actual production environment, resulting in the project being unable to run correctly in the production environment after configuration in the test environment, thereby reducing the security of the actual production process.

[0009] Preferably, as an improvement, in step 2, when creating an outbound configuration package, the migration type of the outbound configuration package and the target environment information of the outbound configuration package are also configured. When configuring the outbound configuration package, the type and target environment of the outbound configuration package can be configured according to the purpose of the outbound configuration package, so that the created outbound configuration package can match the actual needs, and improve the matching degree between the created outbound configuration package and the environment after migration.

[0010] Preferably, as an improvement, in step 2, when adding the dependency to the outbound configuration package, a detection is performed to determine whether the second environment has the same information as the dependency, and a determination is made based on the detection information whether the dependency should be added to the outbound configuration package. While ensuring the integrity of the components and dependent components in the outbound configuration package, by comparing the dependent components with the components already existing in the target environment, repeated addition of dependent components to the outbound configuration package is avoided, which results in bloated content in the outbound configuration package and inconvenience in migrating projects between different environments. At the same time, after the target environment is migrated, component duplication is avoided, which affects the normal progress of project migration.

[0011] Preferably, as an improvement, in step 2, it is also used to configure the migration mode of each data in the data set, and in step 4, the data in the data set is deployed according to the content of the migration mode when the outbound configuration package is deployed. By configuring the migration mode of the migrated data set, the data content in the migrated data set can be updated in the target environment according to the actual situation of the migration environment and the specific content of the data, ensuring that the data in the data set can match the actual situation of the data set after migration, which is convenient for searching the data after migration; and during migration, the migration mode of different data sets is configured, so that the data can be updated in the target environment in a specified manner during the migration process, avoiding the need to reorganize the data in the target environment after migration, resulting in redundant data in the target environment after the configuration migration is completed, and increasing the difficulty of data management in the target environment.

[0012] Preferably, as an improvement, in step 4, when the outbound configuration file is deployed, the status information of each component can be checked, and the deployment order of each component can be adjusted or some steps can be removed. When the outbound configuration file is deployed, the components of the outbound configuration package can be adjusted during the deployment process according to the actual situation and needs, so as to avoid deployment errors of some components and affect the overall deployment efficiency.

[0013] Preferably, as an improvement, in step 4, after the outbound configuration file is deployed, a configuration comparison report before and after the deployment is completed is generated. This allows for easy viewing of the configuration differences before and after the environment is deployed, and facilitates the relevant staff to view the environment configuration information after the configuration is deployed, and facilitates the relevant staff to grasp the configuration content of the project in a timely manner after the project configuration is changed, and facilitates the later use and maintenance of the project after the configuration is modified.

[0014] Preferably, as an improvement, a verification status parameter is also provided in the outbound configuration file, and the verification status parameter is used to record the verification status in step 3, and step 4 performs an audit and deployment operation on the outbound configuration file according to the verification status parameter. This avoids the outbound configuration file being deployed without verification, ensures the compliance of the process when the outbound configuration file is deployed, and avoids the damage of the target environment caused by the unverified outbound configuration file after deployment, thereby improving the security of configuration migration. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a flowchart of a single-object migration configuration method for pharmaceutical company data in an embodiment of the present invention. DETAILED DESCRIPTION

[0016] The following is further described in detail through specific implementation methods: As attached Figure 1 As shown in the figure, the single object migration configuration method applied to pharmaceutical enterprise data includes the following steps: Step 1: Import the project to be configured into the first environment, and modify the business operations and related configurations in the first environment; specifically, when a new project is needed or the existing project content needs to be adjusted, the content of the project is synchronously deployed in the first environment, so that the project content can be configured and tested in an environment isolated from the second environment. The specific content of importing the project content into the first environment and configuring the project content in the first environment is prior art and will not be described in detail here. The first environment or the second environment is one of a test environment and a production environment. Preferably, in this embodiment, the first environment is a test environment and the second environment is a production environment.

[0017] Wherein in step 1, before importing the project into the first environment, the configuration of the first environment is also compared with the configuration of the second environment, and the configuration comparison result of the first environment and the second environment is generated. The relevant staff adjusts the configuration of the first environment or the second environment according to the configuration comparison result content of the two environments, wherein the comparison result content can be displayed in the form of a table, a document, etc., and the comparison result includes the name, configuration parameters, comparison information, and comparison time of each configuration information of the two environments. The specific content of the comparison between the configuration of the first environment and the configuration of the second environment is the prior art and will not be repeated here. When configuring the project content, it is possible to ensure the consistency of the configuration of the test environment deployed by the project with the configuration of the production environment, and ensure that the project can be directly migrated to the production environment for operation after the test environment is configured, so as to avoid the inconsistency between the configuration of the test environment configured by the project and the actual production environment, resulting in the project being unable to run correctly in the production environment after the configuration in the test environment is completed, thereby reducing the safety of the actual production process.

[0018] Step 2: Create an outbound configuration package with the modified configuration content, add the relevant components that need to be exported to the outbound configuration package, and then generate an outbound configuration file; specifically, when the modified configuration content needs to be exported, after the outbound configuration function is enabled in the first environment, an outbound configuration package is generated, and the configuration information, relevant data and component information related to the configuration content that needs to be exported are packaged and stored in the outbound configuration package. When all the configuration content that needs to be exported is imported into the outbound configuration, a compressed package file of the outbound configuration package is generated.

[0019] When creating an outbound configuration package, the parameters of the outbound configuration package are set, wherein the parameters of the outbound configuration package include the name, description, creation time, modification time, type of the outbound configuration package, and target environment of the outbound configuration package. The type parameters of the outbound configuration package include configuration migration and data migration, and the target environment includes the production environment, the verification environment, and the test environment. When configuring the outbound configuration package, the type and target environment of the outbound configuration package can be configured according to the purpose of the outbound configuration package, so that the created outbound configuration package can match the actual needs, and improve the matching degree between the created outbound configuration package and the environment after migration.

[0020] In the first environment, a component list of the project configuration content is also generated, and the component list displays all component information of the configuration content and component dependency information; in step 2, when adding components to the outbound configuration package, the component information and dependency information that need to be added to the outbound configuration package are checked according to the content in the component list. When adding components to the outbound configuration package, the dependency content of the components that need to be added to the outbound configuration package can be checked intuitively, ensuring the integrity of the component functions added to the outbound configuration package, and avoiding the lack of dependent components in the components added to the outbound configuration package, resulting in some components in the outbound configuration package being unable to operate normally after being migrated to the target environment, resulting in project migration failure.

[0021] When adding a component to an outbound configuration package, the dependent components of the component added to the outbound configuration package are also added to the outbound configuration package according to the dependent components in the component list. When adding a dependent component to the outbound configuration package, a check is performed to see whether there is a component identical to the dependent component in the target environment of the outbound configuration package. When there is no component identical to the dependent component in the target environment, the dependent component is added to the outbound configuration package; when there is a component identical to the dependent component in the target environment, the dependent component is marked, and relevant staff compare the contents of the components to determine whether to add the dependent component to the outbound configuration package to update the corresponding component in the target environment. While ensuring the integrity of the components and dependent components in the outbound configuration package, by comparing the dependent components with the components already existing in the target environment, repeated addition of dependent components in the outbound configuration package is avoided, which results in bloated content in the outbound configuration package and inconvenience in migrating projects between different environments. At the same time, it is avoided that after the target environment is migrated, components are repeated, which affects the normal progress of project migration.

[0022] The outbound configuration package also includes a data set, which is used to store the data information required by the components in the outbound configuration package for synchronous migration; when adding a data set to the outbound configuration package, the parameters of the data set are first set. The parameters of the data set include a data set name and object parameters. The name of the data set is used to distinguish the data set, and the object parameter is used to configure the data content in the data set, and the object parameter contains the specific data content corresponding to the object. The specific content of migrating data through the data set is the existing technology and will not be repeated here. When migrating the configuration, the data sets related to the migrated components are migrated synchronously to ensure that the migrated components can operate normally in different environments, avoiding the components from not operating normally due to the lack of some data information after migrating to the new environment, which increases the difficulty of configuration and debugging after the configuration migration.

[0023] When configuring the object parameters in the data set, the migration mode of each object is also configured. The object migration mode includes four migration modes: create, delete, update, and insert / update. The migration mode is used to update the data of each object in the data set in the environment after migration. The creation mode in the specific object migration mode is used to create the object data in the target environment; the deletion mode is used to delete the matching object data in the target environment, and no matching data will be processed; the update mode is used to update the matching object data in the target environment, and no matching data will be processed; the insert / update mode is used to create a new object if there is no object data in the target environment; if there is data, the existing data will be updated. By configuring the migration mode of the migrated data set, the data content in the migrated data set can be updated in the target environment according to the actual situation of the migration environment and the specific content of the data, ensuring that the data in the data set can match the actual situation of the data set after migration, which is convenient for searching the data after migration; and configuring the migration mode of different data sets during migration, so that the data can be updated in the target environment in a specified way during the migration process, avoiding the need to organize the data in the target environment after migration, resulting in data redundancy in the target environment after the configuration migration is completed, and increasing the difficulty of data management in the target environment.

[0024] Step 3. Import the outbound configuration file generated in step 2 into the verification environment, and verify the content in the outbound configuration file in the verification environment. Specifically, perform operation verification on the configuration content in the configuration file in the verification environment to ensure that the outbound content of the outbound configuration file can run normally, and avoid directly importing the modified configuration content into the production environment, causing the production environment to be affected by the configuration content, making it impossible for the production environment to perform production work normally, resulting in production losses.

[0025] Step 4: Review the outbound configuration file that has passed the verification in the verification environment in step 3, and deploy the relevant components configured in the outbound configuration file to the second environment after the review is passed; the specific content of configuring and deploying the outbound configuration file is the existing technology and will not be repeated here.

[0026] In step 4, when deploying the outbound configuration file, you can check the status of each component, adjust the deployment order of each component, or remove some steps. This allows you to adjust the components of the outbound configuration package during the deployment process according to actual conditions and needs, avoiding deployment errors of some components and affecting the overall deployment efficiency.

[0027] In step 4, after the outbound configuration file is deployed, a configuration comparison report of each component before and after the deployment is generated. This allows for easy viewing of the configuration differences before and after the environment is deployed, and facilitates relevant staff to view the environment configuration information after the deployment.

[0028] There is a verification status parameter in the outbound configuration file. When the outbound configuration file is verified in step 3, the verification status parameter changes to "verified". When the verification status parameter is in the "verified" state, the outbound configuration file is reviewed and deployed in step 4. Avoid deploying the outbound configuration file without verification, ensure the compliance of the process when the outbound configuration file is deployed, and avoid damage to the target environment caused by the unverified outbound configuration file after deployment, thereby improving the security of configuration migration.

[0029] In step 2 to step 4, it also includes authority control, which is used to configure the authority to modify the project content. Specifically in step 2, when configuring the project, the identity information of the operator in the project configuration process is verified. Only the operator with the project configuration authority can allow the project content to be configured, and in the configuration process, the modified content of each operator is recorded. In step 3 and step 4, when the outbound configuration package generated by the configured project is migrated and deployed, when the outbound configuration package of the project is verified, the identity of the person performing the relevant operation is verified. When the identity of the operator meets the authority control requirements, the operator is allowed to perform relevant operations on the outbound configuration package of the project, and the specific operation record of the operator is generated. The specific content of the authority control and the specific content of the identity verification of the operator are prior art, which will not be repeated here. When configuring the project, the integrity and reliability of the project content data can be guaranteed, and the project content is prevented from being tampered with by irrelevant personnel during the project migration configuration process, resulting in damage to the project data content, and the integrity and security of the project and data content in the production process of the pharmaceutical company are guaranteed.

[0030] Compared with the prior art, in this solution, when migrating the project configuration, the component information of the components that need to be migrated is displayed in the form of a list, so that when migrating the outbound configuration package of the configuration migration, the dependent contents of the components that need to be migrated can be migrated synchronously, ensuring the integrity of the contents contained in the outbound configuration package, avoiding the lack of necessary dependent contents in the components in the configured outbound configuration package, resulting in some components not being able to run normally after being migrated to the target environment. In addition, the data sets required by each component are added to the outbound configuration package, so that after the migration of each component, the historical data required for the operation of the component can be migrated together, ensuring the consistency of the supporting data of the components when running in different environments, ensuring the uniformity of the operating effects of each component in different environments, avoiding the different operating effects or non-operation of components due to different data in different environments, and increasing the difficulty of component configuration modification and debugging.

[0031] It should be pointed out that for those skilled in the art, several modifications and improvements can be made without departing from the technical solution of the present invention, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent. The protection scope required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. A single object migration configuration method applied to pharmaceutical enterprise data, characterized by: The following steps are involved: Step 1: Import the project to be configured into the first environment, and modify the project content in the first environment; Step 2: Create an outbound configuration package with the modified configuration content, add the relevant components that need to be exported to the outbound configuration package and generate an outbound configuration file; In step 2, a component list of the project configuration content is also generated, and the component list is used to display all component information of the configuration and dependency information of each component; when adding a component to the outbound configuration package, the dependency of the component added to the outbound configuration package is added to the outbound configuration package according to the dependency information in the component list; The outbound configuration package also includes a data set, which is used to store data information required by the components in the outbound configuration package for synchronous migration; Step 3: Import the outbound configuration file generated in step 2 into the verification environment for verification; Step 4: Review the outbound configuration file that has passed the verification in step 3, and deploy the relevant components configured in the outbound configuration file to the second environment after the review is passed.

2. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized by: In step 1, before importing the project into the first environment, the configuration of the first environment is compared with the configuration of the second environment, and a comparison result of the configuration of the first environment and the configuration of the second environment is generated.

3. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized in that: In step 2, when creating the outbound configuration package, the migration type of the outbound configuration package and the target environment information of the outbound configuration package are also configured.

4. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized in that: In step 2, when adding a dependency to the outbound configuration package, a detection is performed to determine whether there is information identical to the dependency in the second environment, and a determination is made based on the detection information whether to add the dependency to the outbound configuration package.

5. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized in that: In step 2, it is also used to configure the migration mode of each data in the data set. In step 4, when the outbound configuration package is deployed, the data in the data set is deployed according to the content of the migration mode.

6. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized by: In step 4, when the outbound configuration file is deployed, the status information of each component can be viewed, and the deployment order of each component can be adjusted or some steps can be removed.

7. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 6 is characterized by: In step 4, after the outbound configuration file is deployed, a configuration comparison report before and after the deployment is generated.

8. The single object migration configuration method applied to pharmaceutical enterprise data according to claim 1 is characterized by: The outbound configuration file is also provided with a verification status parameter, which is used to record the verification status in step three. Step four is to review and deploy the outbound configuration file according to the verification status parameter.

Images