Multi-region federal structure middle platform service publishing access method, system and device

Abstract

The application discloses a multi-region federation structure middle platform service publishing access method, system and equipment, mainly relates to the technical field of business middle platform service, and is used for solving the problems such as the need of regional registration of existing business application. It comprises the following steps: obtaining API information and service name of IP and port of a proxy service instance to generate a standard service directory; after the standard service directory is audited and published, the published standard service directory is added to the preset global visible service directory of each regional system through federation query technology; a terminal of a business application access obtains the standard service directory through the preset global visible service directory in any regional system; then, the calling permission of API information corresponding to the selected preset middle platform service port name in the standard service directory is obtained; and an access request is sent to the middle platform service gateway corresponding to the calling permission.

Description

Technical Field

[0001] This application relates to the field of business middleware service catalog processing technology, and in particular to a middleware service publishing and access method, system and device with a multi-region federation structure. Background Technology

[0002] As an enterprise-level information platform, the business middle platform is business-centric, aggregating various internal business modules through standardization and modularization to form the infrastructure supporting the overall business activities of the enterprise. As an important component of the business middle platform, the business middle platform service catalog provides comprehensive information and accessibility of middle platform services.

[0003] The business middle platform service approach includes publishing the business middle platform service catalog and application access. Currently, under the organizational structure of "headquarters + N provincial sides," to improve the availability and customization support of business middle platform services, a two-tier, multi-region deployment is adopted. The process of publishing the business middle platform service catalog and application access can be summarized as follows: Headquarters side and Provincial side. Each middle platform service on both the headquarters and provincial sides provides a service name, service instance IP address, and port, and the service catalog is updated and published on the business middle platform management platform. Business applications obtain service invocation permissions from the business middle platform management platform and invoke the business middle platform services on the headquarters side.

[0004] However, under the existing "headquarters + provincial" regional deployment model for the business middle platform, the headquarters and provincial business middle platforms operate independently, each maintaining its own service catalog and processing application registration applications. While this has no impact on business applications dependent on a single region, a large number of business applications within an enterprise call services across regional business middle platforms. In this situation, application information needs to be registered separately on both the headquarters and provincial sides to access the middle platform services in each region. The registration, updating, and publishing of the business middle platform service catalog relies on manual processing by operations and management personnel, making timely and automatic updates impossible and preventing the formation of a globally integrated enterprise middle platform service catalog. Summary of the Invention

[0005] To address the aforementioned shortcomings of existing technologies, this application provides a method, system, and device for publishing and accessing middleware services in a multi-regional federated structure. This solves the technical problem that cross-regional business middleware requires registration of application information in multiple regional systems, which is cumbersome. Furthermore, the registration, updating, and publishing of the business middleware service catalog relies on manual processing by operations and management personnel, which cannot form a global enterprise middleware service catalog.

[0006] Firstly, this application provides a method for publishing and accessing middleware services in a multi-regional federated structure. The method includes: obtaining the IP address and port API information and service name of a proxy service instance to generate a standard service directory; after the standard service directory is reviewed and published, adding the published standard service directory to the preset global visible service directory of each regional system through federated query technology; wherein, the standard service directory includes the regional system name, the preset middleware service port name, the service name, and the API information; the terminal accessing the business application obtains the standard service directory through the preset global visible service directory in any regional system; thereby obtaining the calling permission for the API information corresponding to the selected preset middleware service port name in the standard service directory; and sending an access request to the middleware service gateway corresponding to the calling permission.

[0007] Furthermore, before obtaining the API information and service name of the proxy service instance's IP and port to generate a standard service catalog, the method also includes: registering with the preset registration center within the regional system through the preset middleware service port of the regional system; wherein, the regional system includes the headquarters-side regional system and the provincial-side regional system; and determining the service name and the IP and port of the service instance within the regional system in the preset registration center.

[0008] Furthermore, the API information and service name of the proxy service instance's IP and port are obtained, specifically including: obtaining the registered preset middleware service port based on the service discovery mechanism; and obtaining the API information and service name of the proxy service instance's IP and port through the Swagger interface of the preset middleware service port.

[0009] Furthermore, after obtaining the API information and service name of the proxy service instance's IP and port to generate a standard service catalog, the method also includes: generating a standard service catalog review task after generating the standard service catalog, so as to publish the standard service catalog after the review task passes the review.

[0010] Furthermore, the terminal accessing the business application obtains the standard service directory through the preset global visible service directory in any regional system; then obtains the calling permission for the API information corresponding to the preset middleware service port name selected in the standard service directory; and sends an access request to the middleware service gateway corresponding to the calling permission. Specifically, this includes: uploading registration application information through the preset business middleware management platform in any regional system to obtain AccessKey and SecretKey; selecting the subscribed preset middleware service port name from the standard service directory in the preset global visible service directory of the regional system, and then selecting the API information corresponding to the preset middleware service port name to obtain the calling permission for the API information corresponding to the preset middleware service port name; wherein, the API information corresponding to the preset middleware service port name is the preset middleware service port; the terminal accessing the business application carries the AccessKey and SecretKey to call the preset middleware service port with calling permission in the regional system; and sending an access request to the middleware service gateway of the preset middleware service port with calling permission through the cross-regional service routing connected to the regional system; and the middleware service gateway performing application authentication and service routing based on the access request.

[0011] Secondly, this application provides a multi-regional federated architecture middleware service publishing and access system. The system includes: a publishing module, used to obtain the IP address and port API information and service name of the proxy service instance to generate a standard service directory; after the standard service directory is reviewed and published, the published standard service directory is added to the preset global visible service directory of each regional system through federated query technology; wherein, the standard service directory includes the regional system name, the preset middleware service port name, the service name, and the API information; a business application access module, used by the terminal for business application access to obtain the standard service directory through the preset global visible service directory in any regional system; thereby obtaining the calling permission for the API information corresponding to the preset middleware service port name selected in the standard service directory; and sending an access request to the middleware service gateway corresponding to the calling permission.

[0012] Furthermore, the publishing module includes an acquisition unit, which is used to acquire the registered preset middleware service port based on the service discovery mechanism; and to acquire the API information and service name of the proxy service instance's IP and port through the Swagger interface of the preset middleware service port.

[0013] Furthermore, the publishing module includes a publishing unit, which generates a standard service catalog review task after the standard service catalog is generated, so as to publish the standard service catalog after the review task is approved.

[0014] Furthermore, the business application access module includes a business access unit, used to allow the terminal accessing the business application to upload registration application information through a preset business middleware management platform in any regional system to obtain AccessKey and SecretKey; the terminal accessing the business application selects the subscribed preset middleware service port name from the standard service directory in the preset global visible service directory of the regional system, and then selects the API information corresponding to the preset middleware service port name to obtain the calling permission for the API information corresponding to the preset middleware service port name; wherein, the API information corresponding to the preset middleware service port name is the preset middleware service port; the terminal accessing the business application carries AccessKey and SecretKey to call the preset middleware service port with calling permission in the regional system; through the cross-regional service routing connected to the regional system, it sends an access request to the middleware service gateway of the preset middleware service port with calling permission; the middleware service gateway performs application authentication and service routing according to the access request.

[0015] Thirdly, this application provides a middleware service publishing and access device for a multi-region federation structure. The device includes: a processor; and a memory storing executable code thereon. When the executable code is executed, the processor executes a middleware service publishing and access method for a multi-region federation structure as described above.

[0016] Those skilled in the art will understand that this application has at least the following beneficial effects: This application, building upon traditional business middleware service registration, publishing, subscription, and access, adds a dynamic service directory publishing function. This function dynamically detects newly launched middleware services within its respective region, obtaining service API (Application Program Interface) details (API information such as the IP address and port of the proxy service instance and the service name), and then generates a standard service directory. After review and publication, service directory queries can be performed across regions using federated query technology (federated structure), generating a pre-defined globally visible service directory across all regions in a loosely coupled manner. This solves the problem that the registration, updating, and publishing of the business middleware service directory relied on manual processing by operations and management personnel, failing to create an enterprise-wide middleware service directory. Furthermore, this application provides unified access for business applications. Terminals accessing business applications only need to register and access the nearest regional system, eliminating the need for separate cross-regional registration. The middleware service gateway handles cross-regional service calls (obtaining call permissions for the selected pre-defined middleware service port through the pre-defined globally visible service directory in any regional system), resolving the cumbersome process of registering application information separately in multiple regional systems for cross-regional business middleware. Attached Figure Description

[0017] The following description refers to some embodiments of this disclosure, in which: Figure 1 This is a flowchart of a middleware service publishing and access method for a multi-regional federated structure provided in an embodiment of this application.

[0018] Figure 2 This is a schematic diagram of the internal structure of a multi-regional federated structure middleware service publishing and access system provided in an embodiment of this application.

[0019] Figure 3 This is a schematic diagram of the internal structure of a multi-regional federated structure middleware service publishing and access system provided in an embodiment of this application. Detailed Implementation

[0020] Those skilled in the art should understand that the embodiments described below are merely preferred embodiments of this disclosure and do not imply that this disclosure can only be implemented through these preferred embodiments. These preferred embodiments are merely used to explain the technical principles of this disclosure and are not intended to limit the scope of protection of this disclosure. All other embodiments obtained by those skilled in the art based on the preferred embodiments provided in this disclosure without inventive effort should still fall within the scope of protection of this disclosure.

[0021] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0022] The technical solutions proposed in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0023] This application provides a method for publishing and accessing middleware services in a multi-region federated structure, such as... Figure 1 As shown in the embodiments of this application, the method mainly includes the following steps: Step 110: Obtain the API information and service name of the proxy service instance's IP and port to generate a standard service directory; after the standard service directory is reviewed and published, add the published standard service directory to the preset global visible service directory of each regional system through federated query technology.

[0024] It should be noted that the standard service catalog includes the regional system name, the default middleware service port name, the service name, and API information.

[0025] In addition, prior to this step, this application can register the middleware service. The specific process can be as follows: register with the preset registration center within the regional system through the preset middleware service port of the regional system; wherein, the regional system includes the headquarters-side regional system and the provincial-side regional system; determine the service name and the IP and port of the service instance within the regional system in the preset registration center.

[0026] It should be noted that the regional system includes the headquarters-side regional system and the provincial-side regional system. Each regional system contains several systems, each with a corresponding service name, service instance IP address, and port.

[0027] In step 110, obtaining the API information and service name of the proxy service instance's IP and port can be specifically done by: obtaining the registered preset middleware service port based on the service discovery mechanism; and obtaining the API information and service name of the proxy service instance's IP and port through the Swagger interface of the preset middleware service port.

[0028] The "service discovery mechanism" here can be specifically referred to as a server-side discovery model. Those skilled in the art can trigger the service discovery mechanism during the review and publication of a standard service catalog.

[0029] In this application, after obtaining the API information and service name of the proxy service instance's IP and port to generate a standard service catalog, there is a standard service catalog review process. Specifically, after generating the standard service catalog, a standard service catalog review task is generated, and the standard service catalog is published after the review task is approved.

[0030] It should be added here that the review process for the review task can be carried out manually or through a preset review procedure. The preset review procedure is any feasible procedure written by a person skilled in the art based on actual needs.

[0031] Step 120: The terminal accessing the business application obtains the standard service directory through the preset global visible service directory in any regional system; then obtains the API calling permission corresponding to the preset middleware service port name selected in the standard service directory; and sends an access request to the middleware service gateway corresponding to the calling permission.

[0032] As an example, this step can be specifically described as follows: Through a pre-defined business middleware management platform in any regional system, the terminal accessing the business application uploads registration application information to obtain AccessKey and SecretKey. The terminal then selects the subscribed pre-defined middleware service port name from the standard service directory of the pre-defined globally visible service directory in the regional system, and subsequently selects the API information corresponding to that pre-defined middleware service port name to obtain the calling permission for that API information. The API information corresponding to the pre-defined middleware service port name is the pre-defined middleware service port. The terminal, carrying AccessKey and SecretKey, calls the pre-defined middleware service port with the calling permission from the regional system. Through the cross-regional service routing connected to the regional system, it sends an access request to the middleware service gateway of the pre-defined middleware service port with the calling permission. The middleware service gateway performs application authentication and service routing based on the access request.

[0033] besides, Figure 2 This application provides a multi-regional federated structure middleware service publishing and access system. For example... Figure 2 As shown in the embodiments of this application, the system mainly includes: The publishing module 210 is used to obtain the API information and service name of the proxy service instance's IP and port through the service discovery mechanism of the preset dynamic service directory publishing device, so as to generate a standard service directory; after the standard service directory is reviewed and published, the published standard service directory is added to the preset global visible service directory of each regional system through federated query technology.

[0034] It should be noted that the standard service catalog includes the regional system name, the default middleware service port name, the service name, and API information.

[0035] Specifically, obtaining the API information and service name of the proxy service instance's IP and port can be achieved as follows: the acquisition unit 211 in the publishing module 210 obtains the registered preset middleware service port based on the service discovery mechanism; and obtains the API information and service name of the proxy service instance's IP and port through the Swagger interface of the preset middleware service port.

[0036] Specifically, obtaining the API information and service name of the proxy service instance's IP and port can be achieved by: after generating the standard service directory, the publishing unit 212 in the publishing module 210 generates a standard service directory review task, so as to publish the standard service directory after the review task is approved.

[0037] The business application access module 220 is used by terminals that access business applications to obtain access permissions for selected preset middleware service ports through preset global visible service directories in any regional system, and send access requests to the middleware service gateway corresponding to the selected preset middleware service port.

[0038] The specific process can be as follows: The business access unit 221 in the business application access module 220 uploads the registration application information of the terminal accessing the business application through the preset business middleware management platform in any regional system to obtain the AccessKey and SecretKey; the terminal accessing the business application selects the subscribed preset middleware service port name from the standard service directory in the preset global visible service directory of the regional system, and then selects the API information corresponding to the preset middleware service port name to obtain the calling permission of the API information corresponding to the preset middleware service port name; wherein, the API information corresponding to the preset middleware service port name is the preset middleware service port; the terminal accessing the business application carries the AccessKey and SecretKey and calls the preset middleware service port with calling permission to the regional system; through the cross-regional service routing connected to the regional system, it sends an access request to the middleware service gateway of the preset middleware service port with calling permission; the middleware service gateway performs application authentication and service routing according to the access request.

[0039] The above are method embodiments of this application. Based on the same inventive concept, embodiments of this application also provide a middleware service publishing and access device for a multi-regional federated structure. Figure 3 As shown, the device includes: a processor; and a memory storing executable code thereon, which, when executed, causes the processor to perform a middleware service publishing and access method for a multi-region federation structure as described in the above embodiments.

[0040] Specifically, the server obtains the IP address and port of the proxy service instance, along with its API information and service name, to generate a standard service directory. After the standard service directory is reviewed and published, it is added to the preset global visible service directory of each regional system using federated query technology. The standard service directory includes the regional system name, the preset middleware service port name, the service name, and the API information. Terminals accessing the business application obtain the standard service directory through the preset global visible service directory in any regional system. They then obtain the access permission to call the API information corresponding to the selected preset middleware service port name in the standard service directory and send an access request to the middleware service gateway corresponding to the access permission.

[0041] The technical solutions of this disclosure have been described in conjunction with the preceding embodiments. However, it will be readily understood by those skilled in the art that the scope of protection of this disclosure is not limited to these specific embodiments. Without departing from the technical principles of this disclosure, those skilled in the art can disassemble and combine the technical solutions in the above embodiments, and can also make equivalent changes or substitutions to the relevant technical features. Any changes, equivalent substitutions, improvements, etc., made within the technical concept and / or technical principles of this disclosure will fall within the scope of protection of this disclosure.

Claims

1. A method for publishing and accessing middleware services in a multi-regional federated structure, characterized in that, The method includes: Obtain the IP address, port, API information, and service name of the proxy service instance to generate a standard service directory; after the standard service directory is reviewed and published, add the published standard service directory to the preset global visible service directory of each regional system through federated query technology; the standard service directory includes the regional system name, preset middleware service port name, service name, and API information; Terminals accessing business applications obtain the standard service directory through a preset global visible service directory in any regional system; then obtain the API calling permissions corresponding to the preset middleware service port name selected in the standard service directory; and send an access request to the middleware service gateway corresponding to the calling permissions.

2. The method for publishing and accessing middleware services in a multi-regional federated structure according to claim 1, characterized in that, Before obtaining the API information and service name of the proxy service instance's IP and port to generate the standard service catalog, the method further includes: Register with the pre-set registration center within the regional system through the pre-set middleware service port of the regional system; the regional system includes the headquarters-side regional system and the provincial-side regional system; Determine the service name and service instance IP and port within the regional system of the preset registry center.

3. The method for publishing and accessing middleware services in a multi-regional federated structure according to claim 1, characterized in that, The API information and service name for obtaining the proxy service instance's IP address, port, and service name are as follows: Based on the service discovery mechanism, obtain the pre-defined middleware service port of the registration; By using the Swagger interface of the pre-defined middleware service port, obtain the API information and service name of the proxy service instance's IP address and port.

4. The method for publishing and accessing middleware services in a multi-regional federated structure according to claim 1, characterized in that, After obtaining the API information and service name of the proxy service instance's IP and port to generate a standard service catalog, the method further includes: After generating the standard service catalog, a standard service catalog review task is generated, and the standard service catalog is published after the review task is approved.

5. The method for publishing and accessing middleware services in a multi-regional federated structure according to claim 1, characterized in that, Terminals accessing business applications can obtain the standard service directory through the preset global visible service directory in any regional system; and then obtain the API calling permissions corresponding to the preset middleware service port name selected in the standard service directory. Send an access request to the middleware service gateway corresponding to the access permission, specifically including: Through the preset business middleware management platform in any regional system, the terminal accessing the business application uploads the registration application information to obtain the AccessKey and SecretKey; Terminals accessing business applications select the subscribed preset middleware service port name from the standard service directory in the preset global visible service directory of the regional system, and then select the API information corresponding to the preset middleware service port name to obtain the calling permission of the API information corresponding to the preset middleware service port name; whereby the API information corresponding to the preset middleware service port name is the preset middleware service port. The terminal accessing the business application carries the AccessKey and SecretKey to call the preset middleware service port with calling authority from the regional system; Through the cross-regional service routing of the regional system, an access request is sent to the middleware service gateway of the preset middleware service port corresponding to the calling permission; The middleware service gateway performs application authentication and service routing based on access requests.

6. A middleware service publishing and access system with a multi-regional federated structure, characterized in that, The system includes: The publishing module is used to obtain the IP address and port of the proxy service instance, API information, and service name to generate a standard service directory. After the standard service directory is reviewed and published, it is added to the preset global visible service directory of each regional system through federated query technology. The standard service directory includes the regional system name, preset middleware service port name, service name, and API information. The business application access module is used by terminals that access business applications to obtain a standard service directory through a preset global visible service directory in any regional system; then obtain the API calling permissions corresponding to the preset middleware service port name selected in the standard service directory; and send an access request to the middleware service gateway corresponding to the calling permissions.

7. The multi-regional federated structure middleware service publishing and access system according to claim 6, characterized in that, The publishing module includes an acquisition unit. Used to obtain the pre-registered middleware service port based on the service discovery mechanism; and to obtain the API information and service name of the proxy service instance's IP and port through the Swagger interface of the pre-registered middleware service port.

8. The multi-regional federated structure middleware service publishing and access system according to claim 6, characterized in that, The publishing module includes publishing units. This is used to generate a standard service catalog review task after the standard service catalog is generated, so that the standard service catalog can be published after the review task is approved.

9. The multi-regional federated structure middleware service publishing and access system according to claim 6, characterized in that, The business application access module includes a business access unit. This is used to allow terminals accessing business applications to upload and register application information via a pre-defined business middleware management platform in any regional system, in order to obtain AccessKey and SecretKey. The terminals then select the subscribed pre-defined middleware service port name from the standard service directory of the pre-defined globally visible service directory in the regional system, and subsequently select the API information corresponding to that pre-defined middleware service port name to obtain the calling permission for that API information. The API information corresponding to the pre-defined middleware service port name is the pre-defined middleware service port. The terminals, carrying AccessKey and SecretKey, call the pre-defined middleware service port with the calling permission from the regional system. Through the cross-regional service routing connected to the regional system, they send an access request to the middleware service gateway of the pre-defined middleware service port with the calling permission. The middleware service gateway performs application authentication and service routing based on the access request.

10. A middleware service publishing and access device with a multi-regional federated structure, characterized in that, The device includes: processor; And a memory having executable code stored thereon, which, when executed, causes the processor to perform a middleware service publishing and access method for a multi-region federation structure as described in any one of claims 1-5.

Images