BizTalk

BizTalk is Microsoft's message-based middleware offering. It provides a framework to build Enterprise Application Integration (EAI) and Business-to-Business Integration (B2Bi) solutions. Other similar, but much more expensive, competitors include Tibco and Vitria.

BizTalk Standard verses Enterprise

When determining infrastructure requirements for a client often the question of whether to use BizTalk Standard or BizTalk Enterprise comes up. If the client is a small enterprise with limited redundancy and scaling needs the Standard Edition of BizTalk should work fine. If the client requires any redundancy or scaling then Enterprise is almost certainly necessary. In other words if your requirements dictate that you require more than one BizTalk server you will need the Enterprise Edition of BizTalk...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Orchestration Designer Crash

I recently encountered a troubling problem while creating a BizTalk 2006 R2 solution. Everything was working fine until I tried to open the Orchestration Designer to edit one of the orchestrations I had been working of for a couple of days. Visual Studio crashed immediately. I tried a few things, but I could not open any orchestration without Visual Studio crashing (no errors in event log, no dialog, nothing...). I finally fixed it by backing up and deleting my Visual Studio profile. The profile...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Orchestration Breakpoints Lock Assemblies

When using orchestration breakpoints, make sure you clear them all when you want to build and redeploy the solution. Any existing orchestration breakpoints will make it impossible to unload the associated assemblies from the GAC. As long as there are any breakpoints in an orchestration the updated assemblies will not be used. This is really a bug and should be addressed
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

WCF Bad Message

When creating a web service using the WCF-BasicHttp adapter, make sure that you adjust the “Maximum received message size” binding configuration to jive with the size of the message you expect to hit the service. If a request is made to the web service that contains a payload that is larger than this setting, an HTTP 400 (Bad Message) error will be generated. The default maximum size is 64K, which seems a bit small...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Interesting BT, WCF, WF Posts

Tomas Restrepo has created a couple of excellent articles about the future of BizTalk, WCF and WF. http://www.winterdom.com/we... http://www.winterdom.com/we...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

BizTalk and SSIS

I’ve been interesting in using SSIS ever since I first heard about it. Since I specialize in doing integration work, primarily with BizTalk, I was curious about this new “Integration Services” component of SQL Server. I was a little bit worried that it would supplant BizTalk for a lot of integration scenarios (worried since I’ve invested so much time understanding BizTalk). Since SQL2005 was released I have had a chance to read a lot more about SSIS and also to use it in a couple of projects. I am...
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati