System integration method and related equipment

Abstract

The present invention relates to the field of software development technology and provides a system integration method and related equipment. The system integration method obtains a portal system and multiple subsystems to be integrated; registers the multiple subsystems with the portal system; controls the portal system to load the multiple subsystems; receives, through the portal system, a call request from the front end of a target subsystem among the multiple subsystems; and, through the portal system, calls the back end of the target subsystem based on the call request. The present invention integrates multiple systems into the portal system, enhancing the stability of the integrated system.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a system integration method, apparatus, computer equipment, and computer-readable storage medium. Background Art

[0002] With the rise of Internet cloud, a concept of integrating multiple different subsystems (services) into an integrated platform and opening it to the outside world has gradually taken shape.

[0003] Building a system platform that integrates different subsystems can lead to inefficient portal page navigation and errors, making it difficult to access the subsystems correctly. Therefore, improving the stability of the integrated system becomes a problem to be solved. Summary of the Invention

[0004] In view of the above, it is necessary to propose a system integration method, apparatus, computer device and computer-readable storage medium, which can integrate multiple systems into an entry system and enhance the stability of the integrated system.

[0005] A first aspect of the present application provides a system integration method, the system integration method comprising:

[0006] Obtain the entry system and multiple subsystems to be integrated;

[0007] registering the plurality of subsystems to the portal system;

[0008] controlling the entry system to load the plurality of subsystems;

[0009] Receiving, through the entry system, a call request from a front end of a target subsystem in the plurality of subsystems;

[0010] The backend of the target subsystem is called according to the call request through the entry system.

[0011] In another possible implementation, registering the multiple subsystems with the portal system includes:

[0012] Get the subsystem name of each subsystem;

[0013] Control each subsystem to package the routing files of each subsystem;

[0014] The name of each subsystem and the file name of each routing file are associated and stored in the entry system.

[0015] In another possible implementation, controlling each subsystem to package the routing files of each subsystem includes:

[0016] Obtain storage variables and routing registration functions of global objects in the entry system;

[0017] Control each subsystem to store the routing file into the storage variable by calling the registration function.

[0018] In another possible implementation, the system integration method further includes:

[0019] Get the preset routing specification;

[0020] The routing file is defined according to the preset routing specification.

[0021] In another possible implementation, before controlling the entry system to load the multiple subsystems, the system integration method further includes:

[0022] Detecting subsystems that do not comply with the specification from the multiple subsystems using a webpack plug-in;

[0023] Stop loading the subsystem that does not meet the specifications, and pop up a prompt box to prompt the subsystem that does not meet the specifications.

[0024] In another possible implementation, before controlling the entry system to load the multiple subsystems, the system integration method further includes:

[0025] Obtaining style codes of the multiple subsystems;

[0026] Identify subsystems where style code does not exist in a namespace as subsystems with errors;

[0027] The subsystem with the error is intercepted by a boundary component.

[0028] In another possible implementation, the system integration method further includes:

[0029] Performing resource deduplication processing on the multiple subsystems;

[0030] Unused codes in the plurality of subsystems are deleted.

[0031] A second aspect of the present application provides a system integration device, the system integration device comprising:

[0032] An acquisition module, used to acquire the entry system and multiple subsystems to be integrated;

[0033] a registration module, configured to register the plurality of subsystems with the portal system;

[0034] A loading module, configured to control the entry system to load the multiple subsystems;

[0035] A receiving module, configured to receive, through the entry system, a call request from a front end of a target subsystem among the multiple subsystems;

[0036] A calling module is used to call the backend of the target subsystem according to the calling request through the entry system.

[0037] A third aspect of the present application provides a computer device, comprising a processor, wherein the processor is configured to implement the system integration method when executing computer-readable instructions stored in a memory.

[0038] A fourth aspect of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon, which implement the system integration method when executed by a processor.

[0039] The present invention obtains a portal system and multiple subsystems to be integrated; registers the multiple subsystems with the portal system; and controls the portal system to load the multiple subsystems. Integrating multiple systems into the portal system enhances the stability of the integrated system. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flow chart of the system integration method provided by an embodiment of the present invention.

[0041] Figure 2 It is a structural diagram of a system integration device provided by an embodiment of the present invention.

