Use BizTalk with NetMsmq binding to asynchronously call IIS WCF service with WAS

Question

I have a thought. There is, of what I know of, no easy way, without implementing workaround with orchestrations, to call a web service one way (no response required) asynchronously from BizTalk.

We have instead solved this with msmq as middleware and a windows service listening on the queue and then calling the web service.

Windows services isn't very intuitive to deploy and monitor so I've been thinking about replacing the windows service by using WAS, IIS and NetMsmq binding to trigger IIS to get the message from msmq and deliver the it to the wcf service. The only backside with this of what I know now is that you must name the msmq-queues according to the path from the root to the wcfservice (eg: WcfServices/MyWcfService.svc).

Are there more disadvantages with this approach? Is this a wrong approach to solve this issue? In that case why and how would you have done it instead?

Regards

Mikael

Integration developer

Answer 1

Hi,

How did you send message to MSMQ from BizTalk? Since it is an one way operation, Biztalk does not expect a reply, why can't you send message to WCF service directly instead of MSMQ?

Answer 2

Hi,

How did you send message to MSMQ from BizTalk? Since it is an one way operation, Biztalk does not expect a reply, why can't you send message to WCF service directly instead of MSMQ?

Hi, thanks for the reply

BizTalk sends the message to MSMQ via the MSMQ-adapter.

If BizTalk sends the message to the wcf service directly then we will loose the asynchronous behavior. Ex: If BizTalk sends messages directly, via wcf, to System A. That would mean if System A doesn't respond for some reason we would get suspended messages. We want BizTalk to retry but that would mean dehydrated orchestrations which we don't because it would mean trouble for the operation personal who might want to stop an entire application during installation.

/Mikael