CN112099841A - Method and system for generating configuration file - Google Patents

Abstract

The invention discloses a method and a system for generating a configuration file, and relates to the technical field of computers. One embodiment of the method comprises: starting the embedded system; the embedded system is used for generating configuration files and managing configuration information, is embedded in an application system, and is independent from the application system; performing, by the embedded system, the steps of: receiving configuration information submitted by a user, and storing the configuration information into an embedded database; and generating a configuration file in a target format according to the configuration information, and storing the configuration file to a specified path of a disk. The implementation method can solve the technical problems that the deployment structure is too large, the network is depended on or the maintenance cost is high.

Description

A method and system for generating configuration files

technical field

The present invention relates to the field of computer technology, and in particular, to a method and system for generating a configuration file.

Background technique

In most systems, system parameters are defined by means of configuration files, and configuration files are configured manually. The user configures the properties in the centralized configuration system. When the application system starts, the configuration information is pulled from the centralized configuration system through the network and saved in the memory for use by the application system.

In the process of realizing the present invention, the inventor found that there are at least the following problems in the prior art:

1) The deployment structure is too large: the application system must rely on the centralized configuration system and cannot run independently; when exporting to the outside world, it is often necessary to deploy a separate centralized configuration file system.

2) Dependency on the network: The application system must be connected through the network to pull configuration information from the centralized configuration system. If the network is interrupted, the configuration information cannot be pulled, causing system failure.

3) High maintenance cost: The centralized configuration system requires special personnel to manage and maintain it.

SUMMARY OF THE INVENTION

In view of this, embodiments of the present invention provide a method and system for generating a configuration file, so as to solve the technical problems that the deployment structure is too large, relies on the network, or has high maintenance costs.

To achieve the above object, according to an aspect of the embodiments of the present invention, a method for generating a configuration file is provided, including:

Start an embedded system; wherein, the embedded system is a system for generating configuration files and managing configuration information, the embedded system is embedded in an application system, and the embedded system and the application system are independent of each other;

Perform the following steps through the embedded system:

Receive the configuration information submitted by the user, and save the configuration information in the embedded database;

A configuration file in a target format is generated according to the configuration information, and the configuration file is saved to a specified path on the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system further performs the following steps:

reading the configuration information in the embedded database to display the configuration information on the user interface;

Modify the configuration information according to the modification instruction of the user, and save the modification record of the configuration information in the modification record table of the embedded database;

Update the configuration file in the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system further performs the following steps:

A generic interface of the centralized configuration file system is invoked, and the configuration file is sent to the centralized configuration file system through the generic interface.

Optionally, the embedded system is embedded in the application system in the form of a software package file format.

Optionally, the software package file format is a jar file.

Optionally, start the embedded system, including:

Start the embedded system with the jar command in java.

Optionally, before starting the embedded system, it also includes:

Build startup loading classes, database connection classes and interface management classes;

A packaging tool is used to package the startup loading class, the database connection class and the interface management class into a jar file, thereby constructing an embedded system.

Optionally, the startup loading class is used to start the embedded system;

The database connection class is used to read data in the embedded database;

The interface management class is used to display the read data on the interface for the user to view, configure or modify the configuration information;

Optionally, the startup loading class is ServerBootStrap.class, the database connection class is DbManager.class, and/or the interface management class is UiManger.class.

Optionally, the configuration information includes environment configuration information of each environment in the application system and system configuration information of the application system.

Optionally, each environment includes at least one of a development environment, a test environment, and a production environment; the attributes of the system configuration information include public attributes and private attributes.

Optionally, the target format includes an xml format or a properties format.

Optionally, the embedded database includes a SQLite database.

In addition, according to another aspect of the embodiments of the present invention, a system for generating a configuration file is provided, including an application system, an embedded system and an embedded database, the embedded system is embedded in the application system, and the embedded system is The system is independent of the application system;

The inline system is used to:

Receive the configuration information submitted by the user, and save the configuration information in the embedded database;

A configuration file in a target format is generated according to the configuration information, and the configuration file is saved to a specified path on the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system is further used to:

reading the configuration information in the embedded database to display the configuration information on the user interface;

Modify the configuration information according to the modification instruction of the user, and save the modification record of the configuration information in the modification record table of the embedded database;

Update the configuration file in the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system is further used to:

A generic interface of the centralized configuration file system is invoked, and the configuration file is sent to the centralized configuration file system through the generic interface.

