CN115291893A

CN115291893A - Code operation deployment system and method

Info

Publication number: CN115291893A
Application number: CN202211008034.6A
Authority: CN
Inventors: 张旭
Original assignee: Individual
Current assignee: Individual
Priority date: 2022-08-22
Filing date: 2022-08-22
Publication date: 2022-11-04

Abstract

The invention provides a code running deployment system and a code running deployment method, and relates to the field of code deployment. The JEE-fk framework is adopted and comprises a starting layer, a framework layer, a service layer and a module layer; the starting layer is used for assembling bottom layer codes of different components when the project is started; the framework layer is used for carrying out framework-level information configuration starting after the bottom layer is started, packaging common codes for developers to use, and issuing different projects to corresponding sub-packages through a private server after the common codes are modified; the service layer is used for providing a plurality of basic access interfaces for the outside after the system framework is started, and each basic access interface is matched with a basic function; the module layer executes the module program after starting the service layer; and the module layer configures the modules according to the rules of the system framework. The bug is reduced, the repeated development of the same function by developers is avoided, and the execution efficiency of the code is improved.

Description

Code operation deployment system and method

Technical Field

The invention relates to the field of code deployment, in particular to a code running deployment system and a code running deployment method.

Background

Many similar or repeated tasks are often involved in system development, such as when enterprise personnel management operations of adding, deleting, modifying and checking are performed, and if they are reprogrammed, the operations are time consuming, labor consuming and extremely unnecessary. Therefore, a code generation tool capable of assisting a developer in project development, reducing the trouble of repeatedly modifying bugs on a plurality of projects, and improving the execution efficiency of codes is needed. The problem that bug occurrence probability is high due to different project configurations can be solved, difficulty in parameter configuration of company developers is reduced, and programs are prevented from being designed repeatedly.

Disclosure of Invention

One of the objectives of the present invention is to provide a code operation deployment system, which can solve the problem of high bug occurrence probability caused by different configuration of each project, avoid repeated development of the same function by developers, and improve the execution efficiency of codes.

One of the purposes of the present invention is to provide a code running and deploying method, which can solve the problem of a high bug occurrence probability caused by different configuration of each project, avoid repeated development of the same function by developers, and improve the execution efficiency of codes.

The embodiment of the invention is realized by the following steps:

in a first aspect, an embodiment of the present application provides a code running deployment system, where a JEE-fk frame is adopted as a system frame, and the system frame includes a boot layer (boot layer), a frame layer (framework layer), a service layer (services layer), and a module layer (modules layer); the starting layer is used for assembling bottom layer codes of different components according to project requirements when a project is started; the framework layer is used for carrying out framework-level information configuration starting after the starting layer is used for carrying out bottom layer starting, packaging common codes for developers to use, carrying out packaging and issuing through a private server after the common codes are modified, and issuing different projects into corresponding sub-packages; the service layer is used for providing a plurality of basic access interfaces for the outside after the system framework is started, and each basic access interface is matched with a basic function responding to the basic access interface; the module layer is used for being executed after the service layer is started and is started as a module program; the module layer configures the modules according to the rules of the system framework.

In some embodiments of the present invention, the above-mentioned start-up layer includes a configuration layer (config layer); the configuration layer is used for configuring the basic functions required to be used in the system starting process, and the basic functions comprise any one or more of a database, a cache, security authentication, a firewall, a script engine, a certificate engine, an internationalized language and message encapsulation.

In some embodiments of the present invention, the configuration layer performs various configuration initializations during the bottom layer boot process, and each configuration is encapsulated in an independent jar file.

In some embodiments of the present invention, the start layer further includes an integration layer (starter layer); the integration layer is used for introducing the framework layer at the upper layer into a jar package of the pom file.

In some embodiments of the present invention, the integration layer introduces other configuration information required while the start-up layer bottom layer configures each of the basic functions to start up.

In some embodiments of the present invention, the above-mentioned framework layer includes a common method layer (common layer); the public method layer is used for encapsulating non-business public methods used daily and providing the non-business public methods for developers to use.

In some embodiments of the present invention, the framework layer further includes a support layer (support layer); the support layer is used for supporting configuration information of a part of default non-boot layers.

In some embodiments of the present invention, the basic access interface provided by the service layer includes any one or more of an access resource management interface, a log management interface, a rights management interface, a client management interface, a server console interface, a dictionary management interface, a firewall configuration interface, a message management interface, a module installation management interface, an organization architecture management interface, a role management interface, a static resource management interface, an upload data management interface, and a user management interface.

In some embodiments of the present invention, the framework layer further comprises a code generator; the code generator is used for configuring according to different databases in the system framework and adding configured related codes as templates for use.

In a second aspect, an embodiment of the present application provides a code running deployment method, which is implemented based on any one of the above-mentioned systems in the first aspect.

Compared with the prior art, the embodiment of the invention has at least the following advantages or beneficial effects:

the JEE-fk frame is integrally designed into a 4-layer framework and comprises a starting layer, a frame layer, a service layer and a module layer; the starting layer is a bottommost code executed when the project starts, and is used for assembling different assemblies according to project requirements, so that the codes are reused, and the problems that a bottom layer frame needs to be built every time the project starts and the bug occurrence probability is high due to different project configurations are solved; the framework layer is used for carrying out framework level information configuration after starting, so that the framework layer is separated from the boot layer, and the structure is clearer; meanwhile, the framework layer is also used for packaging a plurality of codes used daily, so that the repeated development of the same function of a developer is avoided, the codes of a common method are regularly optimized, and the trouble that bugs need to be repeatedly modified on a plurality of projects is reduced, so that the execution efficiency of the codes is improved; after the code is modified, the code is packaged and issued on the private server, and each project is re-issued to a sub-package in the corresponding framework layer, so that the code can be updated; the service layer is an access interface which provides some basic functions to the outside after the system framework is started, so that the trouble of repeatedly compiling the same code for each project is avoided; the module layer is executed after services are started and is started as a module program, and the modules are configured according to the rules of the system framework, so that the standardized configuration of the modules in the system framework can be realized, and the code generation period can be shortened.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.

Fig. 1 is a schematic diagram of a code operation deployment system according to embodiment 1 of the present invention;

fig. 2 is a schematic diagram of a basic access interface in embodiment 1 of the present invention;

fig. 3 is a schematic flowchart of a code operation deployment method in embodiment 1 of the present invention;

fig. 4 is a schematic flowchart of implementation of a start layer in embodiment 1 of the present invention;

fig. 5 is a schematic flow chart of implementation of a framework layer in embodiment 1 of the present invention;

fig. 6 is a schematic diagram of an electronic device according to embodiment 2 of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the description of the present application, it is also to be noted that, unless otherwise explicitly specified or limited, the terms "disposed" and "connected" are to be interpreted broadly, e.g., as being either fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in this application will be understood to be a specific case for those of ordinary skill in the art.

Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the individual features of the embodiments can be combined with one another without conflict.

Example 1

Referring to fig. 1 to 5, fig. 1 to 5 are schematic diagrams illustrating a code operation deployment system according to an embodiment of the present application. The code operation deployment system adopts a JEE-fk frame which comprises a starting layer (boot layer), a frame layer (framework layer), a service layer (services layer) and a module layer (modules layer); the starting layer is used for assembling bottom layer codes of different components according to project requirements when a project is started; the framework layer is used for performing framework-level information configuration starting after the bottom layer starting is performed on the starting layer, packaging common codes for developers to use, performing packaging and issuing through a private server after the common codes are modified, and issuing different projects into corresponding sub-packages; the service layer is used for providing a plurality of basic access interfaces for the outside after the system framework is started, and each basic access interface is matched with a basic function of response; the module layer is used for being executed after the service layer is started and is started as a module program; and the module layer configures the modules according to the rules of the system framework.

The JEE-fk framework is designed to be a 4-layer framework as a whole and comprises a start layer (boot), a framework layer (frame), a service layer (services) and a module layer (modules). The starting layer is the bottommost code executed when the project is started, and different components to be used can be spliced according to the project requirement to assemble the bottommost code. The method avoids the problems that a bottom layer frame needs to be built for each project, the bug probability is high due to different configuration of each project, and the reuse rate of codes is improved.

The service layer is a basic access Interface (Application Programming Interface) provided for the outside after the system framework is started, so that the trouble of repeatedly writing the same code in each project is avoided. Each basic function sets a basic access interface for response, and each component respectively realizes the corresponding effect of different basic functions.

The module layer is a module program executed after the service layer is started, wherein the module is a non-main service function, and can be a small function point or a group of functions, or a subsystem under a main system. And configuring according to the rules of the system framework to realize that the module writes configuration information such as authority, dictionary and the like into the system framework. The module layer can standardize the module and shorten the construction period of developers.

In some embodiments of the present invention, the integration layer introduces other configuration information required while the start-up layer bottom layer configures each basic function to start.

The boot layer is divided into a 2-layer structure including a configuration layer (config layer) and an integration layer (starter layer). The configuration layer is used for configuring the basic functions of a database, a cache, security authentication, a firewall, a script engine, a certificate engine, an international language, message encapsulation and the like which are needed to be used in the starting process of the system. Each component respectively realizes the corresponding effect of different basic functions, and various configuration initializations are carried out in the bottom layer starting process to provide the most basic support for other system layers. For example, the bottom layer uses ehcach or redise to implement caching, and the script engine dynamically loads scripts existing in the database during the starting process, and performs dynamic decryption, dynamic compilation and class loading execution through a custom-developed classloader (class loader). Optionally, the components can be switched or expanded according to different scenes, a configuration layer can form a series of ecology through a private warehouse, the difficulty of configuring parameters by company developers is reduced, repeated wheel manufacturing is avoided, and each configuration is packaged in an independent jar file to achieve the decoupling effect. The integration layer exposes the jar packet of the introduced pom file to the upper framework layer, introduces the configuration of a plurality of configuration layers in the starting layer to realize the expected basic function, and can introduce other configuration information of the configuration layers while starting each basic function in the bottom configuration, thereby achieving good decoupling effect, improving the reusability of codes and reducing the cost of bottom maintenance.

In some embodiments of the present invention, the above framework layer comprises a common method layer (common layer); the public method layer is used for encapsulating non-business public methods used daily and providing the non-business public methods for developers to use.

The frame layer is a two-layer structure including a common method layer and a support layer. And the public method layer is used for encapsulating the non-business public methods used daily, encapsulating and providing the non-business public methods for developers to use. The support layer is used for completing configuration information of some default non-starting layers supported by the framework, such as functions of global transaction, data filling, module installation management, system command and the like. And after the framework layer is modified, the framework layer is published on a private server for packaging and publishing, and each item is re-published to a sub-package in the corresponding framework layer, so that the program updating can be realized.

The multiple basic access interfaces provided by the current service layer include an access resource management interface, a log management interface, a rights management interface, a client management interface, a server console interface, a dictionary management interface, a firewall configuration interface, a message management interface (using the concept of DDD field driven message push), a module installation management interface, an organization architecture management interface, a role management interface, a static resource management interface, an upload data management interface, and a user management interface. The service layer can develop more interface data provided by the service layer through the private warehouse, and can develop a system more quickly after the interface data is expanded to a certain number of service layers, and even can complete most development work of the system through configuration.

The system framework provides a code generator, the code generator can be configured according to different databases, dynamic configuration requires generation of a series of relevant codes corresponding to the database tables, and the codes are not limited to development languages. The generated codes can generate templates according to personal needs, and the templates can be repeatedly used only by compiling once after a project is started, so that the development time can be saved by 50%, the development cost is reduced, and the development difficulty is reduced.

The codes are usually packaged into a jar file for issuing, and when the system framework issues the codes, the codes are packaged into countless small jar packages for issuing, so that the advantages that the specific module or configuration with a problem only needs to update the corresponding small jar file, the project jar file is not required to be integrally replaced, the risk of the problem is reduced, the problem of the whole system is avoided because the function in development exists in the jar to be issued, and the like. The whole system is divided according to different system layers and different functions, a plurality of jar files can be packaged and then issued, and the problem of repeated bug is reduced to the minimum.

Example 2

Referring to fig. 6, fig. 6 is a schematic structural block diagram of an electronic device according to an embodiment of the present disclosure. The electronic device comprises a memory 101, a processor 102 and a communication interface 103, wherein the memory 101, the processor 102 and the communication interface 103 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 101 may be used to store software programs and modules, such as program instructions/modules corresponding to the code generation system provided in embodiment 1 of the present application, and the processor 102 executes the software programs and modules stored in the memory 101, so as to execute various functional applications and data processing. The communication interface 103 may be used for communicating signaling or data with other node devices.

The Memory 101 may be, but not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Read Only Memory (EPROM), an electrically Erasable Read Only Memory (EEPROM), and the like.

The processor 102 may be an integrated circuit chip having signal processing capabilities. The Processor 102 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

It will be appreciated that the configuration shown in fig. 6 is merely illustrative and that the electronic device may include more or fewer components than shown in fig. 6 or have a different configuration than shown in fig. 6. The components shown in fig. 6 may be implemented in hardware, software, or a combination thereof.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block 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 will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

To sum up, a code operation deployment system and method provided by the embodiments of the present application:

the JEE-fk frame is integrally designed into a 4-layer framework and comprises a starting layer, a frame layer, a service layer and a module layer; the starting layer is a bottommost code executed when the project starts, and is used for assembling different assemblies according to project requirements, so that the codes are reused, and the problems that a bottom layer frame needs to be built every time the project starts and the bug occurrence probability is high due to different project configurations are solved; the framework layer is used for carrying out framework level information configuration after starting, so that the framework layer is separated from the boot layer, and the structure is clearer; meanwhile, the framework layer is also used for packaging a plurality of codes used daily, so that the repeated development of the same function by developers is avoided, the codes of a common method are regularly optimized, and the trouble that bugs need to be repeatedly modified on a plurality of projects is reduced, so that the execution efficiency of the codes is improved; after the codes are modified, the codes are packaged and issued on the private server, and each project is reissued to a sub-package in the corresponding framework layer, so that the codes can be updated; the service layer is an access interface which provides some basic functions to the outside after the system framework is started, so that the trouble of repeatedly compiling the same code for each project is avoided; the module layer is executed after services are started and is started as a module program, and the modules are configured according to the rules of the system framework, so that the standardized configuration of the modules in the system framework can be realized, and the code generation period can be shortened. According to the method and the system, a series of ecology is formed through the private warehouse inventory, the difficulty of parameter configuration of company developers is reduced, and repeated design procedures are avoided.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.

Claims

1. A code running deployment system is characterized in that a JEE-fk frame is adopted by a system frame and comprises a start layer (boot layer), a frame layer (framework layer), a service layer (services layer) and a module layer (modules layer); the starting layer is used for assembling bottom layer codes of different components according to project requirements when a project is started; the framework layer is used for performing framework-level information configuration starting after the bottom layer starting is performed on the starting layer, packaging common codes for developers to use, performing packaging and issuing through a private server after the common codes are modified, and issuing different projects into corresponding sub-packages; the service layer is used for providing a plurality of basic access interfaces for the outside after the system framework is started, and each basic access interface is matched with a basic function of response; the module layer is used for being executed after the service layer is started and is started as a module program; and the module layer configures the modules according to the rules of the system framework.

2. A code-run deployment system as claimed in claim 1, wherein the start-up layer comprises a configuration layer (config layer); the configuration layer is used for configuring the basic functions required to be used in the system starting process, and the basic functions comprise any one or more of a database, a cache, security authentication, a firewall, a script engine, a certificate engine, an international language and message encapsulation.

3. The code-run deployment system of claim 2, wherein the configuration layer performs various configuration initializations during the underlying boot process, each configuration being encapsulated in a separate jar file.

4. A code-run deployment system in accordance with claim 2, wherein said boot layer further comprises an integration layer (starter layer); the integration layer is used for introducing the framework layer at the upper layer into a jar package of the pom file.

5. A code-run deployment system as claimed in claim 4, wherein said integration layer introduces other configuration information required while said boot-layer underlying configuration boots each of said base functions.

6. A code-run deployment system as claimed in claim 1, wherein said framework layer comprises a common methods layer (common layer); the public method layer is used for encapsulating non-business public methods used daily and providing the non-business public methods for developers to use.

7. The code run deployment system of claim 6 wherein the framework layer further comprises a support layer (support layer); the support layer is used for supporting configuration information of a part of default non-starting layers.

8. The code run deployment system of claim 6 wherein the framework layer further comprises a code generator; the code generator is used for configuring according to different databases in the system framework and adding configured related codes as templates for use.

9. The code deployment system of claim 1, wherein the basic access interface provided by the business layer comprises any one or more of an access resource management interface, a log management interface, a rights management interface, a client management interface, a server console interface, a dictionary management interface, a firewall configuration interface, a message management interface, a module installation management interface, an organizational architecture management interface, a role management interface, a static resource management interface, an upload data management interface, and a user management interface.

10. A code running deployment method, which is implemented based on the system of any one of claims 1 to 9.