05-13-05 12:49 PM
Do you actually have the receive location that is using MSMQT bound to an
orchestration that is started?
"Das Bose" <FakeAddress@No_where.net> wrote in message
news:45229B5E-01C2-4C9E-BC17-094D71E5BE96@microsoft.com...
> I've been trying since FOREVER, but I can't get my orchestration to
> receive a
> message using MSMQT. it runs great if I receive it as a file drop, but I
> get
> this message when trying to send it to the Q:
>
> MSMQT failed to publish the message coming into the queue
> DIRECT=OS:jjjohnson\Private$\MyQueue, because no consumer was waiting for
> it.
>
> What does this mean??? Some on the web say that is in reality rejecting
> the
> xml as invalid. The same xml works fine as a file drop.
>
> I can't seem to find any definitive tutorial on simply receiving a msg via
> MSMQT.
>
> All I want to do is this:
>
> 1. A remote client sends a message to the Q. The remote client is using
> System.Messaging namespace, and is sending the message as string after
> reading it from the file.
>
> 2. The orchestration receives the message from a receive port using the
> MSMQT adapter and triggers the orchestration.
>
> Sounds simple, but it has eluded me for several days. What articles I
> have
> found seem to indicate that MSMQT is used to guarantee the file gets
> dropped
> in a folder, so that in the end I end up using a file drop to receive the
> xml
> doc anyway. This can't be right...
>
> Please help because we have a major B2B integration to do. We have an
> existing WS endpoint that the partner calls. The WS then drops xml docs
> in a
> queue for processing by custom components. We want to re-use this
> existing
> endpoint, but let BizTalk perform the transformations and integration
> logic.
[ Post a follow-up to this message ]
|