CN113067885B

CN113067885B - Application system, request processing method, electronic device and storage medium

Info

Publication number: CN113067885B
Application number: CN202110349680.8A
Authority: CN
Inventors: 曹子钰; 汪维; 何洋; 王莹; 肖笛; 王梁紫墨
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-03-31
Filing date: 2021-03-31
Publication date: 2024-02-27
Anticipated expiration: 2041-03-31
Also published as: CN113067885A

Abstract

The embodiment of the invention relates to the technical field of the Internet of things and discloses an application system, a request processing method, electronic equipment and a storage medium. The application system comprises a communication service module, a structure conversion service module and a business logic conversion module, wherein the communication service module is used for receiving incoming requests of each enterprise service bus, carrying out request data processing on each incoming request, calling the business logic conversion module, intercepting the requests between the communication service module and the business logic conversion module through the structure conversion service module, carrying out structure conversion on the intercepted incoming requests, and carrying out logic processing on the requests after the structure conversion through the business logic conversion module. By carrying out operations such as data processing, structure conversion and the like on incoming requests with different technologies, protocols and content definition specifications, the docking of the application system and a plurality of enterprise service buses is realized, the application system can be shared in different enterprises, and the development cost is reduced.

Description

Application system, request processing method, electronic device and storage medium

Technical Field

The embodiment of the invention relates to the technical field of the Internet of things, in particular to an application system, a request processing method, electronic equipment and a storage medium.

Background

The enterprise service bus (Enterprise Service Bus, ESB) is an essential element in constructing the enterprise nervous system, providing the most basic connectivity backbone in the network. Integrated business processing, message flow between monitoring systems, business service for managing interaction between systems, and the like can be realized through ESB.

However, the enterprise service buses used by different enterprises are different, e.g., using different technologies (hypertext transfer, message queuing, remote procedure calls, etc.), different protocols (XML, JSON, serialization, etc.), or different content definition specifications. This makes it necessary to re-adapt each ESB when the same application system interfaces with a different ESB of each enterprise, and the development process is time-consuming and laborious. Illustratively, the prior art implements an ESB call-in application system by: the ESB sends the request to an ESB client in the application system, and the ESB client extracts the content in the request and calls a service logic module for processing.

Therefore, the prior art has the following technical problems: the application system only supports the docking of ESBs of a single technology, protocol or content definition specification, is difficult to be compatible with different ESBs, needs to be redeveloped when a new ESB is accessed, and has high project implementation cost.

Disclosure of Invention

The embodiment of the invention provides an application system, a request processing method, electronic equipment and a storage medium, which are used for solving the technical problem that ESB (electronic service bus) with different technologies, protocols and content definition specifications cannot be accessed simultaneously in the prior art.

In a first aspect, an embodiment of the present invention provides an application system, including a communication service module, a structure conversion service module, and a service logic conversion module; wherein,

the communication service module is used for receiving incoming requests of each enterprise service bus, carrying out request data processing on each incoming request and calling the business logic conversion module;

the structure conversion service module is used for intercepting the request between the communication service module and the service logic conversion module, performing structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the service logic conversion module;

the business logic conversion module is used for logically processing the request of the preset data structure.

Optionally, the communication service module comprises an incoming call service unit, a request scheduling unit, an incoming call protocol processing chain unit and a service logic scheduling unit;

The incoming call service unit comprises incoming call services of all protocol types, and is used for receiving incoming call requests of all protocol types and calling a request scheduling unit according to the received incoming call requests;

the request scheduling unit is used for determining an incoming call processing chain identifier according to the protocol type of the incoming call request and calling the incoming call protocol processing chain unit;

the incoming call protocol processing chain unit is used for determining an incoming call processing chain according to the incoming call processing chain identification, sequentially calling corresponding processors according to the incoming call processing chain, carrying out data processing on the incoming call request, and calling a service logic scheduling unit;

the service logic scheduling unit is used for determining service logic according to the data processing result of the incoming call request and calling the service logic, and the service logic is used for logically processing the data processing result.

Optionally, the communication service module further includes a request scheduling configuration unit, where the request scheduling configuration unit is configured to configure an incoming processing chain identifier of each protocol type;

the request scheduling unit sends the protocol type of the incoming call request to the request scheduling configuration unit, and the request scheduling configuration unit determines a corresponding incoming call processing chain identifier based on the protocol type and feeds the corresponding incoming call processing chain identifier back to the request scheduling unit.

Optionally, the communication service module further includes an incoming call processing chain configuration unit, where the incoming call processing chain configuration unit is configured to configure an incoming call processing chain corresponding to each incoming call processing chain identifier;

the incoming call protocol processing chain unit sends an incoming call processing chain identifier corresponding to the incoming call request to the incoming call processing chain configuration unit; the incoming call processing chain configuration unit determines a corresponding processing chain based on the incoming call processing chain identification and feeds back the corresponding processing chain to the incoming call protocol processing chain unit.

Optionally, the communication service module further includes a service logic scheduling configuration unit, where the service logic scheduling configuration unit is configured to configure service logic information corresponding to various data processing results;

the service logic scheduling unit sends the data processing result of the incoming call request to the service logic scheduling configuration unit, and the service logic scheduling configuration unit determines corresponding service logic information according to the data processing result and feeds back the service logic information to the service logic scheduling unit.

Optionally, the service logic conversion module is further configured to generate an outgoing call request with a preset data structure, and call the communication service module;

The structure conversion service module is further used for intercepting the request between the communication service module and the business logic conversion module, carrying out structure conversion on the intercepted outgoing request according to the request type of the outgoing request to obtain a request of an outgoing data structure, and calling the communication service module;

the communication service module is further configured to send the request for calling out the data structure to a target enterprise service bus.

Optionally, the communication service module further includes a communication service interface, an outgoing protocol processing chain unit, an outgoing adaptation unit and an outgoing service unit, where the outgoing service unit includes outgoing services of each protocol type;

the communication service interface receives an outgoing call request, determines an outgoing call processing chain identifier corresponding to the outgoing call request, and invokes a protocol processing chain unit;

the calling protocol processing chain unit is used for determining a calling processing chain according to the calling processing chain identification, sequentially calling a corresponding processor according to the calling processing chain, carrying out data processing on the calling request, and calling a calling adaptation unit;

the call adaptation unit is configured to determine a call service corresponding to the call request according to at least one of a data processing result of the call request and the call processing chain identifier, and invoke a call service in the call service unit, where the call service is used to call the call request.

Optionally, the communication service module further includes a processing chain scheduling configuration unit, configured to configure each protocol type and an outgoing processing chain identifier corresponding to the service type;

the communication service interface sends the protocol type and the service type of the outgoing request to the processing chain scheduling configuration unit;

and the processing chain scheduling configuration unit determines a corresponding outgoing processing chain identifier based on the protocol type and the service type of the outgoing request and feeds the corresponding outgoing processing chain identifier back to the communication service interface.

Optionally, the communication service module further includes an outgoing processing chain configuration unit, configured to configure each outgoing processing chain identifier and a corresponding outgoing processing chain;

the outgoing protocol processing chain unit sends an outgoing processing chain identifier corresponding to the outgoing request to the outgoing processing chain configuration unit; the outgoing processing chain configuration unit determines a corresponding outgoing processing chain based on the outgoing processing chain identification and feeds the corresponding outgoing processing chain back to the outgoing protocol processing chain unit.

Optionally, the communication service module further includes an outgoing communication configuration unit, configured to configure a data processing result and/or an outgoing processing chain identifier corresponding to each outgoing service;

the outgoing call adaptation unit is configured to send at least one of a data processing result of the outgoing call request and the outgoing call processing chain identifier to the outgoing call communication configuration unit;

The outgoing communication configuration unit is used for determining outgoing service corresponding to the outgoing request based on at least one of the data processing result and the outgoing processing chain identifier, and feeding back the outgoing service to the outgoing adaptation unit.

Optionally, the outgoing service unit and the incoming service unit are respectively provided with an expansion interface, and the expansion interfaces are respectively used for accessing the newly added outgoing service and the newly added incoming service.

Optionally, the structure conversion service module comprises a structure conversion interception inlet, an object conversion unit and a call service unit;

the structure conversion interception inlet is used for intercepting requests between the communication service module and the business logic conversion module, wherein the requests comprise incoming requests and outgoing requests;

the object conversion unit is used for carrying out structural conversion according to the source object and the target service object name of the request;

the call service unit is used for calling the target service after the structure conversion is completed.

Optionally, the object conversion unit includes a reflection caller and a converter;

the reflection caller determines a converter for carrying out structural conversion according to the source object and the target service object name in a reflection mode;

The converter is used for carrying out structural transformation on the source object to obtain the target object.

Optionally, the object conversion unit includes an expansion interface, where the expansion interface is used to access the new converter.

In a second aspect, an embodiment of the present invention further provides a request processing method, including:

receiving incoming requests of each enterprise service bus based on the communication service module, carrying out request data processing on each incoming request, and calling a service logic conversion module;

based on a structure conversion service module, intercepting a request between the communication service module and the service logic conversion module, performing structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the service logic conversion module;

and carrying out logic processing on the request of the preset data structure based on the service logic conversion module.

In a third aspect, an embodiment of the present invention further provides a request processing method, including:

generating an outgoing call request of a preset data structure based on a business logic conversion module, and calling a communication service module;

intercepting a request between the communication service module and the business logic conversion module based on a structure conversion service module, performing structure conversion on the intercepted outgoing request according to the request type of the outgoing request to obtain a request of an outgoing data structure, and calling the communication service module;

And sending the call-out request to a target enterprise service bus based on the communication service module.

In a fourth aspect, an embodiment of the present invention further provides an electronic device, including:

one or more processors;

storage means for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a request processing method as provided by any embodiment of the present invention.

In a fifth aspect, an embodiment of the present invention further provides a computer readable storage medium having stored thereon a computer program, which when executed by a processor, implements a request processing method as provided in any embodiment of the present invention.

The embodiments of the above invention have the following advantages or benefits:

the application system provided by the embodiment of the invention comprises a communication service module, a structure conversion service module and a business logic conversion module, wherein the communication service module is used for receiving incoming requests of each enterprise service bus, carrying out request data processing on each incoming request, calling the business logic conversion module, intercepting the requests between the communication service module and the business logic conversion module through the structure conversion service module, carrying out structure conversion on the intercepted incoming requests, and carrying out logic processing on the requests after the structure conversion through the business logic conversion module. When receiving the incoming requests of each enterprise service bus, the embodiment of the invention realizes the butt joint of the application system and a plurality of enterprise service buses by carrying out operations such as data processing, structure conversion and the like on the incoming requests of different technologies, protocols and content definition specifications, thereby realizing the sharing of the application system in different enterprises; and the quick access of a new enterprise service bus can be realized by flexibly configuring the request data processing and the structure conversion, so that the development cost is reduced.

Drawings

In order to more clearly illustrate the technical solution of the exemplary embodiments of the present invention, a brief description is given below of the drawings required for describing the embodiments. It is obvious that the drawings presented are only drawings of some of the embodiments of the invention to be described, and not all the drawings, and that other drawings can be made according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of an application system according to a first embodiment of the present invention;

fig. 2 is a schematic structural diagram of a communication service module according to a second embodiment of the present invention;

fig. 3 is a schematic structural diagram of a preferred communication service module according to a second embodiment of the present invention;

fig. 4 is a schematic structural diagram of a communication service module according to a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of a preferred communication service module according to a fourth embodiment of the present invention;

fig. 6 is a schematic structural diagram of a structural conversion service module according to a fifth embodiment of the present invention;

fig. 7 is a flowchart of a request processing method according to a sixth embodiment of the present invention;

fig. 8 is a flowchart of a request processing method according to a seventh embodiment of the present invention

Fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.

Example 1

Fig. 1 is a schematic structural diagram of an application system according to a first embodiment of the present invention, and as shown in fig. 1, an application system 10 provided in this embodiment includes a communication service module 110, a structural conversion service module 120, and a service logic conversion module 130; the communication service module 110 is configured to receive incoming requests of each enterprise service bus, process request data of each incoming request, and call the service logic conversion module 130; the structure conversion service module 120 is configured to intercept a request between the communication service module 110 and the service logic conversion module 130, perform structure conversion on the intercepted incoming call request after processing, obtain a request with a preset data structure, and call the service logic conversion module 130; the service logic conversion module 130 is configured to logically process a request of a preset data structure.

Among other things, the application system 10 of the present embodiment may interface with one or more ESBs. Specifically, the application system 10 receives an incoming call request sent by each ESB through the communication service module 110. The incoming call request may be a request sent by the ESB for requesting business services from the application system 10, such as a transfer request, a cash withdrawal request, a balance inquiry request, etc.

In one embodiment, the communication service module 110 of the application system 10 performs request data processing on each incoming request, including: the communication service module 110 determines a calling technique and a calling protocol of the incoming call request, and performs request data processing on the incoming call request based on the calling technique and the calling protocol of the incoming call request. The calling technology of the incoming call request can be a communication mechanism of the ESB sending the incoming call request and an application system, such as a message queue, a remote procedure call and the like; the call protocol may be a communication protocol of the ESB sending the incoming request with the application system, e.g., extensible markup language (Extensible Markup Language, XML), javaScript object notation (JavaScript Object Notation, JSON), serialization, etc. Specifically, the communication service module 110 may be preconfigured with various call technologies and data processing rules corresponding to call protocols, and after determining the call technologies and call protocols of the incoming call request, request data processing is performed on the incoming call request according to the data processing rules corresponding to the call technologies and call protocols. By way of example, the data request processing may be message decryption, message header format processing, integrity checking, and the like.

The communication service module 110 directly invokes the service logic conversion module 130 after processing the request data of the incoming request. It should be noted that, since the content definition specifications of the incoming requests may be different, the incoming requests need to be structurally converted before the service logic conversion module 130 is invoked to logically process the incoming requests. Therefore, in this embodiment, the structure conversion service module 120 is configured to intercept the request between the communication service module 110 and the service logic conversion module 130, so as to perform structure conversion on the incoming request after the request data processing to obtain a request with a preset data structure, and call the service logic conversion module 130. It should be noted that the preset data structure may be a standard data structure configured in advance, and the specific configuration of the preset data structure is not limited in this application.

In this embodiment, the communication service module 110 may process corresponding request data for incoming requests of various call protocols and call technologies, and the structure conversion service module 120 may perform format conversion for incoming requests of various content definition specifications, so as to implement processing of incoming requests of different call protocols, call technologies and content definition specifications, and further implement docking of an application system with ESBs using different technologies, protocols and content definition specifications, thereby reducing development cost.

In this embodiment, the communication service module 110 invokes the service logic conversion module 130, and the purpose of the configuration conversion service module 120 to intercept the request between the communication service module 110 and the service logic conversion module 130 is to: by directly adding the structure conversion service module for intercepting the request, the calling logic between the original communication service module and the business logic conversion module is not required to be changed, and the coupling degree of the structure conversion service module, the communication service module and the business logic conversion module is reduced, so that the development cost is reduced.

Of course, in another embodiment, after the communication service module 110 performs the request data processing on the incoming call request, the structure conversion service module 120 may be directly called, and the structure conversion service module 120 performs the structure conversion on the incoming call request after the request data processing to obtain a request with a preset data structure, and call the service logic conversion module 130.

After obtaining the request of the preset data structure, the structure conversion service module 120 of this embodiment invokes the service logic conversion module 130 to perform logic processing on the request of the preset data structure. The logic processing may be to perform corresponding processing on the request service of the incoming request. For example, the logical process of the incoming call request for transfer process may be deducting the transfer amount in the transfer account, adding the transfer amount in the transferred account, and the like.

The application system provided by the embodiment comprises a communication service module, a structure conversion service module and a business logic conversion module, wherein the communication service module is used for receiving incoming requests of each enterprise service bus, carrying out request data processing on each incoming request, calling the business logic conversion module, intercepting the requests between the communication service module and the business logic conversion module through the structure conversion service module, carrying out structure conversion on the intercepted incoming requests, and carrying out logic processing on the requests after the structure conversion through the business logic conversion module. When receiving the incoming requests of each enterprise service bus, the embodiment of the invention realizes the butt joint of the application system and a plurality of enterprise service buses by carrying out operations such as data processing, structure conversion and the like on the incoming requests of different technologies, protocols and content definition specifications, thereby realizing the sharing of the application system in different enterprises; and the quick access of a new enterprise service bus can be realized by flexibly configuring the request data processing and the structure conversion, so that the development cost is reduced.

Example two

Fig. 2 is a schematic structural diagram of a communication service module according to a second embodiment of the present invention, where the communication service module includes an incoming call service unit, a request scheduling unit, an incoming call protocol processing chain unit, and a service logic scheduling unit, which are optional based on the foregoing embodiments. Wherein the explanation of the same or corresponding terms as those of the above embodiments is not repeated herein.

Referring to fig. 2, the communication service module 210 provided in the present embodiment includes an incoming call service unit 2101, a request scheduling unit 2102, an incoming call protocol processing chain unit 2103, and a service logic scheduling unit 2104; wherein the incoming call service unit 2101 includes an incoming call service of each protocol type, for receiving an incoming call request of each protocol type, and calling the request scheduling unit 2102 according to the received incoming call request; the request scheduling unit 2102 is configured to determine an incoming processing chain identifier according to a protocol type of an incoming request, and call the incoming protocol processing chain unit 2103; the incoming protocol processing chain unit 2103 is used for determining an incoming processing chain according to the incoming processing chain identification, sequentially calling corresponding processors according to the incoming processing chain, performing data processing on an incoming request, and calling the service logic scheduling unit 2104; the service logic scheduling unit 2104 is configured to determine service logic according to a data processing result of the incoming request, and invoke the service logic, where the service logic is configured to logically process the data processing result.

Among them, the protocol type incoming call service includes, but is not limited to, an http incoming call service, a webservice incoming call service, a message queue incoming call service, and a remote call incoming call service. The incoming call service unit 2101 may include, for example, an http incoming call service, a webservice incoming call service, a message queue incoming call service, and a remote call incoming call service. Specifically, each incoming call service is configured to receive an incoming call request of a corresponding protocol type. For example, the http incoming call service is used for receiving an incoming call request of the http protocol type, and the message queue incoming call service is used for receiving an incoming call request of the message queue type. Note that, according to the protocol type of each ESB to which the application system is actually connected, each of the incoming services of the protocol type may be configured in advance in the incoming service unit 2101, and the incoming services are only examples, and the present application does not limit the incoming services configured in the incoming service unit 2101 or the number of the incoming services configured.

In one embodiment, the incoming call service unit 2101 is provided with an expansion interface for accessing the newly added incoming call service. The newly added incoming call service can be flexibly configured according to the protocol and technology of ESB of the actual access application system. The number of newly added incoming services may be one or a plurality of newly added incoming services. The purpose of setting an extension interface at the incoming service unit 2101 is to: the access of the ESB of the new technology and protocol is realized, the extension of the incoming call service of the application system is further realized, and the application system is supported to quickly access the new ESB.

Specifically, the incoming call service unit 2101 receives an incoming call request of each protocol type according to an incoming call service of each protocol type, and invokes the request scheduling unit 2102 according to the received incoming call request. In this embodiment, the request scheduling unit 2102 may determine an incoming processing chain identification according to a protocol type of an incoming request. The incoming processing chain identifier may be description information of a processing chain that processes the incoming request. In other words, each protocol type has a corresponding incoming processing chain identification, the request scheduling unit 2102 determines an incoming processing chain identification from the protocol type of the incoming request, and invokes the incoming protocol processing chain unit 2103.

The incoming protocol processing chain unit 2103 may determine a corresponding incoming processing chain according to the incoming processing chain identification determined by the request scheduling unit 2102 and call the corresponding processors in order based on the incoming processing chain to perform data processing on the incoming request by each processor. The incoming processing chains corresponding to the different incoming processing chain identifiers can be the same or different. Illustratively, the incoming processing chain identification a corresponds to the incoming processing chain a, and the incoming processing chain identification B corresponds to the incoming processing chain B. In this embodiment, the incoming call processing chain may include processor information and a call order of the processors. The processor may be a processor such as a message decryption processor, a message header format processor, an attribute mapping processor, an integrity check processor, a tracking number generation processor, and the like. Illustratively, the incoming processing chain a is: the message Wen Jiemi processor-message header format processor-attribute mapping processor; the incoming processing chain B is: attribute mapping processor-integrity check processor.

The incoming protocol processing chain unit 2103 calls the service logic scheduling unit 2104 after calling the corresponding processor to process the incoming request; the service logic scheduling unit 2104 determines service logic based on the data processing result of the incoming request and invokes the service logic. Wherein, the business logic can be used for carrying out logic processing on the data processing result.

The communication service module of the embodiment comprises an incoming call service unit, a request scheduling unit, an incoming call protocol processing chain unit and a business logic scheduling unit, and receives incoming call requests of all protocol types through incoming call services of all protocol types configured in the incoming call service unit, so that the access of incoming call requests of all protocol types is realized, and further the butt joint of an application system and ESB of all protocol types is realized; and the incoming call processing chain identification is determined through the request scheduling unit, the incoming call processing chain is determined through the incoming call protocol processing chain unit, and the corresponding processor is called, so that the incoming call request is subjected to data processing, the processing of the incoming call requests of various protocol types is realized, the simultaneous access of a plurality of ESBs to an application system is further realized, the sharing of the application system in different enterprises is realized, and independent development of each enterprise is not required.

Optionally, the communication service module 210 further includes a request scheduling configuration unit, where the request scheduling configuration unit is configured to configure an incoming processing chain identifier of each protocol type; the request scheduling unit 2102 sends the protocol type of the incoming call request to the request scheduling configuration unit, and the request scheduling configuration unit determines a corresponding incoming call processing chain identifier based on the protocol type and feeds back the incoming call processing chain identifier to the request scheduling unit 2102.

The request scheduling configuration unit is pre-configured with incoming call processing chain identifiers corresponding to all protocol types. Specifically, the request scheduling unit 2102 may send the protocol type of the incoming request to the request scheduling configuration unit, so as to determine, according to the request scheduling configuration unit, an incoming processing chain identifier corresponding to the protocol type of the incoming request.

Optionally, the communication service module 210 further includes an incoming processing chain configuration unit, where the incoming processing chain configuration unit is configured to configure an incoming processing chain corresponding to each incoming processing chain identifier; the incoming protocol processing chain unit 2103 transmits an incoming processing chain identification corresponding to the incoming request to the incoming processing chain configuration unit; the incoming processing chain configuration unit determines a corresponding processing chain based on the incoming processing chain identification, and feeds back to the incoming protocol processing chain unit 2103.

The incoming processing chain configuration unit is pre-configured with incoming processing chains corresponding to the incoming processing chain identifiers. Specifically, the incoming protocol processing chain unit 2103 may send an incoming processing chain identifier corresponding to the incoming request to the incoming processing chain configuration unit, so as to determine a corresponding processing chain of the incoming processing chain identifier corresponding to the incoming request according to the incoming processing chain configuration unit.

Optionally, the communication service module 210 further includes a service logic scheduling configuration unit, where the service logic scheduling configuration unit is configured to configure service logic information corresponding to each type of data processing result; the service logic scheduling unit 2104 sends the data processing result of the incoming call request to the service logic scheduling configuration unit, and the service logic scheduling configuration unit determines corresponding service logic information according to the data processing result and feeds back the service logic information to the service logic scheduling unit 2104.

The service logic scheduling configuration unit is pre-configured with service logic information corresponding to each type of data processing result. Specifically, the service logic scheduling unit 2104 may send the data processing result of the incoming request to the service logic scheduling configuration unit, so as to determine service logic information corresponding to the data processing result of the incoming request according to the service logic scheduling configuration unit.

In a preferred embodiment, the application system comprises a communication service module, a structure conversion service module and a business logic conversion module; the communication service module 310 includes an incoming service unit 3101, a request scheduling unit 3102, a request scheduling configuration unit 3103, an incoming protocol processing chain unit 3104, an incoming processing chain configuration unit 3105, a service logic scheduling unit 3106, and a service logic scheduling configuration unit 3107, and as shown in fig. 3, a schematic structural diagram of a preferred communication service module is illustrated.

The incoming call service unit 3101 includes an incoming call service of each protocol type, and is configured to receive an incoming call request of each protocol type, and call the request scheduling unit 3102 according to the received incoming call request;

the request scheduling unit 3102 sends the protocol type of the incoming call request to the request scheduling configuration unit 3103, the scheduling configuration unit 3103 configures incoming call processing chain identifiers of the protocol types, determines a corresponding incoming call processing chain identifier based on the protocol type sent by the request scheduling unit 3102, and feeds back to the request scheduling unit 3102; the request scheduling unit 3102 calls the incoming protocol processing chain unit 3104 after determining the incoming processing chain identification;

the incoming call protocol processing chain unit 3104 sends an incoming call processing chain identifier corresponding to the incoming call request to the incoming call processing chain configuration unit 3105, the incoming call processing chain configuration unit 3105 configures incoming call processing chains corresponding to the incoming call processing chain identifiers, determines corresponding processing chains based on the incoming call processing chain identifiers sent by the incoming call protocol processing chain unit 3104, feeds back the corresponding processing chains to the incoming call protocol processing chain unit 3104, and after determining the processing chains, the incoming call protocol processing chain unit 3104 sequentially calls corresponding processors according to the processing chains, performs data processing on the incoming call request, and calls the service logic scheduling unit 3106;

The service logic scheduling unit 3106 sends the data processing result of the incoming request to the service logic scheduling configuration unit 3107, the service logic scheduling configuration unit 3107 configures service logic information corresponding to the data processing result of each type, determines corresponding service logic information according to the data processing result sent by the service logic scheduling unit 3106, and feeds back the service logic information to the service logic scheduling unit 3106, and the service logic scheduling unit 3106 invokes the service logic after determining the service logic, where the service logic is used for logically processing the data processing result.

Example III

The application system provided in this embodiment is, based on the foregoing embodiments, optionally, a service logic conversion module of the application system, and further configured to generate an outgoing call request of a preset data structure, and call a communication service module; the structure conversion service module is also used for intercepting the request between the communication service module and the business logic conversion module, carrying out structure conversion on the intercepted outgoing request according to the request type of the outgoing request, obtaining the request of an outgoing data structure, and calling the communication service module; and the communication service module is also used for sending the request of the outgoing data structure to the target enterprise service bus.

Specifically, the application system comprises a communication service module, a structure conversion service module and a business logic conversion module; wherein,

the communication service module is used for receiving the incoming call requests of each enterprise service bus, carrying out request data processing on each incoming call request, and calling the business logic conversion module;

the structure conversion service module is used for intercepting the request between the communication service module and the service logic conversion module, carrying out structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the service logic conversion module;

the business logic conversion module is used for carrying out logic processing on a request of a preset data structure;

the business logic conversion module is also used for generating an outgoing call request of a preset data structure and calling the communication service module;

the structure conversion service module is also used for intercepting the request between the communication service module and the business logic conversion module, carrying out structure conversion on the intercepted outgoing request according to the request type of the outgoing request, obtaining the request of an outgoing data structure, and calling the communication service module;

and the communication service module is also used for sending the request of the outgoing data structure to the target enterprise service bus.

The application system of this embodiment may generate an outgoing request and send to the docked ESB. Specifically, the service logic conversion module may generate an outgoing call request of a preset data structure, the structure conversion service module intercepts a request between the communication service module and the service logic conversion module, converts the intercepted outgoing call request structure of the preset data structure into a request of an outgoing call data structure, and the communication service module sends the request of the outgoing call data structure to the target enterprise service bus. The outgoing data structure may be a preset standard structure of a request output by the application system; the target enterprise service bus is the recipient ESB of the outgoing request.

According to the application system provided by the embodiment, the service logic conversion module is used for generating an outgoing call request of a preset data structure, the communication service module is called, the communication service module is used for intercepting the request between the communication service module and the service logic conversion module, converting the request into the request of the outgoing call data structure, calling the communication service module, and sending the request of the outgoing call data structure to the target ESB. The application system is abutted to a plurality of enterprise service buses, and sharing among different enterprises is further achieved.

Example IV

Fig. 4 is a schematic structural diagram of a communication service module according to a fourth embodiment of the present invention, where the communication service module further includes a communication service interface, an outgoing protocol processing chain unit, an outgoing adaptation unit, and an outgoing service unit, which are optional based on the foregoing embodiments. Wherein the explanation of the same or corresponding terms as those of the above embodiments is not repeated herein.