[0042] Figure 3 Schematic diagram of a computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0043] In order to more clearly understand the above-mentioned objects, features and advantages of the present invention, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, in the absence of conflict, the embodiments of the present application and the features therein may be combined with each other.

[0044] In the following description, many specific details are set forth to facilitate a full understanding of the present invention. The described embodiments are only some, rather than all, embodiments of the present invention.

[0045] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0046] Preferably, the system integration method of the present invention is applied to one or more computer devices. The computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.

[0047] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.

[0048] Example 1

[0049] Figure 1 The flowchart of the system integration method provided in the first embodiment of the present invention is shown in FIG. The system integration method is applied to computer equipment and is used to integrate multiple systems into an entry system to enhance the stability of the integrated system.

[0050] like Figure 1 As shown, the system integration method includes:

[0051] 101. Obtain an entry system and multiple subsystems to be integrated.

[0052] The portal system is the unified access entrance of the platform, providing functions such as loading routes, managing shared resources, etc. The portal system can be referred to as portal.

[0053] For example, the entrance system is a functional system maintained by the human resources department. It is the entrance to multiple subsystems, which may include the attendance subsystem, salary subsystem, office supplies subsystem, etc.

[0054] 102. Register the multiple subsystems to the portal system.

[0055] Each subsystem has a project configuration file (such as project.config.js), which includes the abbreviation of the subsystem, such as "zhcz-uum". Registering the multiple subsystems with the entry system requires packaging routing files. When packaging routing files, the subsystem determines the file name of the routing file based on the abbreviation of the subsystem, such as "zhcz-uum_router.js". Running the entry system requires loading the routing file in the entry system. When loading the routing file, the entry system finds the corresponding "zhcz-uum_router" file through the "zhcz-uum" configured in the routing list configuration file.

[0056] In a specific embodiment, registering the plurality of subsystems to the portal system includes:

[0057] Get the subsystem name of each subsystem;

[0058] Control each subsystem to package the routing files of each subsystem;

[0059] The name of each subsystem and the file name of each routing file are associated and stored in the entry system.

[0060] The subsystem names of the three subsystems can be obtained, and the subsystem names of the three subsystems are A, B, and C respectively; the routing files of subsystem A, subsystem B, and subsystem C are controlled to be packaged respectively, and the routing file a corresponding to subsystem A, the routing file b corresponding to subsystem B, and the routing file c corresponding to subsystem C are obtained; Aa, Bb, and Cc are associated and stored in the entry system.

[0061] When the entry system starts, the corresponding routing file (js file) is requested through the associated stored information.

[0062] Registering a route enables the entry system to access a specific route address, find the specific page component through the route address in the entry system, and render the content of the page component.

[0063] In a specific embodiment, the controlling each subsystem to package each subsystem's routing file includes:

[0064] Obtain storage variables and routing registration functions of global objects in the entry system;

[0065] Control each subsystem to store the routing file into the storage variable by calling the registration function.

[0066] Each system manages its own code repository, is packaged independently, and is deployed independently. The system's routing files and all code files are deployed on the nginx service. The entry system obtains the corresponding routing files by requesting each system's nginx server and registers them with the entry system's app.

[0067] For example, app.routes = [{Path: " / 101 / user / userManage", Component: function() {}}], app.routes represents the routing file in the storage variable, Path is the routing path, and component is the page to be displayed corresponding to the routing.

[0068] The app object is the global management center object of the entry system, managing common objects required by subsystems, such as the connect function required for program data status and shared business components among subsystems. The app object provides a route registration function. Any subsystem that runs this registration function stores the subsystem's route file in a storage variable. When a subsystem packages its route file, it also includes the route registration function. When the entry system loads the route file, it runs the registration function and indicates that the registration is successful.

[0069] In another embodiment, the system integration method further includes:

[0070] Get the preset routing specification;

[0071] The routing file is defined according to the preset routing specification.

[0072] For example, a route file is defined in a route definition file specified by a preset route specification. In this way, during the subsystem package build, the entry system can load the preset route specification through the preset file entry address and define the route file in the route definition file specified by the preset route specification. The preset route specification includes the writing method of the route, which needs to be distinguished by system code to avoid page pollution caused by different systems using the same route address.

[0073] The routes of the multiple subsystems adopt a registration mechanism. In the project, the business system needs to set all routes that can be accessed by the system according to unified specifications, provide a unified access entry file, and set a unique system identifier. The route entry access file is packaged to a unified location through the webpack packaging tool. In this way, the entry system uses the unique identifier to splice into a specific path to load the route and register it in the global app object. When all routes are loaded, the page can be initialized and presented to the user.

[0074] 103. Control the entry system to load the multiple subsystems.

[0075] Register the multiple subsystems to the portal system, control the portal system to find the page components of the multiple subsystems by loading the routes of the multiple subsystems, and render and display the content of each page component.

[0076] In another embodiment, before controlling the entry system to load the multiple subsystems, the system integration method further includes:

[0077] Detecting subsystems that do not comply with the specification from the multiple subsystems using a webpack plug-in;

[0078] Stop loading the subsystem that does not meet the specifications, and pop up a prompt box to prompt the subsystem that does not meet the specifications.

[0079] By customizing development specifications and using a webpack plugin for detection, we constrain and alert non-compliant front-end code, preventing it from being submitted. We also employ a unified namespace management approach to isolate potentially cross-contaminating code resources. Furthermore, all system components are intercepted by a boundary error component. Any component error only affects that component, not the entire system. This can be checked and alerted using Eslint in the development tools.

[0080] In another embodiment, before controlling the entry system to load the multiple subsystems, the system integration method further includes:

[0081] Obtaining style codes of the multiple subsystems;

[0082] Identify subsystems where style code does not exist in a namespace as subsystems with errors;

[0083] The subsystem with the error is intercepted by a boundary component.

[0084] A unified boundary component is defined, which wraps the subsystem's page components. When any error occurs in the page component, the error will be intercepted by the boundary component and an error message will be displayed, thus avoiding the following situation: the entire system cannot be used normally due to an error in a page component.

[0085] In another embodiment, before intercepting the subsystem with the error by the boundary component, the system integration method further includes:

[0086] Obtain the routing definition file;

[0087] Determining, according to the routing definition file, a subsystem that does not comply with routing specifications as the subsystem with an error;

[0088] Get the preset js code specification file;

[0089] According to the js code specification file, the subsystem that does not comply with the js code specification is determined as the subsystem with error.

[0090] 104. Receive, through the portal system, a call request from a front end of a target subsystem among the multiple subsystems.

[0091] When a user clicks on a target subsystem in a portal system that has registered multiple subsystems, the portal system receives the user's access request to the target subsystem, causing the front end of the target subsystem to make a call request to the back end of the target subsystem through the portal system, and the call request from the front end of the target subsystem is received through the portal system.

[0092] 105. Call the backend of the target subsystem according to the call request through the entry system.

[0093] The entry system forwards the call request to the backend of the target subsystem, so that the backend of the target subsystem returns a call response to the entry system in response to the call request. The entry system forwards the call response to the frontend of the target subsystem, so that the target subsystem is rendered to the current interface and implements the corresponding function.

[0094] When the call request is a page resource request, when the portal system first calls the backend of the target subsystem according to the call request, the portal system obtains the call response from the backend of the target subsystem and caches the call response; when the portal system calls the backend of the target subsystem again according to the call request, the cached call response is returned to the frontend of the target subsystem. The call request for the first call can be the first call subrequest, and the call request for the second call can be the second call subrequest, that is, the two call requests can be different call requests issued by different subsystems.

[0095] In another embodiment, the system integration method further includes:

[0096] Performing resource deduplication processing on the multiple subsystems;

[0097] Unused codes in the plurality of subsystems are deleted.

[0098] The multiple subsystems may have overlapping functions, causing the multiple subsystems to reference the same static resource files, such as third-party JavaScript libraries and CSS style sheets. At this time, the resource files of the multiple subsystems are scanned by the entry system, and duplicate files are filtered out by the Hash algorithm, thereby reducing the number of requests for resource files. For the target file after deduplication processing, the code file in the target file is subjected to code static analysis by the entry system to find unused codes such as defined and unused variables, functions, objects, modules, etc., and delete the unused codes. This achieves the effect of reducing the size of dependent resources and optimizing the network transmission of data packets.

[0099] The system integration method of embodiment 1 obtains a portal system and multiple subsystems to be integrated; registers the multiple subsystems with the portal system; and controls the portal system to load the multiple subsystems. Integrating multiple systems into the portal system enhances the stability of the integrated system.

[0100] Example 2

[0101] Figure 2 2 is a structural diagram of a system integration device provided in a second embodiment of the present invention. The system integration device 20 is applied to computer equipment. The system integration device 20 is used to integrate multiple systems into a portal system to enhance the stability of the integrated system.

[0102] like Figure 2 As shown, the system integration device 20 may include an acquisition module 201 , a registration module 202 , a loading module 203 , a receiving module 204 , and a calling module 205 .

[0103] The acquisition module 201 is used to acquire the entry system and multiple subsystems to be integrated.

[0104] The portal system is the unified access entrance of the platform, providing functions such as loading routes, managing shared resources, etc. The portal system can be referred to as portal.

[0105] For example, the entrance system is a functional system maintained by the human resources department. It is the entrance to multiple subsystems, which may include the attendance subsystem, salary subsystem, office supplies subsystem, etc.

[0106] The registration module 202 is configured to register the plurality of subsystems with the portal system.

[0107] Each subsystem has a project configuration file (such as project.config.js), which includes the abbreviation of the subsystem, such as "zhcz-uum". Registering the multiple subsystems with the entry system requires packaging routing files. When packaging routing files, the subsystem determines the file name of the routing file based on the abbreviation of the subsystem, such as "zhcz-uum_router.js". Running the entry system requires loading the routing file in the entry system. When loading the routing file, the entry system finds the corresponding "zhcz-uum_router" file through the "zhcz-uum" configured in the routing list configuration file.

[0108] In a specific embodiment, registering the plurality of subsystems to the portal system includes:

[0109] Get the subsystem name of each subsystem;

[0110] Control each subsystem to package the routing files of each subsystem;

[0111] The name of each subsystem and the file name of each routing file are associated and stored in the entry system.

[0112] The subsystem names of the three subsystems can be obtained, and the subsystem names of the three subsystems are A, B, and C respectively; the routing files of subsystem A, subsystem B, and subsystem C are controlled to be packaged respectively, and the routing file a corresponding to subsystem A, the routing file b corresponding to subsystem B, and the routing file c corresponding to subsystem C are obtained; Aa, Bb, and Cc are associated and stored in the entry system.

[0113] When the entry system starts, the corresponding routing file (js file) is requested through the associated stored information.

[0114] Registering a route enables the entry system to access a specific route address, find the specific page component through the route address in the entry system, and render the content of the page component.

[0115] In a specific embodiment, the control of each subsystem to package each subsystem's routing file includes:

[0116] Obtain storage variables and routing registration functions of global objects in the entry system;

[0117] Control each subsystem to store the routing file into the storage variable by calling the registration function.

[0118] Each system manages its own code repository, is packaged independently, and is deployed independently. The system's routing files and all code files are deployed on the nginx service. The entry system obtains the corresponding routing files by requesting each system's nginx server and registers them with the entry system's app.

[0119] For example, app.routes = [{Path: " / 101 / user / userManage", Component: function() {}}], app.routes represents the routing file in the storage variable, Path is the routing path, and component is the page to be displayed corresponding to the routing.

[0120] The app object is the global management center object of the entry system, managing common objects required by subsystems, such as the connect function required for program data status and shared business components among subsystems. The app object provides a route registration function. Any subsystem that runs this registration function stores the subsystem's route file in a storage variable. When a subsystem packages its route file, it also includes the route registration function. When the entry system loads the route file, it runs the registration function and indicates that the registration is successful.

[0121] In another embodiment, the system integration device 20 further includes a definition module for obtaining a preset routing specification;

[0122] The routing file is defined according to the preset routing specification.

[0123] For example, a route file is defined in a route definition file specified by a preset route specification. In this way, during the subsystem package build, the entry system can load the preset route specification through the preset file entry address and define the route file in the route definition file specified by the preset route specification. The preset route specification includes the writing method of the route, which needs to be distinguished by system code. The purpose of this distinction is to avoid page pollution caused by different systems using the same route address.

[0124] The routes of the multiple subsystems adopt a registration mechanism. In the project, the business system needs to set all routes that can be accessed by the system according to unified specifications, provide a unified access entry file, and set a unique system identifier. The route entry access file is packaged to a unified location through the webpack packaging tool. In this way, the entry system uses the unique identifier to splice into a specific path to load the route and register it in the global app object. When all routes are loaded, the page can be initialized and presented to the user.

[0125] The loading module 203 is used to control the entry system to load the multiple subsystems.

[0126] Register the multiple subsystems to the portal system, control the portal system to find the page components of the multiple subsystems by loading the routes of the multiple subsystems, and render and display the content of each page component.

[0127] In another embodiment, before controlling the entry system to load the plurality of subsystems, the system integration device 20 further includes a stopping module for detecting a subsystem that does not meet the specification from the plurality of subsystems through a webpack plug-in;

[0128] Stop loading the subsystem that does not meet the specifications, and pop up a prompt box to prompt the subsystem that does not meet the specifications.

[0129] By customizing development specifications and using a webpack plugin for detection, we constrain and alert non-compliant front-end code, preventing it from being submitted. We also employ a unified namespace management approach to isolate potentially cross-contaminating code resources. Furthermore, all system components are intercepted by a boundary error component. Any component error only affects that component, not the entire system. This can be checked and alerted using Eslint in the development tools.

[0130] In another embodiment, before controlling the entry system to load the plurality of subsystems, the system integration device 20 further includes an interception module for obtaining style codes of the plurality of subsystems;

[0131] Identify subsystems where the style code does not exist in the namespace as subsystems with errors;

[0132] The subsystem with the error is intercepted by a boundary component.

[0133] Define a unified boundary component that wraps the subsystem's page components. When any errors occur in the page components, they are intercepted by the boundary component and an error message is displayed. This prevents a single page component error from rendering the entire system unusable.

[0134] In another embodiment, before intercepting the subsystem with the error by the boundary component, the system integration device 20 further includes a determination module for determining the subsystem that does not comply with the routing specification as the subsystem with the error according to the routing definition file;

[0135] Get the preset js code specification file;

[0136] According to the js code specification file, the subsystem that does not comply with the js code specification is determined as the subsystem with error.

[0137] The receiving module 204 is configured to receive, through the portal system, a call request from a front end of a target subsystem among the multiple subsystems.

[0138] When a user clicks on a target subsystem in a portal system that has registered multiple subsystems, the portal system receives the user's access request to the target subsystem, causing the front end of the target subsystem to make a call request to the back end of the target subsystem through the portal system, and the call request from the front end of the target subsystem is received through the portal system.

[0139] The calling module 205 is configured to call the backend of the target subsystem according to the calling request through the entry system.

[0140] The entry system forwards the call request to the backend of the target subsystem, so that the backend of the target subsystem returns a call response to the entry system in response to the call request. The entry system forwards the call response to the frontend of the target subsystem, so that the target subsystem is rendered to the current interface and implements the corresponding function.

[0141] When the call request is a page resource request, when the portal system first calls the backend of the target subsystem according to the call request, the portal system obtains the call response from the backend of the target subsystem and caches the call response; when the portal system calls the backend of the target subsystem again according to the call request, the cached call response is returned to the frontend of the target subsystem. The call request for the first call can be the first call subrequest, and the call request for the second call can be the second call subrequest, that is, the two call requests can be different call requests issued by different subsystems.

[0142] In another embodiment, the system integration device 20 further includes a deletion module for performing resource deduplication processing on the multiple subsystems;

[0143] Unused codes in the plurality of subsystems are deleted.

[0144] The multiple subsystems may have overlapping functions, causing the multiple subsystems to reference the same static resource files, such as third-party JavaScript libraries and CSS style sheets. At this time, the resource files of the multiple subsystems are scanned by the entry system, and duplicate files are filtered out by the Hash algorithm, thereby reducing the number of requests for resource files. For the target file after deduplication processing, the code file in the target file is subjected to code static analysis by the entry system to find unused codes such as defined and unused variables, functions, objects, modules, etc., and delete the unused codes. This achieves the effect of reducing the size of dependent resources and optimizing the network transmission of data packets.

[0145] The system integration device 20 of the second embodiment obtains a portal system and multiple subsystems to be integrated; registers the multiple subsystems with the portal system; and controls the portal system to load the multiple subsystems. Integrating multiple systems into the portal system enhances the stability of the integrated system.

[0146] Example 3

[0147] This embodiment provides a computer-readable storage medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor, the steps in the above-mentioned system integration method embodiment are implemented, such as Figure 1 Steps 101-105 shown:

[0148] 101, obtaining an entry system and multiple subsystems to be integrated;

[0149] 102, registering the multiple subsystems to the portal system;

[0150] 103, controlling the entry system to load the multiple subsystems;

[0151] 104. Receive, through the portal system, a call request from a front end of a target subsystem among the multiple subsystems;

[0152] 105. Call the backend of the target subsystem according to the call request through the entry system.

[0153] Alternatively, when the computer-readable instructions are executed by the processor, the functions of the modules in the above-mentioned device embodiment are realized, for example Figure 2 Modules 201-205:

[0154] An acquisition module 201 is used to acquire an entry system and multiple subsystems to be integrated;

[0155] a registration module 202 for registering the plurality of subsystems to the portal system;

[0156] A loading module 203, configured to control the entry system to load the multiple subsystems;

[0157] A receiving module 204 is configured to receive a call request from a front end of a target subsystem in the plurality of subsystems through the entry system;

[0158] The calling module 205 is configured to call the backend of the target subsystem according to the calling request through the entry system.

[0159] Example 4

[0160] Figure 3Schematic diagram of a computer device provided in Embodiment 3 of the present invention. The computer device 30 includes a memory 301, a processor 302, and computer-readable instructions 303 stored in the memory 301 and executable on the processor 302, such as a system integration program. When the processor 302 executes the computer-readable instructions 303, the steps in the above-mentioned system integration method embodiment are implemented, such as Figure 1 101-105 shown:

[0161] 101, obtaining an entry system and multiple subsystems to be integrated;

[0162] 102, registering the multiple subsystems to the portal system;

[0163] 103, controlling the entry system to load the multiple subsystems;

[0164] 104. Receive, through the portal system, a call request from a front end of a target subsystem among the multiple subsystems;

[0165] 105. Call the backend of the target subsystem according to the call request through the entry system.

[0166] Alternatively, when the computer-readable instructions are executed by the processor, the functions of the modules in the above-mentioned device embodiment are realized, for example Figure 2 Modules 201-205:

[0167] An acquisition module 201 is used to acquire an entry system and multiple subsystems to be integrated;

[0168] a registration module 202 for registering the plurality of subsystems to the portal system;

[0169] A loading module 203, configured to control the entry system to load the multiple subsystems;

[0170] A receiving module 204 is configured to receive a call request from a front end of a target subsystem in the plurality of subsystems through the entry system;

[0171] The calling module 205 is configured to call the backend of the target subsystem according to the calling request through the entry system.

[0172] Exemplarily, the computer-readable instructions 303 may be divided into one or more modules, which are stored in the memory 301 and executed by the processor 302 to complete the method. The one or more modules may be a series of computer-readable instruction segments capable of completing specific functions, which are used to describe the execution process of the computer-readable instructions 303 in the computer device 30. For example, the computer-readable instructions 303 may be divided into Figure 2 For the acquisition module 201, registration module 202, loading module 203, receiving module 204, and calling module 205, please refer to the second embodiment for the specific functions of each module.

[0173] Those skilled in the art will understand that the schematic Figure 3 This is merely an example of the computer device 30 and does not constitute a limitation of the computer device 30 . The computer device 30 may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the computer device 30 may also include input and output devices, network access devices, buses, etc.

[0174] The processor 302 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor 302 may be any conventional processor. The processor 302 is the control center of the computer device 30 and connects various parts of the entire computer device 30 using various interfaces and lines.

[0175] The memory 301 can be used to store the computer-readable instructions 303. The processor 302 implements various functions of the computer device 30 by running or executing the computer-readable instructions or modules stored in the memory 301 and calling the data stored in the memory 301. The memory 301 may mainly include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function (such as a sound playback function, an image playback function, etc.); the data storage area may store data created based on the use of the computer device 30. In addition, the memory 301 may include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a SmartMedia Card (SMC), a Secure Digital (SD) card, a flash card, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0176] If the module integrated in the computer device 30 is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when the computer-readable instructions are executed by the processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer-readable instructions include computer-readable instruction codes, and the computer-readable instruction codes can be in source code form, object code form, executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device that can carry the computer-readable instruction code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory).

[0177] In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the module division is merely a logical functional division, and actual implementation may employ other division methods.

[0178] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0179] In addition, the functional modules in various embodiments of the present invention may be integrated into a single processing module, each module may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or hardware plus software functional modules.

[0180] The integrated modules implemented in the form of software functional modules can be stored in a computer-readable storage medium. The software functional modules stored in the storage medium include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the system integration method described in various embodiments of the present invention.

[0181] It is obvious to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the invention is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims be included in the present invention. Any accompanying figure marks in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other modules or steps, and the singular does not exclude the plural. Multiple modules or devices stated in the system claims may also be implemented by one module or device through software or hardware. Words such as first and second are used to indicate names and do not indicate any particular order.

[0182] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not limiting. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A system integration method, characterized in that: The system integration method comprises: Obtain the entry system and multiple subsystems to be integrated; registering the plurality of subsystems to the portal system; controlling the entry system to load the plurality of subsystems; Receiving, through the entry system, a call request from a front end of a target subsystem in the plurality of subsystems; The backend of the target subsystem is called according to the call request by the entry system, including: when the call request is a page resource request, when the backend of the target subsystem is called for the first time according to the call request by the entry system, a call response is obtained from the backend of the target subsystem through the entry system, and the call response is cached; when the backend of the target subsystem is called again according to the call request by the entry system, the call response is returned to the front end of the target subsystem, wherein the call request for the first call includes a first call sub-request, and the call request for the second call includes a second call sub-request.

2. The system integration method according to claim 1, wherein: Registering the plurality of subsystems to the portal system includes: Get the subsystem name of each subsystem; Control each subsystem to package the routing files of each subsystem; The name of each subsystem and the file name of each routing file are associated and stored in the entry system.

3. The system integration method according to claim 2, wherein: The control of each subsystem to package each subsystem's routing file includes: Obtain storage variables and routing registration functions of global objects in the entry system; Control each subsystem to store the routing file into the storage variable by calling the registration function.

4. The system integration method according to claim 3, wherein: The system integration method further includes: Get the preset routing specification; The routing file is defined according to the preset routing specification.

5. The system integration method according to any one of claims 1 to 4, characterized in that: Before controlling the entry system to load the multiple subsystems, the system integration method further includes: Detecting subsystems that do not comply with the specification from the multiple subsystems using a webpack plug-in; Stop loading the subsystem that does not meet the specifications, and pop up a prompt box to prompt the subsystem that does not meet the specifications.

6. The system integration method according to any one of claims 1 to 4, characterized in that: Before controlling the entry system to load the multiple subsystems, the system integration method further includes: Obtaining style codes of the multiple subsystems; Identify subsystems where the style code does not exist in the namespace as subsystems with errors; The subsystem with the error is intercepted by a boundary component.

7. The system integration method according to any one of claims 1 to 4, characterized in that: The system integration method further includes: performing resource deduplication processing on the multiple subsystems; Unused codes in the plurality of subsystems are deleted.

8. A system integration device, characterized in that: The system integration device includes: An acquisition module, used to acquire the entry system and multiple subsystems to be integrated; a registration module, configured to register the plurality of subsystems with the portal system; A loading module, configured to control the entry system to load the multiple subsystems; A receiving module, configured to receive, through the entry system, a call request from a front end of a target subsystem among the multiple subsystems; A calling module, for calling the backend of the target subsystem according to the calling request through the entry system, including: when the calling request is a page resource request, when the backend of the target subsystem is called for the first time through the entry system according to the calling request, obtaining a calling response from the backend of the target subsystem through the entry system and caching the calling response, and when the backend of the target subsystem is called again through the entry system according to the calling request, returning the calling response to the frontend of the target subsystem, wherein the calling request for the first call includes a first calling sub-request, and the calling request for the second call includes a second calling sub-request.

9. A computer device, characterized in that: The computer device includes a processor configured to execute computer-readable instructions stored in a memory to implement the system integration method according to any one of claims 1 to 7.

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

Images