Browse by Tags -

Browse by Tags

XmlDisassemble in a passthrough pipeline?

So, I a couple of weeks ago now I opened a case on Connect , and this is just to wrap it up in a blog-post for discovery and archive purposes. Background We use BAM for infrastructure tracking. We apply a simple tracking profile to all our ports for all our customers in all our environments. BAM does...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Sat, Sep 11 2010
Pure Messaging Acknowledgements - Follow up

This post is a follow up to my previous post Delivery Notifications outside Orchestrations - a pure Messaging approach . The sole reason for this is to provide a downloadable demo and a walkthrough of that. The demo features a solution with one pipeline component and one passthrough pipeline using the...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Sun, Apr 20 2008
Consuming pipeline issue fix for BizTalk 2006

I previously blogged about an issue I was experiencing building a custom pipeline component in BizTalk Server 2006, and that I had found it was fixed and was not longer an issue in R2. Now there is a KB ( KB941802 ) out that deals with a fix for that problem in 2006. I think the description of the problem...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Fri, Apr 18 2008
Delivery Notifications outside Orchestrations - a pure Messaging approach

Scenario You have a pure messaging solution (no orchestrations) and you wan't to be able to keep track of messages delivered to their destination by send ports and adapters for internal logging purposes. That is, you want delivery notifications, or acknowledgements, that a message has been successfully...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Mon, Mar 31 2008
Removing Xml Namespace in a pipeline component

Richard Hallgren recently blogged about how to remove Xml namespaces from Xml documents , as has Kirk Allen Evans earlier here and here . While the latter writes from a general .NET and ASP.NET perspective Richard's post is from a BizTalk perspective and in his post he asks for alternative ways,...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Mon, Jan 7 2008
Consuming Pipeline Component issue fixed in R2

I previously experienced an issue with a general purpose (not an assembler/disassembler) consuming pipeline component in BizTalk Server 2006. For those of you unfamilliar with the term a consuming pipeline component is just that, a component that consumes the messages and returns null to stop pipline...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by logical on Sat, Jan 5 2008
Custom Pipeline Components Development Best Practices

There is much to be said about pipeline component development. Online, in the helpfiles, in books there are step by step guidance on how to build pipeline components of different types (Assembers, Dissassemblers, General Purpose etc.). I'm not going to repeat any of that. Instead I'm going to...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Wed, Jan 2 2008
Visualizing the benefit of forwardonly streaming in custom pipeline components

When doing custom pipeline component development you need to be aware of the forward-only streaming best practice. In short this means developing your pipeline components so that they do their logic either as a custom stream implementation or by reacting to the events availble to you through the Microsoft...

Posted to Be Logical - writings by Johan Hedberg (Weblog) by Johan Hedberg on Thu, Dec 20 2007

Page 1 of 1 (8 items)