Referring to fig. 4, the communication service module 410 provided in this embodiment further includes a communication service interface 4108, an outgoing protocol processing chain unit 4109, an outgoing adaptation unit 4110, and an outgoing service unit 4111, where the outgoing service unit 4111 includes outgoing services of each protocol type; the communication service interface 4108 receives the outgoing request, determines an outgoing processing chain identifier corresponding to the outgoing request, and invokes the outgoing protocol processing chain unit 4109;

an outgoing protocol processing chain unit 4109, configured to determine an outgoing processing chain according to the outgoing processing chain identifier, and call a corresponding processor according to the outgoing processing chain in sequence, perform data processing on an outgoing request, and call an outgoing adaptation unit 4110;

the outgoing adaptation unit 4110 is configured to determine an outgoing service corresponding to the outgoing request according to at least one of a data processing result and an outgoing processing chain identifier of the outgoing request, and invoke the outgoing service in the outgoing service unit 4111, where the outgoing service is used to make an outgoing request.

The communication service interface 4108 of the communication service module 410 may determine an outgoing processing chain identifier corresponding to the received outgoing request. The outgoing processing chain identification may be descriptive information of the processing chain that processed the outgoing request. In this embodiment, the communication service interface 4108 may determine the corresponding outgoing processing chain identifier according to the service type of the outgoing request. For example, if the service type is building Transfer, the corresponding outgoing processing chain is identified as transfer_a; and if the service type is the worker Transfer, the corresponding outgoing processing chain is identified as transfer_B.

Specifically, the communication service interface 4108 invokes the outgoing protocol processing chain unit 4109 after determining the outgoing processing chain identifier corresponding to the outgoing request, where the outgoing protocol processing chain unit 4109 determines an outgoing processing chain according to the outgoing processing chain identifier, and invokes the corresponding processors according to the outgoing processing chain sequence, so as to perform data processing on the outgoing request through each processor. The outgoing protocol processing chain unit 4109 invokes the outgoing adaptation unit 4110 after performing data processing on the outgoing request, and the outgoing adaptation unit 4110 determines an outgoing service corresponding to the outgoing request according to the data processing result and/or the outgoing processing chain identifier, and invokes the outgoing service in the outgoing service unit 4111 to make outgoing of the outgoing request based on the invoked outgoing service.

In the present embodiment, the outgoing services in the outgoing service unit 4111 include, but are not limited to, an http outgoing service, a webservice outgoing service, a message queue outgoing service, and a remote call outgoing service. Specifically, each outgoing service is configured to send an outgoing request of a corresponding protocol type. For example, an http outgoing service is used to send outgoing requests of the http protocol type.

Note that, the outgoing call adaptation unit 4110 may determine the outgoing call service corresponding to the outgoing call request only according to the data processing result, may determine the outgoing call service corresponding to the outgoing call request only according to the outgoing call processing chain identifier, and may determine the outgoing call service corresponding to the outgoing call request according to the data processing result and the outgoing call processing chain identifier.

The communication service module of the embodiment further comprises a communication service interface, an outgoing protocol processing chain unit, an outgoing adaptation unit and an outgoing service unit, and receives an outgoing request through the communication service interface and determines an outgoing processing chain identifier corresponding to the outgoing request; determining an outgoing processing chain corresponding to the outgoing processing chain identification through an outgoing protocol processing chain unit, and sequentially calling a corresponding processor according to the outgoing processing chain to process data on an outgoing request; the outgoing service corresponding to the outgoing requests is determined through the outgoing adaptation unit, the outgoing processing of each outgoing request is achieved, and further the butt joint of the application system and the ESBs is achieved, so that the application system can be shared among different enterprises, and independent development is not required for each enterprise.

Optionally, the communication service module 410 further includes a processing chain scheduling configuration unit, configured to configure each protocol type and an outgoing processing chain identifier corresponding to the service type; the communication service interface 4108 sends the protocol type and the service type of the outgoing request to the processing chain scheduling configuration unit; the processing chain schedule configuration unit determines a corresponding outgoing processing chain identifier based on the protocol type and the service type of the outgoing request, and feeds back the corresponding outgoing processing chain identifier to the communication service interface 4108.

The processing chain scheduling configuration unit is pre-configured with the calling processing chain identification corresponding to each protocol type and service type. Specifically, the communication service interface 4108 may send the protocol type and the service type of the outgoing request to the processing chain scheduling configuration unit, so as to determine, according to the processing chain scheduling configuration unit, an outgoing processing chain identifier corresponding to the outgoing request.

Optionally, the communication service module 410 further includes an outgoing processing chain configuration unit, configured to configure each outgoing processing chain identifier and a corresponding outgoing processing chain; the outgoing protocol processing chain unit 4109 sends an outgoing processing chain identifier corresponding to the outgoing request to the outgoing processing chain configuration unit; the outgoing processing chain configuration unit determines a corresponding outgoing processing chain based on the outgoing processing chain identification and feeds back to the outgoing protocol processing chain unit 4109.

The calling processing chain configuration unit is pre-configured with calling processing chains corresponding to the calling processing chain identifiers. The outgoing protocol processing chain unit 4109 may send an outgoing processing chain identification corresponding to the outgoing request to the outgoing processing chain configuration unit to determine a corresponding processing chain of the outgoing processing chain identification of the outgoing request according to the outgoing processing chain configuration unit.

Optionally, the communication service module 410 further includes an outgoing communication configuration unit, configured to configure data processing results and/or outgoing processing chain identifiers corresponding to each outgoing service; an outgoing call adaptation unit 4110, configured to send at least one of a data processing result and an outgoing call processing chain identifier of the outgoing call request to the outgoing call communication configuration unit; the outgoing communication configuration unit is configured to determine an outgoing service corresponding to the outgoing request based on at least one of the data processing result and the outgoing processing chain identifier, and feed back the outgoing service to the outgoing adaptation unit 4110.

The outgoing communication configuration unit is pre-configured with data processing results and/or outgoing processing chain identifiers corresponding to the outgoing services. That is, the outgoing communication configuration unit stores the corresponding relationship between each data processing result and/or outgoing processing chain identifier and each outgoing service. Specifically, the outgoing call adaptation unit 4110 may transmit at least one of the data processing result and the outgoing call processing chain identifier of the outgoing call request to the outgoing call communication configuration unit. And determining, by the outgoing communication configuration unit, an outgoing service corresponding to the outgoing request based on the stored correspondence, the data processing result of the outgoing request, and/or the outgoing processing chain identifier.

Optionally, the outgoing service unit 4111 is provided with an extension interface, where the extension interface is used to access the newly added outgoing service. The newly added calling service can be flexibly configured according to the protocol and technology of ESB which is actually in butt joint with the application system. The number of newly added outgoing services may be one or a plurality of newly added outgoing services. The purpose of setting an extension interface at the outgoing service unit 4111 is to: the docking of ESB of the new technology and protocol is realized, and further the expansion of the calling service of the application system is realized.

In one embodiment, the outgoing service unit and the incoming service unit may be respectively provided with an expansion interface, where the expansion interfaces are respectively used to access the newly added outgoing service and the newly added incoming service.

