Databases
StackOverflow2013
Postsdbo
POSending message directly to BizTalk or via MSMQ?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSending message directly to BizTalk or via MSMQ?
    text
    copied!<p>This is the first time I'm using BizTalk for cross-machine, asynchronous, reliable communication.<br> I would like to know is there a way to directly send messages from one machine to BizTalk queue or I have to use local MSMQ which in turn sends messages to BizTalk?</p> <p>In C#, is there a binding that is used in order to send messages to BizTalk queues?<br> For MSMQ I know that there is NetMsmqBinding. </p> <p>Cheers</p> <p><strong>Update:</strong></p> <p>Since I've introduced a bit of confusion, I'll try to explain a bit and please correct me if I'm wrong.<br> As far as I know, ESBs implement the concept of queues or message channels that can be used for reliable, asynchronous communication (messaging in short). Now, I'm having difficulty placing BizTalk into this concept. There are dozens of interpretation of ESB concept and same number of opinions on if BizTalk is an ESB, like Sonic or TIBCO...<br> Now, as far as I know, for example in TIBCO which implements JMS API, there are no queues or queueing services on local client machine (e.g. MSMQ), but they are present and configured on TIBCO ESB and from client app I use JMS API to send messages to these queues.<br> So when I want to communicate via BizTalk with apps on different machines and I want to use messaging, I'll be using MSMQ on local machine and MSMQ will transfer these messages to BizTalk and other apps downstream?<br> Also, where should I configure the communication between local MSMQ and BizTalk? Should I configure BizTalk to listen to a given MSMQ for new messages or there is some configuration that should take place on MSMQ itself, as well?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload