BizTalk ChalkTalk : Troubleshooting Common Problems in a BizTalk Server 2004 Platform Installation

BizTalk ChalkTalk : Troubleshooting Common Problems in a BizTalk Server 2004 Platform Installation

A fellow Innovative Architect was running into problems installing BizTalk 2004 on Windows XP. This article may be useful in troubleshooting what is going on. The best part is that it covers what software different services in BizTalk are dependent upon. This is important in relation to Windows XP installations because SharePoint will not run on Windows XP. This means that BAS and HWS cannot be installed on Windows XP.



Google Groups : microsoft.public.biztalk.general

Google Groups : microsoft.public.biztalk.general

This news post describes a very similar format that I have to follow to commicate with Freddie Mac’s Desktop Underwriter system. It looks like I will be writing a custom adapter to handle this (ugh!).

I may be using this:
GotDotNet User Sample: Biztalk Server Adapter Framework 1.1 with VB.NET support FINAL

This link may be useful to me in this process as well:

More to come…


Matt’s Musings on Messaging – Send XML to a SQL stored procedure (RELOADED)

Matt’s Musings on Messaging – Send XML to a SQL stored procedure (RELOADED)

This sample looks promising. I need to do some fairly complex CRUD operations on a table to keep track of attributes related to a business transaction. Instead of separating create/update/delete statements into separate ports, I want to do it all at once using an xml fragment that I will parse in a stored procedure.

I would use an update-gram, but the only output generated is a “success” message. I want the flexibility of returning the table data post-update back to biztalk. This requirement is not supported in an update-gram.


XSL Transformations

XSL Transformations

This is a really good resource for xsl transformations. One of the useful things to me is the section about using xsl:element and xsl:attribute when transforming from xml to xml.

I had an interesting case where I needed to transform an “extensible” database model into a more usable xml structure.

This is the original output of a SQL Server stored proc using For Xml Auto:

<transaction transactionid=”1″>
<vendor vendordescription=”DU”>
<status statusdescription=”Created”>
<transactionattribute attributeid=”1″ attributekey=”TestAttribute1″
attributevalue=”TestValue1″ attributedatatype=”String”>
<transactionattribute attributeid=”2″ attributekey=”TestAttribute2″
attributevalue=”TestValue2″ attributedatatype=”String”>

I needed the output to be in a format somewhat like this:


So, to accomplish this I created this xsl transformation script:

<?xml version=”1.0″ encoding=”ISO-8859-1″ ?>
<xsl:stylesheet version=”1.0″ xmlns:xsl=””&gt;
<xsl:output method=”xml” indent=”yes” omit-xml-declaration=”no” />
<xsl:template match=”/”>
<xsl:element name=”TransactionID”>
<xsl:value-of select=”//Transaction/@TransactionID” />
<xsl:element name=”VendorName”>
<xsl:value-of select=”//Vendor/@VendorDescription” />
<xsl:element name=”Status”>
<xsl:value-of select=”//Status/@StatusDescription” />
<xsl:for-each select=”//TransactionAttribute”>
<xsl:element name=”{@AttributeKey}”>
<xsl:value-of select=”@AttributeValue” />