I removed the SOAP header envelope with simple string manipulation and was left with an Xml response that I could then load into an XmlDocument type.

The Xml message was then used as the source to a custom XSLT map which did not work properly even though in unit testing the map worked fine.

I removed carriage returns and line feeds from the original string but that did not help either.

Only after indenting the xml string (using System.Xml.Formatting.Indented) and then loading the string into an XmlDocument did the map finally work.

Hope this helps someone else with a similar issue.

Figure 1 is an image of the visio diagram for the production environment.

Production

Figure 1.

Figure 2 shows a BizTalk Server with IIS shape.

Figure 2.

Visio can retrieve the server data from a sharepoint list and link the data to the server shapes by a simple drag and drop process. You can manually refresh the data from the sharepoint site or schedule an automatic update.

I created 2 visio shapes, one for BizTalk Server and one for BizTalk Server with IIS, to more quickly convey the server landscape for each environment.

You can download these 2 shapes from here. The download file is a .vss file but for some reason it appears as a .vsd file in the download dialog box. Just change it to .vss before saving it to your hard disk.

To retrieve the Most recent 100 service instances use the query shown in the sceen shot below (Search for Tracked Service Instances).

Most Recent 100 Instances

The HAT is still used to to display the Message Flow and Orchestration Debugger when right clicking on a service instance in the above screen shot.

You can still bring up the HAT at the command line  as shown below(replace the MgmtSvr and MgmtDb with the appropriate values).

“C:\Program Files\Microsoft BizTalk Server 2009\”BTSHatApp.exe btshat: MgmtSvr:CSI00SRV01 MgmtDb:BiztalkMgmtDb

Command Line

But only the File and Help menus appear. The Reporting, Queries and Tools menu do not appear. Apparently, you can only invoke these functions from the Admin Console.

HAT

When we tried to bind a one way send port to the orchestration it did not show up in the drop down list of available send ports to bind to. Apparently Biztalk was expecting a two way port perhaps because the first operation was two way.

Anyway, I had to create a new wsdl that contained only the one way operation, set a web reference to that wsdl in the orchestration and then I could bind the one way send port to the orchestration.

The code supports both single and multiroot schemas.

BTSchemas

Download the code from here