Complex data interface management platform based on multiple systems and multiple protocols

Abstract

The invention discloses a complex data interface management platform based on multiple systems and multiple protocols. The complex data interface management platform comprises an interface configuration management module, an interface gateway module and an interface development management module, the interface configuration management module configures interfaces of applications, systems, domain names, back ends and routers; the interface gateway module is a unified management entrance of external system interface requests and carries out unified interception processing on requests for accessing ERP (Enterprise Resource Planning). The interface development management module uniformly manages interfaces needing to be opened to the external system and formulates standardized interfaces. According to the invention, unified interface management and secure routing are carried out by using a gateway, asynchronous tasks are processed by combining a message queue system RabbitMQ, efficient caching of data is realized by using Redis, and communication between systems is carried out by supporting multiple protocols such as HTTP (Hyper Text Transport Protocol) and the like; technical components act together to help to improve the stability and maintainability of the system, and meanwhile, the data interaction and cooperation efficiency between the systems is optimized.

Description

Technical Field

[0001] The present invention relates to the field of interface management, and in particular to a multi-system and multi-protocol complex data interface management platform. Background Art

[0002] ERP systems need to exchange data and call interfaces with multiple systems. Most of the data interface management platforms currently used are for a single system or a single protocol, and data interface management platforms for complex multiple systems and multiple protocols are relatively scarce. Traditional solutions may be limited to specific fields or technology stacks, and cannot effectively integrate and manage data exchanges between multiple systems and multiple protocols. They are also prone to system fragmentation and data silos, insufficient protocol compatibility, incomplete log monitoring, and insufficient early warning mechanisms. Summary of the invention

[0003] The purpose of the present invention is to propose a multi-system multi-protocol complex data interface management platform based on the above-mentioned technical problems, so as to solve the problems of interface data transmission and communication difficulties between multiple business systems, unified interface specifications, multi-protocol support, chain log collection and monitoring, and interface warnings that cannot be fed back to business personnel in a timely manner.

[0004] A multi-system multi-protocol complex data interface management platform, including an interface configuration management module, an interface gateway module, and an interface development management module; The interface configuration management module configures the interfaces of application, system, domain name, backend and routing; The interface gateway module is a unified management entry for external system interface requests, and uniformly intercepts and processes requests to access ERP; The interface development management module uniformly manages interfaces that need to be opened to external systems and formulates standardized interfaces.

[0005] Furthermore, a multi-system multi-protocol complex data interface management platform is provided, wherein the interface configuration management module includes an interface application authority configuration management submodule, an interface system configuration management submodule, an interface domain name management submodule, an interface backend service management submodule, and an interface routing management submodule; The interface application authority configuration management submodule is used for configuring interface authority and allocating corresponding interface authority to the application through signature authentication; The interface system configuration management submodule provides a system identifier for the interface registered on the interface platform and configures a unique system for each service; The interface domain name management submodule identifies the domain name of the real address of the service forwarding; The interface backend service management submodule corresponds to the business interface and configures the interface forwarding path and service information; The interface routing management submodule provides a request interface to the outside world and defines the associated service information of the routing.

[0006] Furthermore, a complex data interface management platform based on multiple systems and multiple protocols is provided, wherein the interface gateway module is deployed separately on the bastion host.

[0007] Furthermore, a complex data interface management platform based on multiple systems and multiple protocols is provided, wherein the interface development management module uses nacos middleware as a service registration tool, uses redis cache middleware, and uses rabbitmq message middleware.

[0008] Further, a multi-system multi-protocol complex data interface management platform, the interface configuration management module functions to define services and define interfaces for external systems; Define services to define the functions or service types provided by external systems; Defining an interface is to define specific operations and data interaction methods.

[0009] Further, a multi-system multi-protocol complex data interface management platform, wherein the defined services include user authentication and data query; The defined interface includes the path and HTTP method of the RESTful API.

