Unified portal-based access method and system, and application service platform

Abstract

The invention discloses an access method and system based on a unified portal and an application service platform, the access method is applied to a micro-front-end architecture comprising a main application and a plurality of sub-applications, and the main application is provided with a unified portal system; the access method comprises a first access step of accessing a back-end service by a sub-application, and the first access step is used for obtaining a service access request of the sub-application, and the service access request is used for accessing the back-end service; responding to the service access request, and establishing an access link between the unified portal system and a back-end server; sending the service access request to a back-end server; and in response to the service access request, returning the service data of the back-end server to the sub-application through the unified portal system.

Description

Technical Field

[0001] The present invention belongs to the technical field, and in particular relates to an access method, system and application service platform based on a unified portal. Background Art

[0002] A portal is a website that provides a single point of access to applications and information. It refines the complex and diverse information and services provided to users and simplifies them into a single interface that meets user needs and interests. It is a user interface architecture for integrating "other" applications, content, and processes, and includes multiple features such as single sign-on and content management.

[0003] With the digitalization and networking of enterprises, the ecosystem of enterprise application systems continues to grow. The application systems include a wide variety of applications, covering various work scenarios such as project management, procurement management, supplier service management, and various applications continue to emerge.

[0004] As the application integration of enterprise application systems becomes increasingly complex and each application has its own operating interface, traditional single sign-on (SSO) technology and unified portal are not easy to use in the face of such complexity and cannot meet current usage requirements. Summary of the invention

[0005] The purpose of the present invention is to solve the above technical problems and provide an access method, system and application service platform based on a unified portal.

[0006] In order to solve the above problems, the present invention is implemented according to the following technical solutions:

[0007] In a first aspect, the present invention provides an access method based on a unified portal, which is applied to a micro-frontend architecture including a main application and multiple sub-applications, wherein the main application has a unified portal system;

[0008] The access method includes a first access step of the sub-application accessing the backend service, and the first access step includes:

[0009] Obtain a service access request from a sub-application, where the service access request is used to access a backend service;

[0010] In response to the service access request, an access link between the unified portal system and a backend server is established;

[0011] Sending the service access request to the backend server;

[0012] In response to the service access request, the business data of the backend server is returned to the sub-application through the unified portal system.

[0013] In combination with the first aspect, the present invention further provides a first specific implementation manner of the first aspect, specifically, the first access step further includes:

[0014] When the unified portal system cannot be accessed;

[0015] Use the proxy rules configured in vue.config.js to send the service access request to the backend server; or,

[0016] The service access request is sent to the backend server using the proxy rules configured in Nginx.

[0017] In combination with the first aspect, the present invention further provides a second specific implementation manner of the first aspect, specifically, the service access request is divided into a development access service request and a production access service request;

[0018] The unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server;

[0019] The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

[0020] In combination with the first aspect, the present invention further provides a third specific implementation manner of the first aspect. Specifically, the access method includes a second access step of accessing the sub-application through the unified portal system of the main application, the main application embeds multiple sub-applications based on iframe, and the second access step includes:

[0021] Get the login credentials of all sub-applications;

[0022] Loading a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications;

[0023] According to the input sub-application selection information, load the corresponding sub-application according to the deployment address;

[0024] Generate a sub-application access request based on login credentials, permission information, and routing configuration, and send it to the sub-application;

[0025] Get the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

[0026] In combination with the first aspect, the present invention further provides a fourth specific implementation manner of the first aspect, specifically, the sub-application includes a centralized procurement system, a supplier portal system, and a contract system;

[0027] The backend server includes an SRM server, a CMS server, a DUP server and a BSP server.

[0028] In a second aspect, the present invention further provides an access system based on a unified portal, wherein the access system adopts a micro-frontend architecture including a main application and multiple sub-applications, and the main application has a unified portal system;

[0029] The main application is used to proxy the sub-application to access the backend service, and the unified portal system of the main application includes:

[0030] An acquisition module, which is used to acquire a service access request of a sub-application, wherein the service access request is used to access a backend service;

