CN119172369A - A unified portal-based access method, system and application service platform - Google Patents
A unified portal-based access method, system and application service platform Download PDFInfo
- Publication number
- CN119172369A CN119172369A CN202411286984.4A CN202411286984A CN119172369A CN 119172369 A CN119172369 A CN 119172369A CN 202411286984 A CN202411286984 A CN 202411286984A CN 119172369 A CN119172369 A CN 119172369A
- Authority
- CN
- China
- Prior art keywords
- sub
- application
- access
- service
- unified portal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 210000004258 portal system Anatomy 0.000 claims abstract description 98
- 238000011161 development Methods 0.000 claims description 23
- 238000004519 manufacturing process Methods 0.000 claims description 18
- 238000004891 communication Methods 0.000 claims description 9
- 238000007726 management method Methods 0.000 description 18
- 230000000875 corresponding effect Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000005065 mining Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本发明公开了一种基于统一门户的访问方法、系统及应用服务平台，访问方法应用于包含主应用和多个子应用的微前端架构中，所述主应用具有统一门户系统；其中，所述访问方法包括子应用访问后端服务的第一访问步骤，所述第一访问步骤用于包括：获取子应用的服务访问请求，所述服务访问请求用于访问后端服务；响应所述服务访问请求，建立所述统一门户系统与后端服务器的访问链路；向后端服务器发送所述服务访问请求；响应于所述服务访问请求，通过统一门户系统向子应用返回所述后端服务器的业务数据。
The present invention discloses an access method, system and application service platform based on a unified portal, wherein the access method is applied to a micro-front-end 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, wherein 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 a 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.
Description
Technical Field
The invention belongs to the technical field, and particularly relates to an access method, an access system and an application service platform based on a unified portal.
Background
A portal is a Web site providing single point access to applications and information, which refines the complex and diverse information and services provided to users, simplifies into a single interface meeting user requirements and interests, and is a user interface architecture for integrating "other" applications, content and processes, including multiple features such as single sign-on, content management, etc.
Along with the digitization and networking construction of enterprises, the ecological system of enterprise application systems is continuously growing, the application systems comprise a plurality of application types, various working scenes such as project management, purchase management, provider service management and the like are covered, and various applications are continuously appeared.
Because the application integration of enterprise application systems is increasingly complex, and each application has its own operation interface, the conventional Single Sign On (SSO) technology and unified portal have insufficient usability when facing such complexity, and cannot meet the current use requirements.
Disclosure of Invention
The invention aims to solve the technical problems and provides an access method, an access system and an application service platform based on a unified portal.
In order to solve the problems, the invention is realized according to the following technical scheme:
In a first aspect, the present invention provides a unified portal-based access method, applied to a micro front-end architecture including a main application and a plurality of sub-applications, where the main application has a unified portal system;
The access method comprises a first access step of the sub-application to access the back-end service, wherein the first access step comprises the following steps:
acquiring a service access request of a sub-application, wherein the service access request is used for accessing a 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 responding to the service access request, and returning the service data of the back-end server to the sub-application through the unified portal system.
With reference to the first aspect, the present invention further provides a1 st specific implementation manner of the first aspect, and specifically, the first accessing step further includes:
when the unified portal system cannot be accessed;
transmitting the service access request to a back-end server by using proxy rules configured in vue.config.js, or
And sending the service access request to a back-end server by using the proxy rule configured in Nginx.
With reference to the first aspect, the present invention further provides a2 nd 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;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
With reference to the first aspect, the present invention further provides a3 rd specific implementation manner of the first aspect, and specifically, the accessing method includes a second accessing step of accessing the sub-applications through a unified portal system of the main application, where the main application embeds a plurality of sub-applications based on the iframe, and the second accessing step includes:
obtaining login credentials of all sub-applications;
Loading a portal menu of the unified portal system, wherein the portal menu comprises a sub-application catalog configured with deployment addresses of a plurality of sub-applications;
loading corresponding sub-applications according to the deployment addresses according to the input sub-application selection information;
generating a sub-application access request according to the login credentials, the authority information and the routing configuration, and sending the sub-application;
And acquiring a sub-application interface returned by the sub-application, and displaying the sub-application interface in the main application based on the iframe.
With reference to the first aspect, the invention further provides a 4 th specific implementation manner of the first aspect, and specifically, the sub-application includes a collection and mining system, a provider portal system and a contract system;
the back-end servers include SRM servers, CMS servers, DUP servers, and BSP servers.
In a second aspect, the present invention also provides an access system based on a unified portal, where the access system adopts a micro front-end architecture including a main application and a plurality of sub-applications, and the main application has a unified portal system;
the main application is used for proxy the sub-application to access the back-end service, and the unified portal system of the main application comprises:
An acquisition module for acquiring a service access request of a sub-application, the service access request is used for accessing the back-end service;
the communication module is used for responding to the service access request and establishing an access link between the unified portal system and the back-end server;
A sending module, configured to send the service access request to a backend server;
And the return module is used for responding to the service access request and returning the service data of the back-end server to the sub-application through the unified portal system.
With reference to the second aspect, the present invention further provides a 1 st specific implementation manner of the second aspect, specifically, the sub-application includes:
A first rule access module for sending the service access request to a back-end server using proxy rules configured in vue.config.js when the unified portal system cannot be accessed, or
And the second rule access module is used for sending the service access request to a back-end server by using the proxy rule configured in the Nginx when the unified portal system cannot be accessed.
With reference to the second aspect, the present invention further provides a2 nd 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;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
With reference to the second aspect, the present invention further provides a3 rd specific implementation manner of the second aspect, specifically, the main application embeds a plurality of sub-applications based on iframe, and the unified portal system further includes:
the acquisition module is also used for acquiring login credentials of all sub-applications;
a menu module for loading a portal menu of the unified portal system, the portal menu comprising a sub-application directory configured with deployment addresses of a plurality of sub-applications;
the loading module is used for loading the corresponding sub-application according to the deployment address according to the input sub-application selection information;
the sending module is also used for generating a sub-application access request according to the login credentials, the authority information and the routing configuration and sending the sub-application;
And the display module is used for acquiring a sub-application interface returned by the sub-application and displaying the sub-application interface in the main application based on the iframe.
In a third aspect, the present invention further provides an application service platform, where the application service platform includes a main application, a plurality of sub-applications, and a data center system, where the main application, the plurality of sub-applications, and the data center system are connected to each other;
wherein the host application comprises a unified portal system, the host application being configured to perform a unified portal based access method according to the first aspect.
Compared with the prior art, the invention has the beneficial effects that:
The invention provides an access method based on a unified portal, which is applied to a micro front-end architecture comprising a main application and a plurality of sub-applications, wherein the main application is provided with a unified portal system, the access method comprises a first access step of accessing back-end services by the sub-applications, the first access step is used for obtaining service access requests of the sub-applications, the service access requests are used for accessing the back-end services, an access link between the unified portal system and a back-end server is established in response to the service access requests, the service access requests are sent to the back-end server, and service data of the back-end server are returned to the sub-applications through the unified portal system in response to the service access requests.
In the technology of the present invention, a plurality of sub-applications are managed based on one main application (unified portal system) in the micro front-end architecture as a central node. The main application and each sub-application can be independently developed and deployed, and a plurality of sub-applications share the interface and user session of the same main application. The invention has the technical effects of centralized management, unified authentication, simplified sub-application development and improved user experience. On the other hand, the cross-domain problem of sub-application back-end access and the like can be effectively processed through the main application, and the main application has better compatibility. An effective sub-application and back-end service communication mechanism is provided for the micro front-end architecture, and meanwhile, the modularization and the expandability of the system are maintained.
Drawings
The invention is described in further detail below with reference to the attached drawing figures, wherein:
FIG. 1 is a flow chart of a unified portal-based access method of the present invention
FIG. 2 is a schematic flow diagram of a main application and sub-application accessing backend services of the present invention;
FIG. 3 is a flow diagram of a main application accessing sub-applications of the present invention;
FIG. 4 is a flow chart of a unified portal system, sub-applications and login and newly added users of the system in data of the application service platform of the present invention.
FIG. 5 is a flow chart of user synchronization of a unified portal system, sub-applications, and in-data system of the application service platform of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described below with reference to the accompanying drawings, it being understood that the preferred embodiments described herein are for illustration and explanation of the present invention only, and are not intended to limit the present invention.
Referring to fig. 1, a flow chart of a unified portal-based access method according to the present invention is shown. In the invention, the access method is applied to a micro front-end architecture comprising a main application and a plurality of sub-applications, wherein the main application is provided with a unified portal system.
In one preferred embodiment of the present invention,
In the art, micro front end architecture is a modern style of software architecture for building large front end applications. The method mainly solves the problems of maintainability, expandability and development efficiency of the traditional single front-end application after the scale is enlarged. It will be appreciated that each functional module in the micro-front-end architecture is considered as a separate micro-application, with its own business logic, view and state management. Each micro-application can be independently developed, tested, deployed and maintained without being affected by other micro-applications. The micro-application may choose to use a different front-end framework or library, such as React, vue, angular, etc., and may even use non-JavaScript techniques.
In the present invention, the host application serves as a host for the micro-applications, providing a unified entry point and basic services such as routing, state management, user authentication, etc. A plurality of sub-applications, which can be understood as applications, are broken down into a plurality of small, loosely coupled modules, each of which is responsible for a portion of the functionality.
In the micro-front-end architecture, the sub-applications include a collection system, a vendor portal system, and a contract system. The centralized acquisition system is used for centralized purchase management, and allows enterprises to uniformly manage purchase flows, including demand collection, supplier selection, order processing and the like. The vendor portal system is used for the vendor to view and manage his own order status.
While the contract system is used for contract creation, storage, execution tracking or risk management, etc. The contract system allows users to create, review, and approve contract documents. And the contract documents are stored and managed in a centralized way, so that the retrieval and the audit are facilitated. Monitoring performance of contract terms includes payment, service delivery, and the like. Identify contract risk and take corresponding action.
In the micro front-end architecture, the collection system, the provider portal system and the contract system are used as independent sub-applications, so that the change of service requirements can be flexibly adapted, and the cooperation with other systems is maintained. This architecture improves maintainability, scalability, and development efficiency of the system.
Based on the micro front end architecture, the invention provides a powerful framework through the unified portal system of the main application, allows a plurality of sub-applications to work cooperatively and provide consistent user experience while maintaining independence. The present invention is suitable for large enterprise-level applications where the complexity and scale of the application requires a high degree of modularity and flexibility.
As shown in fig. 1, the access method includes a first access step of accessing a backend service by a sub-application, where the first access step includes:
S100, acquiring a service access request of the sub-application, wherein the service access request is used for accessing the back-end service.
It will be appreciated that the sub-application may trigger a request, either through user interaction or internal logic, that is encapsulated as an API call or other form of communication request. For example, the sub-application initiates the HTTP request by user interaction or internal logic triggering an API request, such as a fetch API or axios library using JavaScript. The request is encapsulated in JSON format containing the necessary authentication information and service data.
And S200, responding to the service access request, and establishing an access link between the unified portal system and the back-end server.
In the invention, after the main application receives the access service request of the sub-application, a communication link with a back-end server is established to access the back-end service. In one example, the unified portal system establishes a connection with a backend service using an HTTP request, webSocket connection, or other communication protocol. This step may also include authentication and authorization procedures to ensure the security of the communication.
In one implementation, the backend servers include SRM servers, CMS servers, DUP servers, and BSP servers.
It is understood that in the micro-front-end architecture, a back-end server generally refers to a server that provides back-end functions for business logic processing, data storage, application services, and the like. For SRM server, CMS server, DUP server and BSP server, each server assumes different business responsibilities, but they together provide the necessary data and services for the front-end application. The following is a specific description of these backend servers:
1. an SRM server (Supplier Relationship MANAGEMENT SERVER). A vendor relationship management system for managing relationships and interactions with vendors. Responsibility for processing vendor information, evaluating vendor performance, managing purchase orders, and supply chain flows. The technical implementation may include database operations, business logic processing, integration with external systems, etc.
2. CMS server (Content MANAGEMENT SYSTEM SERVER). Function, content management system for creating and managing digital content. Responsibility is to store text, pictures, video, etc., and provide content creation, editing, distribution and archiving functionality. Technical implementation generally involves content storage, user rights management, workflow processing, etc.
3. A BSP server (Backend Service Portal Server). And the back-end service platform provides unified access points for various back-end services. Responsibility may include authentication, data aggregation, API management, etc. The technique is implemented as an API gateway or service bus that processes requests from the front-end application and routes to the corresponding service.
And S300, sending the service access request to a back-end server.
In one implementation, the original request of the sub-application is forwarded to the back-end server so that the back-end can process the request and return the corresponding data. In one implementation, the request may require the addition or modification of HTTP header information to include the authentication token.
In one implementation, the service access requests are divided into development access service requests and production access service requests;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
It will be appreciated that the processing of service access requests may vary from development environment to production environment. The following is an explanation of the manner in which access service requests are made and access service requests are produced:
Regarding development access service requests, in the development stage, a developer needs to test interaction between a sub-application and a back-end service to ensure correct realization of functions. Embodiments use the vue.config.js proxy rules-in the Vue project, the vue.config.js file is used to configure Webpack the proxy rules of the development server. When a sub-application initiates API requests, the requests are forwarded to the specified backend services according to proxy rules.
Regarding the production of access service requests, in a production environment, it is necessary to ensure that a user's operation request can be safely and efficiently transmitted to a backend service. Proxy configuration using a production environment in which proxy requests are typically not forwarded through Webpack development servers, but rather are handled through a deployed Web server (e.g., nmginx) or through server logic. The Nginx proxy rules are used-set in the Nginx configuration file, forwarding requests in the production environment to the backend service.
And S400, responding to the service access request, and returning the service data of the back-end server to the sub-application through the unified portal system.
In the invention, after the back-end server processes the request, the result is sent back to the unified portal system, which in turn delivers the data to the sub-application of the original request.
In one implementation, after the backend server processes the request, the results are returned to the child applications through the portal system, typically using JSON format. The unified portal system may need to deal with cross-domain issues, using the CORS policy.
Referring to FIG. 2, back-end services in the micro front-end architecture of the present invention, front-end sub-applications (e.g., collection system, vendor portal system, and contract system) interact with these back-end servers through a unified portal system. The unified portal system may take the role of API GATEWAY, route front-end requests to the correct back-end services, and handle authentication, request forwarding, error handling, etc. The centralized mining system may need to interact with the SRM server and the BSP server to obtain vendor information and perform the purchasing process. The provider portal system may rely on the CMS server to manage its content presentation. The contract system may need to communicate with the DUP server and the BSP server to manage the contract documentation and to execute the contract-related business logic.
In this way, the micro front-end architecture can improve flexibility and maintainability of the application while ensuring that each part can be independently developed and expanded.
In a preferred implementation, the first access step further comprises:
And S10, when the unified portal system cannot be accessed, sending the service access request to a back-end server by using a proxy rule configured in vue.config.js, or sending the service access request to the back-end server by using a proxy rule configured in Nginx.
In the present invention, when the unified portal system is temporarily inaccessible, possibly for maintenance, failure or other reasons, a backup scheme is required to ensure that the sub-applications can continue to communicate with the backend server. The following is a description of the alternate access steps, and the meaning and examples of the terms involved:
In one implementation, using the vue.config.js proxy rule, the child application may configure a development server proxy (devServer.proxy) to forward the request to the backend server when the unified portal system is not available. This is typically used in a development environment, allowing a developer to continue front-end development when a portal system is not available.
Specifically, the configuration file in the Vue. Config. Js: vue CLI project is used for customizing Webpack the configuration, including developing server proxy rules.
In one implementation, the Nginx proxy rules are used in that in a production environment, if a unified portal system is not available, the proxy rules may be configured using the Nginx or other reverse proxy server to forward the request directly to the backend server. In particular, a high-performance HTTP server and reverse proxy server are widely used for deployment and reverse proxy of Web services.
Through the standby access steps and the related technologies, even if a unified portal system is not available, communication between the sub-application and the back-end service is not affected, so that the availability and fault tolerance of the whole system are improved.
In a preferred implementation, the access method includes a second access step of accessing the sub-applications through a unified portal system of a main application, the main application embedding a plurality of sub-applications based on iframes, the second access step including:
s1000, obtaining login credentials of all sub-applications.
In implementations, when a user logs into the main application, the system automatically obtains or generates login credentials, such as OAuth tokens or JWT, required by the sub-application.
And S2000, loading a portal menu of the unified portal system, wherein the portal menu comprises a sub-application catalog configured with deployment addresses of a plurality of sub-applications.
In a specific implementation, all available sub-applications are exposed, allowing the user to select the sub-applications they want to access. The portal menu may be a navigation bar or drop down list listing the names and icons of all sub-applications and configured with the deployment address of each sub-application.
S3000, loading the corresponding sub-application according to the deployment address according to the input sub-application selection information.
In a specific implementation, the corresponding sub-application is loaded and displayed according to the selection of the user. After clicking the sub-application in the portal menu, the system loads the corresponding sub-application through the iframe according to the configured deployment address.
S4000, generating a sub-application access request according to the login credentials, the authority information and the routing configuration, and sending the sub-application.
In a specific implementation, it is ensured that the sub-application can load the user interface correctly according to the login credentials and rights information of the user. The system constructs an access request according to the login credentials, the authority and the routing configuration of the user, and sends the access request to the sub-application, and can adopt an API call or a specific authentication protocol.
S5000, acquiring a sub-application interface returned by the sub-application, and displaying the sub-application interface in the main application based on the iframe.
In an implementation, after the sub-application is loaded, the HTML content of the user interface is returned. The main application embeds the main application into the page of the main application through the iframe, and a user can directly interact with the sub-application in the main application.
In the second access step, the iframe is an HTML element, allowing one HTML document to be embedded in another document, forming a framework. Examples < IFRAME SRC = "http:// supp. Sample. Com"/> routing rules defined in the front-end application are used to decide which component or page the different URLs correspond to load. Rights information-the access rights of users in the system, determine which resources they can access.
Specifically, as shown in FIG. 3, the general technical route of the second access step includes 1, obtaining login credentials of all subsystems. In order to realize the login of the user in all the sub-applications, the login credentials of the user in each sub-system need to be acquired. After the user logs in the unified portal system, the system automatically acquires or generates access rights to each sub-application. 2. A portal menu is acquired. The method aims at displaying all sub-applications which can be accessed by a user and providing a navigation function. Implementation the portal menu exposes a list of all sub-applications, possibly including system modules like srm (vendor relation management), bsp (business support platform), cms (content management system), etc. 3. Subsystem pages are embedded by iframe technology. The method aims at embedding sub-applications in the interface of the unified portal system, so that a user can access different applications in one interface. When a user selects a certain sub-application, the portal system uses the iframe tag to load a corresponding sub-system page. 4. Obtain login credentials from the portal system, etc. The objective is to ensure that the subsystem is able to recognize and accept user credentials from the portal system, allowing user access. Implementation when subsystem pages are loaded, login credentials are received from the portal system through a specific API or configuration. 5. Address + menu route gets subsystem page. The purpose is to load the corresponding subsystem page according to the selection of the user. Each sub-application has a basic deployment address, and can be positioned to a specific page by combining with menu routing. The portal system requests the subsystem page by building the complete URL. 6. Embedded into a unified portal system. The method aims at embedding the subsystem page into the iframe of the portal system to realize seamless integration. The implementation is that the portal system dynamically creates an iframe and embeds a subsystem page as a source into the iframe. 7. The method aims to solve the problem of safety limitation caused by that a factor system and a portal system are not in the same domain. Implementation, cross-domain request and data transmission are allowed by using a CORS (cross-source resource sharing) strategy or by a proxy server and the like. 8. Click menu outward turning the objective is to provide the user with the ability to navigate from the current sub-application to other sub-applications. When the user clicks different options in the portal menu, the portal system updates the sub-application page in the iframe to reflect the user's selection.
The invention also provides an access system based on the unified portal, which adopts a micro front-end architecture comprising a main application and a plurality of sub-applications, wherein the main application is provided with the unified portal system. The access system is used for realizing the access method based on the unified portal.
The main application is used for proxy the sub-application to access the back-end service, and the unified portal system of the main application comprises:
An acquisition module for acquiring a service access request of a sub-application, the service access request is used for accessing the back-end service;
the communication module is used for responding to the service access request and establishing an access link between the unified portal system and the back-end server;
A sending module, configured to send the service access request to a backend server;
And the return module is used for responding to the service access request and returning the service data of the back-end server to the sub-application through the unified portal system.
Specifically, the sub-application includes:
A first rule access module for sending the service access request to a back-end server using proxy rules configured in vue.config.js when the unified portal system cannot be accessed, or
And the second rule access module is used for sending the service access request to a back-end server by using the proxy rule configured in the Nginx when the unified portal system cannot be accessed.
Specifically, the service access request is divided into a development access service request and a production access service request;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
Specifically, the main application embeds a plurality of sub-applications based on the iframe, and the unified portal system further comprises:
the acquisition module is also used for acquiring login credentials of all sub-applications;
a menu module for loading a portal menu of the unified portal system, the portal menu comprising a sub-application directory configured with deployment addresses of a plurality of sub-applications;
the loading module is used for loading the corresponding sub-application according to the deployment address according to the input sub-application selection information;
the sending module is also used for generating a sub-application access request according to the login credentials, the authority information and the routing configuration and sending the sub-application;
And the display module is used for acquiring a sub-application interface returned by the sub-application and displaying the sub-application interface in the main application based on the iframe.
In the present invention, there is also provided an application service platform, the application service platform including 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 with each other;
Wherein the host application comprises a unified portal system, the host application being configured to perform a unified portal based access method as described above.
In implementations, the sub-applications include a collection system, a vendor portal system, and a contract system. Specifically, as shown in fig. 4 and fig. 5, the descriptions of user login, newly added user, and user information synchronization of the main application, the sub application, and the data center system are as follows:
User authentication and authorization process
1. Checking the incoming parameters-when the user attempts to log in, the system first checks the credentials (e.g., username and password) entered by the user.
2. Judging whether the same user name exists or not, wherein the system checks whether the user name exists in the database or not, so that the uniqueness of the user is ensured.
3. Verification passes that if the user credentials are valid, the system will generate a token based on the user information.
4. Generating token tokens:
The system creates JWT (JSON Web Token) or other form of token that contains information about the user's role, rights, etc., and has a certain expiration date (e.g., 7 days).
5. The generated token is used for the subsequent access request of the user to each subsystem, and single sign-on is realized.
(II) user data and rights management
1. And taking all roles, menus and authority information of the user call, wherein the system retrieves all roles and authority information of the user so as to provide corresponding access menus and functions.
2. The system determines the system modules and data which can be accessed by the user according to the role and authority information of the user.
(III) data synchronization flow
1. Judging whether user synchronization is needed, namely judging whether the user data are needed to be synchronized to other systems or data centers by the system when the user data are changed in the system.
2. And (3) notifying the data center service to synchronize, wherein if the data center service needs to be synchronized, the system notifies the data center service and triggers a data synchronization flow.
3. And a new user or user change message, wherein the system requests the data center service to update the user information for the change of the new user or the existing user.
4. Judging whether the same user name exists or not, and checking the uniqueness of the user name again by the system when the user is newly added, so that repetition is avoided.
5. User information synchronization-finally, the system ensures that the user information remains consistent and up-to-date across all relevant systems.
JWT (JSON Web Token) a compact, URL-secured way to pass claims between web application environments. JWT may be used to authenticate user identity.
Token, an access control mechanism, for identifying users or services and controlling access to resources.
Data center systems-central repositories that store and manage organizational data are typically responsible for the persistence, backup, and recovery of data.
The access method, system and other structures of the application service platform based on the unified portal described in this embodiment refer to the prior art.
The present invention is not limited to the preferred embodiments, and any modifications, equivalent variations and modifications made to the above embodiments according to the technical principles of the present invention are within the scope of the technical proposal of the present invention.
Claims (10)
1. An access method based on a unified portal is characterized by being applied to a micro front-end architecture comprising a main application and a plurality of sub-applications, wherein the main application is provided with a unified portal system;
The access method comprises a first access step of the sub-application to access the back-end service, wherein the first access step comprises the following steps:
acquiring a service access request of a sub-application, wherein the service access request is used for accessing a 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 responding to the service access request, and returning the service data of the back-end server to the sub-application through the unified portal system.
2. The unified portal based access method as claimed in claim 1 wherein the first access step further comprises:
when the unified portal system cannot be accessed;
transmitting the service access request to a back-end server by using proxy rules configured in vue.config.js, or
And sending the service access request to a back-end server by using the proxy rule configured in Nginx.
3. The unified portal based access method of claim 1, wherein:
the service access request is divided into a development access service request and a production access service request;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
4. The unified portal based access method of claim 1, wherein:
The access method comprises a second access step of accessing the sub-applications through a unified portal system of a main application, wherein the main application is embedded with a plurality of sub-applications based on iframes, and the second access step comprises the following steps:
obtaining login credentials of all sub-applications;
Loading a portal menu of the unified portal system, wherein the portal menu comprises a sub-application catalog configured with deployment addresses of a plurality of sub-applications;
loading corresponding sub-applications according to the deployment addresses according to the input sub-application selection information;
generating a sub-application access request according to the login credentials, the authority information and the routing configuration, and sending the sub-application;
And acquiring a sub-application interface returned by the sub-application, and displaying the sub-application interface in the main application based on the iframe.
5. A unified portal based access method according to any of claims 1 to 4 wherein:
The sub-applications comprise a collection system, a provider portal system and a contract system;
the back-end servers include SRM servers, CMS servers, DUP servers, and BSP servers.
6. An access system based on a unified portal is characterized in that the access system adopts a micro front-end architecture comprising a main application and a plurality of sub-applications, wherein the main application is provided with the unified portal system;
the main application is used for proxy the sub-application to access the back-end service, and the unified portal system of the main application comprises:
An acquisition module for acquiring a service access request of a sub-application, the service access request is used for accessing the back-end service;
the communication module is used for responding to the service access request and establishing an access link between the unified portal system and the back-end server;
A sending module, configured to send the service access request to a backend server;
And the return module is used for responding to the service access request and returning the service data of the back-end server to the sub-application through the unified portal system.
7. The unified portal based access system of claim 6, wherein the sub-application comprises:
A first rule access module for sending the service access request to a back-end server using proxy rules configured in vue.config.js when the unified portal system cannot be accessed, or
And the second rule access module is used for sending the service access request to a back-end server by using the proxy rule configured in the Nginx when the unified portal system cannot be accessed.
8. A unified portal based access system as claimed in claim 6 wherein:
the service access request is divided into a development access service request and a production access service request;
The unified portal system sends the development access service request to a back-end server by using the proxy rule configured in the vue.config.js;
The unified portal system sends the production access service request to a back-end server by using proxy rules configured in vue.
9. The unified portal based access system as claimed in claim 6 wherein the host application embeds a plurality of sub-applications based on iframes, the unified portal system further comprising:
the acquisition module is also used for acquiring login credentials of all sub-applications;
a menu module for loading a portal menu of the unified portal system, the portal menu comprising a sub-application directory configured with deployment addresses of a plurality of sub-applications;
the loading module is used for loading the corresponding sub-application according to the deployment address according to the input sub-application selection information;
the sending module is also used for generating a sub-application access request according to the login credentials, the authority information and the routing configuration and sending the sub-application;
And the display module is used for acquiring a sub-application interface returned by the sub-application and displaying the sub-application interface in the main application based on the iframe.
10. An application service platform, wherein the application service platform comprises a main application, a plurality of sub-applications and a data center system, and the main application, the plurality of sub-applications and the data center system are mutually connected;
Wherein the host application comprises a unified portal system, the host application being configured to perform a unified portal based access method as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411286984.4A CN119172369A (en) | 2024-09-13 | 2024-09-13 | A unified portal-based access method, system and application service platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202411286984.4A CN119172369A (en) | 2024-09-13 | 2024-09-13 | A unified portal-based access method, system and application service platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119172369A true CN119172369A (en) | 2024-12-20 |
Family
ID=93878122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202411286984.4A Pending CN119172369A (en) | 2024-09-13 | 2024-09-13 | A unified portal-based access method, system and application service platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN119172369A (en) |
-
2024
- 2024-09-13 CN CN202411286984.4A patent/CN119172369A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10244058B2 (en) | Extending functionality of applications | |
| US7903656B2 (en) | Method and system for message routing based on privacy policies | |
| US7752335B2 (en) | Networked computing using objects | |
| US9578088B2 (en) | Globally distributed utility computing cloud | |
| EP1872227B1 (en) | System and method of testing wireless component applications | |
| KR101066659B1 (en) | Present Process Flow and Correlation Controllers as Web Services | |
| US8140987B2 (en) | GUI modeling of web services | |
| US8775671B2 (en) | Managing information exchange between business entities | |
| US20020116454A1 (en) | System and method for providing communication among legacy systems using web objects for legacy functions | |
| US20080141350A1 (en) | Authentication for computer system management | |
| KR101497167B1 (en) | Management of external hardware devices in distributed operating systems | |
| CN1333342C (en) | Exchange infrastructure system and method | |
| Indrasiri | Beginning WSO2 ESB | |
| JP2002358290A (en) | Information processing service providing method, program and system | |
| JP2004246747A (en) | Existing service wrapping method and device | |
| US6880151B2 (en) | Apparatus and method of providing common distributed services for system management applications across heterogeneous environments | |
| US20060026260A1 (en) | Method of communicating between web applications and local client application while maintaining remote user session | |
| EP1468544B1 (en) | Method and apparatus for controlling a multi-node process | |
| CN119172369A (en) | A unified portal-based access method, system and application service platform | |
| CN116132344B (en) | Container service debugging method and device based on K8s cluster and electronic equipment | |
| Davies et al. | WebSphere MQ V6 Fundamentals | |
| CN117407041A (en) | Docking methods, electronic devices and storage media | |
| JPH1185686A (en) | Method and device for processing information and storage medium storing program for controlling server | |
| CN114461424A (en) | Inter-unit service discovery method, device and system under unitized deployment architecture | |
| Sakar | Building Modern Serverless Web APIs: Develop Microservices and Implement Serverless Applications with. NET Core 3.1 and AWS Lambda (English Edition) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |