 Forum main
page
Most
active member
Login page
Register
Log out
Search page
View our event calendar
Add general event such as an upcoming
software release or conference
View all birthdays
Public image gallery
Upload your images in your profile
Profile editing page
Subscription list page
Address book page
Member list page
View the
most active member
User groups listing
Private message page
|
Request Response Receive and Solicit Response Send Ports-Can they be linked without orchestrations?
View related threads:
(in this forum
| in all forums)
|
Logged in as: Guest
|
|
Users viewing this topic: none
|
|
Login  | |
|
Request Response Receive and Solicit Response Send Port... - 5 February 2008
|
|
|
dino
Posts: 2
Score: 0
Joined: 5 February 2008
Status: offline
|
I am implementing a BizTalk 2006 R1 two way interface between two HL7 systems. The source system generates a query which is forwarded to BizTalk. BizTalk waits for a reply from the destination systems and sends the response back down the originating connection.
I can bind the request response receive port and solicit response send port to an orchestration, but its too slow. 4 seconds to be precise. I can probably shave a couple of seconds if I tried but would it not be faster if orchestrations were not required?
Therefore I want to have a two way request response receive port to receive the query messages on, a solicit response send port which sends the query message, waits for a response and then somehow routes the response message back to the initiating request response receive location.
Can it be done? What is the trick?
Any ideas appreciated.
Dino
|
|
|
|
|
RE: Request Response Receive and Solicit Response Send ... - 11 February 2008
|
|
|
dino
Posts: 2
Score: 0
Joined: 5 February 2008
Status: offline
|
To answer my own question yes this can be done without an orchestration. The end Point Manager EPM is smart enough to route the message back to the publisher of the original message. The send port needs to subscribe to the message received from the two way receive location which it will route back to the receive location using an internal property called epmRRCorrelationToken. Clever! Hope this helps someone out there.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version
Email TopXML