If you are pulling your hair out wondering why you followed the tutorial to the letter and yet things aren’t working as it should be, here is Lisa’s Blog site that provides the latest updates to the tutorial. Please make sure you download the latest tutorial from MSDN site instead of using the out-of-dated one comes with BizTalk installation. Trust me this will save you a lot of sleepless nights.
This tool examines a BizTalk Server 2006 deployment and generates a list of best practices issues it discovers. I haven’t tried, but it should be very useful if it works as advertised.
Microsoft just released a new document to help developers with programming issues within a BizTalk application.
It contains 120 (!) pages of useful info about every aspect of BizTalk – including best practices. Additional info about the document is available here and here.
After scanning it over, I found several topics that are still missing. I guess that’s OK as it leaves me with material I can add to this blog : )
I am a late bloomer to blogging, but have realized that I do in fact have something to say on such subjects as BizTalk Server and SharePoint Technologies – and how to make these things work. So, if you share an interest – stay tuned.
However, not all blog entries need be original, right? So let’s start with someone else’s good idea.
Today, I tried to find some solutions for initializing a Multi-Part Message within an orchestration. We’ve all called a SQL Stored Procedure from within an orchestration. But why can’t you simply construct the Request/Response message with a Message Assignment Shape? It appears that this is not easy to do, because of the nature of multi-part messages. One can use a map to construct the message by simply setting default values within he map, but this seems like egregious overkill.
Recently, a client of ours was running into a problem with our SQL Receive Locations being automatically disabled by BizTalk 2006. This happened whenever the IT admins took down the SQL 2000 servers and/or the network for maintenance.
Some background: BizTalk 2K6 is used in an integration solution that requires querying a SQL 2K database for new records. Due to requirements of the system, the data needs to be pulled every 15 seconds.
The problem is when BizTalk receives 5 errors in a row trying to retrieve data from the SQL data source – when this happens, BizTalk will disable the receive location and generate an error in the event log.
Since we poll the SQL server every 15 seconds, this results in the receive location being disabled anytime the server or network is down for over a minute. And since the client hasn’t implemented event log monitoring, an entire weekend would go by before anyone would notice that…
It’s that time of the year again where we get to help clients understand what BizTalk Server can do for them. As part of the Tallan Fall Seminars series (http://www.tallan.com/fallseminars/) we will be giving seminars on SOA and BizTalk Server 2006 at Microsoft’s Manhattan offices on Oct. 17 and a TBD venue in Hartford on Oct. 19. The seminars will cover the basics of BizTalk Server for developers with an architecture overview and live demos. These seminars will be really useful for individuals who are new to BizTalk Server or who need to upgrade to the 2006 version. Hope to see you there!
If you want use a desktop tool to read and publish blogs, I highly recommend the following tools.
RSS Bandit, a very neat blog reading tool. It is open-source and written in C#.
w.bloggar, a very popular blog authoring tool. It can be launched standalone, or from RSS Bandit context menu. I am creating this post using w.bloggar. You can configure it to access WordPress, which is the blog software this site uses, among many others. Just make sure you use the following settings for blogging on this site:
Account Tool: WordPress