Optionally, the embedded system is embedded in the application system in the form of a software package file format.

Optionally, the software package file format is a jar file.

Optionally, the embedded system is started by the following method:

Start the embedded system with the jar command in java.

Optionally, the embedded system is constructed and obtained by adopting the following method:

Build startup loading classes, database connection classes and interface management classes;

A packaging tool is used to package the startup loading class, the database connection class and the interface management class into a jar file.

Optionally, the startup loading class is used to start the embedded system;

The database connection class is used to read data in the embedded database;

The interface management class is used to display the read data on the interface for the user to view, configure or modify the configuration information;

Optionally, the startup loading class is ServerBootStrap.class, the database connection class is DbManager.class, and/or the interface management class is UiManger.class.

Optionally, the configuration information includes environment configuration information of each environment in the application system and system configuration information of the application system.

Optionally, each environment includes at least one of a development environment, a test environment, and a production environment; the attributes of the system configuration information include public attributes and private attributes.

Optionally, the target format includes an xml format or a properties format.

Optionally, the embedded database includes a SQLite database.

According to another aspect of the embodiments of the present invention, an electronic device is also provided, including:

one or more processors;

storage means for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

According to another aspect of the embodiments of the present invention, there is also provided a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, implements the method described in any of the foregoing embodiments.

An embodiment of the above invention has the following advantages or beneficial effects: because the embedded system is adopted: receiving the configuration information submitted by the user, saving the configuration information in the embedded database, generating the configuration file in the target format according to the configuration information, and The technical means of saving the configuration file to the specified path of the disk overcomes the technical problems of too large deployment structure, reliance on the network or high maintenance cost in the prior art. The embodiment of the present invention defines, modifies, and takes effect of the configuration through the embedded system, and generates the configuration file in a standardized manner, which can reduce the workload of repeated configuration in different environments and different systems, and reduce the risk of system errors caused by manual modification of the configuration file; Moreover, the application system can read the configuration file without relying on the network at all, getting rid of the dependence of the centralized configuration system, and also significantly reducing the maintenance cost. Therefore, the embodiments of the present invention reduce manual configuration operations, improve configuration efficiency, and reduce configuration risks.

Further effects of the above non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present invention and do not constitute an improper limitation of the present invention. in:

1 is a schematic diagram of the main flow of a method for generating a configuration file according to an embodiment of the present invention;

2 is a schematic diagram of a data structure of configuration information according to an embodiment of the present invention;

3 is a schematic diagram of the main flow of a method for generating a configuration file according to a referenced embodiment of the present invention;

4 is a schematic diagram of the main flow of a method for generating a configuration file according to another referenced embodiment of the present invention;

5 is a schematic diagram of main modules of a system for generating a configuration file according to an embodiment of the present invention;

FIG. 6 is an exemplary system architecture diagram to which an embodiment of the present invention may be applied;

FIG. 7 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

In an ordinary application system, it is generally divided into three environments: development environment, test environment, and production environment. At this time, three sets of configuration files are required. For special systems, there will also be a pre-release environment, a uat (User Acceptance Test, user acceptance test) environment, and a poc (roof of Concept, verification test) environment, etc. At this time, six sets of configuration files are required. If you follow the current popular technical route (such as micro-services, micro-architecture, etc.), a system will often be split into two systems: the foreground and the background, or even a system will be split into 3-5 subsystems.

At this time, the number of configuration files will increase exponentially, which is a huge workload for operation and maintenance. In addition, the configuration of some environments is the same. If you modify a parameter, you often need to modify multiple places. At this time, the risk caused by the error of the configuration file will become prominent.

At present, a centralized configuration system is usually used to configure attributes. When the application system is started, the configuration information is pulled from the centralized configuration system through the network and stored in the memory for use by the application system. However, the application server using the centralized configuration system must completely rely on the centralized configuration system, and because there are two services, it must depend on the network. If there is a problem with the centralized configuration system, the configuration information cannot be obtained. Therefore, high availability and low latency of the centralized configuration system must be guaranteed. However, the centralized configuration system has the technical problems of too large deployment structure and high maintenance cost. In order to solve these technical problems, the embodiment of the present invention provides a method for generating a configuration file, which can intuitively configure the configuration file through an embedded system. To define, modify, and take effect, configuration files can be generated in a standardized manner. Through automatic configuration, manual operations are reduced, efficiency is improved, and risks are reduced; and there is no need for a network or the deployment of a huge system structure.

FIG. 1 is a schematic diagram of a main flow of a method for generating a configuration file according to an embodiment of the present invention. As an embodiment of the present invention, as shown in FIG. 1 , the method for generating a configuration file may include:

Step 101 , starting an embedded system; wherein, the embedded system is embedded in an application system, and the embedded system and the application system are independent of each other.

In the embodiment of the present invention, the embedded system does not depend on external containers (such as tomcat, weblogic, etc.), the embedded system is a system for generating configuration files and managing configuration information, and the embedded system It is embedded in the application system in the form of a software package file format (such as an executable jar package file). Since the embedded system exists in the application system in the form of an executable jar package, the embedded system can be started directly by using the jar command in java to start the embedded system java without relying on the application system. The startup of the embedded system, based on the common Netty network programming framework, implements a simple http server and starts it through the jar command.

Optionally, before step 101, an embedded system needs to be constructed first, and the steps of constructing the embedded system include: constructing a startup loading class, a database connection class, and an interface management class; using a packaging tool to package the startup loading class, the The database connection class and the interface management class are packaged into a jar file, thereby constructing an embedded system. The startup loading class is used to start the embedded system; the database connection class is used to read the data in the embedded database; the interface management class is used to display the read data on the interface for the user to view , configure or modify configuration information. Specifically, the startup loading class listens to port 19999. When the user accesses port 19999 through a browser, the startup loading class starts the embedded system, then the database connection class reads the data in the embedded database, and finally reads the data through the interface management class. The user can view, modify, and add configuration information on the interface.

Optionally, the startup loading class is ServerBootStrap.class, and ServerBootStrap.class can quickly start the embedded system. Optionally, the database connection class is DbManager.class, and the data in the embedded database can be quickly read and the configuration information configured by the user can be saved in the embedded database through DbManager.class. Optionally, the interface management class is UiManger.class, and the user can view, modify, and add configuration information on the interface.

It should be pointed out that the application system and the embedded system belong to two independent systems. Both the application system and the embedded system can be started separately without interdependence. The embedded system can be embedded in the application system and activated when needed (for example, when you need to view configuration information, modify configuration information, or add new configuration information). The embedded system can be started independently regardless of whether the application system is started or not.

Steps 102 and 103 are performed by the embedded system.

Step 102: Receive the configuration information submitted by the user, and save the configuration information in the embedded database.

After the embedded system is started, the configuration information can be viewed through the user interface and the configuration information submitted by the user can be received, and then the received configuration information can be saved in the embedded database in real time. In order to avoid non-compliant configuration or other low-level errors, pre-defined rule filters (such as date rules, number rules, IP rules, mailbox rules, etc.) can filter the embedded system in real time when configuring properties.

Optionally, the configuration information includes environment configuration information of each environment in the application system and system configuration information of the application system. Optionally, each environment includes at least one of a development environment, a test environment, and a production environment; the attributes of the system configuration information include public attributes and private attributes. A project often has multiple environments (such as development environment, test environment, production environment, etc., and there may also be pre-release environment, uat environment, poc environment), so it is necessary to define the configuration content in groups. In multiple environments, there will be the same configuration content, so it is also necessary to define the sharing level of the configuration: private, public, etc. Public refers to configuration items that are common between different environments; private refers to configuration items that are unique between different environments.

As shown in Figure 2, each group represents an environment, and the sharing level needs to be configured when configuring the configuration information of the environment: public or private. If the configuration item is "public", it will be available in each environment in the post-generated configuration file to reduce the workload of repeated configuration in different environments; if the configuration item is "private", only The configuration item is generated in the configured environment (configured by the group to which it belongs).

Relatively speaking, the content of the configuration file is not much, and large-scale data is not required. Therefore, the embodiment of the present invention saves the configuration information in the embedded database. Optionally, the embedded database includes a SQLite database. SQLite is an embedded database, the entire database is a file and does not need to depend on other components. The configuration file will be copied to another place to form a new independent database. Moreover, the memory of the embedded database is small, and the entire database only needs one file, which can be started locally. Optionally, the embedded database may also be Progress, Empress, mSQL, or eXtremeDB, etc., which is not limited in this embodiment of the present invention.

Step 103: Generate a configuration file in a target format according to the configuration information, and save the configuration file to a specified path on the disk.

