CN102364921A - Realization method and equipment for enterprise service bus and corresponding platform - Google Patents
Realization method and equipment for enterprise service bus and corresponding platform Download PDFInfo
- Publication number
- CN102364921A CN102364921A CN2011103721268A CN201110372126A CN102364921A CN 102364921 A CN102364921 A CN 102364921A CN 2011103721268 A CN2011103721268 A CN 2011103721268A CN 201110372126 A CN201110372126 A CN 201110372126A CN 102364921 A CN102364921 A CN 102364921A
- Authority
- CN
- China
- Prior art keywords
- equipment
- soa
- request message
- esb
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention provides a realization method and realization equipment for an enterprise service bus and a corresponding platform, which relate to an enterprise application system interaction technology and solve the technical problem that the realization method for the enterprise service bus (ESB) in the prior art is excessively heavy for a system. The method provided by the invention mainly comprises that: service-oriented architecture ESB (SOA.ESB) equipment receives a request message which is defined according to a request message protocol from service consumer equipment; the SOA.ESB equipment determines whether the service consumer equipment has security right over requesting or not according to a user identifier carried by the request message; and if the service consumer equipment has the security right over the requesting, the SOA.ESB equipment forwards the request message to corresponding service provider equipment when a message parameter carried by the request message indicates synchronization processing. The method, the equipment and the platform are mainly used for intra-enterprise interaction.
Description
Technical field
The present invention relates to the mutual technology of enterprise application system, relate in particular to a kind of ESB (Enterprise Service Bus, implementation method ESB), equipment and corresponding system.
Background technology
Along with the system that some large and medium-sized enterprise are inner is more and more, the relation between the system becomes increasingly complex.In this case, large-scale distributed enterprise application need simple and practical relatively middleware Technology simplify and unify to become increasingly complex, loaded down with trivial details enterprise-level information system platform.Therefore SOA (Service-Oriented Architecture, service-oriented architecture) technology is arisen at the historic moment.The SOA technology can connect the different function units of application program through definition excellent interface and contract between the service, make the user can repeat each self-application without restriction.
The key that supports SOA is that its message is transmitted framework, i.e. ESB.ESB can be used to realize enterprise application different messages and information accurately, efficient and safe transfer, it can also eliminate the technological disparity between the different application simultaneously, lets different application service coordinate operation, realizes communication and integration between the different services.
The ESB model is very complete in the prior art, and has very rich functions usually, comprises communication function, service function of exchange, integrated functionality, service quality function, security functions, service abatement functions and modeling function etc.
But; It is too much that this ESB of prior art has the function that following technical problem: ESB supports; Some function such as modeling function etc. also are of little use, and its existence this moment becomes a kind of burden on the contrary, and is too heavy for whole enterprise application system; Cause system configuration, maintenance difficult, also make the corresponding increase of purchase cost simultaneously.
Summary of the invention
Embodiments of the invention provide implementation method, equipment and the corresponding platform of a kind of ESB, and the realization ESB of lightweight alleviates the burden that ESB causes system configuration, maintenance etc.
For achieving the above object, embodiments of the invention adopt following technical scheme:
A kind of implementation method of ESB comprises:
ESB kernel service SOA.ESB equipment receives the request message according to the definition of request message contractual agreement from service consumer equipment;
This SOA.ESB equipment confirms that according to the user side sign of carrying in this request message this service consumer equipment is to have security permission to ask;
Ask if define security permission, then when the message parameter that carries in this request message was designated as Synchronous Processing, this SOA.ESB equipment was forwarded to corresponding device of service provider with this request message; When the message parameter that carries in this request message is designated as asynchronous process; This SOA.ESB equipment sends to ESB message queue service SOA.MSMQ equipment with this request message and carries out asynchronous process, and by this SOA.MSMQ equipment this request message is forwarded to corresponding device of service provider.
Wherein, before above-mentioned SOA.MSMQ equipment was forwarded to this request message corresponding device of service provider, this method also comprised:
If network occurs unusual or this asynchronous process surpasses the scheduled time; Then this SOA.MSMQ equipment sends to ESB database SOADB equipment with this request message that is designated as asynchronous process, and this SOADB equipment is stored the request message that this is designated as asynchronous process as the request message that sends failure;
The automatic duplicate services SOA.Autosend equipment of ESB regularly is retransmitted to this corresponding ISP to the request message that this transmission of storing in this SOADB equipment is failed.
Preferably, this method also comprises:
This SOA.ESB equipment receives the processing of request result of request message institute to this Synchronous Processing that this corresponding device of service provider is replied;
This SOA.ESB equipment sends to this ESB log services SOA.ESBlog equipment with this request message and this processing of request result that is designated as Synchronous Processing;
This SOA.ESBlog equipment sends to this SOADB equipment with this processing of request result as diary information with the request message of this Synchronous Processing and stores, so that this diary information of storing in this SOADB equipment of the ESB background maintenance SOAMgm of system device access.
Further, preferably, this method can also comprise:
Whether normally this ESB monitor service SOA.Monitor equipment transmits heartbeat message respectively to this SOA.ESB equipment, this SOA.MSMQ equipment, this SOA.ESBlog equipment and this SOA.Autosend equipment, and then monitor the operation of this SOA.ESB equipment, this SOA.MSMQ equipment, this SOA.ESBlog equipment and this SOA.Autosend equipment.
In addition, this method can also comprise:
To the request message from this SOA.ESB equipment, this corresponding device of service provider will arrive this service consumer equipment through this SOA.ESB device replied to the result of this request message according to this message contractual agreement definition.
Wherein, above-mentioned this request message of message contractual agreement definition adopts the XML form, and the header packet information of this request message comprises: services request ID, service consumer IP address of equipment, request type, asynchronous message parameter.
A kind of realization equipment of ESB comprises:
Receiver module is used to receive the request message according to the definition of message request message contractual agreement from service consumer equipment;
Authentication module, the user side sign that is used for carrying according to this request message confirms that this service consumer equipment is to have security permission to ask;
Synchronous processing module is used for defining security permission and asking when this authentication module, and the message parameter that carries in this request message is forwarded to corresponding device of service provider with this request message when being designated as Synchronous Processing.
Asynchronous redirect module; Be used for asking when this authentication module defines authority; And when the message parameter that carries in this request message is designated as asynchronous process, this request message is sent to this SOA.MSMQ equipment carry out asynchronous process, and send the reception success message to this service consumer equipment.
Preferably, the said equipment can also comprise:
Collection module is used to receive the processing of request result of request message institute to this Synchronous Processing that this corresponding device of service provider is replied;
The dump module; Be used for this is designated as the request message and this processing of request result of Synchronous Processing; Send to this SOA.ESBlog equipment; So that this SOA.ESBlog equipment sends to this ESB database SOADB equipment with this processing of request result as diary information with the request message of this Synchronous Processing and stores, and then makes this diary information of storing in this SOADB equipment of SOAMgm device access.
A kind of platform of service-oriented architecture comprises: SOA.ESB equipment, SOA.MSMQ equipment;
This SOA.ESB equipment; Be used to receive request message according to the definition of request message contractual agreement from service consumer equipment; And confirm that according to the user side that carries in this request message sign this service consumer equipment is to have security permission to ask; Ask if define security permission, then when the message parameter that carries in this request message is designated as Synchronous Processing, this request message is forwarded to corresponding device of service provider; When the message parameter that carries in this request message is designated as asynchronous process, this request message is sent to this SOA.MSMQ equipment carry out asynchronous process;
This SOA.MSMQ equipment is used to receive this request message, and the line asynchronous of going forward side by side is handled, and again this request message is forwarded to corresponding device of service provider.
In addition, this ESB platform can also comprise: SOADB equipment and SOA.Autosend equipment;
This SOA.MSMQ equipment also is used for occurring unusual or this asynchronous process surpasses the scheduled time at network, and this request message that is designated as asynchronous process is sent to this SOADB equipment;
This SOADB equipment is used for the request message that this request message that is designated as asynchronous process is failed as transmission is stored;
This SOA.Autosend equipment, the request message that this transmission that is used for regularly this SOADB equipment being stored is failed is retransmitted to this corresponding ISP.
Further, this ESB platform can also comprise: SOA.ESBlog equipment, SOADB equipment and SOAMgm equipment;
This SOA.ESB equipment; Also be used to receive the processing of request result of request message institute that this corresponding device of service provider is replied to this Synchronous Processing; And, send to this SOA.ESBlog equipment with this request message and this processing of request result that is designated as Synchronous Processing;
This SOA.ESBlog equipment is used for the request message of this Synchronous Processing is sent to this ESB database SOADB equipment with this processing of request result as diary information;
This SOADB equipment is used for, and stores above-mentioned diary information;
This SOAMgm equipment is used for visiting this diary information that this SOADB equipment is stored, so that this diary information of user inquiring.
ESB in the technical scheme provided by the invention can carry out the security permission checking to the request message according to the definition of message contractual agreement that receives; And to carry out the synchronous asynchronous processing through the message of checking; Send to corresponding device of service provider at last, belong to a kind of lightweight ESB that supports the function of tonic chord, not only can make system interaction process safety; Succinctly; Efficient is high, can also realize making communication and the integration between the different services, alleviates the burden that ESB causes system configuration, maintenance etc. simultaneously.
Description of drawings
Fig. 1 is the structure sketch map of the ESB platform in the embodiment of the invention one;
Fig. 2 is the schematic flow sheet of the implementation method of a kind of ESB in the embodiment of the invention one;
Fig. 3 is the schematic flow sheet of the security permission method of calibration in the embodiment of the invention one;
Fig. 4 is the structural representation of the realization equipment of a kind of ESB in the embodiment of the invention two.
Embodiment
Present embodiment combines ESB platform shown in Figure 1, and the implementation method of a kind of ESB is provided, and as shown in Figure 2, this method comprises:
Wherein, Above-mentioned message contractual agreement is the unified message definition mechanism that service consumer equipment and device of service provider all adopt, and be used to define described request message and adopt the XML form, and the header packet information of described request message comprises (with reference to following table one) at least: the services request ID; The service consumer IP address of equipment; Request type, asynchronous message parameter etc., the content beyond the header packet information are the concrete business information that needs device of service provider to handle.Be that request message adopts the XML form; And the final unified single face that is delivered to the message supplier; Device of service provider is resolved after the identification to the request message that adopts such definition; Request type according to this request message carries out concrete processing again, and with result equally according to being returned to service consumer equipment after the definition of this message contractual agreement.Specifically the manage business process of information of device of service provider is identical with prior art, does not give unnecessary details at this.This mechanism in the present embodiment just adopts fixing definition mode at the request message header information simply; (concrete definition mode such as following table one; Wherein, More commonly used like AsyncRequest, User ID etc. in a plurality of attributes of definition in the table one, remaining can omit or follow default value as required), but the exploitation of service and the complexity of interface simplified greatly.
Particularly, step 102 can realize through following mode: as shown in Figure 2, comprise
Table one
Wherein, device of service provider also should re-send to SOA.ESB equipment according to after above-mentioned this result of message contractual agreement definition.
Preferably, provide in the present embodiment in the method, can also comprise a kind of added machinery, be used to above-mentioned asynchronous process process service.Introduce the concrete scheme of this compensation mechanism below:
In step 107; This SOA.MSMQ equipment is forwarded to this request message before the corresponding device of service provider of this destination address; If network occurs unusual or this asynchronous process surpasses the scheduled time; Then SOA.MSMQ equipment sends to SOADB equipment with this request message, and SOADB equipment is stored this request message as the request message that sends failure; And SOA.Autosend equipment regularly conducts interviews to the request message that the above-mentioned transmission of storing in the SOADB equipment is failed, and retransmits through connecting 45 according to predetermined number of repetition, up to successfully sending to corresponding device of service provider.If after reaching this predetermined number of repetition, request message does not still send to, then SOA.Autosend equipment is stored in request message in the tabulation of special record failure, carries out follow-up processing by manual work.
Preferably, also a kind of administrative mechanism will be provided in the method for this enforcement, so as to real above-mentioned synchronously or request message or result in the asynchronous process process manage.Comprise:
After executing above-mentioned steps 105; That is: SOA.ESB equipment can above-mentioned this handled the result directly reply to service consumer equipment after; The above-mentioned request message that is designated as Synchronous Processing (is comprised the information of carrying in this request message; Like culture/version/referenceid/Transno/sessionid/requested etc.) and corresponding device of service provider above-mentioned this of replying handle the result; Send to SOA.ESBlog equipment, SOA.ESBlog equipment for diary information, and sends to their arrangements SOADB equipment and stores; When the user needs to handle, like inquiry or manage this diary information, promptly the request message of Synchronous Processing or its processing of request are as a result the time, and the user can utilize the said diary information of storing in the SOAMgm device access SOADB equipment.
In like manner; SOA.MSMQ equipment also can be with the request message that is designated as asynchronous process; (comprising the information of carrying in this request message), send to SOA.ESBlog equipment like culture/version/referenceid/Transno/sessionid/requestid etc.; Said SOA.ESBlog equipment sends to SOADB equipment with the request message of said asynchronous process as diary information, and storage; When the user need handle like inquiry or manages this diary information, promptly during the request message of this asynchronous process, the user can utilize this note information of storing in the SOAMgm device access SOADB equipment.
Preferably, in the method that present embodiment provides, a kind of monitoring mechanism is provided also, can be used for monitoring synchronously or the asynchronous process process whether normally carry out.Comprise:
SOA.Monitor equipment regularly transmits heartbeat message to SOA.ESB equipment, SOA.MSMQ equipment, SOA.ESBlog equipment 34 and SOA.Autosend equipment, and normally whether monitoring SOA.ESB equipment, SOA.MSMQ equipment, SOA.ESBlog equipment and SOA.Autosend equipment operation.If when not receiving the heartbeat response message of a certain device replied in SOA.ESB equipment, SOA.MSMQ equipment, SOA.ESBlog equipment and the SOA.Autosend equipment; Then represent this equipment to break down, this moment, SOA.Monitor equipment can send warning message.
In addition; If SOA.ESB device step 101 has arbitrary step failure in the process of step 105; For example SOA.ESB equipment is in the process of wait service supplier equipment return results; If overtime, situation such as network is unusual, SOA.ESB equipment turns back to service consumer equipment etc. with error message, all represents the request message of this indication Synchronous Processing to send failure; Then SOA.ESB equipment automatically with the failure the request message final entry in SOA.ESBDB35, the user can carry out the analysis of searching of problem through the SOAMgm equipment query.
SOA.SOA.ESB equipment or SOA.SOA.MSMQ equipment can be with the situation of all request messages processing in the process of synchronous or asynchronous process request message; Record in the counter, comprise the unusual number of times of visit capacity, success rate, mortality, network, average response duration of service consumer equipment, last response time etc.; The request message quantity that certain service consumer equipment is initiated in counter occurs unusual; Or mortality surpasses under the situation of warning line in the continuous certain hour of certain device of service provider, and OA.SOA.ESB equipment or SOA.SOA.MSMQ equipment can send alarm mail automatically to the system maintenance personnel.
In Fig. 1, combine to comprise that the ESB platform of SOA.ESB equipment and a SOA.MSMQ equipment is that example has been described the method that present embodiment provides; In fact; According to request message treating capacity ground needs, SOA.ESB equipment and SOA.MSMQ equipment also can be for a plurality of, and each function is with SOA.ESB equipment in the present embodiment and SOA.MSMQ equipment; Also be that those skilled in the art can obtain from foregoing description easily, do not give unnecessary details at this.
In the method that present embodiment provides; Device of service provider is in the process of exploitation service; The message format of its service interface must adopt the XML form; And header packet information must adopt the as above described unified Definition of table one, and this header packet information can be used for providing to SOA.ESB equipment and carries out safety, Authority Verification, and the route effect of message.ESB service with other is the same, when the service of this enforcement is reached the standard grade, also need register in SOA improvement, and whether the total interface that must indicate service name, address of service during registration, provides, and the template of service interface need log configuration etc.Service consumer equipment can browse to needed information on services through the tabulation of existing service library, but and the interface contract design documentation of download service supplier equipment, carry out the exploitation of client-side program.Before the service of service consumer device access; Need carry out the registration of corresponding authority application and client ip; After audit is passed through; It is medium that its corresponding authority relation will offer SOA.ESB equipment institute's service recorder and white list or list of access rights, and SOA.ESB carries out the checking of the safety and the authority of request message according to it.During the service of service consumer device access; With the requirement of request message according to the ISP, adopt the XML layout sequenceization, send to SOA.ESB equipment; SOA.ESB equipment just can be handled according to relevant rule afterwards, and final result is returned to service consumer equipment.
Present embodiment provides the implementation method of a lightweight ESB through comparatively succinct mode.Can carry out the synchronous/asynchronous request message effectively and handle, security permission checking, message route and message compensation; Monitoring and daily management etc. can realize communication, service interaction, Core Features such as safety and service improvement; And support high concurrent service consumer to visit; What make numerous service consumer equipment and numerous device of service provider becomes more succinct alternately, has reduced the complexity of system, avoids disposing, the difficulty of maintenance system; Promoted the availability of system, extensibility and maintainability.
Embodiment two
Present embodiment provides the realization equipment of a kind of ESB, can be used as above-mentioned SOA.ESB equipment and uses.As shown in Figure 4, comprising: receiver module 41, authentication module 42, synchronous processing module 43, asynchronous redirect module 44.
Receiver module 41 is used to receive the request message according to the definition of message contractual agreement from service consumer equipment; Authentication module 42, the user side sign that is used for carrying according to described request message confirms that said service consumer equipment is to have authority to ask; Synchronous processing module 43 is used for defining authority and asking when said authentication module 42, and the message parameter that carries in the described request message is when being designated as Synchronous Processing, with the described request forwards to corresponding device of service provider; Asynchronous redirect module 44; Be used for asking when said authentication module 42 defines security permission; And when the message parameter that carries in the described request message is designated as asynchronous process; Described request message is sent to said SOA.MSMQ equipment carry out asynchronous process, and send the reception success message to said service consumer equipment.
Preferably, this equipment also can comprise: collection module 45, dump module 46.
Collection module 45 is used to receive the processing of request result of request message institute to said Synchronous Processing that the device of service provider of said correspondence is replied;
Dump module 46; Be used for the said request message of Synchronous Processing and the result of described request of being designated as; Send to said SOA.ESBlog equipment; So that said SOA.ESBlog equipment sends to said ESB database SOADB equipment with the result of the request message of said Synchronous Processing and described request as diary information and stores, and then makes the said diary information of storing in the said SOADB equipment of SOAMgm device access.
The ESB that present embodiment provides realizes that equipment can be according to the Core Features such as request message execution synchronous/asynchronous communication according to the definition of message contractual agreement that receive, and implementation procedure is simple, is convenient to system configuration and maintenance, can simplify the complexity of whole system.
Embodiment three
Present embodiment provides the platform of a kind of ESB, and is as shown in Figure 1, and this platform comprises: SOA.ESB equipment, SOA.MSMQ equipment;
This SOA.ESB equipment; Be used to receive request message according to the definition of request message contractual agreement from service consumer equipment; And confirm that according to the user side that carries in described request message sign said service consumer equipment is to have security permission to ask; Ask if define security permission, then when the message parameter that carries in the described request message is designated as Synchronous Processing, request message is forwarded to corresponding device of service provider; When the message parameter that carries in the described request message is designated as asynchronous process, this request message is sent to SOA.MSMQ equipment carry out asynchronous process;
This SOA.MSMQ equipment is used to receive described request message, and the line asynchronous of going forward side by side is handled, again with the device of service provider of described request forwards to correspondence.
Preferably, as shown in Figure 1, also comprise: SOADB equipment and SOA.Autosend equipment;
This SOA.MSMQ equipment also is used for unusual or said asynchronous process occurring at network and surpasses the scheduled time, and the said request message that is designated as asynchronous process is sent to this SOADB equipment;
This SOADB equipment is used for the said request message that is designated as asynchronous process is stored as the request message that sends failure;
This SOA.Autosend equipment, the request message that the said transmission that is used for regularly said SOADB equipment being stored is failed is retransmitted to the ISP of above-mentioned correspondence.
Preferably, as shown in Figure 1, this ESB platform also comprises: SOA.ESBlog equipment, SOADB equipment and SOAMgm equipment;
This SOA.ESB equipment; Also be used to receive the processing of request result of request message institute that the device of service provider of said correspondence is replied to said Synchronous Processing; And, send to SOA.ESBlog equipment with this request message and this processing of request result that is designated as Synchronous Processing;
Above-mentioned SOA.ESBlog equipment is used for the request message of above-mentioned Synchronous Processing is sent to this ESB database SOADB equipment with this processing of request result as diary information;
This SOADB equipment is used for, and stores above-mentioned diary information;
This SOAMgm equipment is used for visiting the said diary information that said SOADB equipment is stored, so that the said diary information of user inquiring.
The ESB platform that present embodiment provides can transmit the request message between a plurality of service consumer equipment and a plurality of device of service provider; Make each service consumer need not to understand the relevant information that the device of service provider of service is provided too much for it, most reciprocal process is accomplished by the ESB platform, and reciprocal process mainly comprises the synchronous/asynchronous processing; Core Features such as daily information management; Therefore reciprocal process is simple, has reduced system complexity, has simplified the handling process of system.
The above; Be merely embodiment of the present invention, but protection scope of the present invention is not limited thereto, any technical staff who is familiar with the present technique field is in the technical scope that the present invention discloses; Can expect easily changing or replacement, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion by said protection range with claim.
Claims (11)
1. the implementation method of an ESB is characterized in that, comprising:
ESB kernel service SOA.ESB equipment receives the request request message according to the definition of message contractual agreement from service consumer equipment;
Said SOA.ESB equipment confirms that according to the user side sign of carrying in the described request message said service consumer equipment is to have security permission to ask;
Ask if define security permission, then when the message parameter that carries in the described request message was designated as Synchronous Processing, said SOA.ESB equipment was with the device of service provider of described request forwards to correspondence; When the message parameter that carries in the described request message is designated as asynchronous process; Said SOA.ESB equipment sends to ESB message queue service SOA.MSMQ equipment with described request message and carries out asynchronous process, and by said SOA.MSMQ equipment with the device of service provider of described request forwards to correspondence.
2. the implementation method of ESB according to claim 1 is characterized in that, before said SOA.MSMQ equipment arrived corresponding device of service provider with the described request forwards, this method also comprised:
If network unusual or said asynchronous process occurs and surpasses the scheduled time; Then said SOA.MSMQ equipment sends to ESB database SOADB equipment with the said request message that is designated as asynchronous process, and said SOADB equipment is stored the said request message that is designated as asynchronous process as the request message that sends failure;
The request message that the automatic duplicate services SOA.Autosend equipment of ESB is regularly failed to the said transmission of storing in the said SOADB equipment is retransmitted to the ISP of said correspondence.
3. the implementation method of ESB according to claim 1 and 2 is characterized in that, also comprises:
Said SOA.ESB equipment receives the processing of request result of request message institute to said Synchronous Processing of the device of service provider answer of said correspondence;
Said SOA.ESB equipment sends to said ESB log services SOA.ESBlog equipment with said request message and the said processing of request result of institute who is designated as Synchronous Processing;
Said SOA.ESBlog equipment sends to said SOADB equipment with the result of the request message of said Synchronous Processing and described request as diary information and stores, so that the said diary information of storing in the said SOADB equipment of the ESB background maintenance SOAMgm of system device access.
4. the implementation method of ESB according to claim 1 is characterized in that, also comprises:
Whether normally said ESB monitor service SOA.Monitor equipment transmits heartbeat message respectively to said SOA.ESB equipment, said SOA.MSMQ equipment, said SOA.ESBlog equipment and said SOA.Autosend equipment, and then monitor the operation of said SOA.ESB equipment, said SOA.MSMQ equipment, said SOA.ESBlog equipment and said SOA.Autosend equipment.
5. according to the implementation method of any described ESB in the claim 1 to 4, it is characterized in that, also comprise:
To described request message from said SOA.ESB equipment; The device of service provider of said correspondence defines according to said message contractual agreement, will arrive said service consumer equipment through said SOA.ESB device replied to the result of described request message.
6. according to the implementation method of any described ESB in the claim 1 to 4; It is characterized in that; Said message contractual agreement definition described request message adopts the XML form, and the header packet information of described request message comprises: services request ID, service consumer IP address of equipment; Request type, the asynchronous message parameter.
7. the realization equipment of an ESB is characterized in that, comprising:
Receiver module is used to receive the request message according to the definition of message contractual agreement from service consumer equipment;
Authentication module, the user side sign that is used for carrying according to described request message confirms that said service consumer equipment is to have security permission to ask;
Synchronous processing module is used for defining security permission and asking when said authentication module, and the message parameter that carries in the described request message is when being designated as Synchronous Processing, with the described request forwards to corresponding device of service provider;
Asynchronous redirect module; Be used for asking when said authentication module defines authority; And when the message parameter that carries in the described request message is designated as asynchronous process; Described request message is sent to said SOA.MSMQ equipment carry out asynchronous process, and send the reception success message to said service consumer equipment.
8. the service equipment of ESB according to claim 7 is characterized in that, also comprises:
Collection module is used to receive the processing of request result of request message institute to said Synchronous Processing that the device of service provider of said correspondence is replied;
The dump module; Be used for the said request message of Synchronous Processing and the result of described request of being designated as; Send to said SOA.ESBlog equipment; So that said SOA.ESBlog equipment sends to said ESB database SOADB equipment with the result of the request message of said Synchronous Processing and described request as diary information and stores, and then makes the said diary information of storing in the said SOADB equipment of SOAMgm device access.
9. the platform of a service-oriented architecture is characterized in that, comprising: SOA.ESB equipment, SOA.MSMQ equipment;
Said SOA.ESB equipment; Be used to receive request message according to the definition of message contractual agreement from service consumer equipment; And confirm that according to the user side that carries in described request message sign said service consumer equipment is to have security permission to ask; Ask if define security permission, then when the message parameter that carries in the described request message is designated as Synchronous Processing, the device of service provider of described request forwards to correspondence; When the message parameter that carries in the described request message is designated as asynchronous process, described request message is sent to said SOA.MSMQ equipment carry out asynchronous process;
Said SOA.MSMQ equipment is used to receive described request message, and the line asynchronous of going forward side by side is handled, again with the device of service provider of described request forwards to correspondence.
10. the platform of service-oriented architecture according to claim 9 is characterized in that, also comprises: SOADB equipment and SOA.Autosend equipment;
Said SOA.MSMQ equipment also is used for unusual or said asynchronous process occurring at network and surpasses the scheduled time, and the said request message that is designated as asynchronous process is sent to said SOADB equipment;
Said SOADB equipment is used for the said request message that is designated as asynchronous process is stored as the request message that sends failure;
Said SOA.Autosend equipment, the request message that the said transmission that is used for regularly said SOADB equipment being stored is failed is retransmitted to the ISP of said correspondence.
11. the platform of service-oriented architecture according to claim 9 is characterized in that, also comprises: SOA.ESBlog equipment, SOADB equipment and SOAMgm equipment;
Said SOA.ESB equipment; Also be used to receive the processing of request result of request message institute that the device of service provider of said correspondence is replied to said Synchronous Processing; And, send to said SOA.ESBlog equipment with the said request message of Synchronous Processing and the result of described request of being designated as;
Said SOA.ESBlog equipment is used for the request message of said Synchronous Processing and the result of described request are sent to said ESB database SOADB equipment as diary information;
Said SOADB equipment is used for, and stores above-mentioned diary information;
Said SOAMgm equipment is used for visiting the said diary information that said SOADB equipment is stored, so that the said diary information of user inquiring.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2011103721268A CN102364921A (en) | 2011-11-21 | 2011-11-21 | Realization method and equipment for enterprise service bus and corresponding platform |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2011103721268A CN102364921A (en) | 2011-11-21 | 2011-11-21 | Realization method and equipment for enterprise service bus and corresponding platform |
Publications (1)
Publication Number | Publication Date |
---|---|
CN102364921A true CN102364921A (en) | 2012-02-29 |
Family
ID=45691473
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2011103721268A Pending CN102364921A (en) | 2011-11-21 | 2011-11-21 | Realization method and equipment for enterprise service bus and corresponding platform |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN102364921A (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103297295A (en) * | 2013-05-24 | 2013-09-11 | 广东电网公司电力科学研究院 | Test method and test system for ESB (enterprise service bus) communication modes |
CN103997509A (en) * | 2013-02-20 | 2014-08-20 | 中国移动通信集团北京有限公司 | Service oriented architecture-based service processing method and apparatus |
CN104731912A (en) * | 2015-03-24 | 2015-06-24 | 浪潮集团有限公司 | Message transmission method and device for message middleware MQ |
CN104869163A (en) * | 2015-05-26 | 2015-08-26 | 湖南傻蛋科技有限公司 | Dynamic service call method based on agent under cluster environment |
CN105959385A (en) * | 2016-06-06 | 2016-09-21 | 浪潮软件集团有限公司 | Information communication method, device and system |
CN106656706A (en) * | 2017-02-25 | 2017-05-10 | 华南理工大学 | Service-oriented robot open-type control system and method based on software bus |
CN106681843A (en) * | 2015-11-05 | 2017-05-17 | 中国科学院沈阳自动化研究所 | Parameter transmission method among sub-modules on the basis of assembly-type development mode loose coupling |
CN106936687A (en) * | 2015-12-30 | 2017-07-07 | 航天信息软件技术有限公司 | A kind of wechat public number access device, system and method and mobile terminal |
CN107071048A (en) * | 2017-05-12 | 2017-08-18 | 浪潮软件股份有限公司 | It is a kind of based on http request forward without intrusive mood enterprise level service bus |
CN107845415A (en) * | 2016-09-18 | 2018-03-27 | 心医国际数字医疗系统(大连)有限公司 | Hospital enterprise service bus realization device and method |
CN109062848A (en) * | 2018-08-01 | 2018-12-21 | 武汉索雅信息技术有限公司 | Purchasing management method, apparatus and bus platform based on ESB bus platform |
CN109150858A (en) * | 2018-08-01 | 2019-01-04 | 武汉索雅信息技术有限公司 | Request processing method, equipment, system and the storage medium of data interaction bus |
CN109298950A (en) * | 2018-08-15 | 2019-02-01 | 深圳壹账通智能科技有限公司 | Enterprise Service Bus system, data processing method, terminal and storage medium |
WO2019109957A1 (en) * | 2017-12-08 | 2019-06-13 | 深圳壹账通智能科技有限公司 | Esb-based service providing method, apparatus and device, and readable storage medium |
CN110166459A (en) * | 2019-05-24 | 2019-08-23 | 深圳前海微众银行股份有限公司 | A kind of means of defence and device of unserializing loophole |
CN110689386A (en) * | 2019-08-19 | 2020-01-14 | 苏宁云计算有限公司 | Electronic bill issuing method and system |
CN113569123A (en) * | 2021-06-28 | 2021-10-29 | 杭州涂鸦信息技术有限公司 | Log query method, system and computer readable storage medium |
US20210349810A1 (en) * | 2018-11-28 | 2021-11-11 | Sap Se | Asynchronous consumer-driven contract testing in micro service architecture |
CN115208668A (en) * | 2022-07-15 | 2022-10-18 | 广东广信通信服务有限公司 | Application integration control method, system and device based on service bus system technology |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101184056A (en) * | 2007-12-04 | 2008-05-21 | 浙江大学 | Distributed enterprise service bus message switching method |
CN101394420A (en) * | 2008-10-23 | 2009-03-25 | 中国移动通信集团山西有限公司 | Method for implementing service sharing of heterogeneous IT system, method for precise marketing and enterprise service bus |
CN101827115A (en) * | 2009-12-31 | 2010-09-08 | 厦门市美亚柏科信息股份有限公司 | Holographic enterprise service bus |
-
2011
- 2011-11-21 CN CN2011103721268A patent/CN102364921A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101184056A (en) * | 2007-12-04 | 2008-05-21 | 浙江大学 | Distributed enterprise service bus message switching method |
CN101394420A (en) * | 2008-10-23 | 2009-03-25 | 中国移动通信集团山西有限公司 | Method for implementing service sharing of heterogeneous IT system, method for precise marketing and enterprise service bus |
CN101827115A (en) * | 2009-12-31 | 2010-09-08 | 厦门市美亚柏科信息股份有限公司 | Holographic enterprise service bus |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103997509A (en) * | 2013-02-20 | 2014-08-20 | 中国移动通信集团北京有限公司 | Service oriented architecture-based service processing method and apparatus |
CN103997509B (en) * | 2013-02-20 | 2017-10-10 | 中国移动通信集团北京有限公司 | A kind of service processing method and device based on Services Oriented Achitecture |
CN103297295B (en) * | 2013-05-24 | 2016-04-27 | 广东电网公司电力科学研究院 | The method of testing of the communication mode of ESB and test macro |
CN103297295A (en) * | 2013-05-24 | 2013-09-11 | 广东电网公司电力科学研究院 | Test method and test system for ESB (enterprise service bus) communication modes |
CN104731912B (en) * | 2015-03-24 | 2017-12-19 | 浪潮集团有限公司 | A kind of message-oriented middleware MQ method for message transmission and device |
CN104731912A (en) * | 2015-03-24 | 2015-06-24 | 浪潮集团有限公司 | Message transmission method and device for message middleware MQ |
CN104869163A (en) * | 2015-05-26 | 2015-08-26 | 湖南傻蛋科技有限公司 | Dynamic service call method based on agent under cluster environment |
CN106681843A (en) * | 2015-11-05 | 2017-05-17 | 中国科学院沈阳自动化研究所 | Parameter transmission method among sub-modules on the basis of assembly-type development mode loose coupling |
CN106936687A (en) * | 2015-12-30 | 2017-07-07 | 航天信息软件技术有限公司 | A kind of wechat public number access device, system and method and mobile terminal |
CN105959385A (en) * | 2016-06-06 | 2016-09-21 | 浪潮软件集团有限公司 | Information communication method, device and system |
CN107845415A (en) * | 2016-09-18 | 2018-03-27 | 心医国际数字医疗系统(大连)有限公司 | Hospital enterprise service bus realization device and method |
CN106656706A (en) * | 2017-02-25 | 2017-05-10 | 华南理工大学 | Service-oriented robot open-type control system and method based on software bus |
CN106656706B (en) * | 2017-02-25 | 2020-06-19 | 华南理工大学 | Software bus-based service-oriented robot open control system and method |
CN107071048A (en) * | 2017-05-12 | 2017-08-18 | 浪潮软件股份有限公司 | It is a kind of based on http request forward without intrusive mood enterprise level service bus |
WO2019109957A1 (en) * | 2017-12-08 | 2019-06-13 | 深圳壹账通智能科技有限公司 | Esb-based service providing method, apparatus and device, and readable storage medium |
CN109062848A (en) * | 2018-08-01 | 2018-12-21 | 武汉索雅信息技术有限公司 | Purchasing management method, apparatus and bus platform based on ESB bus platform |
CN109150858A (en) * | 2018-08-01 | 2019-01-04 | 武汉索雅信息技术有限公司 | Request processing method, equipment, system and the storage medium of data interaction bus |
CN109298950A (en) * | 2018-08-15 | 2019-02-01 | 深圳壹账通智能科技有限公司 | Enterprise Service Bus system, data processing method, terminal and storage medium |
US20210349810A1 (en) * | 2018-11-28 | 2021-11-11 | Sap Se | Asynchronous consumer-driven contract testing in micro service architecture |
US11755461B2 (en) * | 2018-11-28 | 2023-09-12 | Sap Se | Asynchronous consumer-driven contract testing in micro service architecture |
CN110166459A (en) * | 2019-05-24 | 2019-08-23 | 深圳前海微众银行股份有限公司 | A kind of means of defence and device of unserializing loophole |
CN110166459B (en) * | 2019-05-24 | 2022-12-27 | 深圳前海微众银行股份有限公司 | Protection method, device and equipment for deserialization loophole and readable storage medium |
CN110689386A (en) * | 2019-08-19 | 2020-01-14 | 苏宁云计算有限公司 | Electronic bill issuing method and system |
CN110689386B (en) * | 2019-08-19 | 2022-10-11 | 苏宁云计算有限公司 | Electronic bill issuing method and system |
CN113569123A (en) * | 2021-06-28 | 2021-10-29 | 杭州涂鸦信息技术有限公司 | Log query method, system and computer readable storage medium |
CN115208668A (en) * | 2022-07-15 | 2022-10-18 | 广东广信通信服务有限公司 | Application integration control method, system and device based on service bus system technology |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102364921A (en) | Realization method and equipment for enterprise service bus and corresponding platform | |
CN103944924B (en) | Method of ubiquitous network publish-subscribe middleware model based on RESTful | |
CN103124981B (en) | The electronic document system for the distribution of commodities and electronic document circulation method | |
CN110166409A (en) | Equipment cut-in method, related platform and computer storage medium | |
CN102387075B (en) | Dynamic service routing method and device for enterprise service bus | |
US9946984B2 (en) | System and method for transporting a document between a first service provider and a second service provider | |
CN101163117B (en) | Packet management method, packet resource sharing method and instant communication equipment | |
CN104484187B (en) | A kind of information integration method and system | |
CN101854348B (en) | Realization method of SOA (Service Oriented Architecture) accessing core supporting system in peripheral system | |
CN101447862A (en) | Security exchange system and security exchange method thereof | |
CN103220292A (en) | Cross-safe-area data transmission method and system | |
CN105868032A (en) | Message processing system and method supporting multi-system access | |
CN103475726A (en) | Virtual desktop management method, server and client side | |
CN104811371A (en) | Brand-new instant messaging system | |
CN103795793A (en) | Road vehicle monitoring platform system based on double server clusters | |
CN105812480A (en) | Remote management device and remote management method for intelligent bulk grain carrier vehicle | |
EP2916522A1 (en) | File transmission method and system thereof | |
CN103338206A (en) | Method and device for achieving data exchange based on data bus technology | |
KR101416280B1 (en) | Event handling system and method | |
CN104657841A (en) | Express item delivery method, delivery processing method, express cabinet terminal and service system | |
CN113992769A (en) | Industrial internet information exchange method | |
CN1973282A (en) | System and method for managing a change to a cluster configuration | |
CN105959385A (en) | Information communication method, device and system | |
CN102629345B (en) | Chain type links up collaboration method, Apparatus and system | |
CN106789965A (en) | A kind of Internet of Things data exchange method and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120229 |