[0031] A communication module, which is used to respond to the service access request and establish an access link between the unified portal system and the back-end server;

[0032] A sending module, which is used to send the service access request to the back-end server;

[0033] The return module is used to return the business data of the backend server to the sub-application through the unified portal system in response to the service access request.

[0034] In combination with the second aspect, the present invention further provides a first specific implementation manner of the second aspect, specifically, the sub-application includes:

[0035] The first rule access module is used to send the service access request to the backend server by using the proxy rules configured in vue.config.js when the unified portal system cannot be accessed; or,

[0036] The second rule access module is used to send the service access request to the backend server by using the proxy rules configured in Nginx when the unified portal system cannot be accessed.

[0037] In combination with the second aspect, the present invention further provides a second specific implementation manner of the second aspect, specifically, the service access request is divided into a development access service request and a production access service request;

[0038] The unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server;

[0039] The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

[0040] In combination with the second aspect, the present invention further provides a third specific implementation of the second aspect, specifically, the main application embeds multiple sub-applications based on iframe, and the unified portal system further includes:

[0041] The acquisition module is also used to obtain the login credentials of all sub-applications;

[0042] A menu module, which is used to load a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications;

[0043] A loading module, which is used to load the corresponding sub-application according to the input sub-application selection information and the deployment address;

[0044] The sending module is further used to generate a sub-application access request according to the login credentials, permission information and routing configuration, and send the sub-application;

[0045] The display module is used to obtain the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

[0046] In a third aspect, the present invention further provides an application service platform, the application service platform comprising a main application, a plurality of sub-applications and a data center system, the main application, the plurality of sub-applications and the data center system being interconnected;

[0047] The main application includes a unified portal system, and the main application is configured to execute the access method based on the unified portal described in the first aspect.

[0048] Compared with the prior art, the present invention has the following beneficial effects:

[0049] The present invention provides an access method based on a unified portal, which is applied to a micro-frontend architecture including a main application and multiple sub-applications, wherein the main application has a unified portal system; wherein the access method includes a first access step for the sub-application to access a back-end service, and the first access step is used to include: obtaining a service access request of the sub-application, wherein the service access request is used to access the back-end service; responding to the service access request, establishing an access link between the unified portal system and the back-end server; sending the service access request to the back-end server; and responding to the service access request, returning the business data of the back-end server to the sub-application through the unified portal system.

[0050] In the technology of the present invention, a main application (unified portal system) in a micro-frontend architecture is used as a central node to manage multiple sub-applications. The main application and each sub-application can be independently developed and deployed, and multiple sub-applications share the interface and user session of the same main application. The present invention has the technical effects of centralized management, unified authentication, simplified sub-application development, and improved user experience. On the other hand, the main application can effectively handle cross-domain issues such as sub-application backend access, and the main application has better compatibility. An effective sub-application and backend service communication mechanism is provided for the micro-frontend architecture, while maintaining the modularity and scalability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The specific embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings, wherein:

[0052] Figure 1 This is a flow chart of an access method based on a unified portal of the present invention.

[0053] Figure 2 It is a schematic diagram of the process of the main application and sub-application accessing the backend service of the present invention;

[0054] Figure 3 It is a schematic diagram of the process of the main application accessing the sub-application of the present invention;

[0055] Figure 4 It is a flowchart of the unified portal system, sub-applications and data system login and adding new users of the application service platform of the present invention.

[0056] Figure 5 It is a flowchart of user synchronization of the unified portal system, sub-applications and data systems of the application service platform of the present invention. DETAILED DESCRIPTION

[0057] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0058] like Figure 1 , a flow chart of an access method based on a unified portal according to the present invention. In the present invention, the access method is applied to a micro-frontend architecture including a main application and multiple sub-applications, and the main application has a unified portal system.

[0059] In a preferred implementation,

[0060] In this field, micro-frontend architecture is a modern software architecture style used to build large-scale front-end applications. It mainly solves the maintainability, scalability and development efficiency problems faced by traditional monolithic front-end applications after they are scaled up. It is understandable that each functional module in the micro-frontend architecture is regarded as an independent micro-application with its own business logic, view and state management. Each micro-application can be developed, tested, deployed and maintained independently without being affected by other micro-applications. Micro-applications can choose to use different front-end frameworks or libraries, such as React, Vue, Angular, etc., and even non-JavaScript technologies.

[0061] In the present invention, the main application acts as a host for the micro-applications, providing a unified entry point and basic services, such as routing, state management, user authentication, etc. Multiple sub-applications can be understood as an application being decomposed into multiple small, loosely coupled modules, each module being responsible for a part of the functionality.

[0062] In the micro-frontend architecture, sub-applications include the centralized procurement system, supplier portal system, and contract system. The centralized procurement system is used for centralized procurement management, allowing enterprises to uniformly manage procurement processes, including demand collection, supplier selection, order processing, etc. The supplier portal system is used for suppliers to view and manage their order status.

[0063] The contract system is used for contract creation, storage, execution tracking or risk management. The contract system allows users to create, review and approve contract documents. Centrally store and manage contract documents for easy retrieval and audit. Monitor the fulfillment of contract terms, including payment, service delivery, etc. Identify contract risks and take appropriate measures.

[0064] In the micro-frontend architecture, the centralized procurement system, supplier portal system, and contract system are independent sub-applications that can flexibly adapt to changes in business needs while maintaining collaboration with other systems. This architecture improves the maintainability, scalability, and development efficiency of the system.

[0065] In the present invention, based on the micro front-end architecture, the present invention provides a powerful framework through the unified portal system of the main application, allowing multiple sub-applications to work together and provide a consistent user experience while maintaining independence. The present invention is suitable for large-scale enterprise-level applications, where the complexity and scale of the application require a high degree of modularity and flexibility.

[0066] like Figure 1 As shown, the access method includes a first access step of a sub-application accessing a backend service, and the first access step includes:

[0067] S100: Obtain a service access request of a sub-application, where the service access request is used to access a backend service.

[0068] It is understandable that the sub-application may trigger a request through user interaction or internal logic, and the request is encapsulated as an API call or other forms of communication requests. For example, the sub-application triggers an API request through user interaction or internal logic, such as using JavaScript's fetch API or axios library to initiate an HTTP request. The request is encapsulated in JSON format and contains necessary authentication information and business data.

[0069] S200: Responding to the service access request, establishing an access link between the unified portal system and a backend server.

[0070] In the present invention, after receiving the access service request from the sub-application, the main application establishes a communication link with the back-end server to access the back-end service. In one example, the unified portal system uses HTTP request, WebSocket connection or other communication protocols to establish a connection with the back-end service. This step may also include identity authentication and authorization processes to ensure the security of communication.

[0071] In a specific implementation, the backend server includes an SRM server, a CMS server, a DUP server and a BSP server.

[0072] It is understandable that in the micro front-end architecture, the back-end server usually refers to the server that provides back-end functions such as business logic processing, data storage, and application services. For the SRM server, CMS server, DUP server, and BSP server, each server has different business responsibilities, but they work together to provide the required data and services for the front-end application. The following is a specific description of these back-end servers:

[0073] 1. SRM Server (Supplier Relationship Management Server). Function: Supplier relationship management system, used to manage relationships and interactions with suppliers. Responsibilities: Process supplier information, evaluate supplier performance, manage purchase orders and supply chain processes. Technical implementation: may include database operations, business logic processing, integration with external systems, etc.

[0074] 2. CMS Server (Content Management System Server). Function: Content management system, used to create and manage digital content. Responsibilities: Store text, pictures, videos and other content, and provide content creation, editing, publishing and archiving functions. Technical implementation: Usually involves content storage, user rights management, workflow processing, etc.

[0075] 3. BSP Server (Backend Service Portal Server). Function: Backend service platform, providing a unified access point for various backend services. Responsibilities: may include authentication, data aggregation, API management, etc. Technical implementation: As an API gateway or service bus, it processes requests from front-end applications and routes them to the corresponding services.

[0076] S300: Sending the service access request to a backend server.