In a preferred embodiment, the communication service module 510 further includes a communication service interface 5108, a processing chain schedule configuration unit 5109, an outgoing protocol processing chain unit 5110, an outgoing processing chain configuration unit 5111, an outgoing adaptation unit 5112, an outgoing communication configuration unit 5113, and an outgoing service unit 5114. As shown in fig. 5, a schematic structural diagram of a preferred communication service module is shown. The outgoing service unit 5114 includes outgoing services of each protocol type, the processing chain scheduling configuration unit 5109 is configured to configure outgoing processing chain identifiers corresponding to each protocol type and each service type, the outgoing processing chain configuration unit 5111 is configured to configure each outgoing processing chain identifier and a corresponding outgoing processing chain, and the outgoing communication configuration unit 5113 is configured to configure data processing results and/or outgoing processing chain identifiers corresponding to each outgoing service; the specific exhalation flow is as follows:

The communication service interface 5108 receives the outgoing request, and sends the protocol type and the service type of the outgoing request to the processing chain scheduling configuration unit 5109; the processing chain scheduling configuration unit 5109 determines a corresponding outgoing processing chain identifier based on the protocol type and the service type of the outgoing request, and feeds back the corresponding outgoing processing chain identifier to the communication service interface 5108; the communication service interface 5108 invokes the outgoing protocol processing chain unit 5110;

the outgoing protocol processing chain unit 5110 sends an outgoing processing chain identifier corresponding to the outgoing request to the outgoing processing chain configuration unit 5111, the outgoing processing chain configuration unit 5111 determines a corresponding outgoing processing chain based on the outgoing processing chain identifier and feeds back the corresponding outgoing processing chain to the outgoing protocol processing chain unit 5110, and the outgoing protocol processing chain unit 5110 sequentially invokes a corresponding processor according to the outgoing processing chain to process data of the outgoing request and invokes the outgoing adaptation unit 5112;

the outgoing adaptation unit 5112 sends at least one of the data processing result and the outgoing processing chain identifier of the outgoing request to the outgoing communication configuration unit 5113, the outgoing communication configuration unit 5113 determines an outgoing service corresponding to the outgoing request based on at least one of the data processing result and the outgoing processing chain identifier, and feeds back the outgoing service to the outgoing adaptation unit 5112, and the outgoing adaptation unit 5112 invokes the outgoing service in the outgoing service unit 5114, where the outgoing service is used to make outgoing calls for the outgoing request.

Example five

Fig. 6 is a schematic structural diagram of a structural conversion service module according to a fifth embodiment of the present invention, where the structural conversion service module includes a structural conversion interception entry, an object conversion unit, and a call service unit. Wherein the explanation of the same or corresponding terms as those of the above embodiments is not repeated herein.

Referring to fig. 6, the structure conversion service module 610 provided in the present embodiment includes a structure conversion interception entry 6101, an object conversion unit 6102, and a call service unit 6103; the structure conversion interception entry 6101 is used for intercepting a request between the communication service module and the business logic conversion module, where the request includes an incoming request and an outgoing request; the object conversion unit 6102 is configured to perform structural conversion according to the source object and the target service object name of the request; the call service unit 6103 is for calling a target service after the structure conversion is completed.

The structure conversion interception entry 6101 may intercept incoming requests and outgoing requests between the communication service module and the service logic conversion module. The object conversion unit 6102 may perform structural conversion according to the source object and the target service object name of the request with respect to the intercepted request. The call service unit 6103 may call the target service after the structure conversion is completed.

Optionally, the object conversion unit 6102 includes a reflection caller and a converter; the reflection caller determines a converter for carrying out structural conversion according to the names of the source object and the target service object in a reflection mode; the converter is used for carrying out structural transformation on the source object to obtain the target object. Specifically, the object conversion unit 6102 determines a converter for performing structural conversion by using a reflection caller, and performs structural conversion on the source object by using the determined converter to obtain the target object. Note that, the object conversion unit 6102 may include one or more converters, and the converters for performing structural conversion corresponding to different source objects and target service object names may be the same or different.

Optionally, the object conversion unit 6102 includes an expansion interface, where the expansion interface is used to access the newly added converter. The newly added converter can be flexibly configured according to the content definition specification of the ESB which is actually in butt joint with the application system. The number of the new converters may be one or more. The object conversion unit 6102 is provided with an expansion interface for the purpose of: the docking of ESB of the newly-added content definition specification is realized, and further, the extension of the incoming and outgoing services of the application system is realized.

The structure conversion service module provided by the embodiment comprises a structure conversion interception inlet, an object conversion unit and a calling service unit, wherein the structure conversion interception inlet is used for intercepting an incoming request and an outgoing request between the communication service module and the business logic conversion module, the object conversion unit is used for carrying out structure conversion according to the source object and the target service object name of the request, and the calling service unit is used for calling the target service after the structure conversion is completed. By carrying out structural conversion on the requests of different content definition specifications, the docking of an application system and ESBs of a plurality of different content definition specifications is realized, and the development cost is reduced.

Example six

Fig. 7 is a flow chart of a request processing method provided in a sixth embodiment of the present invention, where the embodiment is applicable to a case of logically processing a received incoming request of each enterprise service bus, and is particularly applicable to a case of performing request data processing, structure conversion and logic processing on a received incoming request of each enterprise service bus to perform service response on a received incoming request, and the method may be performed by an application system, and the application system may be implemented by hardware and/or software, where the method specifically includes the following steps:

S710, receiving the incoming call requests of each enterprise service bus based on the communication service module, carrying out request data processing on each incoming call request, and calling the business logic conversion module.

S720, based on a structure conversion service module, intercepting the request between the communication service module and the business logic conversion module, performing structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the business logic conversion module.

And S730, carrying out logic processing on the request of the preset data structure based on the service logic conversion module.

Optionally, the communication service module receives an incoming call request of each enterprise service bus, performs request data processing on each incoming call request, and invokes the service logic conversion module, including:

receiving an incoming call request of each protocol type based on the incoming call service of each protocol type in an incoming call service unit of a communication service module, and calling a request scheduling unit in the communication service module according to the received incoming call request;

determining an incoming call processing chain identifier based on the protocol type of the incoming call request by the request scheduling unit, and calling an incoming call protocol processing chain unit in the communication service module;

Determining an incoming processing chain according to the incoming processing chain identification based on an incoming protocol processing chain unit, sequentially calling a corresponding processor according to the incoming processing chain, performing data processing on the incoming request, and calling a service logic scheduling unit;

and determining service logic based on the data processing result of the incoming call request by the service logic scheduling unit, calling the service logic, and performing logic processing on the data processing result according to the service logic.

Optionally, the determining, based on the request scheduling unit, the incoming processing chain identifier according to the protocol type of the incoming request includes:

the protocol type of the incoming call request is sent to a request scheduling configuration unit in the communication service module through a request scheduling unit;

and determining a corresponding incoming call processing chain identifier according to the protocol type based on the request scheduling configuration unit, and feeding back the incoming call processing chain identifier to the request scheduling unit, wherein the request scheduling configuration unit is used for configuring the incoming call processing chain identifier of each protocol type.

Optionally, the determining the incoming processing chain based on the incoming protocol processing chain unit according to the incoming processing chain identifier includes:

transmitting an incoming processing chain identifier corresponding to the incoming request to an incoming processing chain configuration unit in a communication service module based on an incoming protocol processing chain unit;

And determining a corresponding processing chain according to the incoming processing chain identification based on the incoming processing chain configuration unit and feeding back to the protocol processing chain unit, wherein the incoming processing chain configuration unit is used for configuring the incoming processing chain corresponding to each incoming processing chain identification.

Optionally, the service logic determining unit determines service logic according to the data processing result of the incoming call request, including:

transmitting the data processing result of the incoming call request to a service logic scheduling configuration unit in a communication service module based on a service logic scheduling unit;

and determining corresponding service logic information according to the data processing result based on the service logic scheduling configuration unit, and feeding back the service logic information to the service logic scheduling unit, wherein the service logic scheduling configuration unit is used for configuring the service logic information corresponding to various types of data processing results.

Optionally, based on a structure conversion service module, intercepting a request between the communication service module and the service logic conversion module, and performing structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the service logic conversion module, including:

Intercepting requests of the communication service module and the business logic conversion module based on a structure conversion interception inlet in a structure conversion service module, wherein the requests comprise incoming requests and outgoing requests;

based on an object conversion unit in the structure conversion service module, performing structure conversion according to the source object and the target service object name of the request;

and calling the target service after the structure conversion is completed based on the calling service unit in the structure conversion service module.

Optionally, based on an object conversion unit in the structure conversion service module, performing structure conversion according to the source object and the target service object name of the request, including:

determining a converter for performing structural conversion according to the source object and the target service object name in a reflection mode based on a reflection caller in an object conversion unit;

and carrying out structural transformation on the source object based on the converter in the object transformation unit to obtain the target object.

According to the technical scheme, the incoming requests of the enterprise service buses are received based on the communication service module, request data processing is carried out on the incoming requests, the requests between the communication service module and the business logic conversion module are intercepted based on the structure conversion service module, the intercepted and processed incoming requests are subjected to structure conversion to obtain requests with preset data structures, the requests with the preset data structures are logically processed based on the business logic conversion module, the butt joint of an application system and a plurality of enterprise service buses is achieved, and the application system is shared in different enterprises; and the quick access of a new enterprise service bus can be realized by flexibly configuring the request data processing and the structure conversion, so that the development cost is reduced.

Example seven

Fig. 8 is a flow chart of a request processing method provided in a seventh embodiment of the present invention, where the embodiment is applicable to a case of generating an outgoing request and sending the outgoing request to a target ESB, and is particularly applicable to a case of generating the outgoing request, and sending the outgoing request to the target ESB after performing a structural conversion on the outgoing request, where the method may be executed by an application system, and the application system may be implemented by hardware and/or software, and the method specifically includes the following steps:

s810, generating an outgoing call request of a preset data structure based on the business logic conversion module, and calling the communication service module.

S820, intercepting the request between the communication service module and the business logic conversion module based on the structure conversion service module, performing structure conversion on the intercepted outgoing request according to the request type of the outgoing request to obtain a request of an outgoing data structure, and calling the communication service module.

And S830, sending the call request to a target enterprise service bus based on the communication service module.

Optionally, sending the outgoing request to a target enterprise service bus based on the communication service module includes:

based on a communication service interface in the communication service module, receiving an outgoing call request, determining an outgoing call processing chain identifier corresponding to the outgoing call request, and calling an outgoing call protocol processing chain unit;

Based on an outgoing protocol processing chain unit in the communication service module, determining an outgoing processing chain according to the outgoing processing chain identification, sequentially calling a corresponding processor according to the outgoing processing chain, performing data processing on the outgoing request, and calling an outgoing adaptation unit;

based on the calling adaptation unit in the communication service module, determining calling service corresponding to the calling request according to at least one of the data processing result of the calling request and the calling processing chain identifier, and calling the calling service in the calling service unit, wherein the calling service is used for calling the calling request.

Optionally, based on the communication service interface in the communication service module receiving the outgoing call request, determining an outgoing call processing chain identifier corresponding to the outgoing call request includes:

transmitting the protocol type and the service type of the outgoing request to a processing chain scheduling configuration unit in the communication service module based on the communication service interface;

and determining a corresponding outgoing processing chain identifier according to the protocol type and the service type of the outgoing request based on the processing chain scheduling configuration unit, and feeding back the corresponding outgoing processing chain identifier to the communication service interface, wherein the processing chain scheduling configuration unit is used for configuring the outgoing processing chain identifier corresponding to each protocol type and service type.

Optionally, based on an outgoing protocol processing chain unit in the communication service module, determining an outgoing processing chain according to the outgoing processing chain identifier includes:

transmitting an outgoing processing chain identifier corresponding to the outgoing request to an outgoing processing chain configuration unit in the communication service module based on an outgoing protocol processing chain unit in the communication service module;

and determining a corresponding outgoing processing chain according to the outgoing processing chain identification based on the outgoing processing chain configuration unit, and feeding back the outgoing processing chain to the outgoing protocol processing chain unit, wherein the outgoing processing chain configuration unit is used for configuring each outgoing processing chain identification and the corresponding outgoing processing chain.

Optionally, based on an outgoing call adaptation unit in the communication service module, determining an outgoing call service corresponding to the outgoing call request according to at least one of a data processing result of the outgoing call request and the outgoing call processing chain identifier, including:

transmitting at least one of the data processing result of the outgoing call request and the outgoing call processing chain identifier to an outgoing call communication configuration unit in the communication service module based on an outgoing call adaptation unit in the communication service module;

And determining the outgoing service corresponding to the outgoing request according to at least one of the data processing result and the outgoing processing chain identifier based on an outgoing communication configuration unit in the communication service module, and feeding back to the outgoing adaptation unit, wherein the outgoing communication configuration unit is used for configuring the data processing result and/or the outgoing processing chain identifier corresponding to each outgoing service.

According to the technical scheme, the service logic conversion module is used for generating an outgoing call request of a preset data structure, the communication service module is called, the communication service module is used for intercepting the request between the communication service module and the service logic conversion module, converting the request into the request of the outgoing call data structure, calling the communication service module, and sending the request of the outgoing call data structure to the target ESB. The application system is abutted to a plurality of enterprise service buses, and sharing among different enterprises is further achieved.

Example eight

Fig. 9 is a schematic structural diagram of an electronic device according to an eighth embodiment of the present invention. Fig. 9 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 9 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention. Device 12 is typically an electronic device that assumes the incoming request receiving and processing functions.

As shown in fig. 9, the electronic device 12 is in the form of a general purpose computing device. Components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting the different components, including the memory 28 and the processing unit 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry standard architecture (Industry StandardArchitecture, ISA) bus, micro channel architecture (Micro Channel Architecture, MCA) bus, enhanced ISA bus, video electronics standards association (Video Electronics StandardsAssociation, VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnect, PCI) bus.

Electronic device 12 typically includes a variety of computer-readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 28 may include computer device readable media in the form of volatile memory, such as random access memory (Random Access Memory, RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, storage device 34 may be used to read from or write to a non-removable, non-volatile magnetic media (not shown in FIG. 9, commonly referred to as a "hard disk drive"). Although not shown in fig. 9, a disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from and writing to a removable nonvolatile optical disk (e.g., a Compact Disc-Read Only Memory (CD-ROM), digital versatile Disc (DigitalVideo Disc-Read Only Memory, DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product 40, with program product 40 having a set of program modules 42 configured to perform the functions of embodiments of the present invention. Program product 40 may be stored, for example, in memory 28, such program modules 42 include, but are not limited to, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.

The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, mouse, camera, etc., and display), with one or more devices that enable a user to interact with the electronic device 12, and/or with any device (e.g., network card, modem, etc.) that enables the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks (e.g., local area network (Local Area Network, LAN), wide area network Wide Area Network, WAN) and/or a public network, such as the internet) via the network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk array (Redundant Arrays of Independent Disks, RAID) devices, tape drives, data backup storage devices, and the like.

The processor 16 executes various functional applications and data processing by running a program stored in the memory 28, for example, implementing the request processing method provided by the above-described embodiment of the present invention, including:

Of course, those skilled in the art will understand that the processor may also implement the technical solution of the request processing method provided in any embodiment of the present invention.

Example nine

A ninth embodiment of the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a request processing method as provided in any embodiment of the present invention, the method comprising:

The computer storage media of embodiments of the invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims

1. The application system is characterized by comprising a communication service module, a structure conversion service module and a business logic conversion module; wherein,

the communication service module is used for receiving the incoming call requests of all enterprise service buses, determining the calling technology and the calling protocol of the incoming call requests, carrying out request data processing on the incoming call requests based on the calling technology and the calling protocol of the incoming call requests, and calling the business logic conversion module; the calling technology of the incoming call request is a communication mechanism between the ESB sending the incoming call request and the application system;

the business logic conversion module is used for logically processing the request of the preset data structure;

the communication service module comprises an incoming call protocol processing chain unit;

wherein the incoming call processing chain includes processor information and a calling sequence of the processor;

wherein, the communication service module also comprises an outgoing protocol processing chain unit;

the calling protocol processing chain unit is used for determining a calling processing chain according to the calling processing chain identification, sequentially calling a corresponding processor according to the calling processing chain, carrying out data processing on a calling request and calling a calling adaptation unit;

The structure conversion service module comprises a structure conversion interception inlet, an object conversion unit and a calling service unit;

the object conversion unit is used for carrying out structural conversion according to the source object and the target service object name of the request; wherein the object conversion unit comprises a reflection caller and a converter; the reflection caller determines a converter for carrying out structural conversion according to the source object and the target service object name in a reflection mode; the converter is used for carrying out structural transformation on the source object to obtain a target object;

the call service unit is used for calling the target service after the structure conversion is completed;

the object conversion unit comprises an expansion interface, wherein the expansion interface is used for accessing a newly added converter;

the communication service module also comprises an incoming call service unit, a request scheduling unit and a service logic scheduling unit;

the service logic scheduling unit is used for determining service logic according to the data processing result of the incoming call request and calling the service logic, and the service logic is used for logically processing the data processing result;

the communication service module also comprises a service logic scheduling configuration unit, wherein the service logic scheduling configuration unit is used for configuring service logic information corresponding to various data processing results;

2. The application system according to claim 1, wherein the communication service module further includes a request scheduling configuration unit, the request scheduling configuration unit is configured to configure an incoming processing chain identifier of each protocol type;

3. The application system according to claim 1, wherein the communication service module further includes an incoming call processing chain configuration unit, and the incoming call processing chain configuration unit is configured to configure an incoming call processing chain corresponding to each incoming call processing chain identifier;

4. The application system of claim 1, wherein the application system comprises a plurality of processors,

5. The application system of claim 4, wherein the communication service module further comprises a communication service interface, an outgoing call adaptation unit, and an outgoing call service unit, wherein the outgoing call service unit comprises outgoing call services of each protocol type;

the communication service interface receives an outgoing call request, determines an outgoing call processing chain identifier corresponding to the outgoing call request, and invokes an outgoing call protocol processing chain unit;

6. The application system according to claim 5, wherein the communication service module further comprises a processing chain scheduling configuration unit, configured to configure outgoing processing chain identifiers corresponding to each protocol type and service type;

7. The application system according to claim 5, wherein the communication service module further comprises an outgoing processing chain configuration unit for configuring each outgoing processing chain identifier and a corresponding outgoing processing chain;

8. The application system according to claim 5, wherein the communication service module further comprises an outgoing communication configuration unit, configured to configure a data processing result and/or an outgoing processing chain identifier corresponding to each outgoing service;

9. The application system according to claim 5, wherein the outgoing service unit and the incoming service unit are provided with extension interfaces, respectively, for accessing a newly added outgoing service and a newly added incoming service, respectively.

10. A method of processing a request, comprising:

receiving an incoming call request of each enterprise service bus based on a communication service module, determining a calling technology and a calling protocol of the incoming call request, performing request data processing on the incoming call request based on the calling technology and the calling protocol of the incoming call request, and calling a service logic conversion module; the calling technology of the incoming call request is a communication mechanism between the ESB sending the incoming call request and an application system; the application system comprises the communication service module, a structure conversion service module and the business logic conversion module;

based on the structure conversion service module, intercepting a request between the communication service module and the service logic conversion module, performing structure conversion on the intercepted and processed incoming call request to obtain a request with a preset data structure, and calling the service logic conversion module;

Carrying out logic processing on the request of the preset data structure based on the service logic conversion module;

the communication service module receives an incoming call request of each enterprise service bus, determines a calling technology and a calling protocol of the incoming call request, processes request data of the incoming call request based on the calling technology and the calling protocol of the incoming call request, and calls a service logic conversion module, and the communication service bus comprises:

determining service logic according to a data processing result of an incoming call request based on a service logic scheduling unit, calling the service logic, and performing logic processing on the data processing result according to the service logic;

Wherein the incoming call processing chain includes the processor information and a calling order of the processors;

the service module based on structure conversion intercepts the request between the communication service module and the service logic conversion module, and performs structure conversion on the intercepted incoming call request after processing to obtain a request with a preset data structure, and invokes the service logic conversion module, and the service logic conversion module comprises:

based on a calling service unit in the structure conversion service module, calling a target service after the structure conversion is completed;

the service logic based scheduling unit determines service logic according to the data processing result of the incoming call request, and comprises the following steps:

Based on the service logic scheduling configuration unit, corresponding service logic information is determined according to the data processing result and fed back to the service logic scheduling unit, wherein the service logic scheduling configuration unit is used for configuring the service logic information corresponding to various types of data processing results;

the object conversion unit in the structure conversion service module performs structure conversion according to the source object and the target service object name of the request, and includes:

11. A method of processing a request, comprising:

Transmitting the outgoing request to a target enterprise service bus based on the communication service module;

wherein the sending the outgoing request to the target enterprise service bus based on the communication service module includes:

based on an outgoing protocol processing chain unit in the communication service module, determining an outgoing processing chain according to an outgoing processing chain identifier, sequentially calling a corresponding processor according to the outgoing processing chain, performing data processing on the outgoing request, and calling an outgoing adaptation unit;

the structure conversion service module intercepts a request between the communication service module and the business logic conversion module, performs structure conversion on the intercepted outgoing request according to the request type of the outgoing request to obtain a request of an outgoing data structure, and invokes the communication service module, and the method comprises the following steps:

12. An electronic device, the electronic device comprising:

one or more processors;

storage means for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the request processing method of claim 10.

13. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the request processing method as claimed in claim 10.