XML from the Coffee Shop

The 'not-so-very' Recoverable Interchange in BizTalk 2006 explained

Tue, 19 Jun 2007 15:17:04 GMT

Richard (Blewett) and I have talked about this subject often. Richard has finally found the time to write down what's wrong with the current implementation of 'Recoverable Interchange'. No, it's not the pipeline, messaging engine or adapter at fault. It's the XMLDisassembler!!!

Accessing Context Properties from within a map in BizTalk

Thu, 01 Feb 2007 16:00:36 GMT

It's been a while, but i hope this will make up for being quiet again. I've run across the question many times, but never found the time to really dive into it. Now that time was found. And attached is the result. It is not a 100% clean construct because BizTalk really tries to do its best to disallow access to internal classes and runtime. However, utilitzing some thread local storage and (what i think is) a reasonable assumption, this functoid is actually able to retrieve any of the message context properties in a receive port (no orchestrations required) ContextAccessor.zip (255.35 KB)

BizTalk Server 2006 RTM

Tue, 28 Mar 2006 10:26:44 GMT

The wait has been long and difficult, but it is here.... right now!

BizTalk Server 2006 has gone RTM.

For universal subscribers

Now... the waiting for 2008 starts ;)

Guerrilla Biztalk 2006 planned in London too!

Wed, 31 Aug 2005 13:45:04 GMT

I already notified you of the upcomming Biztalk 2006 @ Microsoft. I'm happy to announce the European version is now also planned and availalbe for registration.

Schedule date is November 2005 in London!

Hope to see you all there.

Biztalk 2004 and the Eventlog

Fri, 19 Aug 2005 10:56:22 GMT

I've now come across several issues, like the BizTalk service restarting all the time or not being able to run configureFramework.exe correctly.

After some searching & spelunking(tm) I've found the NT Eventlog to be the culprit!

As we all know Biztalk dumps tremendous amounts of logging information into the NT Eventlog. In certain circumstances (like configuring & un-configuring a number of times) the eventlog might run into its configured limit. When this happens Biztalk kind of chokes.

The error of not being able to write to the eventlog, is being written to the NT eventlog.

Ehhh.. anyone got a problem with that?

Just remember to set up your development system using a 'overwrite when needed' configured NT Eventlog

'RSS Feed usage' continued...

Sun, 10 Jul 2005 18:51:30 GMT

In one of my previous posts i mentioned an idea about using a tool i'de read about, using an RSS feed representing the eventlog. This was based on my thoughts on BizTalks 'report in NT Eventlog' behaviour.

This weekend i was together with a number of my friends and was pointed to a post from Dominick which presented the same link.

I now have to admit to either 'trying to highjack his post' or 'not being up-to-date' with it. I think i'll tell the truth this time and say; it is the latter. Sorry Dom!

Fun part is thinking about how we both thought of the use at almost the same time.