Portal system construction method and device, electronic equipment and storage medium
By converting heterogeneous menu data into a standard menu table and integrating access menus in the portal system, the problem of heterogeneous data integration is solved, and low-cost and efficient cross-system unified authentication and data storage are achieved.
Patent Information
- Application Number
- CN202510628268.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-15
- Publication Date
- 2025-09-05
AI Technical Summary
Existing technologies are unable to effectively centrally store heterogeneous data and integrate menu data from heterogeneous systems into the portal system, resulting in service integration differentiation problems and high costs.
By acquiring heterogeneous menu data from access systems, converting them into standard menu tables based on standardized data structures, and integrating access menus into basic portal systems, unified cross-system authentication is achieved using standardized data structures and integration frameworks.
It realizes the centralized storage and unified authentication of heterogeneous data, reduces the cost and complexity of service integration, and ensures the consistency of permissions and functions between the portal system and the access system.
Smart Images

Figure CN120596086A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device, and storage medium for constructing a portal system. Background Art
[0002] As enterprise businesses continue to expand, the demand for enterprise portals from both internal employees and external partners is also growing. Enterprise portals improve employee productivity and ensure the security of corporate information. For enterprises, a portal system that centrally stores heterogeneous model data and implements unified authentication services is becoming increasingly important. Furthermore, the heterogeneous systems connected to the portal system each have their own unique system architectures, interface formats, and interface fields. These differences pose significant challenges and costs for service integration, necessitating a low-cost, standardized, and efficient solution to address these differences.
[0003] Therefore, there is an urgent need for a method for constructing a portal system that can centrally store heterogeneous menu data and integrate the menu data of heterogeneous systems into the portal system. Summary of the Invention
[0004] In view of this, the present application proposes a method, device, electronic device and storage medium for constructing a portal system, aiming to solve the problem in current technology that heterogeneous data cannot be centrally stored and menu data of heterogeneous systems cannot be integrated into the portal system.
[0005] In the first aspect, the present application provides a method for constructing a portal system, including: obtaining heterogeneous menu data of a target function of an access system; the heterogeneous menu data includes: menu information and access permission information; the access permission information represents the access permissions of users of different levels to the target function; based on a standardized data structure, the heterogeneous menu data is converted into a standard menu table; based on the standard menu table, an access menu for the target function of the access system is integrated into the basic portal system.
[0006] In some embodiments, the standard menu table includes: function menu parameters and access permission parameters; the function menu parameters are obtained by performing a standardized conversion based on menu information; and the access permission parameters are obtained by performing a standardized conversion based on access permission information.
[0007] In some embodiments, obtaining heterogeneous menu data of a target function of an access system includes: obtaining heterogeneous menu data of a target function of an access system based on an integration framework; wherein the integration framework includes a first mode integration framework and a second mode integration framework.
[0008] In some embodiments, the first mode integration framework includes: a general data acquisition interface and a heterogeneous data acquisition interface; when the integration framework is the first mode integration framework, obtaining the heterogeneous menu data of the target function of the access system includes: determining whether the data structure of the heterogeneous menu data of the access system is the same as the data structure of the menu data of the basic portal system; if so, obtaining the heterogeneous menu data of the access system based on the general data acquisition interface; if not, obtaining the heterogeneous menu data of the access system based on the heterogeneous data acquisition interface.
[0009] In some embodiments, the second mode integration framework includes: a standard acquisition interface; when the integration framework is the second mode integration framework, obtaining heterogeneous menu data of the target function of the access system includes: obtaining heterogeneous menu data sent by the access system calling the standard acquisition interface.
[0010] In some embodiments, before obtaining heterogeneous menu data of the target function of the access system, the method also includes: obtaining application loader information of the access system; traversing the applications of the access system based on the application loader information to determine available applications; and determining the functions covered by the available applications as the target functions.
[0011] In a second aspect, a construction device for a portal system is provided, including an acquisition unit and a processing unit; the acquisition unit is used to acquire heterogeneous menu data of a target function of an access system; the heterogeneous menu data includes: menu information and access permission information; the access permission information represents the access permissions of users of different levels to the target function; the processing unit is used to convert the heterogeneous menu data into a standard menu table based on a standardized data structure; the processing unit is also used to integrate an access menu for the target function of the access system in the basic portal system based on the standard menu table.
[0012] In a third aspect, an electronic device is provided, comprising a memory and a processor; the memory is used to store computer-executable instructions, and the processor is connected to the memory via a bus; when the electronic device is running, the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes any one of the methods provided in the first aspect.
[0013] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including computer execution instructions, which, when executed on a computer, causes the computer to execute any one of the methods provided in the first aspect.
[0014] In a fifth aspect, a computer program product is provided, the computer program product comprising: computer execution instructions, which, when executed on an electronic device, cause the electronic device to execute any one of the methods provided in the first aspect above.
[0015] It should be noted that the above-mentioned computer-executable instructions may be stored in whole or in part on a computer-readable storage medium. The computer-readable storage medium may be packaged together with the processor of the electronic device or separately from the processor of the electronic device, and this embodiment of the application is not limited to this.
[0016] The description of the second, third, fourth and fifth aspects of this application can refer to the detailed description of the first aspect.
[0017] In the embodiments of this application, the names of the aforementioned portal system building devices do not limit the devices or functions themselves. In actual implementation, these devices or functional modules may appear with other names. For example, the processing unit may also be called a processing module, a processor, etc. As long as the functions of each device or functional module are similar to those of this application, they are within the scope of the claims of this application and their equivalents.
[0018] This application obtains heterogeneous menu data for the target functions of the access system and converts the heterogeneous menu data into a standard menu table based on a standardized data structure. Based on the standard menu table, an access menu for the target functions of the access system is integrated into the basic portal system. By converting the heterogeneous menu data into a standard menu table, heterogeneous data from different access systems can be stored simultaneously. This allows the access menu for the target functions of the access system to be integrated into the basic portal system, allowing the portal system to access the menu data of the access system and achieve unified authentication across systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0020] Figure 1 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;
[0021] Figure 2 A flowchart of a method for constructing a portal system provided in an embodiment of the present application;
[0022] Figure 3 A schematic diagram of a pull mode integration framework provided in an embodiment of the present application;
[0023] Figure 4 A schematic diagram of a push mode integration framework provided in an embodiment of the present application;
[0024] Figure 5A flowchart of another method for constructing a portal system provided in an embodiment of the present application;
[0025] Figure 6 A schematic diagram of the structure of a portal system construction device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0027] In the description of this application, it should be understood that the terms "upper," "lower," "left," "right," "front," "back," "inner," "outer," and the like, indicating directions or positional relationships, are based on the directions or relative positional relationships shown in the accompanying drawings and are intended solely to facilitate the description of this application and simplify the description. They do not indicate or imply that the devices or components referred to must have a specific direction, be constructed, or operate in a specific direction. Therefore, they should not be construed as limitations on this application. Unless otherwise specified, the above-mentioned directionality descriptions may be flexibly set in actual application, provided that the relative positional relationships shown in the accompanying drawings are met.
[0028] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature specified as "first" or "second" may explicitly or implicitly include one or more of such features. Throughout this application, unless otherwise specified, "plurality" means two or more.
[0029] In the embodiments of the present application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, article, or device comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of other identical elements in the process, article, or device comprising the element.
[0030] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.
[0031] In the description of this specification, specific features, structures, materials or characteristics may be combined in an appropriate manner in any one or more embodiments or examples.
[0032] A portal system is an application framework that integrates various application systems, data resources, and internet resources into an information management platform, providing users with a unified user interface. It enables enterprises to quickly establish information channels between customers, employees, and other businesses, allowing them to release a wide range of internal information.
[0033] The portal system allows for quick access to various applications, requiring each application's system to be connected to the portal system. Each system has its own authentication service, and cross-system access from the portal system may require the user password of the access system, so authentication must be established between the portal system and all access systems.
[0034] At the same time, each system has its own data model, including basic data such as users, organizations, permissions, menus, etc., which will be used in the access from the portal system to the access system. In order to achieve functional-level access, it is necessary to synchronize and transform these heterogeneous models for centralized storage and query to ensure that the permissions and functional views of the portal system are consistent with those of the access system.
[0035] Each system has its own unique system architecture, interface format, interface fields, etc. This difference poses a huge challenge and cost for service integration, requiring a low-cost, standardized, and efficient solution to the problem of differentiated service integration.
[0036] Therefore, it is necessary to build a standardized integration framework to centrally store the menu data of multiple heterogeneous systems in the portal system and realize cross-system access based on a unified identity authentication service to avoid separate authentication development for each system.
[0037] In this case, an embodiment of the present application provides a method for constructing a portal system, including: obtaining heterogeneous menu data of a target function of an access system; the heterogeneous menu data includes: menu information and access permission information; the access permission information represents the access permissions of users of different levels to the target function; based on a standardized data structure, the heterogeneous menu data is converted into a standard menu table; based on the standard menu table, an access menu for the target function of the access system is integrated into the basic portal system.
[0038] As can be seen from the above, the present application obtains the heterogeneous menu data of the target function of the access system, converts the heterogeneous menu data into a standard menu table based on a standardized data structure, and integrates the access menu for the target function of the access system into the basic portal system based on the standard menu table. Based on this, by converting the heterogeneous menu data into a standard menu table, the heterogeneous data of different access systems can be stored simultaneously. In this way, the access menu for the target function of the access system can be integrated into the basic portal system, so that the menu data of the access system can be accessed through the portal system, and unified authentication across systems can be achieved.
[0039] like Figure 1 FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application, wherein the electronic device includes a processor 11, a memory 12, a communication interface 13, and a bus 14. The processor 11, the memory 12, and the communication interface 13 may be connected via the bus 14.
[0040] The processor 11 is the control center of the electronic device and can be a single processor or a collective term for multiple processing elements. For example, the processor 11 can be a general-purpose central processing unit (CPU) or other general-purpose processor. The general-purpose processor can be a microprocessor or any conventional processor.
[0041] As an embodiment, the processor 11 may include one or more CPUs, such as Figure 1 CPU 0 and CPU 1 are shown in Figure 1.
[0042] The memory 12 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
[0043] In one possible implementation, memory 12 can exist independently of processor 11 and can be connected to processor 11 via bus 14 to store instructions or program code. When processor 11 calls and executes the instructions or program code stored in memory 12, the portal architecture method provided in the following embodiments of this application can be implemented.
[0044] In another possible implementation, the memory 12 may also be integrated with the processor 11 .
[0045] The communication interface 13 is used to connect the electronic device to other devices via a communication network, which may be Ethernet, wireless access network, wireless local area network (WLAN), etc. The communication interface 13 may include a receiving unit for receiving data and a sending unit for sending data.
[0046] The bus 14 may be an ISA bus, a PCI bus, or an EISA bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, Figure 1 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.
[0047] It should be pointed out that Figure 1 The structure shown in the figure does not constitute a limitation on the electronic device, except Figure 1 In addition to the components shown, the electronic device may include more or fewer components than shown, or combine certain components, or arrange the components differently.
[0048] The following is a detailed description of the method for constructing the portal system provided in the embodiment of the present application with reference to the accompanying drawings.
[0049] Figure 2 This is a flow chart of a method for constructing a portal system according to an exemplary embodiment. Exemplarily, the method can be applied to electronic devices, and the method steps include the following S201-S203.
[0050] S201: Obtain heterogeneous menu data of a target function of an access system.
[0051] The heterogeneous menu data includes menu information and access permission information; the access permission information represents the access permissions of users of different levels to the target function.
[0052] In an embodiment of the present application, when accessing a portal system, it is necessary to centrally store the menu information and access permission information of the access system, so as to ensure that the permissions of the portal system and the access system remain consistent.
[0053] S202: Based on the standardized data structure, convert the heterogeneous menu data into a standard menu table.
[0054] Among them, the standardized data structure is provided by the portal system and is used to convert heterogeneous menu data into a standard menu table.
[0055] It should be noted that since access systems have their own unique system architecture, when integrating the access system into the portal system, it is necessary to convert the heterogeneous menu data of the access system into a standard menu table and store the standard menu table in the portal system to solve the problem of differentiation of heterogeneous systems.
[0056] Specifically, a unified standardized data structure is provided for different access systems. When heterogeneous menu data of the access system is obtained, the menu data and access permission data of the access system are converted into a standard menu table for unified storage, so as to realize the unified storage of menus according to user level, user corresponding permission and user accessible menus.
[0057] In a possible implementation, the standard menu table includes: function menu parameters and access permission parameters; the function menu parameters are obtained by performing a standardized conversion based on menu information; and the access permission parameters are obtained by performing a standardized conversion based on access permission information.
[0058] The function menu parameters may include the source system of the menu, menu name, menu address, menu level, parent menu, menu ID, etc. The access permission parameters may include menu accessible user information, user permission information, etc.
[0059] S203: Based on the standard menu table, an access menu for the target function of the access system is integrated into the basic portal system.
[0060] In an embodiment of the present application, after obtaining the standard menu table of the access system, an access menu for the target function of the access system can be integrated into the basic portal system, thereby obtaining a new portal system. The new portal system is integrated with the access system, allowing users to directly access the access system's menu and other data in the portal system.
[0061] Specifically, after the access menu for the target function of the access system is integrated into the basic portal system, the user can see and access the access menu for the target function of the access system in the portal system. In response to the user clicking the access menu for the target function of the access system in the portal system, the user can normally jump to the corresponding access menu interface of the access system.
[0062] As can be seen from the above, the present application obtains the heterogeneous menu data of the target function of the access system, converts the heterogeneous menu data into a standard menu table based on a standardized data structure, and integrates the access menu for the target function of the access system into the basic portal system based on the standard menu table. Based on this, by converting the heterogeneous menu data into a standard menu table, the heterogeneous data of different access systems can be stored simultaneously. In this way, the access menu for the target function of the access system can be integrated into the basic portal system, so that the menu data of the access system can be accessed through the portal system, and unified authentication across systems can be achieved.
[0063] In some embodiments of the present application, obtaining heterogeneous menu data of the target function of the access system may specifically include: obtaining heterogeneous menu data of the target function of the access system based on an integration framework; wherein the integration framework includes a first mode integration framework and a second mode integration framework.
[0064] Specifically, the portal system may periodically obtain heterogeneous menu data of the target function of the access system through the integration framework, and when the heterogeneous menu data of the target function of the access system changes, it may be synchronized to the portal system.
[0065] It can be seen that through the integration framework, the heterogeneous menus of the target functions of the access system can be accurately obtained, thereby laying a foundation for integrating the access menus of the target functions of the access system into the basic portal system.
[0066] In some embodiments of the present application, the first mode integration framework may include: a general data acquisition interface and a heterogeneous data acquisition interface; when the integration framework is the first mode integration framework, obtaining the heterogeneous menu data of the target function of the access system may specifically include: determining whether the data structure of the heterogeneous menu data of the access system is the same as the data structure of the menu data of the basic portal system; if so, obtaining the heterogeneous menu data of the access system based on the general data acquisition interface; if not, obtaining the heterogeneous menu data of the access system based on the heterogeneous data acquisition interface.
[0067] For example, the first mode framework may be a pull mode integration framework. Figure 3 , which is a schematic diagram of a pull mode integration framework provided in an embodiment of the present application.
[0068] Among them, the general data acquisition interface can be Figure 3 The general integration implementation in ; heterogeneous data acquisition interface can be Figure 3 The access system integration is realized in .
[0069] The scheduling center is used to schedule the universal integration framework and trigger the data pulling process. For example, a scheduled task can be set to trigger the data pulling process and obtain the standard menu table of the access system.
[0070] The universal integration framework provides a unified framework and interface for access systems, responding to dispatch requests from the dispatch center. The universal integration framework includes both universal integration implementations and access system integration implementations. The universal integration implementation serves as the universal, default integration implementation, enabling most access systems to pull data. Access systems that cannot use the universal integration implementation must re-establish their own integration framework to pull data.
[0071] The general integration framework may also include a field mapping configuration for mapping the standard fields provided by the general integration framework with the original fields of the access system to support configuration implementation.
[0072] In an embodiment of the present application, in the process of using the pull mode integration framework to obtain menu data of the access system, the task log can be recorded through the integration process record, or the number of reports, time, data volume, etc. can be recorded to ensure that the process of obtaining data can be tracked, monitored and audited.
[0073] The access system primarily includes a standard HTTP collection interface, which is used to call different access systems using standard protocols and fields and collect menu data from these access systems. When the portal system triggers the data pull process, the access system can query incremental menu and permission data through the standard HTTP collection interface. For example, SQL statements can be used for querying.
[0074] In an embodiment of the present application, an integrated service framework can be used to provide a unified interface, and when a query request from an http standard collection interface is received, data increments are provided for the http annotation collection interface.
[0075] From the above, we can see that by determining whether the data structure of the heterogeneous menu data of the access system is the same as that of the menu data of the basic portal system, different data collection interfaces are selected to obtain the heterogeneous menu data of the access system. In this way, the heterogeneous menu data of the access system can be accurately obtained.
[0076] In some embodiments of the present application, the second mode integration framework includes: a standard acquisition interface; when the integration framework is the second mode integration framework, obtaining heterogeneous menu data of the target function of the access system includes: obtaining heterogeneous menu data sent by the access system calling the standard acquisition interface.
[0077] Exemplarily, the second mode integration framework may be a push mode integration framework. Figure 4 , which is a schematic diagram of a push mode integration framework provided in an embodiment of the present application.
[0078] Among them, the standard acquisition interface can be Figure 4 The http reporting interface in.
[0079] The standard HTTP reporting interface is used to obtain menu data reported by the access system and send the data to the data reporting control. The data reporting control is used to control the data reporting logic and ensure the change of permission increment and menu increment.
[0080] The http reporting interface of the access system is used to actively report data such as the access system's permission increment and menu increment directly to the portal system, without the portal system actively obtaining it.
[0081] In an embodiment of the present application, the push mode integration framework also supports recording task logs through an integrated process recording module, or recording the number of reports, time, data volume, etc., to ensure that the process of obtaining data can be tracked, monitored and audited.
[0082] In an embodiment of the present application, when integrating an access menu for a target function of an access system into a basic portal system, a pull-mode integration framework or a push-mode integration framework can be used. The specific integration framework to be used is selected by the access system. When the data of the access system changes frequently, a push-mode integration framework can be selected; when the data of the access system changes infrequently, a pull-mode integration framework can be selected.
[0083] From the above, we can see that by directly acquiring the heterogeneous menu data sent by the access system calling the standard collection interface, the heterogeneous menu data can be accurately and comprehensively acquired, laying the foundation for subsequent integration operations.
[0084] See also Figure 5 , which is a flow chart of another method for constructing a portal system provided by an embodiment of the present application. Before obtaining heterogeneous menu data of a target function of the access system, the method may further include:
[0085] S501: Obtain application loader information of the access system.
[0086] The application loader information includes all applications connected to the system.
[0087] For example, a scheduled task may be set to periodically obtain information about the application loader accessing the system, so as to achieve the purpose of timely data update.
[0088] S502: Traverse the applications connected to the system based on the application loader information to determine available applications.
[0089] Specifically, after obtaining the application loader information, the system traverses the applications connected to the system, screens and filters out unavailable applications, and thereby determines available applications, wherein available applications refer to applications that can be normally accessed.
[0090] S503: Determine the functions covered by the available applications as target functions.
[0091] Specifically, after determining the available applications, since the portal system can obtain the heterogeneous menu data of the access system in a timely manner, the functions covered by the available applications can be determined as target functions.
[0092] As can be seen above, after obtaining the access system's application loader information, the system's applications are traversed based on the application loader information to determine available applications, and the functions covered by the available applications are determined as target functions. This allows for real-time and accurate acquisition of the access system's target functions, laying the foundation for subsequently integrating the target function's access menu into the basic portal system.
[0093] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0094] In the embodiment of the present application, the construction device of the portal system can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software functional modules. Optionally, the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.
[0095] like Figure 6 FIG. 1 is a schematic diagram of a structure of a portal system construction device provided in an embodiment of the present application. Figure 6 The device shown includes: an acquisition unit 601 and a processing unit 602.
[0096] The acquisition unit 601 is used to obtain heterogeneous menu data of the target function of the access system; the heterogeneous menu data includes: menu information and access permission information; the access permission information represents the access permissions of users of different levels to the target function; the processing unit 602 is used to convert the heterogeneous menu data into a standard menu table based on a standardized data structure; the processing unit 602 is also used to integrate an access menu for the target function of the access system in the basic portal system based on the standard menu table.
[0097] Optionally, obtaining heterogeneous menu data of a target function of the access system includes: obtaining heterogeneous menu data of the target function of the access system based on an integration framework; wherein the integration framework includes a first mode integration framework and a second mode integration framework.
[0098] Optionally, the first mode integration framework includes: a general data acquisition interface and a heterogeneous data acquisition interface; when the integration framework is the first mode integration framework, obtaining the heterogeneous menu data of the target function of the access system includes: determining whether the data structure of the heterogeneous menu data of the access system is the same as the data structure of the menu data of the basic portal system; if so, obtaining the heterogeneous menu data of the access system based on the general data acquisition interface; if not, obtaining the heterogeneous menu data of the access system based on the heterogeneous data acquisition interface.
[0099] Optionally, the second mode integration framework includes: a standard acquisition interface; when the integration framework is the second mode integration framework, obtaining heterogeneous menu data of the target function of the access system includes: obtaining heterogeneous menu data sent by the access system calling the standard acquisition interface.
[0100] Optionally, before obtaining the heterogeneous menu data of the target function of the access system, the method also includes: obtaining application loader information of the access system; traversing the applications of the access system based on the application loader information to determine the available applications; and determining the functions covered by the available applications as the target functions.
[0101] An embodiment of the present application also provides an electronic device, including a processor and a memory; the memory is used to store computer-executable instructions, and the processor and the memory are connected via a bus; when the construction device of the portal system is running, the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the portal system construction method described in the first aspect.
[0102] An embodiment of the present application further provides a computer-readable storage medium, which includes computer-executable instructions. When the computer-executable instructions are executed on a computer, the computer executes the portal system construction method described in the first aspect.
[0103] The embodiment of the present application also provides a computer program product, which can be directly loaded into a memory and contains software code. After being loaded and executed by a computer, the computer program product can implement the portal system construction method provided in the above embodiment.
[0104] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or a combination of software and hardware embodiments. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0105] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0106] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0107] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.
[0108] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered by the scope of protection of the claims of the present invention.
Claims
1. A method for constructing a portal system, characterized in that: include: Obtain heterogeneous menu data of target functions of access system; The heterogeneous menu data includes: menu information and access permission information; the access permission information represents the access permission of users of different levels to the target function; Based on a standardized data structure, converting the heterogeneous menu data into a standard menu table; Based on the standard menu table, an access menu for the target function of the access system is integrated into the basic portal system.
2. The method according to claim 1, characterized in that The standard menu table includes: Function menu parameters and access permission parameters; the function menu parameters are obtained by performing a standardized conversion based on the menu information; the access permission parameters are obtained by performing a standardized conversion based on the access permission information.
3. The method according to claim 1, characterized in that The acquiring of heterogeneous menu data of a target function of the access system includes: Heterogeneous menu data of a target function of the access system is acquired based on an integration framework; wherein the integration framework includes a first mode integration framework and a second mode integration framework.
4. The method according to claim 3, characterized in that The first mode integration framework includes: a universal data acquisition interface and a heterogeneous data acquisition interface; when the integration framework is the first mode integration framework, the step of obtaining heterogeneous menu data of a target function of the access system includes: Determining whether the data structure of the heterogeneous menu data of the access system is the same as the data structure of the menu data of the basic portal system; if so, acquiring the heterogeneous menu data of the access system based on the universal data acquisition interface; If not, the heterogeneous menu data of the access system is acquired based on the heterogeneous data acquisition interface.
5. The method according to claim 3, characterized in that The second mode integration framework includes: a standard acquisition interface; when the integration framework is the second mode integration framework, obtaining heterogeneous menu data of the target function of the access system includes: Obtaining heterogeneous menu data sent by the access system calling the standard acquisition interface.
6. The method according to claim 1, characterized in that Before acquiring heterogeneous menu data of a target function of the access system, the method further includes: Obtaining application loader information of the access system; Traversing the applications accessing the system based on the application loader information to determine available applications; A function covered by the available application is determined as the target function.
7. A device for constructing a portal system, characterized in that: The device comprises: An acquisition unit, configured to acquire heterogeneous menu data of a target function of an access system; the heterogeneous menu data comprising menu information and access permission information; the access permission information representing access permissions of users of different levels to the target function; a processing unit, configured to convert the heterogeneous menu data into a standard menu table based on a standardized data structure; The processing unit is further configured to integrate an access menu for the target function of the access system into the basic portal system based on the standard menu table.
8. An electronic device, characterized in that: include: A processor and a memory; wherein the memory is used to store one or more programs, and the one or more programs include computer-executable instructions. When the device is running, the processor executes the computer-executable instructions stored in the memory to enable the device to perform the method according to any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that When the computer-executable instructions stored in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device can perform the method according to any one of claims 1 to 6.
Citation Information
Cited By
Integration method of cross-system menu convenient access system
CN121092030A