CN114553932A - System integration docking method, device, equipment and medium - Google Patents
System integration docking method, device, equipment and medium Download PDFInfo
- Publication number
- CN114553932A CN114553932A CN202210433520.6A CN202210433520A CN114553932A CN 114553932 A CN114553932 A CN 114553932A CN 202210433520 A CN202210433520 A CN 202210433520A CN 114553932 A CN114553932 A CN 114553932A
- Authority
- CN
- China
- Prior art keywords
- service
- message
- request
- message queue
- function
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a system integration docking method, a device, equipment and a medium. The method comprises the steps of acquiring a functional interface to be operated in a service system A, and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service; assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP), and sending the function request to a service system B; obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue; and pushing the service corresponding to the MQ asynchronous message through the service system A. By using the message queue as an intermediate medium, the times of interactive request failure among systems are reduced, the probability of service flow execution interruption is reduced, the problem of asynchronous notification failure is solved, and the invoicing of functional service is improved.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a system integration docking method, a device, equipment and a medium.
Background
In the field of computer software, various different application software carries out transaction delivery on an application market platform, after the transaction delivery is completed, the various different application software can realize functional services on various terminals, before the transaction delivery of the application software is completed, the application market and a software service provider need to be butted, and the application software can be put on shelf for transaction delivery after the butting. Therefore, in the process of realizing transaction delivery of various application software on an application market platform, many scenarios of docking and integration of systems occur.
The interaction mode for realizing the docking integration among the internal systems may be HTTP request, PRC call, message queue, and the like, while the docking integration among the multiple systems is realized in the interaction mode with HTTP request as the most important interaction mode among the multiple systems, and in the process of realizing the docking integration among the multiple systems with HTTP request, when various problems such as down service of a target party or network non-smoothness occur in the process of performing the functional service by one of the systems, the problems of request failure among the systems, interruption of service flow execution, asynchronous notification failure, and the like may be caused, and finally, the problem of low functional service invoicing between the software service platform and the application market platform may be caused.
Disclosure of Invention
The invention mainly aims to provide a system integration docking method, a device, equipment and a medium, aiming at solving the problem of low functional service calling performance when an application market platform is docked with a software service platform.
In order to achieve the above object, the present invention provides a system integration docking method, which includes the following steps:
acquiring a functional interface to be operated in a service system A, and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP), and sending the function request to a service system B;
obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue;
and pushing the service corresponding to the MQ asynchronous message through the service system A.
Preferably, before the step of acquiring a functional interface to be operated in the service system a and sending a message queue MQ functional message corresponding to the functional interface to the message queue of the system integration docking service, the system integration docking method further includes:
storing MQ messages from different systems by operating a message middleware RabbitMq message queue in the system integration docking service;
running a Mysql database in the system integration docking service, and recording a storage log of the MQ message in the RabbitMq message queue;
and running the system integration docking service based on the RabbitMq message queue and the Mysql database.
Preferably, the step of acquiring a functional interface to be operated in the service system a and sending a message queue MQ functional message corresponding to the functional interface to the message queue of the system integration docking service includes:
calling a functional interface to be operated in the service system A;
acquiring parameter data in the functional interface, and assembling corresponding MQ functional messages according to the parameter data;
and sending the MQ function message to a message queue of the system integration docking service.
Preferably, after the step of acquiring the functional interface to be operated in the service system a and sending the message queue MQ functional message corresponding to the functional interface to the message queue of the system integration docking service, the system integration docking method further includes:
recording a request log of the MQ functional message corresponding to the functional interface in the message queue, and judging the abnormal condition of the request log;
if the request log indicates that the MQ function message is failed to be called, the MQ function message is placed into a message queue again, and the failure times of the MQ function message in calling failure are recorded;
and when the failure times of the MQ function message calling failure exceed a preset threshold value, sending a request log corresponding to the MQ function message to an initiating terminal.
Preferably, the step of obtaining, by the service system B, a request result corresponding to the function request and returning an MQ asynchronous message corresponding to the request result to the message queue includes:
responding the function request based on a preset response algorithm through the service system B to obtain a request result corresponding to the function request;
based on the request results, a corresponding MQ asynchronous message is determined and returned to the message queue.
Preferably, the step of pushing the service corresponding to the MQ asynchronous message through the service system a includes:
returning a request result corresponding to the MQ asynchronous message to the service system A;
determining the service logic corresponding to the functional interface and the request result through the service system A;
the corresponding resulting business service is determined by processing the business logic in the business system a.
Preferably, after the step of pushing the result service corresponding to the MQ asynchronous message through the service system a, the system integration interfacing method further includes:
obtaining a service result corresponding to the result service through the service system A;
and the service result notification is sent to the user by adopting WebSocket through the service system A.
In addition, to achieve the above object, the present invention also provides a system integrated docking apparatus, including:
the system comprises an acquisition module, a message queue and a service module, wherein the acquisition module is used for acquiring a functional interface to be operated in a service system A and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
the sending module is used for assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP) and sending the function request to a service system B;
a returning module, configured to obtain a request result corresponding to the function request through the service system B, and return an MQ asynchronous message corresponding to the request result to the message queue;
and the pushing module is used for pushing the service corresponding to the MQ asynchronous message through the service system A.
Preferably, the obtaining module is further configured to:
calling a functional interface to be operated in the service system A;
acquiring parameter data in the functional interface, and assembling corresponding MQ functional messages according to the parameter data;
and sending the MQ function message to a message queue of the system integration docking service.
Preferably, the return module is further configured to:
responding the function request based on a preset response algorithm through the service system B to obtain a request result corresponding to the function request;
based on the request results, a corresponding MQ asynchronous message is determined and returned to the message queue.
Preferably, the pushing module is further configured to:
returning a request result corresponding to the MQ asynchronous message to the service system A;
determining the service logic corresponding to the functional interface and the request result through the service system A;
and determining the corresponding business service by processing the business logic in the business system A.
In addition, to achieve the above object, the present invention also provides a system-integrated docking apparatus, including: a memory, a processor and a system integrated docking program stored on the memory and executable on the processor, the system integrated docking control program when executed by the processor implementing the steps of the system integrated docking method as described above.
In addition, to achieve the above object, the present invention also provides a medium which is a computer readable storage medium having a system integration docking program stored thereon, and the system integration docking program, when executed by a processor, implements the steps of the system integration docking method as described above.
The system integration docking method, the device, the equipment and the medium provided by the invention have the advantages that the functional interface to be operated in the service system A is obtained, and the message queue MQ functional message corresponding to the functional interface is sent to the message queue of the system integration docking service; assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP), and sending the function request to a service system B; obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue; and pushing the service corresponding to the MQ asynchronous message through the service system A. The invention stores the MQ function message corresponding to the function interface acquired from the service system A into the message queue of the system integrated docking service, determines the function request through the MQ function message, processes the function request in the service system B to obtain the corresponding request result, sends the MQ asynchronous message corresponding to the request result to the message queue, sends the MQ asynchronous message to the service system A through the message queue in the system integrated docking service, completes the function service call between the service system A and the service system B, directly connects the requirement of the service system A with the service of the service system B by using the message queue as the intermediate medium, reduces the times of interactive request failure between the systems, reduces the probability of service flow execution interruption, solves the problem of asynchronous notification failure, and solves the problem that when the application market platform is docked with the software service platform, and the functional service has low calling performance.
Drawings
FIG. 1 is a schematic diagram of an apparatus structure of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a system integration docking method according to the present invention;
FIG. 3 is a schematic diagram of a system integration timing sequence according to a first embodiment of the system integration docking method of the present invention, taking the billing requirement of the user as an example;
fig. 4 is a schematic flowchart of step S101 in a second embodiment of the system integration docking method according to the present invention;
FIG. 5 is a flowchart illustrating a system integration docking method according to a second embodiment of the present invention;
fig. 6 is a flowchart illustrating a step S102 in a third embodiment of the system integration docking method according to the present invention;
FIG. 7 is a flowchart illustrating a system integration docking method according to a third embodiment of the present invention;
fig. 8 is a flowchart illustrating a step S400 of a fourth embodiment of the system integration docking method according to the present invention;
FIG. 9 is a flowchart illustrating a system integration docking method according to a fourth embodiment of the present invention;
fig. 10 is a functional block diagram of a system integrated docking apparatus according to a first embodiment of the system integrated docking method of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, fig. 1 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present invention.
The device of the embodiment of the invention can be a terminal or a server.
As shown in fig. 1, the apparatus may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. The communication bus 1002 is used to implement connection communication among these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration of the apparatus shown in fig. 1 is not intended to be limiting of the apparatus and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a system integration interfacing program.
The operating system is a program for managing and controlling system integrated docking equipment and software resources, and supports the running of a network communication module, a user interface module, a system integrated docking program and other programs or software; the network communication module is used for managing and controlling the network interface 1002; the user interface module is used to manage and control the user interface 1003.
In the system-integrated docking apparatus shown in fig. 1, the system-integrated docking apparatus calls a system-integrated docking program stored in a memory 1005 through a processor 1001 and performs operations in various embodiments of the system-integrated docking method described below.
Based on the hardware structure, the embodiment of the system integration docking method is provided.
Referring to fig. 2, fig. 2 is a schematic flow chart of a first embodiment of the system integration docking method of the present invention, and the method includes:
step S10, acquiring a functional interface to be operated in a service system A, and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
step S20, based on the HTTP, assembling the function request corresponding to the MQ function message in the message queue, and sending the function request to the service system B;
step S30, obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue;
step S40, pushing the service corresponding to the MQ asynchronous message through the service system a.
The communication method for system integrated docking of the embodiment stores the functional MQ message corresponding to the functional interface acquired in the service system A into the message queue of the system integrated docking service, determines the functional request through the functional MQ message, processes the functional request in the service system B to obtain the corresponding request result, sends the MQ asynchronous message corresponding to the request result to the message queue, sends the MQ asynchronous message to the service system A through the message queue in the system integrated docking service, completes the function service call between the service system A and the service system B, directly connects the requirement of the service system A with the service of the service system B by using the message queue as an intermediate medium, reduces the number of interactive request failures among the systems, reduces the probability of service flow execution interruption, and solves the problem of asynchronous notification failure, the problem of low functional service calling performance when an application market platform is in butt joint with a software service platform is solved.
The respective steps will be described in detail below:
step S10, acquiring a functional interface to be operated in a service system A, and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
the step of acquiring the functional interface to be operated in the service system A and sending the message queue MQ functional message corresponding to the functional interface to the message queue of the system integration docking service comprises the following steps:
calling a functional interface to be operated in the service system A;
acquiring parameter data in the functional interface, and assembling corresponding MQ functional messages according to the parameter data;
and sending the MQ function message to a message queue of the system integration docking service.
In a specific embodiment, the services capable of running different functions are developed in a development system to obtain software applications with different functions, the software applications are stored in a service system A, a functional interface is established with different software applications in the service system A according to some specific function requirements acquired from a user side, the functional interface can realize communication and interaction of interfaces of two parties developed by any programming language, an API request between the two parties is directly initiated through a simple calling mode irrelevant to the development language, an interface for connecting and communicating between the two parties is realized through the API request, and a method in the service system is called in the service system through the interface to realize certain functional services.
The API interface is an interface for transferring data back and forth between software in a formalized manner, and is a set of definitions, programs, and protocols, and realizes communication between computer software through the API interface. The API is also a middleware for providing data sharing for various different platforms, and the interface between the development system and the service system realizes the data sharing between the development system and the service system, enables the functional services with different functions in the development system to be connected with the data containing various functional service requirements in the service system, and enables the functional service requirements to be in communication connection with the functional services.
In this embodiment, when the application market service receives a billing request of a user, a billing interface is called from the service system a according to the billing requirement of the user, and the system integration service in this scheme assembles a corresponding billing request according to parameter data in the billing interface by acquiring some parameter data uploaded by the user inside a service corresponding to the functional interface, where the parameter data may include information of the billing request of the user, data of a drawer, and the like, and the assembling process based on the parameter data may also be parameter data filling, acquiring a corresponding billing request, and in the application market MQ service, converting the billing request into a corresponding billing message, and sending the billing message to a message queue to wait for processing.
It should be further noted that the MQ message is a "first-in first-out" data structure in the basic data structure. The method is generally used for solving the problems of application decoupling, asynchronous messages, flow peak clipping and the like, and realizes a high-performance, high-availability, scalable and final consistency framework. MQ queue messaging refers to storing data or messages to be transmitted in a queue, and using a queue mechanism to realize message transmission, wherein a producer generates messages and puts the messages in the queue, and then a consumer processes the messages, so that a user can pull the messages to the specified queue or subscribe to the corresponding queue, and an MQ server pushes the messages to the specified queue.
Step S20, based on the HTTP, assembling the function request corresponding to the MQ function message in the message queue, and sending the function request to the service system B;
in a specific embodiment, in the system integration service, the function interfaces corresponding to the user requirements are assembled by using a hypertext transfer protocol HTTP, the corresponding function requests are obtained, the obtained function requests are sent to the corresponding service system B for processing, for example, after obtaining the invoicing MQ messages corresponding to the invoicing interfaces, the invoicing MQ messages are assembled based on the hypertext transfer protocol HTTP, the corresponding invoicing requests are obtained, and the invoicing requests are sent to a third party invoice platform for processing.
To explain in detail, the hypertext Transfer Protocol (HTTP) is a simple request-response Protocol, which usually runs on top of TCP, that specifies what messages a client may send to a server and what responses it gets, the beginning of the request and response messages being given in ASCII form; and the message content has a MIME-like format.
HTTP is an application layer protocol, which is a protocol for implementing a specific application like other application layer protocols, and an application program running in a user space implements the function thereof. The HTTP is based on B/S architecture for communication, the server side implementation program of the HTTP is httpd, nginx and the like, the implementation program of the client side is mainly a Web browser, such as Firefox, Internet Explorer, Google Chrome, Safari, Opera and the like, in addition, the command line tool of the client side is also elink, curl and the like, the Web service is based on TCP, therefore, in order to respond the request of the client side at any time, the Web server needs to monitor an 80/TCP port, and the communication between the client side browser and the Web server can be carried out through the HTTP.
Step S30, obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue;
the step of obtaining the request result corresponding to the function request through the service system B and returning the MQ asynchronous message corresponding to the request result to the message queue comprises the following steps:
responding the function request based on a preset response algorithm through the service system B to obtain a request result corresponding to the function request;
based on the request results, corresponding MQ asynchronous messages are determined and returned to the message queue.
In a specific embodiment, the service system B responds to the assembled HTTP function request, and processes the client requirement included in the HTTP function request after the response to obtain a request result corresponding to the HTTP function request, for example, after sending the assembled HTTP invoicing request to a third party invoicing platform, performs invoicing on the user invoicing request included in the HTTP invoicing request to obtain a corresponding invoicing result. And converting the billing result into an MQ asynchronous message through the system integration service, and returning the MQ asynchronous message corresponding to the billing result to a message queue in the system integration service.
It should be specifically explained that the above-mentioned MQ asynchronous message in the message queue returned to the system integration service is identical in form to the invoiced MQ message sent from the development system a to the message queue in the system integration service, and the only difference is that the invoiced MQ message is used as the message queue to receive information from the development system a, and the MQ asynchronous message is used as the message queue to transmit information to the development system a; the billing MQ messages serve as message queues for sending messages to the service system B, and the MQ asynchronous messages serve as receiving messages from the service system B.
Step S40, pushing the result service corresponding to the MQ asynchronous message through the service system a.
The step of pushing the resulting service corresponding to the MQ asynchronous message through the service system a includes:
returning a request result corresponding to the MQ asynchronous message to the service system A;
determining the service logic corresponding to the functional interface and the request result through the service system A;
the corresponding resulting business service is determined by processing the business logic in the business system a.
In a specific embodiment, the message queue of the system integration service returns the MQ asynchronous message corresponding to the request result to the service system a for returning the request result, acquires a service logic corresponding to a certain function requirement and the request result on the basis of the request result, processes the service logic, determines a corresponding result service, and pushes the result service through the service system a.
Referring to fig. 3, fig. 3 is a system integration timing chart of the system integration docking method according to the present embodiment, taking the billing requirement of the user as an example. Specifically, a user inputs a self invoicing requirement on an interactive interface of an application market, an application market service assembles a corresponding invoicing request through the invoicing requirement, acquires an invoicing MQ message corresponding to the invoicing request and sends the invoicing MQ message to a message queue for waiting execution, when the invoicing MQ message is executed by the message queue, a queue message carries out HTTP-based assembly on an execution instruction containing the invoicing MQ message, sends the invoicing HTTP request to a third party invoice platform, performs invoicing operation on the third party invoice platform by using a pre-developed invoicing function to obtain a corresponding invoicing result, informs the invoicing result to the application market by sending a corresponding MQ asynchronous message to the message queue, and pushes a corresponding result service to the application market.
The system integration docking method of the embodiment stores MQ function messages corresponding to a function interface acquired from a service system A into a message queue of system integration docking service, determines a function request through the MQ function messages, processes the function request in a service system B to obtain a corresponding request result, sends MQ asynchronous messages corresponding to the request result to the message queue, sends the MQ asynchronous messages to the service system A through the message queue in the system integration docking service, completes function service calling between the service system A and the service system B, directly connects the requirements of the service system A with the service of the service system B by using the message queue as an intermediate medium, reduces the number of times of interactive request failure between systems, reduces the probability of service flow execution interruption, and solves the problem of asynchronous notification failure, the problem of low functional service calling performance when an application market platform is in butt joint with a software service platform is solved.
Further, based on the first embodiment of the system integration docking method of the present invention, a second embodiment of the system integration docking method of the present invention is provided.
The second embodiment of the system integration docking method is different from the first embodiment of the system integration docking method in that, before step S10, the system integration docking method further includes a scheme for running a RabbitMq message queue and a Mysql database, and before step S10, the method further includes:
and step S101, operating a RabbitMq message queue and a Mysql database.
Referring to fig. 4, fig. 4 is a specific step of step S101 of the system integration docking method according to this scheme, where in step S101, before the system integration docking service is used, a RabbitMq message queue and a Mysql database need to be operated as a scheme foundation, where the RabbitMq message queue is used to store MQ messages generated in real time, and the Mysql database is used to record storage logs of the MQ messages.
Referring to fig. 5, step S101 specifically includes:
step S1011, storing MQ messages from different systems in the system integration docking service by operating a message middleware RabbitMq message queue;
in a particular embodiment, the message queue is implemented by a RabbitMq and is used to store MQ messages from different systems. The message queue is a container that holds messages during their transmission, which are units of data transmitted between two calculators, and can be very simple data, such as data containing text strings, but also complex data containing embedded objects, and the message queue manager acts as a middleman in relaying a message from its source to its destination. The main purpose of the queues is to provide routing and guarantee delivery of messages; if the recipient is not available when the message is sent, the message queue will hold the messages until they can be successfully delivered.
The message queue realized by the RabbitMq realizes high-level open source message agent software, is also message-oriented middleware, has scalable cluster service and message persistence, and persists the message from the memory to the hard disk and then loads the message from the hard disk to the memory. The middleware which is realized by the RabbitMq and transmits the messages most is an important component in a distributed system, can solve the problems of application decoupling, asynchronous messages, traffic cutting and the like, and can realize a high-performance, high-availability, scalable and final consistency framework.
The MQ message generated by the message queue realized by the RabbitMq sequentially processes transmission data in a first-in first-out data structure mode, the MQ message is realized by a plurality of modules in one service, or one message has a plurality of systems needing corresponding processing, only one MQ is sent after the main service is finished, and the other modules consume the MQ message, so that the service can be realized, and the coupling between the modules is reduced; after the execution of the main service is finished, the subordinate service is asynchronously executed through the MQ, so that the response time of the service is shortened, and the user experience is improved; under the condition of high concurrency, the service is processed asynchronously, the service processing capacity in the peak period is provided, and the system paralysis is avoided.
Step S1012, running a Mysql database in the system integration docking service, and recording a storage log of the MQ message in the RabbitMq message queue;
in a specific embodiment, the storage log of the MQ message queue is recorded based on the Mysql database, detailed records are made on each piece of MQ function information transmitted from the development system or MQ result information returned by the service system, and tight communication connection is realized among systems to be subjected to docking integration.
It should be specifically explained that the Mysql database is a relational database management system, and various storage data are stored in different tables, so that the storage data have high flexibility. And the storage log for storing the MQ message alignment is recorded and stored in detail, so that the capability of monitoring some abnormal data in real time can be improved.
Step S1013, the system integration docking service is operated based on the RabbitMq message queue and the Mysql database.
The system integration docking method of the embodiment realizes the system integration docking service through the RabbitMq message queue and the Mysql database, the RabbitMq message queue is used as a message intermediate station for realizing communication between systems, docking between the systems is indirectly realized, a user system does not need to pay attention to the problems of abnormal logic processing, event compensation, log backtracking and the like which are only paid attention to by a developer system, the problems can be uniformly and perfectly processed by the system integration service between the systems, the times of interactive request failure between the systems are reduced, the probability of service flow execution interruption is reduced, the efficiency of realizing the requirements and function docking between different systems is improved, and meanwhile, the real-time monitoring of abnormal calling in the function calling process between the systems is realized based on the Mysql database.
Further, based on the first and second embodiments of the system integration docking method of the present invention, a third embodiment of the system integration docking method of the present invention is provided.
The third embodiment of the system integrated docking method is different from the first and second embodiments of the system integrated docking method in that, after step S10, the system integrated docking method further includes a scheme of recording an abnormal situation of the request log, and after step S10, the method further includes:
step S102, recording the abnormal condition of the request log.
Referring to fig. 6, fig. 6 is a specific step of step S102 of the system integration docking method according to this scheme, where in step S102, after the system integration docking service sends the MQ message corresponding to the functional interface to the message queue, it is further required to record an abnormal condition of the request log sent by the MQ message to the message queue.
Referring to fig. 7, step S102 specifically includes:
step S1021, recording a request log of the MQ function message corresponding to the function interface in the message queue, and judging the abnormal condition of the request log;
step S1022, if the request log is that the MQ function message fails to be called, the MQ function message is placed into a message queue again, and the failure times of the MQ function message failing to be called are recorded;
and step S1023, when the failure times of the MQ function message calling failure exceed a preset threshold value, sending a request log corresponding to the MQ function message to an initiating terminal.
In a specific embodiment, after a system integration service receives a corresponding functional MQ message through a RabbitMq message queue, storing a request log of the functional MQ message in the RabbitMq message queue in a database, assembling a corresponding functional request through HTTP and forwarding the functional request to a target service, when the system integration service receives the message and prepares to forward the request to the target service, and the target service fails to send the request abnormally due to downtime or network failure, if the request is sent and called unsuccessfully, placing the invoicing message into the message queue again for later retry sending, performing three retry forwarding retries through a message retry mechanism of the message queue, if the request is still sent unsuccessfully after three retry retries, recording a failure log and notifying a developer, and if the request is still failed after retries, recording a request exception log into the database, and sends a notification such as a mail to the subscribed administrator for follow-up processing. The abnormal compensation is divided into manual compensation and automatic compensation, and the system integration service can create a request that a periodic scanning call of a timing task fails and then re-trigger a call logic to perform automatic compensation, or a development operator triggers retry in interface operation.
The system integration docking method in the embodiment records the function call exception in real time in the process of performing function call between multiple systems through an exception retry and compensation mechanism, reduces the frequency of interactive request failure between the systems, reduces the probability of service flow execution interruption, solves the problem of asynchronous notification failure, and improves the invocability of function service when the application market platform is docked with the software service platform.
Further, a fourth embodiment of the system integration docking method of the present invention is proposed based on the first, second, and third embodiments of the system integration docking method of the present invention.
The fourth embodiment of the system integration docking method is different from the first, second, and third embodiments of the system integration docking method in that after step S40, the system integration docking method further includes a scheme of sending a result of the business service to the user through the business system a, and after step S40, the method further includes:
step S400, the result of the service is sent to the user through the service system A.
Referring to fig. 8, fig. 8 is a specific step of step S400 of the system integration docking method according to this scheme, where in step S400, after the system integration docking service pushes the result service corresponding to the MQ asynchronous message, the service result of the result service needs to be sent to the user.
Referring to fig. 9, step S400 specifically includes:
step S401, obtaining a service result corresponding to the result service through the service system A;
and step S402, adopting Websocket through the service system A, and sending the service result notification to a user.
In a specific embodiment, after the service system a performs corresponding operations for the function requirements of the user, a corresponding function result is obtained, and the function result is returned to the interactive interface of the user through the WebSocket, so that the user knows that the function requirements of the user are completed, and for the function result, the user can also print and download the function result, which is convenient for the user to use better.
Specifically, the WebSocket is a protocol for performing full-duplex communication on a single TCP connection, and makes data exchange between the client and the server simpler, and allows the server to actively push data to the client. In the WebSocket API, the browser and the server only need to complete one handshake, and persistent connection can be directly established between the browser and the server, and bidirectional data transmission is carried out.
In the embodiment, the service result is sent to the interactive interface operated by the user at the service side through the service system A, and the interaction between the service result and the user is realized through the Websocket, so that the data transmission with durability and high compression rate is realized, and the interactive effect between the service system A and the user is optimized.
In some other embodiments, the system integration docking service in the system integration docking method of the present method may be used in all scenarios of docking with an external system, for example, a company has multiple system platforms, an e-commerce platform and a warehouse management system WMS, and when a customer purchases a commodity on the e-commerce platform to place an order, the e-commerce platform may process some services notifying the WMS system of shipment through the system integration docking service. The system integration docking method has corresponding application as long as the systems are subjected to integration docking.
The invention also provides a system integration butt joint device. Referring to fig. 10, the system-integrated docking apparatus of the present invention includes:
an obtaining module 10, configured to obtain a functional interface to be operated in a service system a, and send a message queue MQ functional message corresponding to the functional interface to a message queue of the system integrated docking service;
a sending module 20, configured to assemble a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol HTTP, and send the function request to the service system B;
a returning module 30, configured to obtain a request result corresponding to the function request through the service system B, and return an MQ asynchronous message corresponding to the request result to the message queue;
and the pushing module 40 is configured to push, through the service system a, the service corresponding to the MQ asynchronous message.
Furthermore, the present invention also provides a computer readable storage medium, preferably a computer readable storage medium, having stored thereon a system integrated docking program, which when executed by a processor, implements the steps of the system integrated docking method as described above.
In the embodiment of the system integrated docking device and medium of the present invention, all technical features of the embodiments of the system integrated docking method are included, and the description and explanation contents are basically the same as those of the embodiments of the system integrated docking method, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A system integration docking method is applied to a system integration docking service, and comprises the following steps:
acquiring a functional interface to be operated in a service system A, and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP), and sending the function request to a service system B;
obtaining a request result corresponding to the function request through the service system B, and returning an MQ asynchronous message corresponding to the request result to the message queue;
and pushing the service corresponding to the MQ asynchronous message through the service system A.
2. The system integrated docking method as claimed in claim 1, wherein before the step of acquiring the functional interface to be operated in the service system a and sending the message queue MQ functional message corresponding to the functional interface to the message queue of the system integrated docking service, the system integrated docking method further comprises:
storing MQ messages from different systems by operating a message middleware RabbitMq message queue in the system integration docking service;
running a Mysql database in the system integration docking service, and recording a storage log of the MQ message in the RabbitMq message queue;
and running the system integration docking service based on the RabbitMq message queue and the Mysql database.
3. The system integrated docking method as claimed in claim 1, wherein the step of acquiring the functional interface to be operated in the service system a and sending the message queue MQ functional message corresponding to the functional interface to the message queue of the system integrated docking service comprises:
calling a functional interface to be operated in the service system A;
acquiring parameter data in the functional interface, and assembling corresponding MQ functional messages according to the parameter data;
and sending the MQ function message to a message queue of the system integration docking service.
4. The system integrated docking method as claimed in claim 1, wherein after the step of acquiring the functional interface to be operated in the service system a and sending the message queue MQ functional message corresponding to the functional interface to the message queue of the system integrated docking service, the system integrated docking method further comprises:
recording a request log of the MQ functional message corresponding to the functional interface in the message queue, and judging the abnormal condition of the request log;
if the request log indicates that the MQ function message is failed to be called, the MQ function message is placed into a message queue again, and the failure times of the MQ function message in calling failure are recorded;
and when the failure times of the MQ function message calling failure exceed a preset threshold value, sending a request log corresponding to the MQ function message to an initiating terminal.
5. The system integrated docking method as claimed in claim 1, wherein the step of obtaining, by the service system B, a request result corresponding to the function request and returning MQ asynchronous messages corresponding to the request result to the message queue comprises:
responding the function request based on a preset response algorithm through the service system B to obtain a request result corresponding to the function request;
based on the request results, corresponding MQ asynchronous messages are determined and returned to the message queue.
6. The system integrated docking method as claimed in claim 1, wherein the step of pushing the service corresponding to the MQ asynchronous message through the service system a comprises:
returning a request result corresponding to the MQ asynchronous message to the service system A;
determining the service logic corresponding to the functional interface and the request result through the service system A;
and determining the corresponding service by processing the service logic in the service system A.
7. The system integrated docking method as claimed in claim 1, wherein after the step of pushing the service corresponding to the MQ asynchronous message through the service system a, the system integrated docking method further comprises:
acquiring a service result corresponding to the service through the service system A;
and sending the service result notification to a user by adopting WebSocket through the service system A.
8. A system integrated docking device, comprising:
the system comprises an acquisition module, a message queue and a service module, wherein the acquisition module is used for acquiring a functional interface to be operated in a service system A and sending a message queue MQ functional message corresponding to the functional interface to a message queue of the system integration docking service;
the sending module is used for assembling a function request corresponding to the MQ function message in the message queue based on a hypertext transfer protocol (HTTP) and sending the function request to a service system B;
a returning module, configured to obtain, by the service system B, a request result corresponding to the function request, and return an MQ asynchronous message corresponding to the request result to the message queue;
and the pushing module is used for pushing the service corresponding to the MQ asynchronous message through the service system A.
9. A system integrated docking device, comprising: a memory, a processor, and a system integrated docking program stored on the memory and executable on the processor, the system integrated docking program when executed by the processor implementing the steps of the system integrated docking method as recited in any of claims 1 to 7.
10. A medium which is a computer-readable storage medium having stored thereon a system integration docking program, which when executed by a processor, implements the steps of the system integration docking method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210433520.6A CN114553932A (en) | 2022-04-24 | 2022-04-24 | System integration docking method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210433520.6A CN114553932A (en) | 2022-04-24 | 2022-04-24 | System integration docking method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114553932A true CN114553932A (en) | 2022-05-27 |
Family
ID=81666995
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210433520.6A Pending CN114553932A (en) | 2022-04-24 | 2022-04-24 | System integration docking method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114553932A (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130111500A1 (en) * | 2011-10-28 | 2013-05-02 | International Business Machines Corporation | Message queuing application access to specific api services through a generic api interface intergrating a message queue |
| US20140149486A1 (en) * | 2012-11-29 | 2014-05-29 | Compuware Corporation | System And Methods For Tracing Individual Transactions Across A Mainframe Computing Environment |
| US20180324118A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | Messaging queue service api optimization system |
| CN111222862A (en) * | 2018-11-27 | 2020-06-02 | 北京京东金融科技控股有限公司 | Data processing method and system, medium and computer system |
| CN111666145A (en) * | 2020-06-24 | 2020-09-15 | 深圳壹账通智能科技有限公司 | Message processing method and system of message queue and computer equipment |
| CN112948174A (en) * | 2021-02-03 | 2021-06-11 | 江苏苏宁物流有限公司 | Message processing method and device, computer equipment and storage medium |
| WO2021179156A1 (en) * | 2020-03-10 | 2021-09-16 | 深圳市欢太科技有限公司 | Message processing method, device and system, and server |
| CN113938516A (en) * | 2021-10-13 | 2022-01-14 | 中国银行股份有限公司 | Method and system for synchronously realizing transaction processing of heterogeneous system |
| CN113986566A (en) * | 2021-09-30 | 2022-01-28 | 重庆斯欧智能科技研究院有限公司 | Message path selection method for industrial Internet |
| CN114040031A (en) * | 2021-09-30 | 2022-02-11 | 重庆斯欧智能科技研究院有限公司 | Transmission protocol adaptation method of industrial Internet |
| CN114217932A (en) * | 2021-12-24 | 2022-03-22 | 四川启睿克科技有限公司 | Third-party docking exception handling method and system |
-
2022
- 2022-04-24 CN CN202210433520.6A patent/CN114553932A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130111500A1 (en) * | 2011-10-28 | 2013-05-02 | International Business Machines Corporation | Message queuing application access to specific api services through a generic api interface intergrating a message queue |
| US20140149486A1 (en) * | 2012-11-29 | 2014-05-29 | Compuware Corporation | System And Methods For Tracing Individual Transactions Across A Mainframe Computing Environment |
| US20180324118A1 (en) * | 2017-05-05 | 2018-11-08 | Dell Products L.P. | Messaging queue service api optimization system |
| CN111222862A (en) * | 2018-11-27 | 2020-06-02 | 北京京东金融科技控股有限公司 | Data processing method and system, medium and computer system |
| WO2021179156A1 (en) * | 2020-03-10 | 2021-09-16 | 深圳市欢太科技有限公司 | Message processing method, device and system, and server |
| CN111666145A (en) * | 2020-06-24 | 2020-09-15 | 深圳壹账通智能科技有限公司 | Message processing method and system of message queue and computer equipment |
| CN112948174A (en) * | 2021-02-03 | 2021-06-11 | 江苏苏宁物流有限公司 | Message processing method and device, computer equipment and storage medium |
| CN113986566A (en) * | 2021-09-30 | 2022-01-28 | 重庆斯欧智能科技研究院有限公司 | Message path selection method for industrial Internet |
| CN114040031A (en) * | 2021-09-30 | 2022-02-11 | 重庆斯欧智能科技研究院有限公司 | Transmission protocol adaptation method of industrial Internet |
| CN113938516A (en) * | 2021-10-13 | 2022-01-14 | 中国银行股份有限公司 | Method and system for synchronously realizing transaction processing of heterogeneous system |
| CN114217932A (en) * | 2021-12-24 | 2022-03-22 | 四川启睿克科技有限公司 | Third-party docking exception handling method and system |
Non-Patent Citations (2)
| Title |
|---|
| 王师: "播出系统中消息服务器的应用和维护", 《中国广播影视》 * |
| 童小念等: "以MSMQ为中间件的短信业务处理系统", 《计算机工程与设计》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9961042B2 (en) | Universal mobile device messaging | |
| US7929523B2 (en) | System and method for communicating asynchronously with synchronous web services using a mediator service | |
| CN110351342A (en) | Service order processing method, device, computer equipment and storage medium | |
| US20060235970A1 (en) | System and method for exposing synchronous web services as notification style web services | |
| US8726079B2 (en) | Handling of messages in a message system | |
| EP2779583B1 (en) | Telecommunication method and system | |
| US9280400B2 (en) | App system platform | |
| US8484281B2 (en) | System and method for callbacks based on web service addressing | |
| US10834033B2 (en) | Method and system for transferring messages between messaging systems | |
| US20180359362A1 (en) | Intermediary device for data message network routing | |
| CN112783672A (en) | Remote procedure call processing method and system | |
| US10505878B1 (en) | Workflow management and corresponding integrated notification processing platform | |
| CN114827280A (en) | Request processing method, device, equipment and medium | |
| US8660989B2 (en) | Generic framework for application specific data exchange | |
| EP1715432A1 (en) | System and Method for Exposing Synchronous Web Services as Notification Style Web Services | |
| CN114553932A (en) | System integration docking method, device, equipment and medium | |
| CN114422467B (en) | Customer service message management system and method | |
| CN101685523A (en) | Service processing system for clients at mobile phone terminals | |
| CN110764932A (en) | Data processing method, system, medium and computing device | |
| CN114979308B (en) | Message processing method and device | |
| US20070162539A1 (en) | System and method for callbacks based on Web service addressing | |
| CN112788074B (en) | Data transmitting method, processing method, receiving method, apparatus thereof, and storage medium | |
| CN116108105A (en) | Service processing system, method and equipment, and data synchronization method and equipment | |
| CN113762677A (en) | Service processing method and device | |
| CN115866048A (en) | Data processing method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220527 |