[0010] Further, a multi-system multi-protocol complex data interface management platform, the interface configuration management module function also includes adding and configuring the request header information of each external system; The request header information includes authentication credentials, security tokens or custom HTTP headers.

[0011] The beneficial effects of the present invention are as follows: through a complex data interface management platform based on multiple systems and multiple protocols, a gateway is used for unified interface management and secure routing, the message queue system RabbitMQ is combined to process asynchronous tasks, Redis is used to achieve efficient data caching, and multiple protocols such as HTTP are supported for communication between systems; the technical components work together to help improve the stability and maintainability of the system, while optimizing the data interaction and collaborative efficiency between systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 It is a structural diagram of a complex data interface management platform based on multiple systems and multiple protocols. DETAILED DESCRIPTION

[0013] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described with reference to the accompanying drawings.

[0014] As attached Figure 1As shown, a multi-system multi-protocol complex data interface management platform includes an interface configuration management module, an interface gateway module, and an interface development management module; The interface configuration management module configures the interfaces of application, system, domain name, backend and routing; The interface gateway module is a unified management entry for external system interface requests, and uniformly intercepts and processes requests to access ERP; The interface development management module uniformly manages interfaces that need to be opened to external systems and formulates standardized interfaces.

[0015] Furthermore, a multi-system multi-protocol complex data interface management platform is provided, wherein the interface configuration management module includes an interface application authority configuration management submodule, an interface system configuration management submodule, an interface domain name management submodule, an interface backend service management submodule, and an interface routing management submodule; The interface application authority configuration management submodule is used for configuring interface authority and allocating corresponding interface authority to the application through signature authentication; The interface system configuration management submodule provides a system identifier for the interface registered on the interface platform and configures a unique system for each service; The interface domain name management submodule identifies the domain name of the real address of the service forwarding; The interface backend service management submodule corresponds to the business interface and configures the interface forwarding path and service information; The interface routing management submodule provides a request interface to the outside world and defines the associated service information of the routing.

[0016] Furthermore, a complex data interface management platform based on multiple systems and multiple protocols is provided, wherein the interface gateway module is deployed separately on the bastion host.

[0017] Furthermore, a complex data interface management platform based on multiple systems and multiple protocols is provided, wherein the interface development management module uses nacos middleware as a service registration tool, uses redis cache middleware, and uses rabbitmq message middleware.

[0018] Further, a multi-system multi-protocol complex data interface management platform, the interface configuration management module functions to define services and define interfaces for external systems; Define services to define the functions or service types provided by external systems; Defining an interface is to define specific operations and data interaction methods.

[0019] Further, a multi-system multi-protocol complex data interface management platform, wherein the defined services include user authentication and data query; The defined interface includes the path and HTTP method of the RESTful API.

[0020] Further, a multi-system multi-protocol complex data interface management platform, the interface configuration management module function also includes adding and configuring the request header information of each external system; The request header information includes authentication credentials, security tokens or custom HTTP headers.

[0021] Interface management platform construction: 1. Middleware configuration Rabbitmq message queue: This message queue is mainly used to collect the interface log chain. The rabbitmq message queue can accurately and timely collect the log information of each module and save it to the database.

[0022] Nacos service registration: Using a combination of nacos and openFeign, you can call the interface under the service through service registration.

[0023] Redis cache middleware: publishes and subscribes to messages and uses cache to improve the efficiency of data query.

[0024] saToken authentication: Use the sa-token interceptor to intercept and filter incoming requests.

[0025] 2. Gateway module The gateway module service is deployed independently as a unified entry point for all external requests to achieve centralized management, security control, traffic shaping and monitoring of interfaces, and enhance system stability and security.

[0026] 3. Interface development management module This service needs to be integrated into the business system, and unified specifications should be formed for the interfaces that need to be released externally, including specifications for input parameter types and output parameter types, and all interfaces that allow external systems to access should be managed uniformly.

[0027] 4. Interface configuration management module This service needs to be integrated into the business system to define and publish routes, view logs, and provide a visual management interface through various configuration use cases.

[0028] Steps to use the interface management platform: 1. Creating services in the inter module can support RestFul type interfaces and WebService type interfaces. The interface path exposed by RestFul is: / inter / agent, and the path exposed by WebService is / webservice / agent; 2. If it is a RestFul type, you need to create a service under the com.qm.erp.inter.service package.

[0029] The interface application permission configuration management submodule is used to provide corresponding interface permissions for third-party services. First, you need to create an application, then add interface request permissions to the application, and generate the corresponding appKey and appSecret. The core code is: public QmPage <gwappauthpo>getGwRouterPos(GwAppDto gwAppDto) { LambdaQueryWrapper <gwappauthpo>queryWrapper = newLambdaQueryWrapper<>(); queryWrapper.eq(GwAppAuthPo::getAppKey, gwAppDto.getAppKey()); queryWrapper.eq(GwAppAuthPo::getStatus, 1); Page <gwappauthpo>gwAppAuthPoPage = gwAppAuthDao.selectPage(PageDTO.of(gwAppDto.getCurrentPage(), gwAppDto.getPageSize()),queryWrapper); List <gwappauthpo>gwAppAuthPos = gwAppAuthPoPage.getRecords(); gwAppAuthPos.stream().forEach(g->{ LambdaQueryWrapper <gwrouterpo>objectLambdaQueryWrapper =new LambdaQueryWrapper<>(); objectLambdaQueryWrapper.eq(GwRouterPo::getRouteCode,g.getRouterCode()); GwRouterPo gwRouterPo = gwRouterDao.selectOne(objectLambdaQueryWrapper); g.setRouteName(gwRouterPo.getRouteName()); }); gwAppAuthPoPage.setRecords(gwAppAuthPos); QmPage <gwappauthpo>result = new QmPage<>(); result.setPageInfo(gwAppAuthPoPage); return result; } / *** Find the effective routing permissions, but without paging* public List <gwappauthpo>getGwRouterPosList(GwAppDto gwAppDto){ LambdaQueryWrapper <gwappauthpo>queryWrapper = newLambdaQueryWrapper<>(); queryWrapper.eq(GwAppAuthPo::getAppKey, gwAppDto.getAppKey()); queryWrapper.eq(GwAppAuthPo::getStatus, 1); return gwAppAuthDao.selectList(queryWrapper); } / ** * Add routing permissions in batches public Boolean addRouterPos(@Validated GwAddDto gwAddDto) { try { / / Determine whether the routing permission is to create or modify List <string>routerCodes = gwAddDto.getRouterCodes(); if (!routerCodes.isEmpty()&&StringUtils.isNotBlank(gwAddDto.getAppKey())) { routerCodes.stream().forEach(r ->{ QueryWrapper <gwappauthpo>objectQueryWrapper = newQueryWrapper<>(); objectQueryWrapper.eq("app_key", gwAddDto.getAppKey()).eq("router_code", r); GwAppAuthPo gwAppAuthPo = gwAppAuthDao.selectOne(objectQueryWrapper); if (gwAppAuthPo == null) { GwAppAuthPo gwAppAuthPo1 = new GwAppAuthPo(); gwAppAuthPo1.setAppKey(gwAddDto.getAppKey()); gwAppAuthPo1.setRouterCode(r); gwAppAuthPo1.setStatus(1); gwAppAuthDao.insert(gwAppAuthPo1); / / Clear the redis cache distributeCache.deleteObject(gwAddDto.getAppKey()); } else { gwAppAuthPo.setStatus(1); gwAppAuthDao.updateById(gwAppAuthPo); / / Clear the redis cache distributeCache.deleteObject(gwAddDto.getAppKey()); }});} return true; } catch (Exception e) { return false;}} / ** * Batch remove router permissions public Boolean removeRouterPos2(List <gwappauthdto>gwAppAuthDtoList) { try { if (!gwAppAuthDtoList.isEmpty()) { String appKey = gwAppAuthDtoList.get(0).getAppKey(); List <string>collect = gwAppAuthDtoList.stream().map(GwAppAuthDto::getRouterCode).collect(Collectors.toList()); List <gwappauthpo>objects = new ArrayList<>(); collect.forEach(c ->{ QueryWrapper <gwappauthpo>objectQueryWrapper = newQueryWrapper<>(); objectQueryWrapper.eq("app_key", appKey).eq("router_code", c); GwAppAuthPo gwAppAuthPo = gwAppAuthDao.selectOne(objectQueryWrapper); gwAppAuthPo.setStatus(0); objects.add(gwAppAuthPo); }); objects.forEach(o ->gwAppAuthDao.updateById(o)); / / Clear the redis cache distributeCache.deleteObject(appKey); } return true; }catch (Exception e){ return false;}}}.

[0030] This solution provides a secure and efficient bridge for the interaction between different systems through a complex data interface management platform based on multiple systems and multiple protocols, achieving seamless connection and integration of data and services in a multi-system environment; it emphasizes scalability and security, and as an API gateway, simplifies API lifecycle management, and strengthens support for access control, traffic regulation, and security protection, ensuring the stability and security of cross-service communications; it reduces integration complexity and improves development efficiency and service innovation capabilities.

[0031] The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention. It should be understood by those skilled in the art that the present invention is not limited to the above embodiments. The above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention to be protected. The scope of protection of the present invention is defined by the attached claims and their equivalents.< / gwappauthpo> < / gwappauthpo> < / string> < / gwappauthdto> < / gwappauthpo> < / string> < / gwappauthpo> < / gwappauthpo> < / gwappauthpo> < / gwrouterpo> < / gwappauthpo> < / gwappauthpo> < / gwappauthpo> < / gwappauthpo>

Claims

1. A multi-system multi-protocol complex data interface management platform, characterized in that: Including interface configuration management module, interface gateway module, interface development management module; The interface configuration management module configures the interfaces of application, system, domain name, backend and routing; The interface gateway module is a unified management entry for external system interface requests, and uniformly intercepts and processes requests to access ERP; The interface development management module uniformly manages interfaces that need to be opened to external systems and formulates standardized interfaces.

2. According to claim 1, a multi-system multi-protocol complex data interface management platform is characterized in that: The interface configuration management module includes an interface application authority configuration management submodule, an interface system configuration management submodule, an interface domain name management submodule, an interface backend service management submodule, and an interface routing management submodule; The interface application authority configuration management submodule is used for configuring interface authority and allocating corresponding interface authority to the application through signature authentication; The interface system configuration management submodule provides a system identifier for the interface registered on the interface platform and configures a unique system for each service; The interface domain name management submodule identifies the domain name of the real address of the service forwarding; The interface backend service management submodule corresponds to the business interface and configures the interface forwarding path and service information; The interface routing management submodule provides a request interface to the outside world and defines the associated service information of the routing.

3. According to claim 1, a multi-system multi-protocol complex data interface management platform is characterized in that: The interface gateway module is deployed separately on the bastion host.

4. According to claim 1, a multi-system multi-protocol complex data interface management platform is characterized in that: The interface development management module uses nacos middleware as a service registration tool, redis cache middleware, and rabbitmq message middleware.

5. The multi-system multi-protocol complex data interface management platform according to claim 1, characterized in that: The interface configuration management module functions to define services and interfaces for external systems; Define services to define the functions or service types provided by external systems; Defining an interface is to define specific operations and data interaction methods.

6. A multi-system multi-protocol complex data interface management platform according to claim 5, characterized in that: The defined services include user authentication and data query; The defined interface includes the path and HTTP method of the RESTful API.

7. The multi-system multi-protocol complex data interface management platform according to claim 5, characterized in that: The interface configuration management module function also includes adding and configuring the request header information of each external system; The request header information includes authentication credentials, security tokens or custom HTTP headers.

Images