Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

Accessing envelope values using BizTalk EDI

I recently received this question by email and I figured I would address this as a blog post.

"I have a 1000+ TP Environment who do Medical billing with us. I have custom envelope values for each of them. I need dynamic routing of messages to them
1. Receive EDI File
2. Custom Promotion of thier ISA and GS Values in Recv Pipeline
3. No Orchestration
4. Custom Send Adapter [determine their end point file UNC]

I am missing the place where I can wrap his outbound message with his Envelope values?

I am not sure I fully understand the question but I can suggest some products that do EDI well. It really depends on what version of BizTalk you are using. If you are using the Base EDI adapter in BizTalk 2006 R1, then you will have to write a custom pipeline component that parses your EDI files and promotes the ISA, GS, and ST segment values. In my search, I found a custom solution which is a replacement of the EDI stack in BizTalk 2004/2006. I was unable to find the original author or site where I found this code. You can download it from here. Please use this code at your own risk.

If you are using BizTalk 2004, then I would highly recommend the Covast EDI Accelerator. This accelerator has a cost but it contains a lot of functionality.

If you are really looking to build a robust solution without any accelerators, then I would recommend BizTalk 2006 R2. R2 has native support for EDI and AS2. Check out the following post to see a comparison of all the features in the recent BizTalk versions. You can also download a CTP of BizTalk 2006 R2 from


August 19, 2007 Posted by | Uncategorized | , | Leave a comment

Using Fiddler2 with BizTalk HTTP Adapters

Fiddler2 is a great tool to use when you need to monitor or debug your HTTP traffic between any two endpoints. In fact, it automatically starts monitoring your Browser traffic when you start it up. It is especially helpful when you need to debug HTTP calls from BizTalk. However, you will notice that Fiddler will not automatically capture BizTalk’s traffic. Fiddler acts as a proxy which routes all your HTTP traffic from programs that use the WinInet HTTP module. IE, Microsoft Office and a number of products use WinInet. However, BizTalk does not use WinInet. So you need to tell BizTalk to route all traffic through fiddler. This can be done one of two ways:

1. Configure the proxy on the Send Handler of the HTTP-based adapter

Send Handler Proxy Configuration

Note that the port number is 8888. This is Fiddler’s listen port (see below). This option requires you to restart the host that this handler belongs to.

Fiddler Options

2. Configure the proxy on a send port of a HTTP-based adapter

Send Port - Proxy Configuration

August 16, 2007 Posted by | Uncategorized | | 1 Comment