NAck Processing using an Orchestration

This is a simple Orchestration to catch Nack’s. Nack’s are Negative Acknowledgements returned from failed BizTalk messages. This Orchestration can be modified to react to specific exceptions as needed.

This sample should work in BizTalk 2004 and BizTalk 2006.

Get more information from the original blog post on this topic: http://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2005/05/26/nack-message-processing-orchestration-for-biztalk-server-2004.aspx

%ufeff

Naming Output Files Inside an Orchestration

Naming output files is always tricky. This sample shows how to use message context properties to control the name of output files.

BizTalk 2004 has two ways to dynamically name your files from inside the Orchestration. The two ways to accomplish this are either to use a Dynamic Send Port or to use the %SourceFileName% macro on the Send Port.

This sample should work with both BizTalk 2004 and BizTalk 2006.

Get more information from the original blog post on this topic: http://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2004/11/13/how-to-name-output-files-inside-an-orchestration.aspx

bts_CleanupMsgbox caveat…

I was just reading Mike
Holdorf’s post on the bts_CleanupMsgbox stored procedure.  The team I work
with has been able to make good use of this sproc as well, especially while stress
testing.

One thing to beware of is this: Your habit for doing this kind of thing might
lead you to open up Sql Query Analyzer, and right click on the stored procedure
– selecting “script to new window as execute.”  This will generate
the following:

DECLARE @RC int
DECLARE @fLeaveActSubs int
-- Set parameter values
EXEC @RC = [BizTalkMsgBoxDb].[dbo].[bts_CleanupMsgbox] @fLeaveActSubs

Ahhh, but the stored procedure actually defaults fLeaveActSubs to “1”,
whereas this code will leave fLeaveActSubs as “0”.  This will cause
all your subscriptions to be deleted, and you will have to redeploy your BizTalk applications. 
Not that I would know….

So just do “exec bts_CleanupMsgbox”…

bts_CleanupMsgbox caveat…

I was just reading Mike
Holdorf’s post on the bts_CleanupMsgbox stored procedure.  The team I work
with has been able to make good use of this sproc as well, especially while stress
testing.

One thing to beware of is this: Your habit for doing this kind of thing might
lead you to open up Sql Query Analyzer, and right click on the stored procedure
– selecting “script to new window as execute.”  This will generate
the following:

DECLARE @RC int
DECLARE @fLeaveActSubs int
-- Set parameter values
EXEC @RC = [BizTalkMsgBoxDb].[dbo].[bts_CleanupMsgbox] @fLeaveActSubs

Ahhh, but the stored procedure actually defaults fLeaveActSubs to “1”,
whereas this code will leave fLeaveActSubs as “0”.  This will cause
all your subscriptions to be deleted, and you will have to redeploy your BizTalk applications. 
Not that I would know….

So just do “exec bts_CleanupMsgbox”…

Community MSMQ Adapter for BizTalk 2004 Now Available


Yesterday Microsoft released a BizTalk 2004 Adapter for MSMQ v2.0.  This works with MSMQ 2.0 and 3.0. 



Here are the key features from the download site:



The BizTalk 2004 Adapter for MSMQ provides support for sending and receiving messages using MSMQ 2.0 and 3.0, and takes advantage of the new features in MSMQ 3.0. Major features of the adapter include support for:


• MSMQ 2.0 and 3.0
• Multi-threading option for faster performance
• Guaranteed delivery when using transactional queues
• Reading from remote non-transactional queues
• Dynamic send ports
• Support for messages up to 2 Gigabytes in size


 


Download this adapter here.


 

BizTalk Server Documentation Update

Get the last BizTalk Server documentation update here.  As always the online help remains available at MSDN as well.
Together with this core documentation, following updated documents are also available for download:

  • the user guide for information workers
  • the BizTalk Server tutorials
  • and last but certainly not least: the installation guide

 

Share this post: Email it! | bookmark it! | digg it! | reddit!