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
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…
You cannot use a pass-through pipeline to receive a file in an orchestration in BizTalk Server 2004
This is an interesting issue. It doesn’t make sense to use the xml receive pipeline to receive a flat-file, but there it is…
Handling Default Namespaces
This article was useful to me in figuring out how to use default namespaces in xslt stylesheets.
MCSD for Microsoft .NET Certification Requirements
Innovative Architects gives bonuses and gets Microsoft Partner points for employee certifications. I want to keep track of this page because it is likely to be the track I would take to Microsoft Certification.
Visual Studio 2005: Technical Resources for Visual Studio 2005
I loaded a virtual pc with VS2005 Beta 2. I’ll be coming back to this site to get some guided tours of new features.
I watched this webcast and was impressed with it:
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.
XSD Object Code Generator
This tool generates a MUCH better class representation of an .xsd schema. The output is a lot easier to consume than the output generated by the default xsd.exe tool that ships with .NET. I wish that the project I am currently working on had used this tool instead of xsd.exe to generate the classes being used.
XML – Prefix problem with XML/XSL
I was running into a little bit of a snaffu with using custom xslt in a BizTalk map. All I had to do was reference the appropriate namespace in the map and voila! If only I had discovered that three or four hours ago! :o(
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:
<transactionattribute attributeid=”1″ attributekey=”TestAttribute1″
<transactionattribute attributeid=”2″ attributekey=”TestAttribute2″
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=”http://www.w3.org/1999/XSL/Transform”>
<xsl:output method=”xml” indent=”yes” omit-xml-declaration=”no” />
<xsl:value-of select=”//Transaction/@TransactionID” />
<xsl:value-of select=”//Vendor/@VendorDescription” />
<xsl:value-of select=”//Status/@StatusDescription” />
<xsl:value-of select=”@AttributeValue” />