CN102025653A - Enterprise service bus and message processing method thereof - Google Patents
Enterprise service bus and message processing method thereof Download PDFInfo
- Publication number
- CN102025653A CN102025653A CN2010101974807A CN201010197480A CN102025653A CN 102025653 A CN102025653 A CN 102025653A CN 2010101974807 A CN2010101974807 A CN 2010101974807A CN 201010197480 A CN201010197480 A CN 201010197480A CN 102025653 A CN102025653 A CN 102025653A
- Authority
- CN
- China
- Prior art keywords
- message
- request
- service
- esb
- processing
- 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
- 238000003672 processing method Methods 0.000 title abstract 2
- 238000012545 processing Methods 0.000 claims abstract description 86
- 238000000034 method Methods 0.000 claims description 32
- 230000008569 process Effects 0.000 claims description 17
- 238000012163 sequencing technique Methods 0.000 claims description 7
- 238000005111 flow chemistry technique Methods 0.000 claims description 2
- 238000004148 unit process Methods 0.000 claims description 2
- 230000001360 synchronised effect Effects 0.000 abstract description 6
- 238000006243 chemical reaction Methods 0.000 abstract description 5
- 230000010354 integration Effects 0.000 description 27
- 238000007726 management method Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 8
- 238000012550 audit Methods 0.000 description 7
- 238000012856 packing Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 229910000831 Steel Inorganic materials 0.000 description 4
- 239000010959 steel Substances 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to an enterprise service bus and a message processing method thereof. The enterprise service bus comprises a message receiving unit, a message array unit, a processing thread group and a request processing unit, wherein the message receiving unit comprises a plurality of message receiving channels, and each message receiving channel is used for receiving a messages including at least one service request; the message array unit is used for receiving the messages from the message receiving channels and sorting the messages according to the predetermined rule; the processing thread group is used for receiving the sorted messages of the predetermined number from the message array unit; and the request processing unit is used for acquiring the service requests in the messages from the processing thread group and processing the service requests. Various application programs are integrated into an electronic transaction platform, and the call among all the application programs is implemented through the enterprise service bus; a service user does not need to carry out complicated asynchronous call, and the conversion from a synchronous mode to an asynchronous mode is carried out through the enterprise service bus.
Description
Technical field
The present invention relates to the e-commerce transaction technical field, relate in particular to a kind of a kind of ESB of E-commerce transaction platform and message treatment method of ESB of being applied to.
Background technology
At present, the application integration service between large enterprise's net is complicated day by day, and the system integration of traditional point-to-point formula seems awkward.In order to address this problem, people have proposed ESB (enterprise service bus, abbreviation ESB) notion, each subsystem of promptly forming enterprise network inserts a public information platform in the mode that is similar to connector, relatively independent each other, carry out unified data dispatch by scheduling engine, with high effective integration data and operation flow.Study the definition of being given with Gartner company of consulting firm according to famous IT, ESB is a kind of architecture, utilize Web service, message-oriented middleware, intelligent route and the switch technology of enterprise to realize, be the product that traditional intermediate technology combines with technology such as XML, Web services, ESB provides connection maincenter the most basic in the network.The target of ESB technology is to realize enterprise's application integration in standardized mode, finish interconnected, the intercommunication and the interoperability of business-to-business application system, standardization effort wherein comprises connector standardsization, management standardization, service message standardization and message criteriaization etc.
The appearance of ESB has changed traditional software architecture, can provide than the more cheap solution of traditional middleware software product, simultaneously it can also eliminate the technological disparity between the different application service, allows different application service coordinate operation, has realized communication and integration between the different services.On function, ESB provides the tupe of event-driven and document guiding, and distributed administrative mechanism, and it supports content-based route and filtration, has possessed the transmittability of complex data, and a series of standard interface is provided.For example, application number discloses a kind of implementation method of ESB for the Chinese patent application of " 200810227316.9 ".
Existing E-commerce transaction platform, it is multi-to-multi that the service user directly calls the ISP, chaotic, be difficult to maintenance management is carried out in the service in the row; The degree of coupling is too high between the realization of service call person and backstage service, often pull one hair and move the whole body, how many callers the backstage service has actually, application call which the service unclear cause difficult in maintenance, reliability between service user and the ISP, transaction, synchronous/asynchronous communication, safety certification management all need to realize separately between the two, lack a public architecture; And, lack the unified approach of the backstage service being monitored, added up and provides the analysis data, be not easy to carrying out maintenance management towards the application of the architecture (Service-Oriented Architecture, J is called for short SOA) of serving.
Summary of the invention
The problem that the present invention solves provides a kind of ESB, when being applied to enterprise's electronic trade platform, can realize integrating between the different application programs, the service user needn't carry out complicated asynchronous call, is finished the conversion that is synchronized to asynchronous mode by service bus.
For addressing the above problem, the invention provides a kind of ESB, comprising:
The message sink unit comprises a plurality of message sink passages, and each message sink passage is used to receive the message that comprises at least one service request;
The message queue unit is used for receiving message from described a plurality of message sink passages, and sorts by pre-defined rule;
The processing threads group is used for from the ordering message of described message queue unit reception predetermined quantity;
Requesting processing is used for obtaining service request the described message from described processing threads group, and handles this service request.
Optionally, the described ordering by pre-defined rule is meant that the time sequencing that sends or receive by message sorts.
Optionally, described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described message sink unit after being used for described message split into service request.
Optionally, described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described message queue unit after being used for the message that described message sink unit receives split into service request.
Optionally, described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described processing threads group after being used for the message that described message queue unit receives split into service request.
Optionally, the described request processing unit comprises multiple request processing pipeline, and a kind of service request of pipeline alignment processing is handled in each request.
Optionally, described request processing unit processes service request comprises by predetermined flow process and generates at least one access request, and calls corresponding application service based on described access request.
Optionally, also comprise: request transmits passage, and the access request that is used for generating from the described request processing unit sends to corresponding application service.
Optionally, describedly comprise that the message of at least one service request is encrypted, described ESB also comprises decrypting device, is used for before the described request processing unit is by predetermined flow processing service request described message being decrypted.
For solving the problems of the technologies described above, the present invention also provides a kind of message treatment method of ESB, comprising:
Receive message, each message comprises at least one service request;
Sort by the message of pre-defined rule to described reception;
Service request in the ordering message of processing predetermined quantity.
Optionally, described message comprises at least two service requests;
Described message treatment method also comprises: described message is split into service request.
Optionally, described processing service request comprises: generate at least one access request by predetermined flow process, and call corresponding application service based on described access request.
Optionally, describedly comprise that the message of at least one service request is encrypted;
Before described processing service request, also comprise described message is decrypted.
Compared with prior art, the present invention has the following advantages:
When ESB provided by the invention is applied to electronic trade platform, the service user needn't directly call the service that the ISP provides, the service user is connected with electronic trade platform by standard interface with the ISP, various application programs are integrated in electronic trade platform, and realize calling between each application program by ESB of the present invention, the service user needn't carry out complicated asynchronous call, is synchronized to the conversion of asynchronous mode by ESB.
And ESB of the present invention does not respond surpassing this number of messages by the quantity of the manageable message of processing threads group qualification electronic trade platform, avoids excessive to the pressure that calls of certain service, causes electronic trade platform to work as machine.
Description of drawings
Fig. 1 is the inside structure schematic diagram of the ESB of the specific embodiment of the invention;
Fig. 2 is the configuration diagram of requesting processing;
Fig. 3 is the process flow block diagram of the access request of specific embodiment;
Fig. 4 is the schematic diagram that the ESB of the specific embodiment of the invention is applied to electronic trade platform.
Embodiment
When the ESB of the specific embodiment of the invention is applied to electronic trade platform, the service user needn't directly call the ISP, the service user is connected with electronic trade platform by standard interface with the ISP, various application services are integrated in electronic trade platform, and by ESB realization of the present invention calling to each application service, the service user needn't carry out complicated asynchronous call, is synchronized to the conversion of asynchronous mode by ESB; And ESB of the present invention limits the quantity of the manageable message of electronic trade platform by the processing threads group, do not respond surpassing this number of messages, avoid excessive, cause electronic trade platform to work as machine the pressure that calls of certain service (application service).
With reference to figure 1, the ESB 100 of the specific embodiment of the invention, comprise: message sink unit 110, be used to receive the message that a plurality of service users send, comprise a plurality of message sink passages, be respectively message sink passage 1, message sink passage 2 ... message sink passage n, each message sink passage receives the message that comprises at least one service request; In order to reduce the service user different service requests is operated respectively, comprise at least one service request in a message sink passage, the service user can once propose a plurality of service requests; When the service user once proposes a plurality of service request, by the request packaged unit the back form with message of a plurality of service requests packings that the user carries out is sent, in this specific embodiment of the present invention, described message comprises at least two service requests, described ESB also comprises request split cells (not shown), sends to described message sink unit 110 after being used for described message split into service request; In specific embodiments of the invention, the message sink passage is also by calling ciphering unit, with the message encryption of message sink passage reception.
In another embodiment of the present invention, the message of packing is split also can be before the message sink passage receives message, and described message comprises at least two service requests; Described ESB also comprises: the request split cells sends to described message queue receiving element after being used for the described message that comprises at least one service request split into service request.In other embodiments of the invention, the message of packing is split also can be before processing threads group of received message, and described message comprises at least two service requests; Described ESB also comprises: the request split cells is used for receiving from described message queue unit message, and sends to described processing threads group after the message that comprises at least one service request that described message queue unit receives split into service request.
Requesting processing 140 is used for obtaining service request the described message from described processing threads group 130, and handles this service request; In this specific embodiment, requesting processing 140 comprises multiple request processing pipeline, and each request is handled pipeline and comprised a plurality of requests processing pipelines, a kind of service request of each request processing pipeline alignment processing; With reference to figure 2, requesting processing 140 comprises multiple request processing pipeline, be respectively first kind of request and handle pipeline 10, second kind of request processing pipeline 20 ... pipeline n0 is handled in the request of N kind, each request is handled pipeline and is comprised a plurality of requests processing pipelines, the service request that pipeline can be handled a plurality of same types is handled in every kind of request, handling pipeline 10 with first kind of request is example, and this first kind request handled pipeline 10 and comprised that pipeline 11 is handled in the request of being respectively of a plurality of requests processing pipeline, pipeline 12 is handled in request ... pipeline 1n is handled in request; Described processing threads 130 obtains message from described message queue unit 110, and sends to corresponding request processing pipeline after the Message Processing that splits into service request that will obtain; Need to prove, there is corresponding relation in the kind that described request is handled pipeline with the kind request of service, pipeline is handled in the request of the corresponding identical type of each service request, the service request that comprises in each message will enter the request of corresponding kind and handle in the pipeline, handles the line treatment service request by request.Wherein, in this specific embodiment, each request is handled pipeline and is comprised the deciphering stage (stage), the processing stage (stage), when this, corresponding message sink passage received message in deciphering stage, call ciphering unit to message encryption, the message of encrypting is deciphered by calling decrypting device, in other embodiments, pipeline is handled in each request can comprise the different stages, for example also can comprise decompression phase.In this specific embodiment of the present invention, handle service request processing stage of described and comprise: generate at least one access request by predetermined flow process, and call corresponding application service based on described access request.Wherein, application service is provided by the ISP, call application service by access request, be to generate access request processing stage pipeline is handled in request according to predetermined predetermined flow process, call application service by access request, application service is handled according to access request, generates the result of access request.
In specific embodiments of the invention, ESB also comprises: request transmits passage, is used for addressing, will send to corresponding application service from the access request that the described request processing unit generates.
The above sends a message to the processing procedure of application service for the service user, and application service will return to the service user according to the result that access request generates access request.In this specific embodiment of the present invention, it is opposite with processing procedure that the service user sends a message to application service that the result that application service generates access request according to access request returns to service user's process, at first transmitting passage by request will call information after the application service and send to corresponding request and handle pipeline, after asking the processing pipeline, send to corresponding processing threads with information encryption, request processing thread sends to corresponding message queue with the result of the service request that receives, send to corresponding message sink passage afterwards, when all service request results that comprise in the message return its corresponding message sink passage, message sink passage call request packaged unit, send to corresponding service user after all message packings that will comprise in the message, this moment, the user can obtain the result of the message that sent.Need to prove, be that the message of returning, the path of request when origin are returned in the meaning of this use " correspondence " speech.
Described message among the present invention can be the transaction message of extensive stock, e-commerce transaction with steel is an example, commodity are steel, transaction message comprises the transaction message (corresponding to outbound, the warehouse-in of steel) of issue steel stock, the Transaction Information of contract (corresponding to the purpose of buying, sale), also comprise registration message (becoming the member of electronic trade platform corresponding to registration), new commodity message more, logout message (corresponding to the member who nullifies electronic trade platform), registration updating message (corresponding to upgrading membership information), integration inquiry, credit inquiry etc.
Need inquire about integration with the service user is the example explanation with information relevant with user profile such as credits, the service user sends searching user's information, the message sink passage receives the message of searching user's information in the message sink unit, because user profile comprises information such as integration, credit, the message of searching user's information comprises the integration service request, credit services request etc., with packings such as the integration service request of searching user's information correspondence, credit services requests, send to the message sink passage of message sink unit afterwards; After the message sink passage receives the message of searching user's information, call encrypting module, to this inquiring user message encryption, message with this searching user's information sends to the message queue unit afterwards, also can from the message sink passage, obtain the message of searching user's information by the message queue unit, call request split cells when receiving message in the message queue unit, searching user's information is split into corresponding integration service request, credit services request etc., therefore the inquiring user message that enters in the message queue unit is the service request after splitting, with reference to figure 1, if inquiring user message is corresponding to message 10, then the integration service request is corresponding to service request 11, and the credit services request is corresponding to service request 12; Integration service request afterwards, credit services requests etc. are handled pipeline via the request that enters the service request correspondence behind the processing threads, the integration service request enters the request of integration service request correspondence and handles pipeline, the credit services request enters the request of credit services request correspondence and handles pipeline, for example, the integration service request enters first kind of request in the request processing pipeline 10 and handles pipeline 11, the credit services request enters second kind of request in the request processing pipeline 20 and handles pipeline, handle pipeline to the integration service request by each self-corresponding request, the credit services request is handled the back and is generated access request, with the integration service request is example, the request of integration service request correspondence is handled pipeline and at first through the deciphering stage integration service request of encrypting is deciphered, the access request in integration data storehouse is called in the processing stage generation that enters the integration service request after the deciphering, inquires about integration from database.
The integration service request of above-described specific embodiment the processing stage, do not relate to concrete business, be the inquiry of simple integration, therefore do not relate to operation flow.Electronic trade platform relates to concrete transaction business, must have operation flow, according to predetermined operation flow business is carried out smoothly, and predetermined flow process is finished decision the kind of the message of transaction needs.
Utilize the concrete enforcement of the electronic trade platform of ESB of the present invention must rely on concrete operation flow, to guarantee carrying out smoothly of electronic transaction, can set different operation flows according to concrete transaction, this operation flow is corresponding to intended flow, and this operation flow is stored in the flow process unit, concrete when carrying out service request, according to service request the processing stage demand call operation flow.
With the contract in e-commerce transaction transaction be example explanation operation flow the processing stage effect.Fig. 3 is an operation flow of finishing the specific embodiment of a contract transaction, according to the operation flow of specific embodiment shown in Figure 3, the contract transaction is divided into four kinds of message: be respectively standard contract issue 200, corresponding to first kind of message; Application closing unit association 300 is corresponding to second kind of message; Contract carries out 400, corresponding to the third message; Contract is honoured an agreement and is applied for 500, corresponding to the 4th kind of message; At first the member issues standard contract, and closing unit is bound in application then, after company's audit is passed through, contract just comes into effect, enter the contract that comes into force, can carry out contract then, enter the contract stage in the execution, after contract is finished or carries out to a certain degree, the member can apply for honouring an agreement, and enters the middle contract of honouring an agreement, after contract is fulfiled and finished, enter the contract of honouring an agreement, this moment, contract was finished.At this, be that example describes with the issue contract, for the transaction of other kinds,, can be divided into the message of different kinds according to predetermined flow process according to the kind of transaction.
Describe the implementation process of concluding the business in detail according to the flow performing contract that should be scheduled to reference to figure 3.
When service user's operative norm contract issue 200, this message is a service request, need not again it to be split, in the time of processing stage the operative norm contract gives out information in request processing pipeline, request is handled pipeline and call operation flow shown in Figure 3 from the flow process unit, request is handled pipeline and according to the predetermined rule in the operation flow relevant with the standard contract issue this service request is divided into a plurality of steps, be specially: step 201, check whether contract price is passed through, request processing this moment pipeline calls the contract price in the database, if contract price is passed through, carry out step 202, check whether publisher member's credit is enough, request this moment is handled pipeline and is called credit block, can not issue contract if member's credit is not enough, if member's credit is enough, can issue contract, and generation standard contract member credit takies, revise standard contract member's credit by credit block, carry out step 203 afterwards, generate standard contract, and the result that will generate standard contract feeds back to the service user, finish the service request that standard contract is issued.
Continuation is with reference to figure 3, the manager of electronic trade platform sees the standard contract of issue, want to buy the standard contract of this issue, make it to become when coming into force contract, application for execution closing unit (corresponding to real client) related 300, this is second kind of message, this message is a service request, need not again it to be split, request is handled pipeline and according to the predetermined rule in the operation flow this service request is divided into a plurality of steps, be specially: step 301, service management personnel audit, wherein Shen He content is stipulated according to the actual needs, if audit is not passed through, contract can not related closing unit, and the result that this can not related closing unit is sent to the service user; If audit is passed through, carry out step 302, the service management personnel import contract by hand and estimate that loss takies, and produce related Contract risk credit and take (corresponding member's credit), call credit block this moment simultaneously, by credit block change member credit, enter step 303 afterwards, the service management personnel upload contract textual scan spare, set up real client contract, and simultaneously actual customer contract scanned copy as related contract annex, next enter step 304, produce related contract credit and take (corresponding transaction credit), simultaneously release standard contract credit takies (corresponding to member's credit), and finish take release with member credit to transaction credit by calling credit block this moment, enter step 305, related contract generates successfully, the result of the contract that comes into force, and this result returned.
Continuation is with reference to figure 3, carried out 400 o'clock carrying out contract, corresponding the third message, this message is a service request, need not again it to be split, request is handled pipeline and according to the predetermined rule of intended flow the execution contract that comes into force specifically is divided into: step 401, find goods, after finding goods, contract enters contract in the execution by the contract that comes into force, can call credit block this moment, according to the ratio release portion of execution amount and contract amount or whole related contract credit, and the result sent to the service user by the message sink passage.
When the service user delivers stock, after the consignee receives goods, to carry out contract honour an agreement the application 500, corresponding to the 4th kind of message, this message is a service request, need not it to be split again, and request is handled pipeline and according to the pre-defined rule of intended flow this service request is divided into a plurality of steps and is specially: step 501, company's audit, if audit is not passed through, output is the result can not honour an agreement, if audit is passed through, the release contract is not honoured an agreement and is taken credit, call credit block, finish and discharge contract and do not honour an agreement and take credit, finish the fulfiling of contract after, enter step 502, contract is converted into the contract of honouring an agreement in honouring an agreement; Can call integration module this moment, carries out the examination of contract integration and distribute.
When above-described ESB provided by the invention is applied to electronic trade platform, the service user needn't directly call the service that the ISP provides, the service user is connected with electronic trade platform by standard interface with the ISP, various application programs are integrated in electronic trade platform, and realize calling between each application program (in this specific embodiment be that example describe with the credit block) by ESB of the present invention, the service user needn't carry out complicated asynchronous call, is synchronized to the conversion of asynchronous mode by ESB.
Above-described specific embodiment, be that example describes only with an independent contract information, in instantiation, can there be a plurality of different clients to send information simultaneously, quantity by thread in the set handling sets of threads, make sets of threads once can only handle the message of some threads, avoid excessive, cause electronic trade platform to work as machine the pressure that calls of certain service.
ESB of the present invention is present among the JVM (Java Virtual Machine, Java Virtual Machine).The node of ESB outside is external service user and ISP, has represented ESB to want integrated external entity, and these external entities can be mutual by the service module of various technology and ESB binding.
Fig. 4 is applied to the framework schematic diagram of electronic trade platform for ESB,
Corresponding with above-described ESB, the present invention also provides a kind of message treatment method of ESB, comprising: receive message, each message comprises at least one service request;
Sort by the message of pre-defined rule to described reception;
Service request in the ordering message of processing predetermined quantity.
Wherein, described message comprises at least two service requests; Described message treatment method also comprises: described message is split into service request.
Described processing service request comprises: generate at least one access request by predetermined flow process, and call corresponding application service based on described access request.
Describedly comprise that the message of at least one service request is encrypted; Before described processing service request, also comprise described message is decrypted.
Though the present invention with preferred embodiment openly as above; but it is not to be used for limiting the present invention; any those skilled in the art without departing from the spirit and scope of the present invention; can utilize the method and the technology contents of above-mentioned announcement that technical solution of the present invention is made possible change and modification; therefore; every content that does not break away from technical solution of the present invention; to any simple modification, equivalent variations and modification that above embodiment did, all belong to the protection range of technical solution of the present invention according to technical spirit of the present invention.
Claims (13)
1. ESB is characterized in that comprising:
The message sink unit comprises a plurality of message sink passages, and each message sink passage is used to receive the message that comprises at least one service request;
The message queue unit is used for receiving message from described a plurality of message sink passages, and sorts by pre-defined rule;
The processing threads group is used for from the ordering message of described message queue unit reception predetermined quantity;
Requesting processing is used for obtaining service request the described message from described processing threads group, and handles this service request.
2. ESB as claimed in claim 1 is characterized in that, the described ordering by pre-defined rule is meant that the time sequencing that sends or receive by message sorts.
3. ESB as claimed in claim 1 is characterized in that described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described message sink unit after being used for described message split into service request.
4. ESB as claimed in claim 1 is characterized in that described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described message queue unit after being used for the message that described message sink unit receives split into service request.
5. ESB as claimed in claim 1 is characterized in that described message comprises at least two service requests;
Described ESB also comprises: the request split cells sends to described processing threads group after being used for the message that described message queue unit receives split into service request.
6. ESB as claimed in claim 1 is characterized in that, the described request processing unit comprises multiple request processing pipeline, and a kind of service request of pipeline alignment processing is handled in each request.
7. ESB as claimed in claim 1 is characterized in that, described request processing unit processes service request comprises by predetermined flow process and generates at least one access request, and calls corresponding application service based on described access request.
8. ESB as claimed in claim 7 is characterized in that also comprising: request transmits passage, and the access request that is used for generating from the described request processing unit sends to corresponding application service.
9. ESB as claimed in claim 1, it is characterized in that, describedly comprise that the message of at least one service request is encrypted, described ESB also comprises decrypting device, is used for before the described request processing unit is by predetermined flow processing service request described message being decrypted.
10. the message treatment method of an ESB is characterized in that comprising:
Receive message, each message comprises at least one service request;
Sort by the message of pre-defined rule to described reception;
Service request in the ordering message of processing predetermined quantity.
11. the message treatment method of ESB as claimed in claim 10 is characterized in that, described message comprises at least two service requests;
Described message treatment method also comprises: described message is split into service request.
12. the message treatment method of ESB as claimed in claim 10 is characterized in that, described processing service request comprises: generate at least one access request by predetermined flow process, and call corresponding application service based on described access request.
13. the message treatment method of ESB as claimed in claim 10 is characterized in that, describedly comprises that the message of at least one service request is encrypted;
Before described processing service request, also comprise described message is decrypted.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010197480.7A CN102025653B (en) | 2010-06-04 | 2010-06-04 | Enterprise service bus and message processing method thereof |
| US12/935,239 US8805938B2 (en) | 2010-06-04 | 2010-08-26 | Enterprise service bus and message processing method thereof |
| PCT/CN2010/076364 WO2011150600A1 (en) | 2010-06-04 | 2010-08-26 | Enterprise service bus and message processing method for enterprise service bus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010197480.7A CN102025653B (en) | 2010-06-04 | 2010-06-04 | Enterprise service bus and message processing method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102025653A true CN102025653A (en) | 2011-04-20 |
| CN102025653B CN102025653B (en) | 2014-01-08 |
Family
ID=43866525
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010197480.7A Expired - Fee Related CN102025653B (en) | 2010-06-04 | 2010-06-04 | Enterprise service bus and message processing method thereof |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102025653B (en) |
| WO (1) | WO2011150600A1 (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102868608A (en) * | 2012-09-04 | 2013-01-09 | 江苏大学 | Message mechanism-based enterprise service bus system |
| CN103455366A (en) * | 2012-06-01 | 2013-12-18 | 阿里巴巴集团控股有限公司 | Method and device for calling services of external system |
| CN105872094A (en) * | 2016-05-31 | 2016-08-17 | 山东大学 | Service robot cloud platform interface system based on SOA and working method thereof |
| CN105978968A (en) * | 2016-05-11 | 2016-09-28 | 山东合天智汇信息技术有限公司 | Real-time transmission processing method, server and system of mass data |
| CN106375173A (en) * | 2016-08-31 | 2017-02-01 | 中车青岛四方机车车辆股份有限公司 | Method and device for accessing information system to enterprise service bus |
| CN107102905A (en) * | 2017-04-13 | 2017-08-29 | 华南理工大学 | The platform and platform processes method of big data service based on Artifact |
| CN107277780A (en) * | 2016-04-07 | 2017-10-20 | 中兴通讯股份有限公司 | A kind of broadcast message sending method and device, mobile terminal |
| CN107632894A (en) * | 2017-08-09 | 2018-01-26 | 中国电力科学研究院 | A kind of implementation method and device for power market transaction service call |
| CN108805379A (en) * | 2017-05-03 | 2018-11-13 | 北京京东尚科信息技术有限公司 | Support that multi-mode is honoured an agreement the system and method for flow |
| CN108966190A (en) * | 2018-06-25 | 2018-12-07 | 北京旅居四方科技有限公司 | Water power stake and method, equipment and storage medium for process instruction |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8805938B2 (en) | 2010-06-04 | 2014-08-12 | Xiben New Line Stock Co., Ltd. | Enterprise service bus and message processing method thereof |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1740974A (en) * | 2005-09-14 | 2006-03-01 | 艾默生网络能源有限公司 | A threading scheduling management method and system |
| US20080201719A1 (en) * | 2007-02-20 | 2008-08-21 | Jerome Daniel | System and method for balancing information loads |
| CN101656659A (en) * | 2008-08-19 | 2010-02-24 | 中兴通讯股份有限公司 | Method for caching mixed service flow and method and device for storing and forwarding mixed service flow |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20080076633A (en) * | 2007-02-16 | 2008-08-20 | 삼성전자주식회사 | Method and system for providing service communication in a communication system |
| US8488448B2 (en) * | 2007-09-26 | 2013-07-16 | Verizon Patent And Licensing Inc. | System and method for message sequencing in a broadband gateway |
| CN101651631B (en) * | 2008-08-12 | 2013-01-30 | 新奥特（北京）视频技术有限公司 | Method for message access in system integration of global station network of television station |
-
2010
- 2010-06-04 CN CN201010197480.7A patent/CN102025653B/en not_active Expired - Fee Related
- 2010-08-26 WO PCT/CN2010/076364 patent/WO2011150600A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1740974A (en) * | 2005-09-14 | 2006-03-01 | 艾默生网络能源有限公司 | A threading scheduling management method and system |
| US20080201719A1 (en) * | 2007-02-20 | 2008-08-21 | Jerome Daniel | System and method for balancing information loads |
| CN101656659A (en) * | 2008-08-19 | 2010-02-24 | 中兴通讯股份有限公司 | Method for caching mixed service flow and method and device for storing and forwarding mixed service flow |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455366A (en) * | 2012-06-01 | 2013-12-18 | 阿里巴巴集团控股有限公司 | Method and device for calling services of external system |
| CN102868608A (en) * | 2012-09-04 | 2013-01-09 | 江苏大学 | Message mechanism-based enterprise service bus system |
| CN107277780A (en) * | 2016-04-07 | 2017-10-20 | 中兴通讯股份有限公司 | A kind of broadcast message sending method and device, mobile terminal |
| CN105978968A (en) * | 2016-05-11 | 2016-09-28 | 山东合天智汇信息技术有限公司 | Real-time transmission processing method, server and system of mass data |
| CN105872094A (en) * | 2016-05-31 | 2016-08-17 | 山东大学 | Service robot cloud platform interface system based on SOA and working method thereof |
| CN105872094B (en) * | 2016-05-31 | 2019-01-01 | 山东大学 | A kind of service robot cloud platform interface system and method based on SOA |
| CN106375173A (en) * | 2016-08-31 | 2017-02-01 | 中车青岛四方机车车辆股份有限公司 | Method and device for accessing information system to enterprise service bus |
| CN106375173B (en) * | 2016-08-31 | 2019-08-27 | 中车青岛四方机车车辆股份有限公司 | A kind of method and device of information system access Enterprise Service Bus |
| CN107102905A (en) * | 2017-04-13 | 2017-08-29 | 华南理工大学 | The platform and platform processes method of big data service based on Artifact |
| CN107102905B (en) * | 2017-04-13 | 2020-08-11 | 华南理工大学 | Artifect-based big data service platform and platform processing method |
| CN108805379A (en) * | 2017-05-03 | 2018-11-13 | 北京京东尚科信息技术有限公司 | Support that multi-mode is honoured an agreement the system and method for flow |
| CN107632894A (en) * | 2017-08-09 | 2018-01-26 | 中国电力科学研究院 | A kind of implementation method and device for power market transaction service call |
| CN108966190A (en) * | 2018-06-25 | 2018-12-07 | 北京旅居四方科技有限公司 | Water power stake and method, equipment and storage medium for process instruction |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2011150600A1 (en) | 2011-12-08 |
| CN102025653B (en) | 2014-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102025653B (en) | Enterprise service bus and message processing method thereof | |
| CN102025649A (en) | Message processing method of enterprise service bus | |
| US8805938B2 (en) | Enterprise service bus and message processing method thereof | |
| CN102025650A (en) | Message processing system and message processing method of enterprise service bus | |
| Korpela et al. | Digital supply chain transformation toward blockchain integration | |
| Ovaska et al. | Architecture as a coordination tool in multi‐site software development | |
| CN102025651B (en) | Event-driven method applied to enterprise service bus | |
| CN111800434A (en) | Multi-channel asset docking platform and working method thereof | |
| CN111538757B (en) | Data storage method, query method, device, server and medium | |
| CN103957188B (en) | A kind of enterprises service of symmetrical two-way decoupling describes method and service dispatch system | |
| CN102156944A (en) | Data processing method and system for realizing bank-enterprise interconnection | |
| CN110851865B (en) | Resource data processing method, device, system and storage medium | |
| CN104811475A (en) | Enterprise service bus middleware based on Restful technology | |
| CN102024233A (en) | Transaction processing system | |
| CN111339177A (en) | SAP platform-based data export method and system | |
| CN102025652A (en) | Service bus and message processing method | |
| Ariffin et al. | The design and implementation of trade finance application based on hyperledger fabric permissioned blockchain platform | |
| CN111127211A (en) | Block chain based transaction method, system, device and computer readable storage medium | |
| CN109985390B (en) | Virtual asset management method and system | |
| CN105224594A (en) | A kind of Service-oriented application data interconnection inquiry system and querying method | |
| Ba et al. | Small companies in the digital economy | |
| CN116866340A (en) | Method, device, equipment and storage medium for capacity sharing cooperation based on block chain | |
| KR20120022491A (en) | Management system for fta origin and verification method of origin using thereof | |
| CN1170404C (en) | System and method for provider to transmit data | |
| CN103150171A (en) | Product combination engine device and system and service method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: XIBEN NEW LINE E-COMMERCE CO., LTD. Free format text: FORMER OWNER: XIBEN NEW LINE CO., LTD Effective date: 20120202 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 200437, room 990, 309 East Sports Club Road, Shanghai, Hongkou District Applicant after: West Ben Shinkansen Ltd. Address before: 200437, room 990, 309 East Sports Club Road, Shanghai, Hongkou District Applicant before: XiBen New Line Stock Co.,Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 200437 HONGKOU, SHANGHAI TO: 215434 SUZHOU, JIANGSU PROVINCE |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20120202 Address after: 215434 No. 88 Binjiang Avenue, Taicang Port Development Zone Applicant after: XiBen New Line Stock Co.,Ltd. Address before: 200437, room 990, 309 East Sports Club Road, Shanghai, Hongkou District Applicant before: West Ben Shinkansen Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140108 Termination date: 20180604 |