Optionally, in order to generate a configuration file in a target format according to user requirements, it is necessary to define the format of the configuration file in the embedded system before the embedded system executes step 102 or executes step 103, for example, the target format of the configuration file is defined as: xml file or properties file in the form of kv key-value pairs, etc.

Optionally, after saving the configuration file to a specified path of the disk, the embedded system further performs the following steps: reading the configuration information in the embedded database to display the configuration information on the user interface ; modify the configuration information according to the user's modification instruction, and save the modification record of the configuration information in the modification record table of the embedded database; update the configuration file in the disk. The embodiment of the present invention uses an embedded database as the database of the embedded service to record configuration information and each modification record. Every modification is recorded in an embedded database for backtracking when needed. After the modification of the configuration information is completed, the configuration file on the disk is further updated to ensure that the configuration information in the configuration file is the latest configuration.

In the embodiment of the present invention, when the configuration file is generated, the storage path of the configuration file in the disk is specified by the user, so the configuration file in the target format (such as xml or properties) can be saved to the specified path according to the path specified by the user After modifying the configuration information, update the configuration file under this path accordingly.

It should be pointed out that, in the embodiment of the present invention, all configuration information and modification records are stored in the embedded database, but cannot be read by the application system. Therefore, the configuration information needs to be saved to the disk in the form of a file for the application system to read and use.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system further performs the following steps: calling a general interface of the centralized configuration file system, and sending the configuration file through the general interface to the centralized configuration file system. Considering that in the actual project, some application systems have been connected to the centralized configuration system, so by calling the general interface, the configuration file configured in the embedded system is sent to the centralized system, so that the application system can configure the system in the centralized system. Switch flexibly between embedded systems.

It should be noted that the application system deployed on the application server may be a parent system or a subsystem, but technically or in terms of deployment method, it is also an independent system. Subsystems are independently deployed and started independently. If you want to share configuration information between parent subsystems, you must first define the configuration in the embedded system of the parent system, then copy the configuration file of the parent system to each subsystem, and finally add the embedded system in the subsystem. The system performs configuration modification, which can reduce the workload of repeated configuration between different systems, and also reduce the risk of system errors caused by manual modification of configuration files.

According to the various embodiments described above, it can be seen that the embodiment of the present invention adopts an embedded system: receiving the configuration information submitted by the user, saving the configuration information in the embedded database, and generating a configuration file in the target format according to the configuration information , and the technical means of saving the configuration file to the specified path of the disk solves the technical problems of too large deployment structure, network dependence or high maintenance cost in the prior art. The embodiment of the present invention defines, modifies, and takes effect of the configuration through the embedded system, and generates the configuration file in a standardized manner, which can reduce the workload of repeated configuration in different environments and different systems, and reduce the risk of system errors caused by manual modification of the configuration file; Moreover, the application system can read the configuration file without relying on the network at all, getting rid of the dependence of the centralized configuration system, and also significantly reducing the maintenance cost. Therefore, the embodiments of the present invention reduce manual configuration operations, improve configuration efficiency, and reduce configuration risks.

FIG. 3 is a schematic diagram of the main flow of a method for generating a configuration file according to a referenced embodiment of the present invention. As another embodiment of the present invention, as shown in FIG. 3 , the method for generating a configuration file may include:

Step 301, building an embedded system.

Specifically, it includes: constructing a startup loading class, a database connection class, and an interface management class; using a packaging tool to package the startup loading class, the database connection class, and the interface management class into a jar file, thereby constructing an embedded system . The startup loading class is used to start the embedded system; the database connection class is used to read the data in the embedded database; the interface management class is used to display the read data on the interface for the user to view , configure or modify configuration information.

Step 302, start the embedded system.

Wherein, the embedded system is embedded in the application system, and the embedded system and the application system are independent of each other. The embedded system does not depend on external containers (such as tomcat, weblogic, etc.), the embedded system is a system for generating configuration files and managing configuration information, and the embedded system is in a software package file format (such as jar file) is embedded in the application system. Since the embedded system exists in the application system in the form of an executable jar package, the embedded system can be started directly with the jar command in java, and the embedded system can be started without relying on the application system. Both the application system and the embedded system can be started separately without interdependence. Embedded systems can be embedded in the application system and activated when needed. The embedded system can be started independently regardless of whether the application system is started or not.

Steps 303 to 307 are performed by the embedded system.

Step 303, receiving the configuration information submitted by the user.

After the embedded system is started, the configuration information can be viewed through the user interface and the configuration information submitted by the user can be received, and then the received configuration information can be saved in the embedded database in real time. In order to avoid non-compliant configuration or other low-level errors, pre-defined rule filters (such as date rules, number rules, IP rules, mailbox rules, etc.) can filter the embedded system in real time when configuring properties.

Step 304: Save the configuration information into an embedded database.

Optionally, the embedded database includes a SQLite database. SQLite is an embedded database, the entire database is a file and does not need to depend on other components. The configuration file will be copied to another place to form a new independent database. Moreover, the memory of the embedded database is small, and the entire database only needs one file, which can be started locally.

Step 305, specify the target format and storage path of the configuration file.

In order to generate a configuration file in a target format according to user requirements, it is necessary to define the format of the configuration file in the embedded system before the embedded system executes step 305, for example, define the target format of the configuration file as an xml file or a kv key-value pair format properties file, etc.

Likewise, before the embedded system executes step 307, the storage path of the configuration file on the disk needs to be specified in the embedded system.

Step 306: Generate a configuration file in a target format according to the configuration information.

Step 307: Save the configuration file to a specified path on the disk.

The configuration file on the disk can be copied to other application servers. If the configuration information is the same, the application system on the application server can directly read the configuration file. If it needs to be modified, the embedded system on the application server will be activated. Update configuration information, thereby updating the configuration file on disk.

The application system deployed on the application server can be a parent system or a subsystem, but technically or in terms of deployment method, it is also an independent system. Subsystems are independently deployed and started independently. If you want to share configuration information between parent subsystems, you must first define the configuration in the embedded system of the parent system, then copy the configuration file of the parent system to each subsystem, and finally add the embedded system in the subsystem. The system performs configuration modification, which can reduce the workload of repeated configuration between different systems, and also reduce the risk of system errors caused by manual modification of configuration files.

In addition, the specific implementation content of the method for generating a configuration file in a referenced embodiment of the present invention has been described in detail in the above-mentioned method for generating a configuration file, so the repeated content will not be described here.

FIG. 4 is a schematic diagram of the main flow of a method for generating a configuration file according to another referenced embodiment of the present invention. As another embodiment of the present invention, as shown in FIG. 4 , the method for generating a configuration file may include:

Step 401, start the embedded system. Wherein, the embedded system is embedded in the application system, and the embedded system and the application system are independent of each other.

Steps 402 to 408 are performed by the embedded system.

Step 402, receiving the configuration information submitted by the user.

Step 403: Save the configuration information into an embedded database.

Step 404: Generate a configuration file in a target format according to the configuration information.

Step 405: Save the configuration file to a specified path on the disk.

Step 406: Read the configuration information in the embedded database to display the configuration information on the user interface.

When the user needs to modify the configuration information, the reading embedded system reads the configuration information in the embedded database, so as to display the configuration information on the user interface.

Step 407: Modify the configuration information according to the user's modification instruction, and save the modification record of the configuration information in the modification record table of the embedded database.

The user can modify the existing configuration information as required, and the embedded system modifies the configuration information in the embedded database according to the user's modification instruction, and at the same time saves the modification record of the configuration information to the modification record table of the embedded database. , for backtracking if needed.

Step 408, update the configuration file in the disk.

After modifying the configuration information, update the configuration file in the disk so that the application system can read the latest configuration information.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system further performs the following steps: calling a general interface of the centralized configuration file system, and sending the configuration file through the general interface to the centralized configuration file system. Considering that in the actual project, some application systems have been connected to the centralized configuration system, so by calling the common interface, the configuration files configured in the embedded system are sent to the centralized system, so that the application system can configure the system in the centralized system. Switch flexibly between embedded systems.

In addition, the specific implementation content of the method for generating a configuration file in another reference embodiment of the present invention has been described in detail in the above-mentioned method for generating a configuration file, so the repeated content will not be described here.

FIG. 5 is a schematic diagram of main modules of a system for generating configuration files according to an embodiment of the present invention. As shown in FIG. 5 , the system 500 for generating configuration files includes an application system 501 , an embedded system 502 and an embedded database 503 . The embedded system is a system for generating configuration files and managing configuration information, the embedded system 502 is embedded in the application system 501, and the embedded system 502 and the application system 501 are independent of each other;

The embedded system 502 is used to:

Receive the configuration information submitted by the user, and save the configuration information into the embedded database 503;

A configuration file in a target format is generated according to the configuration information, and the configuration file is saved to a specified path on the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system 502 is further used to:

Read the configuration information in the embedded database 503 to display the configuration information on the user interface;

Modify the configuration information according to the modification instruction of the user, and save the modification record of the configuration information in the modification record table of the embedded database 503;

Update the configuration file in the disk.

Optionally, after saving the configuration file to a specified path on the disk, the embedded system 502 is further used to:

A generic interface of the centralized configuration file system is invoked, and the configuration file is sent to the centralized configuration file system through the generic interface.

Optionally, the embedded system is embedded in the application system in the form of a software package file format.

Optionally, the software package file format is a jar file.

Optionally, the embedded system is started by the following method:

Start the embedded system with the jar command in java.

Optionally, the embedded system is constructed and obtained by adopting the following method:

Build startup loading classes, database connection classes and interface management classes;

A packaging tool is used to package the startup loading class, the database connection class and the interface management class into a jar file.

Optionally, the startup loading class is used to start the embedded system;

The database connection class is used to read data in the embedded database;

The interface management class is used to display the read data on the interface for the user to view, configure or modify the configuration information;

Optionally, the startup loading class is ServerBootStrap.class, the database connection class is DbManager.class, and/or the interface management class is UiManger.class.

Optionally, the configuration information includes environment configuration information of each environment in the application system and system configuration information of the application system.

Optionally, each environment includes at least one of a development environment, a test environment, and a production environment; the attributes of the system configuration information include public attributes and private attributes.

Optionally, the target format includes an xml format or a properties format; and/or, the embedded database 503 includes an SQLite database.

According to the various embodiments described above, it can be seen that the embodiment of the present invention adopts an embedded system: receiving the configuration information submitted by the user, saving the configuration information in the embedded database, and generating a configuration file in the target format according to the configuration information , and the technical means of saving the configuration file to the specified path of the disk solves the technical problems of too large deployment structure, network dependence or high maintenance cost in the prior art. The embodiment of the present invention defines, modifies, and takes effect of the configuration through the embedded system, and generates the configuration file in a standardized manner, which can reduce the workload of repeated configuration in different environments and different systems, and reduce the risk of system errors caused by manual modification of the configuration file; Moreover, the application system can read the configuration file without relying on the network at all, getting rid of the dependence of the centralized configuration system, and also significantly reducing the maintenance cost. Therefore, the embodiments of the present invention reduce manual configuration operations, improve configuration efficiency, and reduce configuration risks.

It should be noted that the specific implementation content of the system for generating a configuration file of the present invention has been described in detail in the above-mentioned method for generating a configuration file, so the repeated content will not be described here.

FIG. 6 shows an exemplary system architecture 600 of a method for generating a configuration file or a system for generating a configuration file to which embodiments of the present invention may be applied.

As shown in FIG. 6 , the system architecture 600 may include terminal devices 601 , 602 , and 603 , a network 604 and a server 605 . The network 604 is a medium used to provide a communication link between the terminal devices 601 , 602 , 603 and the server 605 . Network 604 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 601, 602, 603 to interact with the server 605 through the network 604 to receive or send messages and the like. Various communication client applications may be placed on the terminal devices 601 , 602 and 603 , such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 605 may be a server that provides various services, such as a background management server that supports shopping websites browsed by the terminal devices 601 , 602 , and 603 (just an example). The background management server can analyze and process the received item information query request and other data, and feed back the processing results (such as target push information, item information—just an example) to the terminal device.

It should be noted that the method for generating a configuration file provided by the embodiment of the present invention is generally executed by the server 605 , and accordingly, the system for generating a configuration file is generally set in the server 605 . The method for generating a configuration file provided by the embodiment of the present invention may also be executed by the terminal devices 601 , 602 , and 603 , and correspondingly, the system for generating a configuration file may be set in the terminal devices 601 , 602 , and 603 .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 6 are merely illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Referring next to FIG. 7 , it shows a schematic structural diagram of a computer system 700 suitable for implementing a terminal device according to an embodiment of the present invention. The terminal device shown in FIG. 7 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present invention.

As shown in FIG. 7, a computer system 700 includes a central processing unit (CPU) 701 which can be loaded into a random access memory (RAM) 703 according to a program stored in a read only memory (ROM) 702 or a program from a storage section 708 Instead, various appropriate actions and processes are performed. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701 , the ROM 702 , and the RAM 703 are connected to each other through a bus 704 . An input/output (I/O) interface 705 is also connected to bus 704 .

The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc. ; and a communication section 709 including a network interface card such as a LAN card, a modem, and the like. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is placed on the drive 710 as needed so that a computer program read therefrom can be placed into the storage section 708 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as computer software programs in accordance with the disclosed embodiments of the present invention. For example, embodiments disclosed herein include a computer program comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and placed from the network through the communication portion 709, and/or placed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-described functions defined in the system of the present invention are executed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer programs according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device implements the following method: starting an embedded system; wherein, the embedded system is used to generate a configuration A system for file and management configuration information, the embedded system is embedded in an application system, and the embedded system and the application system are independent of each other; the following steps are performed by the embedded system: receiving the configuration information submitted by the user, and save the configuration information into an embedded database; generate a configuration file in a target format according to the configuration information, and save the configuration file to a specified path on the disk.

According to the technical solution of the embodiment of the present invention, because the embedded system is adopted: the configuration information submitted by the user is received, and the configuration information is saved in the embedded database, the configuration file in the target format is generated according to the configuration information, and the configuration file is saved in the It is a technical means under the specified path of the disk, so it overcomes the technical problems of too large deployment structure, dependence on the network or high maintenance cost in the prior art. The embodiment of the present invention defines, modifies, and takes effect of the configuration through the embedded system, and generates the configuration file in a standardized manner, which can reduce the workload of repeated configuration in different environments and different systems, and reduce the risk of system errors caused by manual modification of the configuration file; Moreover, the application system can read the configuration file without relying on the network at all, getting rid of the dependence of the centralized configuration system, and also significantly reducing the maintenance cost. Therefore, the embodiments of the present invention reduce manual configuration operations, improve configuration efficiency, and reduce configuration risks.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (15)

1. A method of generating a configuration file, comprising:

starting the embedded system; the embedded system is used for generating configuration files and managing configuration information, is embedded in an application system, and is independent from the application system;

performing, by the embedded system, the steps of:

receiving configuration information submitted by a user, and storing the configuration information into an embedded database;

and generating a configuration file in a target format according to the configuration information, and storing the configuration file to a specified path of a disk.

2. The method of claim 1, wherein after saving the configuration file to a specified path of the disk, further performing, by the embedded system, the steps of:

reading the configuration information in the embedded database to display the configuration information on a user interface;

modifying the configuration information according to a modification instruction of a user, and storing a modification record of the configuration information into a modification record table of the embedded database;

and updating the configuration file in the disk.

3. The method of claim 1, wherein after saving the configuration file to a specified path of the disk, further performing, by the embedded system, the steps of:

and calling a general interface of the centralized configuration file system, and sending the configuration file to the centralized configuration file system through the general interface.

4. The method of any of claims 1-3, wherein the embedded system is embedded in the application system in a software package file format.

5. The method of claim 4, wherein the package file format is jar file.

6. The method of claim 5, wherein initiating an embedded system comprises:

and starting the embedded system by using a jar command in java.

7. The method of claim 5, prior to initiating the embedded system, further comprising:

building a start loading class, a database connection class and an interface management class;

and packaging the boot loading class, the database connection class and the interface management class into jar files by adopting a packaging tool so as to construct an embedded system.

8. The method of claim 7, wherein the boot load class is used to boot an embedded system;

the database connection class is used for reading data in the embedded database;

the interface management class is used for displaying the read data on an interface so that a user can view, configure or modify the configuration information.

9. The method of claim 8, wherein the bootload class is ServerBootStrap. class, the database connection class is DbManager. class, and/or the interface management class is UiManger. class.

10. The method of claim 1, wherein the configuration information comprises environment configuration information of each environment in the application system and system configuration information of the application system.

11. The method of claim 10, wherein the respective environments comprise at least one of a development environment, a test environment, and a production environment; the attributes of the system configuration information include public attributes and private attributes.

12. The method of claim 1, wherein the embedded database comprises a SQLite database.

13. A system for generating configuration files is characterized by comprising an application system, an embedded system and an embedded database, wherein the embedded system is a system for generating configuration files and managing configuration information, the embedded system is embedded in the application system, and the embedded system and the application system are mutually independent;

the embedded system is to:

receiving configuration information submitted by a user, and storing the configuration information into the embedded database;

and generating a configuration file in a target format according to the configuration information, and storing the configuration file to a specified path of a disk.

14. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

the one or more programs, when executed by the one or more processors, implement the method of any of claims 1-12.

15. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-12.

Images