I’ve had an interesting discussion this week with some of my fellow BizTalk MVPs
and also a few MS folks.
Here’s the crux of my beef.
1. Stop a Send Port or Orchestration – it is still Enlisted but
in the Admin Console it’s stopped. (at this stage – you’re stopped and my ‘stopped’
are the same)
2. Shoot a message into BizTalk destined for the stopped Send Port or grab one of
the queued up Suspended-Resumable messages and say “Resume” (mind
you, you do have other options here of Resume in Debug Mode etc)
3. Guess what happens?? BizTalk Queues the message up as it knows the corresponding
Send Port is stopped???? NO!!!!! BizTalk will send the message through the
STOPPED send port – (bang head against wall)
4. This ‘feature’ IS useful for when BizTalk receives a flood
of msgs and an issue arises downstream (backend system or so) and you can ‘trickle
feed’ A msg to the back end system.
5. I think this functionality should be tied into some sort of ‘Resume for Debug’
type wording. Something to indicate that it’s an ‘unusual’ circumstance.
6. The terminology within the Admin Console is what I have an issue with. The port
is Stopped, an NT Service is STOPPED, an application is ‘stopped’ –
so these terms of stopped differ in the biztalk world.
7. Outcome of the week’s discussion: MS are looking into changing the terminology
within the Admin console. 