CN105656947A - Method, device and system for interaction between transaction middleware and third-party system - Google Patents
Method, device and system for interaction between transaction middleware and third-party system Download PDFInfo
- Publication number
- CN105656947A CN105656947A CN201610190313.7A CN201610190313A CN105656947A CN 105656947 A CN105656947 A CN 105656947A CN 201610190313 A CN201610190313 A CN 201610190313A CN 105656947 A CN105656947 A CN 105656947A
- Authority
- CN
- China
- Prior art keywords
- communication protocol
- party system
- transaction middleware
- protocol conversion
- service request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
Abstract
The invention applies to the technical field of middleware, provides a method, device and system for interaction between transaction middleware and a third-party system and is intended to solve the problems that adapting conversion protocols to each type of third-party systems one by one in the prior art leads to low multiplex ratio and long development and maintenance cycle. The method comprises: by a factory component, calling an adapter plugin to carry out first communication protocol conversion on a service request, transmitting the service request converted by the first communication protocol conversion to the third-party system, and using the adapter plugin to carry out second communication protocol conversion on a response message returned by the third-party system. In the technical scheme of the invention, interaction between the transaction middleware and the third-party system is implemented based on the factory component and adapter plugin frame, the factory component performs the communication protocol conversion centrally, the different adapter plugins math with different third-party systems, and therefore, it is possible to quickly complete the interaction and flexible docking of the transaction middleware with the third-party systems, reduce the development and maintenance cost and increase the multiplex ratio.
Description
Technical field
The present invention relates to middleware Technology field, particularly relate to the methods, devices and systems that a kind of transaction middleware is mutual with Third party system.
Background technology
Middleware is a kind of independent systems soft ware and service routine, and Distributed Application software shares resource by this software between different technology. Middleware is positioned on the operating system of client/server, manages computer resource and network communication, is the software connecting two stand-alone utilities or autonomous system. The system being connected, even if they have different interfaces, but remains to exchange information each other by middleware. By middleware, application program may operate in multi-platform or OS environment middleware and operating system, data base are listed as three big basic software platforms.
At present, middleware has included numerous branches such as communication middleware, transaction middleware, object middleware, Security Middleware, data access middleware.
Transaction middleware is an important branch of middleware, is used primarily in online transaction processing system (On-LineTransactionProcessing, OLTP). Along with developing rapidly of computer application level, improving constantly of information level of the enterprise, being continuously increased of corporate client, and the continuous appearance of new business, increasing computer application system to concurrent processing, key business on-line transaction process, cross-platform, have higher requirement across the aspect such as wide area network and multi-data source, in order to solve these actual demands, be born the application model of framework based on transaction middleware, and this framework is referred to as three-decker. The key concept of three-decker is to utilize transaction middleware that user interface, service logic and data are logically divided into three different process layers. Three-decker system based on transaction middleware, not only possesses the system stability of large scale computer, safety, advantage that disposal ability is high, also has the advantages such as open system cost is low, extensibility is strong, the construction cycle is short, easy care simultaneously.
Transaction middleware, as a middle layer software, also has the function accessing Third party system as center-aisle. Third party system can be the system of isomorphism or isomery, and isomorphism system refers to the system of the communication protocol identical with the use of this middleware and service protocol, and heterogeneous system refers to adopt the system of different communication protocol and service protocol from this middleware. Expansion along with transaction middleware service application scale, transaction middleware to dock and also to get more and more with mutual Third party system, how efficiently quickly and other Third party system, particularly heterogeneous system interacts and docks, and becomes the important indicator weighing a transaction middleware functional expansionary.
Existing transaction middleware docks and mutual with Third party system, the mode of adaptation is changed in usual employing one by one, namely by writing transcode, this transaction middleware internal agreement is converted directly into Third party system agreement, this conversion is integrated in transaction middleware inside or provides in plug-in unit mode, for every kind of Third party system, is required for separately encoded and conversion process, relatively complicated, cause that reusability is low, develop and maintenance period is long.
Summary of the invention
It is an object of the invention to provide the methods, devices and systems that a kind of transaction middleware is mutual with Third party system, aim to solve the problem that the reusability that in prior art, adaptive translation-protocol causes one by one to every kind of Third party system is not high, the problem that the development and maintenance cycle is longer.
A first aspect of the present invention, it is provided that a kind of method that transaction middleware is mutual with Third party system, including:
The service request of client is sent to factory component by transaction middleware, and described service request is the interaction request of described client and Third party system;
Described factory component is called adapter card and described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described response message is carried out second time communication Protocol Conversion by described adapter card, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described response message is returned to described transaction middleware by described factory component;
Described response message is returned to described client by described transaction middleware.
A second aspect of the present invention, it is provided that the system that a kind of transaction middleware is mutual with Third party system, including transaction middleware, factory component and adapter card,
Described transaction middleware, for the service request of client is sent to described factory component, described service request is the interaction request of described client and Third party system;
Described factory component, for calling described adapter card, described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to described Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described adapter card, for described response message being carried out second time communication Protocol Conversion, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described factory component, is additionally operable to described response message is returned to described transaction middleware;
Described transaction middleware, is additionally operable to described response message is returned to described client.
A third aspect of the present invention, it is provided that the device that a kind of transaction middleware is mutual with Third party system, including:
First package module, for being packaged interface mutual to described transaction middleware and described Third party system;
Second package module, for being packaged the interface being used for adapter card exploitation;
Described transaction middleware, for the service request of client is sent to factory component, described service request is the interaction request of described client and described Third party system;
Described factory component, for calling adapter card, described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to described Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described adapter card, for described response message being carried out second time communication Protocol Conversion, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described factory component, is additionally operable to described response message is returned to described transaction middleware;
Described transaction middleware, is additionally operable to described response message is returned to described client.
The present invention compared with prior art exists and provides the benefit that: realize the mutual of transaction middleware and Third party system based on factory component and adapter card framework, it is uniformly carried out communication Protocol Conversion by factory component, by the Third party system that different adapter card couplings is different, the adapter card corresponding with this Third party system only need to be loaded when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed, simultaneously because adopt general Development Framework, when transaction middleware needs to dock new Third party system, have only to the interface according to communication Protocol Conversion and complete the exploitation of adapter card, and it is integrated in unified framework, thus realizing the interface flexibility of transaction middleware and Third party system, and make development and maintenance cost reduce, reusability improves.
Accompanying drawing explanation
Fig. 1 is the flow chart of the mutual method of transaction middleware and Third party system that the embodiment of the present invention one provides;
Fig. 2 is the flow chart of the mutual method of transaction middleware and Third party system that the embodiment of the present invention two provides;
Fig. 3 is the structural representation of transaction middleware that the embodiment of the present invention three and embodiment four the provide system mutual with Third party system;
Fig. 4 is the structural representation of the mutual device of transaction middleware and Third party system that the embodiment of the present invention five provides.
Detailed description of the invention
In order to make the purpose of the present invention, technical scheme and advantage clearly understand, below in conjunction with drawings and Examples, the present invention is further elaborated. Should be appreciated that specific embodiment described herein is only in order to explain the present invention, is not intended to limit the present invention.
Below in conjunction with concrete accompanying drawing, the realization of the present invention is described in detail.
Embodiment one:
Fig. 1 is the flow chart of the mutual method of transaction middleware and Third party system that the embodiment of the present invention one provides, specifically includes step S101 to step S105, and details are as follows:
The service request of client is sent to factory component by S101, transaction middleware, and this service request is the interaction request of client and Third party system.
Specifically, client is by calling the service logic interface that transaction middleware provides, according to the service request that the definition of concrete application demand is mutual with Third party system, make transaction middleware can pass through XA interface specification, call xa_write interface and this service request is sent to factory (Factory) assembly.
XA is the interface specification that the X/Open Distributed Transaction organized to set up processes in (DistributedTransactionProcess, DTP) model between transaction middleware and data base. X/OpenDTP model is a kind of Distributed Transaction Processing, including application program (AP, Application), task manager (TM, TransactionManager) and explorer (RM, ResourceManager). Generally, task manager (TM) is transaction middleware, and explorer (RM) is data base, and transaction middleware comes the beginning of notification database affairs, end, submission and rollback etc. by XA.
It should be noted that, XA interface specification in the present embodiment is the specification of transaction middleware operating resource manager (RM), the method it defining a set of operating resource manager, in the XA standard base of compatible X/OpenDTP model, it has been carried out extension and abstract again, compatible thread and process method of calling simultaneously, and single transaction middleware node can connect multiple resource, the operation of multiple resources can be integrated in a transaction server and complete, improve the treatment effeciency of complication system.
S102, factory component are called adapter card and service request are carried out first time communication Protocol Conversion, and the service request after first time communication Protocol Conversion is sent to Third party system, service request is processed by Third party system, and the response message after processing is returned to adapter card, first time communication Protocol Conversion includes the communication Protocol Conversion within transaction middleware being the communication protocol of Third party system.
When docking Third party system, owing to the communication protocol of transaction middleware and the communication protocol of Third party system would be likely to occur difference, it is therefore desirable to communication protocol is changed. In the present embodiment, it is the communication protocol of Third party system by factory component by the communication Protocol Conversion within transaction middleware.
Specifically, the SendRequeest interface that factory component provides by calling adapter card completes the first time communication Protocol Conversion to service request, communication protocol according to Third party system, it is the communication protocol of Third party system by the communication Protocol Conversion within transaction middleware, and the service request after completing first time communication Protocol Conversion is sent to Third party system, response message is returned to adapter card after the service request received is processed by Third party system.
Adapter card provides and communicates the interface that agreement is changed mutually between transaction middleware and Third party system, for each Third party system, all has an adapter card corresponding with it.
Factory component can exist in the way of dynamic base, and adapter card can also be a dynamic base, factory component load, it is achieved with the Seamless integration-of transaction middleware. Transaction middleware is when docking a new Third party system, it is only necessary to load the adapter card corresponding with this Third party system, can realize the interface flexibility with Third party system and quickly mutual. And according to the method that prior art provides, when transaction middleware needs a kind of new Third party system of docking, need to customize the code of complete set for this Third party system, not only the construction cycle is long, and reusability is low, it is impossible to realize the rapid abutting joint of transaction middleware and Third party system and mutual.
Response message is carried out second time communication Protocol Conversion by S103, adapter card, and the response message after second time communication Protocol Conversion is returned to factory component, second time communication Protocol Conversion includes the communication Protocol Conversion of Third party system being the communication protocol within transaction middleware.
Specifically, the response message that adapter card is returned by GetReply interface Third party system, this response message is carried out second time communication Protocol Conversion, namely, by the communication protocol that the communication Protocol Conversion of Third party system is within transaction middleware, and the response message after completing second time communication Protocol Conversion is returned to factory component.
Response message is returned to transaction middleware by S104, factory component.
Response message is returned to client by S105, transaction middleware.
In the present embodiment, based on the method that the transaction middleware of factory component and adapter card framework interacts with Third party system, it is uniformly carried out communication Protocol Conversion by factory component, by the Third party system that different adapter card couplings is different, only need to load the adapter card corresponding with this Third party system when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed.
Embodiment two:
Fig. 2 is the flow chart of the mutual method of transaction middleware and Third party system that the embodiment of the present invention two provides, specifically includes step S201 to step S208, and details are as follows:
S201, transaction middleware load the adapter card of factory component and correspondence according to configuration information.
Specifically, transaction middleware is when starting, and the configuration information of Third party system mutual with transaction middleware as required loads factory component and corresponding adapter card.
The service request of client is sent to factory component by S202, transaction middleware, and this service request is the interaction request of client and Third party system.
Service request is carried out service protocol conversion by S203, factory component, and service protocol is converted to the conversion between transaction middleware and Third party system, same field named.
Service protocol conversion refers between different system, namely the conversion between transaction middleware and the Third party system of the present embodiment, same field named, such as same password field, system A called after password, system B called after PWD, in order to make can to carry out between system A and system B normally alternately, it is necessary to the conversion this password field being named when cross-system.
Specifically, the factory component service request to receiving carries out service protocol conversion, the conversion of this service protocol can be realized by the mode of configuration service protocol conversion rule file, the concrete form of service protocol transformational rule file can be determined according to actual needs, for instance can be the file of XML format.Service protocol transformational rule document definition needs the conversion map relation of the field of conversion, and factory component obtains the conversion map relation of field by resolving this document, and according to this conversion map relation, the field name of service request is changed automatically.
S204, factory component are called adapter card and service request are carried out first time communication Protocol Conversion, and the service request after first time communication Protocol Conversion is sent to Third party system, service request is processed by Third party system, and the response message after processing is returned to adapter card, first time communication Protocol Conversion includes the communication Protocol Conversion within transaction middleware being the communication protocol of Third party system.
Response message is carried out second time communication Protocol Conversion by S205, adapter card, and the response message after second time communication Protocol Conversion is returned to factory component, second time communication Protocol Conversion includes the communication Protocol Conversion of Third party system being the communication protocol within transaction middleware.
Response message is carried out service protocol conversion by S206, factory component.
Specifically, factory component obtains the conversion map relation of field by resolving this document, and according to this conversion map relation, the field name of response message is changed automatically.
Response message is returned to transaction middleware by S207, factory component.
Response message is returned to client by S208, transaction middleware.
In the present embodiment, step S202, step S204, step S205, step S207 are identical with the step S101 of accompanying drawing 1 example, step S102, step S103, step S104 and step S105 respectively with step S208, its relational language related to, concept or technical characteristic etc. are identical with the relational language that step S101, step S102, step S103, step S104 and step S105 relate to, concept or technical characteristic etc., do not repeat herein.
In the present embodiment, based on the method that the transaction middleware of factory component and adapter card framework interacts with Third party system, communication Protocol Conversion and service protocol conversion it is uniformly carried out by factory component, by the Third party system that different adapter card couplings is different, only need to load the adapter card corresponding with this Third party system when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed.
Embodiment three:
Fig. 3 is the structural representation of transaction middleware that the embodiment of the present invention three and embodiment four the provide system mutual with Third party system, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention. The mutual system of the transaction middleware of Fig. 3 example and Third party system can be the executive agent of transaction middleware that previous embodiment one the provides method mutual with Third party system. The mutual system of the transaction middleware of Fig. 3 example and Third party system specifically includes that transaction middleware 31, factory component 32 and adapter card 33. Each functional module describes in detail as follows:
Transaction middleware 31, for the service request of client is sent to factory component 32, this service request is the interaction request of client and Third party system;
Factory component 32, for calling adapter card 33, service request is carried out first time communication Protocol Conversion, and the service request after first time communication Protocol Conversion is sent to Third party system, service request is processed by Third party system, and the response message after processing is returned to adapter card 33, first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is Third party system within transaction middleware 31;
Adapter card 33, for response message being carried out second time communication Protocol Conversion, and the response message after second time communication Protocol Conversion is returned to factory component 32, second time communication Protocol Conversion includes the communication Protocol Conversion of Third party system being the communication protocol within transaction middleware 31;
Factory component 32, is additionally operable to return to response message transaction middleware 31;
Transaction middleware 31, is additionally operable to response message is returned to client.
In the system that the transaction middleware that the present embodiment provides is mutual with Third party system, each module realizes the process of respective function, is specifically referred to the description of aforementioned embodiment illustrated in fig. 1, repeats no more herein.
From the system that the transaction middleware of above-mentioned Fig. 3 example and Third party system are mutual, in the present embodiment, based on the system that the transaction middleware of factory component and adapter card framework interacts with Third party system, it is uniformly carried out communication Protocol Conversion by factory component, by the Third party system that different adapter card couplings is different, only need to load the adapter card corresponding with this Third party system when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed.
Embodiment four:
Please continue to refer to Fig. 3, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention. The mutual system of the transaction middleware of Fig. 3 example and Third party system can be the executive agent of transaction middleware that previous embodiment two the provides method mutual with Third party system. With embodiment three the difference is that, further, in the present embodiment:
Transaction middleware 31, for the service request of client is sent to factory component 32, this service request is the interaction request of client and Third party system;
Factory component 32, for calling adapter card 33, service request is carried out first time communication Protocol Conversion, and the service request after first time communication Protocol Conversion is sent to Third party system, service request is processed by Third party system, and the response message after processing is returned to adapter card 33, first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is Third party system within transaction middleware 31;
Adapter card 33, for response message being carried out second time communication Protocol Conversion, and the response message after second time communication Protocol Conversion is returned to factory component 32, second time communication Protocol Conversion includes the communication Protocol Conversion of Third party system being the communication protocol within transaction middleware 31;
Factory component 32, is additionally operable to return to response message transaction middleware 31;
Transaction middleware 31, is additionally operable to response message is returned to client.
Further, transaction middleware 31, it is additionally operable to load factory component 32 and corresponding adapter card 33 according to configuration information.
Further, factory component 32, it is additionally operable to service request is carried out service protocol conversion, this service protocol is converted to the conversion between transaction middleware 31 and Third party system, same field named.
Further, factory component 32, it is additionally operable to response message is carried out service protocol conversion.
In the system that the transaction middleware that the present embodiment provides is mutual with Third party system, each module realizes the process of respective function, is specifically referred to the description of aforementioned embodiment illustrated in fig. 2, repeats no more herein.
From the system that the transaction middleware of above-mentioned Fig. 3 example and Third party system are mutual, in the present embodiment, based on the system that the transaction middleware of factory component and adapter card framework interacts with Third party system, communication Protocol Conversion and service protocol conversion it is uniformly carried out by factory component, by the Third party system that different adapter card couplings is different, only need to load the adapter card corresponding with this Third party system when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed.
Embodiment five:
Fig. 4 is the structural representation of the mutual device of transaction middleware and Third party system that the embodiment of the present invention five provides, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention. The mutual device of the transaction middleware of Fig. 4 example and Third party system can be the transaction middleware a kind of Development Framework mutual with Third party system or platform.
The mutual device of the transaction middleware of Fig. 4 example and Third party system includes the first package module 401 and the second package module 402, wherein,
First package module 401, for being packaged interface mutual to transaction middleware and Third party system;
Second package module 402, for being packaged the interface being used for adapter card exploitation.
In the device that the transaction middleware of Fig. 4 example is mutual with Third party system, interface mutual to transaction middleware and Third party system has been encapsulated by the first package module 401, make can be uniformly coordinated when transaction middleware and Third party system docking to call these interfaces, formed and be connected when docking with Third party system, initialize, send request, receive response, close the invocation framenort of these operations such as connection, and the interface being used for adapter card exploitation has been encapsulated by the second package module 402, namely, provide the transaction middleware interface prototype mutual with Third party system and the interface prototype for adapter card exploitation, when transaction middleware needs a kind of new Third party system of docking, developer has only to the specification according to adapter card development interface, pay close attention to the protocol conversion between transaction middleware and Third party system, an adapter card corresponding with this Third party system can be gone out by fast Development, the adapter card so developed can be a dynamic base, when transaction middleware needs to dock with Third party system, can be loaded by this dynamic base of factory component, realize the Seamless integration-of this adapter card and transaction middleware, such that it is able to realize the rapid abutting joint of transaction middleware and Third party system neatly and mutual. and according to the method for prior art, when transaction middleware needs a kind of new Third party system of docking, it is necessary to customize the code of complete set for this Third party system, not only the construction cycle is long, and reusability is low, it is impossible to realize the rapid abutting joint of transaction middleware and Third party system and mutual.
Further, the transaction middleware interface mutual with Third party system includes initializing and be connected interface, closes and disconnect interface, sends request interface and receive response interface, includes communication Protocol Conversion interface for the interface of adapter card exploitation, sets up and be connected interface with Third party system and disconnection is connected interface with Third party system.
Specifically, the interface that transaction middleware is mutual with Third party system specifically can be defined as:
Initialize and connect interface:
Int (* xa_open_entry) ();
Close and disconnect interface:
Int (* xa_close_entry) ();
Send request interface:
Int (* xa_write_entry) (void*handle, char*str, intlen);
Receive response interface:
int(*xa_read_entry)(void*handle,char**str,int*len)��
Specifically, the interface for adapter card exploitation specifically can be defined as:
Communication Protocol Conversion interface by the communication Protocol Conversion within transaction middleware is Third party system communication protocol:
SendRequest ();
Communication Protocol Conversion interface by the communication Protocol Conversion of Third party system communication protocol is within transaction middleware:
GetReply ();
Set up and be connected interface with Third party system:
Open ();
Disconnect and be connected interface with Third party system:
Close()��
In the device that the transaction middleware of Fig. 4 example is mutual with Third party system, the major function of transaction middleware, factory component and adapter card describes in detail as follows:
Transaction middleware, for receiving the service request that client sends, and is sent to factory component by service request, and this service request is the interaction request of client and Third party system;
Factory component, for calling adapter card, service request is carried out first time communication Protocol Conversion, and the service request after first time communication Protocol Conversion is sent to Third party system, service request is processed by Third party system, and the response message after processing is returned to adapter card, first time communication Protocol Conversion includes the communication Protocol Conversion within transaction middleware being the communication protocol of Third party system;
Adapter card, for response message being carried out second time communication Protocol Conversion, and the response message after second time communication Protocol Conversion is returned to factory component, second time communication Protocol Conversion includes the communication Protocol Conversion of Third party system being the communication protocol within transaction middleware;
Factory component, is additionally operable to response message is returned to transaction middleware;
Transaction middleware, is additionally operable to response message is returned to client.
In the device that the transaction middleware that the present embodiment provides is mutual with Third party system, transaction middleware, factory component and adapter card realize the process of respective function, are specifically referred to the description of aforementioned embodiment illustrated in fig. 1, repeat no more herein.
From the device that the transaction middleware of above-mentioned Fig. 4 example and Third party system are mutual, in the present embodiment, based on the device that the transaction middleware of factory component and adapter card framework interacts with Third party system, it is uniformly carried out communication Protocol Conversion by factory component, by the Third party system that different adapter card couplings is different, the adapter card corresponding with this Third party system only need to be loaded when transaction middleware needs docking Third party system, the mutual of transaction middleware and Third party system can be rapidly completed, simultaneously because adopt general Development Framework, when transaction middleware needs to dock new Third party system, have only to the interface according to communication Protocol Conversion and complete the exploitation of adapter card, and it is integrated in unified framework, thus realizing the interface flexibility of transaction middleware and Third party system, and make development and maintenance cost reduce, reusability improves.
It should be noted that each embodiment in this specification all adopts the mode gone forward one by one to describe, what each embodiment stressed is the difference with other embodiments, part same or like between each embodiment mutually referring to. For device class embodiment, due to itself and embodiment of the method basic simlarity, so what describe is fairly simple, relevant part illustrates referring to the part of embodiment of the method.
It should be noted that in said apparatus embodiment, included modules is carry out dividing according to function logic, but is not limited to above-mentioned division, as long as being capable of corresponding function; It addition, the concrete title of each functional module is also only to facilitate mutually distinguish, it is not limited to protection scope of the present invention.
One of ordinary skill in the art will appreciate that, realize all or part of step in the various embodiments described above method to can be by the hardware that program carrys out instruction relevant and complete, corresponding program can be stored in a computer read/write memory medium, described storage medium, such as ROM/RAM, disk or CD etc.
The foregoing is only presently preferred embodiments of the present invention, not in order to limit the present invention, all any amendment, equivalent replacement and improvement etc. made within the spirit and principles in the present invention, should be included within protection scope of the present invention.
Claims (10)
1. the method that a transaction middleware is mutual with Third party system, it is characterised in that including:
The service request of client is sent to factory component by transaction middleware, and described service request is the interaction request of described client and Third party system;
Described factory component is called adapter card and described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described response message is carried out second time communication Protocol Conversion by described adapter card, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described response message is returned to described transaction middleware by described factory component;
Described response message is returned to described client by described transaction middleware.
2. the method that transaction middleware according to claim 1 is mutual with Third party system, it is characterised in that before the service request of client is sent to factory component by described transaction middleware, described method also includes:
Described transaction middleware loads factory component and corresponding adapter card according to configuration information.
3. the method that transaction middleware according to claim 1 and 2 and Third party system are mutual, it is characterised in that described factory component is called before described service request carries out first time communication Protocol Conversion by adapter card, and described method also includes:
Described service request is carried out service protocol conversion by described factory component, and described service protocol is converted to the conversion between described transaction middleware and described Third party system, same field named.
4. the method that transaction middleware according to claim 3 is mutual with Third party system, it is characterised in that described response message is returned to before described transaction middleware by described factory component, and described method also includes:
Described response message is carried out described service protocol conversion by described factory component.
5. the system that a transaction middleware is mutual with Third party system, it is characterised in that described system includes transaction middleware, factory component and adapter card,
Described transaction middleware, for the service request of client is sent to described factory component, described service request is the interaction request of described client and Third party system;
Described factory component, for calling described adapter card, described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to described Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described adapter card, for described response message being carried out second time communication Protocol Conversion, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described factory component, is additionally operable to described response message is returned to described transaction middleware;
Described transaction middleware, is additionally operable to described response message is returned to described client.
6. the system that transaction middleware according to claim 5 is mutual with Third party system, it is characterised in that described transaction middleware, is additionally operable to load factory component and corresponding adapter card according to configuration information.
7. the system that the transaction middleware according to claim 5 or 6 is mutual with Third party system, it is characterized in that, described factory component, being additionally operable to described service request is carried out service protocol conversion, described service protocol is converted to the conversion between described transaction middleware and described Third party system, same field named.
8. the system that transaction middleware according to claim 7 is mutual with Third party system, it is characterised in that described factory component, is additionally operable to described response message is carried out described service protocol conversion.
9. the device that a transaction middleware is mutual with Third party system, it is characterised in that described device includes:
First package module, for being packaged interface mutual to described transaction middleware and described Third party system;
Second package module, for being packaged the interface being used for adapter card exploitation;
Described transaction middleware, for the service request of client is sent to factory component, described service request is the interaction request of described client and described Third party system;
Described factory component, for calling adapter card, described service request is carried out first time communication Protocol Conversion, and the described service request after described first time communication Protocol Conversion is sent to described Third party system, described service request is processed by described Third party system, and the response message after processing is returned to described adapter card, described first time communication Protocol Conversion includes the communication protocol that communication Protocol Conversion is described Third party system within described transaction middleware;
Described adapter card, for described response message being carried out second time communication Protocol Conversion, and the described response message after described second time communication Protocol Conversion is returned to described factory component, it is the communication protocol within described transaction middleware that described second time communication Protocol Conversion includes the communication Protocol Conversion of described Third party system;
Described factory component, is additionally operable to described response message is returned to described transaction middleware;
Described transaction middleware, is additionally operable to described response message is returned to described client.
10. the device that transaction middleware according to claim 9 is mutual with Third party system, it is characterized in that, the described transaction middleware interface mutual with described Third party system includes initializing and being connected interface, closing and disconnect interface, send request interface and receive response interface, and the described interface for adapter card exploitation includes first time communication Protocol Conversion interface, second time communication Protocol Conversion interface, set up Third party system connects interface and disconnects Third party system connection interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610190313.7A CN105656947B (en) | 2016-03-30 | 2016-03-30 | A kind of methods, devices and systems that transaction middleware is interacted with third party system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610190313.7A CN105656947B (en) | 2016-03-30 | 2016-03-30 | A kind of methods, devices and systems that transaction middleware is interacted with third party system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105656947A true CN105656947A (en) | 2016-06-08 |
| CN105656947B CN105656947B (en) | 2019-02-01 |
Family
ID=56496526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610190313.7A Active CN105656947B (en) | 2016-03-30 | 2016-03-30 | A kind of methods, devices and systems that transaction middleware is interacted with third party system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105656947B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107677301A (en) * | 2017-10-10 | 2018-02-09 | 四川国信慧通电气技术有限公司 | Monitoring device detection method and device |
| CN109885334A (en) * | 2018-12-30 | 2019-06-14 | 贝壳技术有限公司 | Connection component, message sending, receiving method and edition compatibility system |
| CN111124813A (en) * | 2019-12-04 | 2020-05-08 | 山东浪潮人工智能研究院有限公司 | Monitoring management system based on autonomous controllable software and hardware |
| CN112764995A (en) * | 2021-01-26 | 2021-05-07 | 山东云海国创云计算装备产业创新中心有限公司 | Server hardware resource monitoring method, device and medium |
| CN113556392A (en) * | 2021-07-19 | 2021-10-26 | 广州市百果园网络科技有限公司 | Communication system, method, device and storage medium |
| CN113760577A (en) * | 2021-08-04 | 2021-12-07 | 广东能龙教育股份有限公司 | Dynamic connection answering device, processing method, control device and storage medium |
| CN113760577B (en) * | 2021-08-04 | 2024-04-19 | 广东能龙教育股份有限公司 | Dynamic connection answering device, processing method, control device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101488192A (en) * | 2009-02-24 | 2009-07-22 | 诚迈科技（南京）有限公司 | Large-scale network deployment collocation method model of RFID reading device |
| CN102025727A (en) * | 2010-11-23 | 2011-04-20 | 广州市轩辕网络科技有限公司 | Integrated pushing system and method for collecting and accessing multiple application systems |
| CN104601522A (en) * | 2013-10-30 | 2015-05-06 | 中国移动通信集团北京有限公司 | Method, device and system for realizing interaction between mobile client and service system |
-
2016
- 2016-03-30 CN CN201610190313.7A patent/CN105656947B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101488192A (en) * | 2009-02-24 | 2009-07-22 | 诚迈科技（南京）有限公司 | Large-scale network deployment collocation method model of RFID reading device |
| CN102025727A (en) * | 2010-11-23 | 2011-04-20 | 广州市轩辕网络科技有限公司 | Integrated pushing system and method for collecting and accessing multiple application systems |
| CN104601522A (en) * | 2013-10-30 | 2015-05-06 | 中国移动通信集团北京有限公司 | Method, device and system for realizing interaction between mobile client and service system |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107677301A (en) * | 2017-10-10 | 2018-02-09 | 四川国信慧通电气技术有限公司 | Monitoring device detection method and device |
| CN109885334A (en) * | 2018-12-30 | 2019-06-14 | 贝壳技术有限公司 | Connection component, message sending, receiving method and edition compatibility system |
| CN109885334B (en) * | 2018-12-30 | 2022-10-04 | 贝壳技术有限公司 | Version compatible system and message sending and receiving method |
| CN111124813A (en) * | 2019-12-04 | 2020-05-08 | 山东浪潮人工智能研究院有限公司 | Monitoring management system based on autonomous controllable software and hardware |
| CN112764995A (en) * | 2021-01-26 | 2021-05-07 | 山东云海国创云计算装备产业创新中心有限公司 | Server hardware resource monitoring method, device and medium |
| CN112764995B (en) * | 2021-01-26 | 2023-04-07 | 山东云海国创云计算装备产业创新中心有限公司 | Server hardware resource monitoring method, device and medium |
| CN113556392A (en) * | 2021-07-19 | 2021-10-26 | 广州市百果园网络科技有限公司 | Communication system, method, device and storage medium |
| CN113556392B (en) * | 2021-07-19 | 2023-11-14 | 广州市百果园网络科技有限公司 | Communication system, method, apparatus and storage medium |
| CN113760577A (en) * | 2021-08-04 | 2021-12-07 | 广东能龙教育股份有限公司 | Dynamic connection answering device, processing method, control device and storage medium |
| CN113760577B (en) * | 2021-08-04 | 2024-04-19 | 广东能龙教育股份有限公司 | Dynamic connection answering device, processing method, control device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105656947B (en) | 2019-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105656947A (en) | Method, device and system for interaction between transaction middleware and third-party system | |
| AU686105B2 (en) | System for implementation-independent interface specification | |
| CN100483352C (en) | IDE calling device and calling method therefor | |
| CN107147704A (en) | A kind of generic service middleware system towards block chain | |
| CN108512748A (en) | A kind of implementation method of micro services gateway | |
| CN103905426A (en) | Method and apparatus for securing and segregating host to host messaging on pcie fabric | |
| CN100583043C (en) | System and method for providing shared web modules | |
| CN103729450A (en) | Function authority centralized management method and device | |
| CN105893055A (en) | Method for triggering process engine platformization | |
| CN107222363B (en) | Storage protocol consistency test method and system | |
| US20100057863A1 (en) | Composing message processing pipelines | |
| US20130340027A1 (en) | Provisioning Managed Devices with States of Arbitrary Type | |
| CN109783132B (en) | Method and device for realizing system singleization and distribution | |
| CN104219284A (en) | Server designing method based on semi-synchronization, semi-synchronization and pipe filter mode | |
| CN102479076A (en) | Method and device for recording audit log, and service system | |
| CN103684904A (en) | Tri-networks integration network monitoring system based on IP | |
| CN103995736A (en) | Method and device for transmitting shared memory | |
| JP2024501727A (en) | Multi-adapter compatible library file modules, calling methods, calling systems and devices | |
| CN114024822A (en) | Block chain-based Internet of things equipment management method, equipment, server and medium | |
| KR101660028B1 (en) | Method and apparatus for creating bridging component between hla-dds | |
| CN104702568A (en) | Service management platform | |
| CN105824712A (en) | Method and device for executing business logic | |
| CN113434118A (en) | Layered architecture system of concentrator based on Java platform | |
| CN116301759B (en) | Mobile component sharing method, system, equipment and storage medium | |
| Wedpathak | An Approach of Software Engineering through Middleware |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |