Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>BizTalk communicates with the outside world through artefacts called <strong>adapters</strong>, which can provide an endpoint visible to the outside world over a wide range of messaging protocols.</p> <p>There is an MSMQ adapter, which seems to be able to read from and publish to queues on either the local computer or a remote computer. I've never used it, so I'm coming from a position of reading the <a href="http://msdn.microsoft.com/en-us/library/aa561354.aspx" rel="nofollow">docs</a> on this adapter and finding out as I go along. I've found the BizTalk documentation to be particularly difficult to navigate, particularly as a lot of the microsoft links now go nowhere in particular - it took a little while to find these pages I've mentioned. Do let me know if you find anything kicking around that's not obvious as I'm sure there are useful resources I've never been able to find.</p> <p>To configure BizTalk to listen to a queue:</p> <ul> <li>Create a One-Way Receive Port</li> <li>Create a One-Way Receive Location associated with that port</li> <li>Set the receive location's transport Type to 'MSMQ'</li> <li>Click 'configure'</li> <li>Specify the credentials to use and the queue name (which includes the machine name, implying that it works equally well on remote queues)</li> <li>Set the other properties appropriately to your scenario</li> </ul> <p>That <em>should</em> be all there is to it. Publishing to that queue should then cause a message to be received on that port, which immediately persists it to the message box database. You'll have to do some processing using pipelines and/or maps in order to do anything useful with the message.</p> <p>However, you are by no means limited to MSMQ. A <a href="http://msdn.microsoft.com/library/aa578103.aspx" rel="nofollow">pretty comprehensive list</a> is available, and BizTalk doesn't constrain you to any particular messaging protocol. You can also implement custom adapters with whatever behaviour you need. In order to answer your question more usefully, it'd be helpful to know what your real requirements are - what's the use case for the client application, for example?</p>
    singulars
    1. This table or related slice is empty.
    1. POSending message directly to BizTalk or via MSMQ?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTom W
    1. USTom W
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've tried to be more specific in the update of the question.
      singulars
      1. PO
      1. USdragan.stepanovic
    2. COThanks. That makes the situation a bit clearer. I believe what I've already posted answers your question - you can use a receive port with an MSMQ adapter to receive messages from a queue on either the local or a remote machine - although I'm a bit hazy myself on the details of how exactly you set those up.
      singulars
      1. PO
      1. USTom W
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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