posts - 13, comments - 27, trackbacks - 0

My Links

News

Archives

BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

Moved to here.

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Print | posted on Tuesday, February 24, 2009 10:55 AM |

Feedback

Gravatar

# re: BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

You inspired me to finally sit down and write this blog: http://www.quicklearn.com/blog/post/ESB-Guidance-20-Build-Loosely-Coupled-Solutions-You-Can-Be-Proud-Of.aspx

It offers another way of going about the same thing that is now built into the ESB Guidance CTP.
2/26/2009 10:38 PM | Nick
Gravatar

# re: BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

Very glad to see that support for server side itineraries is included in 2.0. Do you know of any plans to support dynamic changing of itineraries by services invoked along the way?

For example if a message came in & was assigned an itinerary of A -> B -> C, are there any plans to support service B being able to modify the itinerary to run Step D before proceeding onto C (resulting in that message following an A -> B -> D -> C path)?

If not are there any recommendations on the best way to do that?

Thanks,

Tim
8/26/2009 2:31 PM | Tim Weisbrod
Gravatar

# re: BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

Tim,

If you're interested in dynamic itineraries, you should check out Brian Loesgen's post here: http://www.brianloesgen.com/blog/2009/7/23/two-new-esb-toolkit-videos-now-live.html. It details the use of the BRI resolver, which I think does what you need.

Bram.
8/26/2009 2:45 PM | Bram Veldhoen
Gravatar

# re: BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

Bram, I can't download your samples ?

Hooman
9/3/2009 11:59 AM | Hooman
Gravatar

# re: BizTalk ESB Guidance 2.0 - Fixing the Itinerary OnRamp?

Hooman,

You can find the pipeline component also in the ESB.Extensions, see here: http://esbextensions.codeplex.com/.
9/11/2009 9:18 AM | Bram
Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification:
 
 

Powered by: