Interface calling management method and system, electronic equipment and storage medium
Through interface call management methods and systems, the problem of chaos in external interface call management is solved, and the unified management of interface call and the improvement of development efficiency is achieved.
Patent Information
- Application Number
- CN202411691834.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-25
- Publication Date
- 2025-03-18
AI Technical Summary
The prior art lacks a unified proxy or driver engine when handling external interface calls, resulting in confusion in system management, complex development and prone to missed corrections and errors.
It provides an interface call management method and system, by receiving the client's call request information, using the interface registration manager to obtain the interface registration information, convert the request object information into the target request parameter, and perform interface calls according to the interface type adaptation method, and finally encapsulate the return information and send it to the client.
It reduces the development volume of remote interface call functions, realizes unified management of interface calls, enhances the security and standardization of development, and improves software development efficiency.
Smart Images
Figure CN119645681A_ABST
Abstract
Description
Background Art
[0002] With the widespread adoption of microservice architecture and the refinement of system function granularity, almost every system needs to call a certain number of external interfaces. Currently, there are few technologies based on interface RPC (i.e., interface remote call implementation technology, hereinafter referred to as RPC technology) on the market, such as Alibaba's Dubbo or Google's gRPC. However, these technologies are more focused on the interface call layer, that is, simply realizing the registration of interfaces and the discovery of interfaces. However, if more complex customized template configuration of interface request parameters or automatic error retry for interface calls are required, developers need to perform intrusive programming on the code to achieve it.
[0003] Since there is currently no better unified agent or driver engine to optimize such scenarios for external interface calls, each system now independently implements the interface call functions. There are even multiple sets of interface call implementations in one system, which leads to chaotic management of external related interfaces in the entire system and fails to take all scenarios into account when selecting technology each time, resulting in omissions and errors in the system after upgrades, which in turn affects the overall work progress.
[0004] Therefore, it is urgent to provide a technical solution to solve the above problems. Summary of the invention
[0005] In order to solve the above technical problems, the present invention provides an interface call management method, system, electronic device and storage medium.
[0006] In a first aspect, the present invention provides an interface call management method, the technical solution of the method is as follows:
[0007] Receiving a call request message sent by a client for calling a target interface of a server; the call request message includes: an interface identifier and request object information;
[0008] When the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, the request object information is converted into a target request parameter using the interface request parameter template corresponding to the interface identifier;
[0009] Determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and call the target interface by using the interface calling method adapted by the request interface type, in combination with the target request parameters and the request interface configuration information;
[0010] When the call return information of the target interface is successfully obtained, the call return information is encapsulated and sent to the client.
[0011] The beneficial effects of an interface call management method of the present invention are as follows:
[0012] The method of the present invention can reduce the development workload of remote interface calling functions, realize unified management of interface calling, enhance the security and standardization of development, and promote the improvement of software development efficiency.
[0013] Based on the above solution, an interface call management method of the present invention can also be improved as follows.
[0014] In an optional manner, the method further includes:
[0015] When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
[0016] In an optional manner, the request interface type is: http interface type or webservice interface type;
[0017] When the request interface type is an http interface type, the interface calling method is: initiating an interface call through the HttpUtil tool class; when the request interface type is a webservice interface type, the interface calling method is: initiating an interface call through the WebServiceUtil tool class.
[0018] In an optional manner, the request interface configuration information includes: an interface call address, an interface call user name and password, and encryption and decryption information.
[0019] In an optional manner, the method further includes:
[0020] When the call return information of the target interface is not successfully obtained, determining whether the current retry count of the target interface exceeds the maximum retry count;
[0021] If so, a call error prompt message is output; if not, after a preset time interval, the step of calling the target interface by using the interface call method adapted by the request interface type is re-executed in combination with the target request parameters and the request interface configuration information.
[0022] In an optional manner, the step of encapsulating the call return information and sending it to the client includes:
[0023] According to the return encapsulation template corresponding to the client, the call return information is encapsulated and sent to the client.
[0024] In a second aspect, the present invention provides an interface call management system, the technical solution of which is as follows:
[0025] Includes: receiving module, processing module, calling module and returning module;
[0026] The receiving module is used to receive the call request information sent by the client for calling the target interface of the server; the call request information includes: interface identification and request object information;
[0027] The processing module is used to: when the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, the request object information is converted into a target request parameter using the interface request parameter template corresponding to the interface identifier;
[0028] The calling module is used to: determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and use the interface calling method adapted by the request interface type, combined with the target request parameters and the request interface configuration information, to call the target interface;
[0029] The return module is used to: when successfully acquiring the call return information of the target interface, encapsulate the call return information and send it to the client.
[0030] The beneficial effects of an interface call management system of the present invention are as follows:
[0031] The system of the present invention can reduce the development workload of remote interface calling functions, realize unified management of interface calling, enhance the security and standardization of development, and also promote the improvement of software development efficiency.
[0032] Based on the above solution, the interface call management system of the present invention can also be improved as follows.
[0033] In an optional manner, the system further includes: a prompt module; the prompt module is used to:
[0034] When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
[0035] In a third aspect, a technical solution of an electronic device of the present invention is as follows:
[0036] The invention comprises a memory, a processor and a program stored in the memory and running on the processor. When the processor executes the program, the steps of the interface call management method of the present invention are realized.
[0037] In a fourth aspect, the present invention provides a computer-readable storage medium having the following technical solution:
[0038] Instructions are stored in the computer-readable storage medium. When the computer-readable storage medium reads the instructions, the computer-readable storage medium executes the steps of the interface call management method of the present invention.
[0039] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0041] Figure 1 A schematic diagram of a flow chart of an embodiment of an interface call management method of the present invention;
[0042] Figure 2 A schematic diagram of the structure of an embodiment of an interface call management system of the present invention;
[0043] Figure 3 The figure is a schematic structural diagram of an embodiment of an electronic device of the present invention. DETAILED DESCRIPTION
[0044] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0045] Figure 1 The flowchart of an embodiment of an interface call management method provided by the present invention is shown. The interface call management method can be executed by an interface engine. The interface engine is set in an independent terminal device by default, and can also be set according to actual needs. Figure 1 As shown, the following steps are included:
[0046] S1. Receive call request information sent by the client for calling the target interface of the server.
[0047] Among them, the client is the terminal that needs to call the interface, the server is the terminal of the called interface, and the target interface is the interface that the client needs to call the server. The call request information includes: interface identifier and request object information. Each interface has only one unique interface identifier, and the corresponding interface can be clearly identified through the interface identifier. The call request information includes: encapsulated request information provided for the information required to call the target interface. For example, taking the insurance order as an example, in order to call the order details of insurance order A in the target interface test01, the call request information includes: order number, order amount, policyholder information, beneficiary information, etc. of order A.
[0048] S2. When the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, the request object information is converted into target request parameters using the interface request parameter template corresponding to the interface identifier.
[0049] Among them, the interface registration manager in the interface engine pre-stores interface registration information corresponding to multiple preset interface identifiers. Each preset interface identifier corresponds to a different interface registration information. The interface registration management in this embodiment is different from other registration methods. For example, Dubbo registration is registered to the registration center through the application. This embodiment uses a database as a registration management platform. It only needs to maintain the corresponding interface data (interface registration information) in the database table to achieve unified registration of the interface. The method of this embodiment makes the code embedding zero and only needs to provide a simple add, delete, modify and query interface, realizing low-cost maintenance, and using the database table as the data registration center, which is convenient for subsequent statistics of interface registration information or report export and other operations.
[0050] Among them, the interface registration template in the interface engine pre-stores interface request parameter templates corresponding to multiple preset interface identifiers. The template intelligent driving engine of the interface engine is used to convert the request object information into the target request parameter in combination with the interface request parameter template corresponding to the interface identifier. For example, when the request object information includes information such as the order number and the order amount, and the data format of the request object information is javaBean structure data, at this time, if the interface request parameter template corresponding to the target interface only needs the order number to obtain the corresponding order details, and the target interface needs to pass in json format data when interacting, then the template intelligent driving engine is used to extract the order number in the request object information according to the above information and convert it into json format data. The final order number in json format is the target request parameter.
[0051] It should be noted that the template intelligent driving engine uses template dynamic filling technology to make the interface parameters more flexibly configurable, and by configuring request parameter templates and other information, it can support the generation of multiple message formats and obtain target request parameters, reducing the tedious workload of developers for generating request parameters for each interface separately.
[0052] S3. Determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and use the interface calling method adapted by the request interface type, combined with the target request parameters and the request interface configuration information, to call the target interface.
[0053] Among them, the interface registration information includes the request interface type and the request interface configuration information. The request interface type includes but is not limited to: http interface type and webservice interface type. When the request interface type is http interface type, the interface call method is: initiate the interface call through the HttpUtil tool class; when the request interface type is webservice interface type, the interface call method is: initiate the interface call through the WebServiceUtil tool class. The request interface configuration information includes but is not limited to: interface call address url, interface call username and password, and encryption and decryption information.
[0054] It should be noted that the interface polymorphic adapter in the interface engine initiates calls based on the request protocol corresponding to the request interface type. For example, the http interface type initiates interface calls through the HttpUtil tool class and uses the TCP protocol for network communication; the webservice interface type initiates interface calls through the WebServiceUtil tool class and uses the Servlet container to implement the calls.
[0055] S4. When the call return information of the target interface is successfully obtained, the call return information is encapsulated and sent to the client.
[0056] Specifically, the step of encapsulating the call return information and sending it to the client includes:
[0057] According to the return encapsulation template corresponding to the client, the call return information is encapsulated and sent to the client.
[0058] Among them, different return encapsulation templates are used for data encapsulation according to different client interfaces. According to the structure definition of the return encapsulation template, the return of each interface call is uniformly encapsulated, and the result object after return is a global unified object structure, which reduces the developer's characteristic return judgment for each interface.
[0059] It should be noted that after the traditional RPC technology obtains the return value through the interface call, it does not process the return value in any way. By default, the obtained return value is directly returned to the caller (client). The caller needs to process the return of each interface to obtain the corresponding success or failure return result. Based on this scenario, the interface engine in this embodiment introduces driver parsing. It only needs to configure the message format returned by the server under success or failure. The driver parsing will match according to the configured return encapsulation template, and then uniformly encapsulate the return information into a standard object. In this way, the caller no longer needs to parse the return message for a single interface, making the code more concise and reducing the workload of developers. It will also make the interface return of the entire system more unified, and can more conveniently and uniformly manage external related interface call scenarios.
[0060] In an optional manner, the method further includes:
[0061] When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
[0062] When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, it is indicated that the interface identifier is not registered, and a call error prompt message is output to the client.
[0063] In an optional manner, the method further includes:
[0064] When the call return information of the target interface is not successfully obtained, it is determined whether the current retry times of the target interface exceeds the maximum retry times.
[0065] The maximum number of retries can be set according to the actual situation and there is no limit here. The current number of retries is the number of times the target interface has been retried (excluding the current interface call).
[0066] If so, a call error prompt message is output; if not, after a preset time interval, the step of calling the target interface by using the interface call method adapted by the request interface type is re-executed in combination with the target request parameters and the request interface configuration information.
[0067] It should be noted that the intelligent exception retryer in the interface engine is not necessarily triggered, and it will only be triggered when a definition error occurs in this interface call request. The working principle of the intelligent exception retryer is: when a definition error occurs, it is determined whether the current number of retries exceeds the maximum number of retries after this interface call request. If it does not exceed, a retry is automatically initiated. If it exceeds, an error message prompt is directly returned. Different from traditional RPC technology, traditional RPC only initiates interface calls by default, but does not pay attention to whether the interface is normal or whether a retry is required. However, using the intelligent exception retryer in this embodiment, a customizable non-business exception can be generated. When an exception occurs, the intelligent exception retryer will automatically intervene in the work and determine whether this retry has exceeded the maximum number of retries limited, and give corresponding processing according to the judgment result. If it has exceeded, the result of the last retry is directly returned, otherwise a retry is automatically initiated to re-call the interface to obtain the return result.
[0068] The interface engine of this embodiment not only comprehensively optimizes the development complexity of RPC, but also adds template configuration functions and retry mechanisms based on the original RPC basic functions, and greatly reduces the burden of developers in programming in RPC scenarios, allowing them to focus more on the implementation of business logic. While improving the optimization of RPC functions, the interface engine of this embodiment also promotes further improvement of software development efficiency.
[0069] The technical solution of this embodiment can reduce the development workload of remote interface call functions, realize unified management of interface calls, enhance the security and standardization of development, and promote the improvement of software development efficiency.
[0070] Figure 2 FIG. 2 is a schematic diagram showing a structure of an embodiment of an interface call management system 200 provided by the present invention. Figure 2 As shown, the system 200 includes: a receiving module 210, a processing module 220, a calling module 230 and a returning module 240;
[0071] The receiving module 210 is used to: receive the call request information sent by the client for calling the target interface of the server; the call request information includes: interface identification and request object information;
[0072] The processing module 220 is used to: when the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, use the interface request parameter template corresponding to the interface identifier to convert the request object information into the target request parameter;
[0073] The calling module 230 is used to: determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and use the interface calling method adapted by the request interface type, combined with the target request parameters and the request interface configuration information, to call the target interface;
[0074] The return module 240 is used to: when successfully acquiring the call return information of the target interface, encapsulate the call return information and send it to the client.
[0075] In an optional manner, the system further includes: a prompt module; the prompt module is used to:
[0076] When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
[0077] In an optional manner, the request interface type is: http interface type or webservice interface type;
[0078] When the request interface type is an http interface type, the interface calling method is: initiating an interface call through the HttpUtil tool class; when the request interface type is a webservice interface type, the interface calling method is: initiating an interface call through the WebServiceUtil tool class.
[0079] In an optional manner, the request interface configuration information includes: an interface call address, an interface call user name and password, and encryption and decryption information.
[0080] In an optional manner, the method further includes: an abnormal retry module; the abnormal retry module is used to:
[0081] When the call return information of the target interface is not successfully obtained, determining whether the current retry count of the target interface exceeds the maximum retry count;
[0082] If so, a call error prompt message is output; if not, after a preset time interval, the step of calling the target interface by using the interface call method adapted by the request interface type is re-executed in combination with the target request parameters and the request interface configuration information.
[0083] In an optional manner, the returning module 240 is specifically configured to:
[0084] According to the return encapsulation template corresponding to the client, the call return information is encapsulated and sent to the client.
[0085] It should be noted that the beneficial effects of the interface call management system provided in the above embodiment are the same as the beneficial effects of the interface call management method, which will not be described in detail here. In addition, when the system provided in the above embodiment realizes its functions, it only uses the division of the above functional modules as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the system can be divided into different functional modules according to actual conditions to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be described in detail here.
[0086] Among them, the interface call management system of the present invention can be a computer program (including program code) running in a computer device. For example, the interface call management system of the present invention is an application software that can be used to execute the corresponding steps in the interface call management method of the present invention.
[0087] In some embodiments, the interface call management system of the present invention can be implemented in a combination of software and hardware. As an example, the interface call management system of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the interface call management method of the present invention. For example, the processor in the form of a hardware decoding processor can adopt one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs) or other electronic components.
[0088] The modules involved in the embodiments of the present invention may be implemented in software or hardware. The name of a module does not limit the module itself in some cases.
[0089] An electronic device according to an embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, any one of the above-mentioned interface call management methods is implemented. That is to say, an electronic device according to an embodiment of the present invention may include but is not limited to: a processor and a memory; the memory is used to store the computer program; the processor is used to execute the interface call management method shown in any embodiment of the present invention by calling the computer program.
[0090] In an alternative embodiment, an electronic device is provided, such as Figure 3 As shown, Figure 3 The electronic device 4000 shown includes: a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, such as through a bus 4002. Optionally, the electronic device 4000 may also include a transceiver 4004, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 4004 is not limited to one, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present invention.
[0091] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of the present invention. Processor 4001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0092] The bus 4002 may include a path to transmit information between the above components. The bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 4002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 In the figure, only one thick line is used to represent the bus 4002, but this does not mean that there is only one bus or one type of bus.
[0093] The memory 4003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.
[0094] The memory 4003 is used to store the application code (computer program) for executing the solution of the present invention, and the execution is controlled by the processor 4001. The processor 4001 is used to execute the application code stored in the memory 4003 to implement the content shown in the above method embodiment.
[0095] Among them, the electronic device can also be a terminal device, and the terminal device can be any terminal device that can install applications and access web pages through applications, including at least one of a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, a smart TV, and a smart car device.
[0096] It should be noted that Figure 3 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0097] A computer-readable storage medium according to an embodiment of the present invention stores a computer program, and when the computer program is executed by a processor, any of the above-mentioned interface call management methods is implemented.
[0098] Optionally, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
[0099] In an exemplary embodiment, a computer program product or a computer program is also provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the above-mentioned interface call management method.
[0100] Computer program code for performing the operations of the present invention may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0101] It should be understood that the flow charts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the module, the program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0102] The computer-readable storage medium provided by the embodiment of the present invention may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or component.
[0103] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the method shown in the above embodiment.
[0104] The above description is only a preferred embodiment of the present invention and an explanation of the technical principles used. Those skilled in the art should understand that the disclosure scope involved in the present invention is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present invention (but not limited to) by each other.
[0105] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects and represent the definition of a specific order or sequence. The order of use of similar objects can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than the order shown or described.
[0106] Those skilled in the art know that the present invention can be implemented as a system, method or computer program product. Therefore, the present invention can be specifically implemented in the following forms, namely: it can be complete hardware, it can be complete software (including firmware, resident software, microcode, etc.), or it can be a combination of hardware and software, which is generally referred to as "circuit", "module" or "system" herein. In addition, in some embodiments, the present invention can also be implemented in the form of a computer program product in one or more computer-readable media, and the computer-readable medium contains computer-readable program code.
[0107] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.
Claims
1. An interface call management method, characterized in that: include: Receive the call request information sent by the client for calling the target interface of the server; The call request information includes: interface identification and request object information; When the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, the request object information is converted into a target request parameter using the interface request parameter template corresponding to the interface identifier; Determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and call the target interface by using the interface calling method adapted by the request interface type, in combination with the target request parameters and the request interface configuration information; When the call return information of the target interface is successfully obtained, the call return information is encapsulated and sent to the client.
2. The interface call management method according to claim 1, characterized in that: Also includes: When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
3. The interface call management method according to claim 1, characterized in that: The request interface type is: http interface type or webservice interface type; When the request interface type is an http interface type, the interface calling method is: initiating an interface call through the HttpUtil tool class; when the request interface type is a webservice interface type, the interface calling method is: initiating an interface call through the WebServiceUtil tool class.
4. The interface call management method according to claim 1, characterized in that: The request interface configuration information includes: interface call address, interface call user name and password, and encryption and decryption information.
5. The interface call management method according to claim 1, characterized in that: Also includes: When the call return information of the target interface is not successfully obtained, determining whether the current retry count of the target interface exceeds the maximum retry count; If so, a call error prompt message is output; if not, after a preset time interval, the step of calling the target interface by using the interface call method adapted by the request interface type is re-executed in combination with the target request parameters and the request interface configuration information.
6. The interface call management method according to any one of claims 1 to 5, characterized in that: The step of encapsulating the call return information and sending it to the client comprises: According to the return encapsulation template corresponding to the client, the call return information is encapsulated and sent to the client.
7. An interface call management system, characterized in that: include: Receiving module, processing module, calling module and returning module; The receiving module is used to: receive the call request information sent by the client for calling the target interface of the server; The call request information includes: interface identification and request object information; The processing module is used to: when the interface registration information corresponding to the interface identifier is obtained from the interface registration manager, the request object information is converted into a target request parameter using the interface request parameter template corresponding to the interface identifier; The calling module is used to: determine the request interface type and request interface configuration information corresponding to the interface identifier from the interface registration information, and use the interface calling method adapted by the request interface type, combined with the target request parameters and the request interface configuration information, to call the target interface; The return module is used to: when successfully acquiring the call return information of the target interface, encapsulate the call return information and send it to the client.
8. The interface call management system according to claim 7, characterized in that: Also includes: Prompt module; the prompt module is used to: When the interface registration information corresponding to the interface identifier is not obtained from the interface registration manager, a call error prompt message is output.
9. An electronic device, characterized in that: The electronic device includes a processor, the processor is coupled to a memory, the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor so that the electronic device implements the interface call management method as described in any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one computer program, and the at least one computer program is loaded and executed by the processor, so that the computer-readable storage medium implements the interface call management method according to any one of claims 1 to 6.