Thursday, July 15, 2004

Using a Map with Large Messages 

I was intrigued the other day about how maps were behaving in BizTalk Server 2004 with regard to potential memory problems. BizTalk Server 2004 gives us great large message support through streaming messages into the message box. However, what if we specify a map in the Receive port, or indeed anywhere in BizTalk (Orchestration or Send Port)?

Well, BizTalk implements maps as XSLT stylesheets, and the way I understand it, the code uses the XslTransform class to perform the transformation and will load the input message into the DOM. This will require a significant memory footprint if the message is large!

This is often overlooked and is worth pointing out...

Wednesday, July 14, 2004

Fed up of deploying BTS assemblies the 'standard' way? 

Well, this is a little tip about deploying a BizTalk assembly quickly and easily without having to unbind, undeploy, redeploy, rebind and all that wonderful stuff.

If you recompile a BizTalk assembly that does not affect the current bindings then all you need to do is the following:

  • Open a view onto the GAC by clicking Start->Run and then typing assembly
  • Compile BizTalk assembly
  • Drag and drop the compiled assembly from the bin\Development folder (we're developing, right?) into the assembly view window
  • Restart BizTalk NT service from BizTalk Administration snap-in, Services snap-in or the command line using net stop

It really is as simple as that!

DNJ Interview with Solidsoft CTO Andy James 

Ok, ok, so he's my boss ;-) Still, it's a good article about BizTalk and SOA from someone who's been about, if you know what I mean ;-)

DNJ Interview Link

Monday, July 12, 2004

Integration Patterns 

Microsoft has released a whole set of integration patterns here as part of their Platform Architecture Guidance (PAG) efforts.

Well worth a browse!

One-Way Web Methods 

I made quite a cool little discovery the other day with OneWay web methods in ASP.NET. When I hooked the web service up to my orchestration, I discovered that BizTalk had actually taken the OneWay interaction style into account and only offered a request message type, rather than both a request and response message type.

Many people probably know this already, but I found this to be really cool! How many times have I hooked up a web service with an orchestration and ignored the response because the method does not return any value?! More times than I care to remember...

About the Author

You may be wondering who I am (or may not!), but I've been in the industry 16+ years working on a variety of systems from IBM mainframes as a CICS systems programmer, to developing on Unix and Windows based systems. At the moment, I'm currently working for a Microsoft Gold Partner in the UK called Solidsoft who specialise in systems integration using BizTalk Server. My position is generally dictated by what I'm doing, but normally as a solutions architect/consultant helping clients with their integration projects involving, yes you guessed it: BizTalk Server.

Disclaimer: all the views expressed here are my own and do not necessarily represent the views of Solidsoft Ltd or indeed any other company.