[0077] In one specific implementation, the original request of the sub-application is forwarded to the backend server so that the backend can process the request and return corresponding data. In one specific implementation, the request may need to add or modify HTTP header information to include an authentication token.

[0078] In a specific implementation, the service access request is divided into a development access service request and a production access service request;

[0079] The unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server;

[0080] The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

[0081] It is understandable that the processing of service access requests may differ depending on the development environment and the production environment. The following is an explanation of how development access service requests and production access service requests are processed:

[0082] About development access service requests: During the development phase, developers need to test the interaction between sub-applications and backend services to ensure that the functions are implemented correctly. Implementation method: Use vue.config.js proxy rules: In Vue projects, the vue.config.js file is used to configure the proxy rules of the Webpack development server. When sub-applications initiate API requests, these requests are forwarded to the specified backend services according to the proxy rules.

[0083] About production access service requests: In a production environment, you need to ensure that user operation requests can be sent to backend services safely and efficiently. Use proxy configuration for production environments: In a production environment, proxy requests are usually not forwarded through the Webpack development server, but are handled by a deployed web server (such as Nginx) or through server-side logic. Use Nginx proxy rules: Set proxy rules in the Nginx configuration file to forward requests in the production environment to the backend service.

[0084] S400: In response to the service access request, the business data of the backend server is returned to the sub-application through the unified portal system.

[0085] In the present invention, after processing the request, the backend server sends the result back to the unified portal system, and the unified portal system then passes the data to the sub-application of the original request.

[0086] In a specific implementation, after the backend server processes the request, it returns the result to the sub-application through the portal system, usually in JSON format. The unified portal system may need to handle cross-domain issues and use CORS policies.

[0087] You can refer to Figure 2 , back-end services in the micro-front-end architecture of the present invention: front-end sub-applications (such as centralized procurement system, supplier portal system and contract system) interact with these back-end servers through the unified portal system. The unified portal system may act as an API Gateway, routing front-end requests to the correct back-end services, and handling tasks such as identity authentication, request forwarding, and error handling. The centralized procurement system may need to interact with the SRM server and the BSP server to obtain supplier information and execute procurement processes. The supplier portal system may rely on a CMS server to manage its content display. The contract system may need to communicate with the DUP server and the BSP server to manage contract documents and execute contract-related business logic.

[0088] Through this separation and collaboration approach, the micro front-end architecture can improve the flexibility and maintainability of the application while ensuring that each part can be developed and expanded independently.

[0089] In a preferred implementation, the first access step further includes:

[0090] S10: When the unified portal system is inaccessible, the service access request is sent to the backend server using the proxy rules configured in vue.config.js; or, the service access request is sent to the backend server using the proxy rules configured in Nginx.

[0091] In the present invention, when the unified portal system is temporarily inaccessible, possibly due to maintenance, failure or other reasons, a backup plan is required to ensure that the sub-application can continue to communicate with the backend server. The following is a description of the backup access steps, as well as the meanings and examples of the technical terms involved:

[0092] In a specific implementation, using vue.config.js proxy rules: When the unified portal system is unavailable, the sub-application can configure the development server proxy (devServer.proxy) to forward requests to the backend server. This is usually used in a development environment to allow developers to continue front-end development when the portal system is unavailable.

[0093] Specifically, vue.config.js: The configuration file in the Vue CLI project, used to customize the Webpack configuration, including the development server proxy rules.

[0094] In a specific implementation, Nginx proxy rules are used: In a production environment, if the unified portal system is not available, Nginx or other reverse proxy servers can be used to configure proxy rules to forward requests directly to the backend server. Specifically, a high-performance HTTP server and reverse proxy server are widely used for deployment and reverse proxy of Web services.

[0095] Through these backup access steps and related technologies, even if the unified portal system is unavailable, it can ensure that the communication between the sub-application and the back-end service is not affected, thereby improving the availability and fault tolerance of the entire system.

[0096] In a preferred implementation, the access method includes a second access step of accessing the sub-application through a unified portal system of the main application, the main application embeds multiple sub-applications based on iframe, and the second access step includes:

[0097] S1000: Obtain login credentials for all sub-applications.

[0098] In a specific implementation, when a user logs in to the main application, the system automatically obtains or generates the login credentials required by the sub-application, such as OAuth tokens or JWT.

[0099] S2000: Loading a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications.

[0100] In a specific implementation, all available sub-applications are displayed, allowing users to select the sub-application they want to access. The portal menu may be a navigation bar or a drop-down list that lists the names and icons of all sub-applications and is configured with the deployment address of each sub-application.

[0101] S3000: According to the input sub-application selection information, a corresponding sub-application is loaded according to the deployment address.

[0102] In the specific implementation, the corresponding sub-application is loaded and displayed according to the user's selection. After the user clicks on the sub-application in the portal menu, the system loads the corresponding sub-application through the iframe according to the configured deployment address.

[0103] S4000: Generate a sub-application access request based on login credentials, permission information, and routing configuration, and send the sub-application.

[0104] In the specific implementation, ensure that the sub-application can correctly load the user interface according to the user's login credentials and permission information. The system builds an access request based on the user's login credentials, permissions, and routing configuration, and sends it to the sub-application, which can use API calls or specific authentication protocols.

[0105] S5000: Obtain the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

[0106] In the specific implementation, after the sub-application is loaded, the HTML content of the user interface is returned. The main application embeds it into its own page through iframe, and the user can directly interact with the sub-application in the main application.

[0107] In the second access step, iframe: HTML element that allows an HTML document to be embedded in another document, forming a frame. Example: <iframe src＝"http: subapp.example.com">< / iframe>Routing configuration: Routing rules defined in the front-end application, used to determine which component or page to load for different URLs. Permission information: The access permissions of users in the system, which determine which resources they can access.

[0108] Specifically, as shown in Figure 3, the general technical route of the second access step includes: 1. Obtain the login credentials of all subsystems. Purpose: To enable users to log in to all sub-applications, it is necessary to obtain the login credentials of users in each subsystem. Implementation: After the user logs in to the unified portal system, the system automatically obtains or generates access permissions for each sub-application. 2. Obtain the portal menu. Purpose: To display all sub-applications that the user can access and provide a navigation function. Implementation: The portal menu displays a list of all sub-applications, which may include system modules such as srm (Supplier Relationship Management), bsp (Business Support Platform), cms (Content Management System), etc. 3. Embed the subsystem page through iframe technology. Purpose: To embed the sub-application in the interface of the unified portal system, enabling users to access different applications within one interface. Implementation: When the user selects a certain sub-application, the portal system uses the iframe tag to load the corresponding subsystem page. 4. Obtain login credentials, etc. from the portal system. Purpose: To ensure that the subsystem can recognize and accept user credentials from the portal system and allow users to access. Implementation: When the subsystem page is loaded, the login credentials are received from the portal system through a specific API or configuration. 5. Obtain the subsystem page through address + menu routing. Purpose: To load the corresponding subsystem page according to the user's selection. Implementation: Each sub-application has a basic deployment address, and combined with the menu routing, the specific page can be located. The portal system requests the subsystem page by constructing a complete URL. 6. Embed into the unified portal system. Purpose: To embed the subsystem page into the iframe of the portal system to achieve seamless integration. Implementation: The portal system dynamically creates an iframe and embeds the subsystem page as the source into the iframe. 7. Handle cross-domain issues Purpose: To solve the security restrictions caused by the fact that the subsystem and the portal system are not in the same domain. Implementation: Use the CORS (Cross-Origin Resource Sharing) policy, or through a proxy server, etc., to allow cross-domain requests and data transmission. 8. Click to navigate outside the menu: Purpose: To provide users with the ability to navigate from the current sub-application to other sub-applications. Implementation: When the user clicks on different options in the portal menu, the portal system updates the sub-application page in the iframe to reflect the user's selection.

[0109] The present invention also provides an access system based on a unified portal, wherein the access system adopts a micro-front-end architecture including a main application and multiple sub-applications, and the main application has a unified portal system. The access system is used to implement the above-mentioned access method based on a unified portal.

[0110] Wherein, the main application is used to proxy the sub-application to access the backend service, and the unified portal system of the main application includes:

[0111] an acquisition module, which is used to obtain a service access request of a sub-application, wherein the service access request is used to access a backend service;

[0112] a communication module, which is used to respond to the service access request and establish an access link between the unified portal system and the back-end server;

[0113] a sending module, which is used to send the service access request to the back-end server;

[0114] a return module, which is used to respond to the service access request and return the business data of the back-end server to the sub-application through the unified portal system.

[0115] Specifically, the sub-application includes:

[0116] a first rule access module, which is used to send the service access request to the backend server using the proxy rules configured in vue.config.js when the unified portal system cannot be accessed; or,

[0117] The second rule access module is used to send the service access request to the back-end server using the proxy rules configured in Nginx when the unified portal system cannot be accessed.

[0118] Specifically, the service access request is divided into a development access service request and a production access service request;

[0119] Wherein, the unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server;

[0120] The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

[0121] Specifically, the main application embeds multiple sub-applications based on iframe, and the unified portal system also includes:

[0122] an acquisition module, which is also used to obtain login credentials of all sub-applications;

[0123] a menu module, which is used to load a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications;

[0124] a loading module, which is used to load the corresponding sub-application according to the input sub-application selection information and the deployment address;

[0125] a sending module, which is further used to generate a sub-application access request according to the login credentials, permission information and routing configuration, and send the sub-application;

[0126] A display module, which is used to obtain the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

[0127] In the present invention, an application service platform is also provided, the application service platform includes a main application, multiple sub-applications and a data center system, the main application, multiple sub-applications and the data center system are interconnected;

[0128] Wherein, the main application includes a unified portal system, and the main application is configured to execute the above-mentioned access method based on the unified portal.

[0129] In a specific implementation, the sub-applications include a centralized procurement system, a supplier portal system, and a contract system.Specifically, as shown in Figure 4 and Figure 5, the descriptions of user login, new user addition, and user information synchronization for the main application, sub-application, and data center system are as follows:

[0130] (I) User authentication and authorization process

[0131] 1. Verify the incoming parameters: When a user attempts to log in, the system first verifies the credentials (such as username and password) entered by the user.

[0132] 2. Check if there is the same username: The system checks if the username already exists in the database to ensure user uniqueness.

[0133] 3. Verification passed: If the user credentials are valid, the system will generate a token based on the user information.

[0134] 4. Generate the token:

[0135] The system creates a JWT (JSON Web Token) or other form of token, which contains information such as the user's role and permissions and has a certain validity period (such as 7 days).

[0136] 5. For subsequent calls: The generated token will be used for the user's subsequent access requests to each subsystem to achieve single sign-on.

[0137] (II) User data and permission management

[0138] 1. Retrieve all role, menu, and permission information of the user: The system retrieves all role and permission information of the user to provide corresponding access menus and functions.

[0139] 2. The system determines the system modules and data that the user can access based on the user's role and permission information.( III ) Data Synchronization Process

[0141] 1. Determine whether user synchronization is required: When there are changes in user data in the system, the system needs to determine whether these changes need to be synchronized to other systems or data centers.

[0142] 2. Notify the data center service to synchronize: If synchronization is required, the system will notify the data center service and trigger the data synchronization process.

[0143] 3. New user or user change message: For new users or changes to existing users, the system will request the data center service to update user information.

[0144] 4. Determine whether there is an identical user name: When adding a new user, the system will check the uniqueness of the user name again to avoid duplication.

[0145] 5. User Information Synchronization: Ultimately, the system ensures that user information remains consistent and up-to-date in all relevant systems.

[0146] JWT (JSON Web Token): A compact, URL-safe way to transfer statements between network application environments. JWT can be used to authenticate user identities.

[0147] Token: An access control mechanism used to identify users or services and control access to resources.

[0148] Data center system: A central repository for storing and managing an organization's data, typically responsible for data persistence, backup, and recovery.

[0149] For other structures of the unified portal-based access method, system and application service platform described in this embodiment, refer to the prior art.

[0150] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Therefore, any modification, equivalent changes and modifications made to the above embodiments according to the technical essence of the present invention without departing from the technical solution of the present invention are still within the scope of the technical solution of the present invention.

Claims

1. An access method based on a unified portal, characterized in that: Applied to a micro-frontend architecture including a main application and multiple sub-applications, wherein the main application has a unified portal system; The access method includes a first access step of the sub-application accessing the backend service, and the first access step includes: Obtain a service access request from a sub-application, where the service access request is used to access a backend service; In response to the service access request, an access link between the unified portal system and a backend server is established; Sending the service access request to the backend server; In response to the service access request, the business data of the backend server is returned to the sub-application through the unified portal system.

2. The access method based on a unified portal according to claim 1, characterized in that: The first access step further comprises: When the unified portal system cannot be accessed; Use the proxy rules configured in vue.config.js to send the service access request to the backend server; or, The service access request is sent to the backend server using the proxy rules configured in Nginx.

3. The access method based on a unified portal according to claim 1, characterized in that: The service access request is divided into a development access service request and a production access service request; The unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server; The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

4. The access method based on a unified portal according to claim 1, characterized in that: The access method includes a second access step of accessing the sub-application through a unified portal system of the main application, wherein the main application embeds multiple sub-applications based on iframe, and the second access step includes: Get the login credentials of all sub-applications; Loading a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications; According to the input sub-application selection information, load the corresponding sub-application according to the deployment address; Generate a sub-application access request based on login credentials, permission information, and routing configuration, and send it to the sub-application; Get the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

5. The unified portal-based access method according to any one of claims 1 to 4, characterized in that: The sub-applications include a centralized procurement system, a supplier portal system, and a contract system; The backend server includes an SRM server, a CMS server, a DUP server and a BSP server.

6. An access system based on a unified portal, characterized in that: The access system adopts a micro-frontend architecture including a main application and multiple sub-applications, and the main application has a unified portal system; The main application is used to proxy the sub-application to access the backend service, and the unified portal system of the main application includes: An acquisition module, which is used to acquire a service access request of a sub-application, wherein the service access request is used to access a backend service; A communication module, which is used to respond to the service access request and establish an access link between the unified portal system and the back-end server; A sending module, which is used to send the service access request to the back-end server; The return module is used to return the business data of the backend server to the sub-application through the unified portal system in response to the service access request.

7. The unified portal-based access system according to claim 6, characterized in that: The sub-applications include: The first rule access module is used to send the service access request to the backend server by using the proxy rules configured in vue.config.js when the unified portal system cannot be accessed; or, The second rule access module is used to send the service access request to the backend server by using the proxy rules configured in Nginx when the unified portal system cannot be accessed.

8. The unified portal-based access system according to claim 6, characterized in that: The service access request is divided into a development access service request and a production access service request; The unified portal system uses the proxy rules configured in vue.config.js to send the development access service request to the backend server; The unified portal system uses the proxy rules configured in vue.config.js to send the production access service request to the backend server.

9. The unified portal-based access system according to claim 6, characterized in that: The main application embeds multiple sub-applications based on iframe, and the unified portal system further includes: The acquisition module is also used to obtain the login credentials of all sub-applications; A menu module, which is used to load a portal menu of the unified portal system, wherein the portal menu includes a sub-application directory, and the sub-application directory is configured with deployment addresses of multiple sub-applications; A loading module, which is used to load the corresponding sub-application according to the input sub-application selection information and the deployment address; The sending module is further used to generate a sub-application access request according to the login credentials, permission information and routing configuration, and send the sub-application; The display module is used to obtain the sub-application interface returned by the sub-application, and display the sub-application interface in the main application based on the iframe.

10. An application service platform, characterized in that: The application service platform includes a main application, multiple sub-applications and a data center system, and the main application, multiple sub-applications and the data center system are interconnected; The main application includes a unified portal system, and the main application is configured to execute an access method based on a unified portal as described in any one of claims 1 to 5.

Images