Geeks With Blogs
El Grego BizTalk blog November 2004 Entries
The BizTalk SQL Server Adapter isolation level
The isolation setting is fixed and is SERIALIZABLE. So beware that even your most basic receive locations that only execute those very simple SQL statements such as 'select * from tablename' can generate locks. BTW, this is a general misconception: usually people think that select-statements never lock resources. Nothing is less true of course. While having a shared lock on a range of keys, in addition to the keys themselves having locked, no records can be inserted. Here's a sample to demonstrate ......

Posted On Thursday, November 25, 2004 4:35 PM

About publisher policy assembly chaining
I've just found out the hard way that GAC'ed publisher policy assemblies do not chain. When you have a policy.1.0, redirecting the binding of assembly v1.0.0.0 to assembly v1.1.0.0 and also having a policy.1.1, for redirecting the binding of assembly 1.1 to assembly 1.2, this doesn't result in a binding to the assembly 1.2 when your app requests 1.0 (but rather to 1.1). If you want this kind of binding-behavior I guess you will have to use publisher policy versioning. Why do I tell all this? Well, ......

Posted On Tuesday, November 23, 2004 11:14 AM

The BizTalk Configuration Dilemma
I’ve watched several times Jurgen Willis’ excellent online presentation about the Business Rule Engine (BRE). One of the BRE usage scenarios demoed by him contains a sample orchestration that uses the BRE to dynamically configure a delay time. This confused me since it added another option to accomplish dynamic configuration of business processes. We are definitely facing a configuration dilemma now; here are some of the alternatives: Config FilesUse the default .NET config files as the store (BTSNTSvc.exe.config) ......

Posted On Wednesday, November 17, 2004 5:25 AM

Executing pipelines from inside an orchestration: Introducing the LOOPBACK adapter
Let's go over some of the out-of-the-box options for executing a pipeline from inside your orchestration. It struck my mind first that the MSMQT adapter IS in fact the messagebox. MSMQT Set up a schedule with 1 MSMQT send port and 1 MSMQT receive port sharing the same MSMQT queue name (for example ' loopback' would make a lot of sense) Create a correlation type and set based on the my MSMQT label property. Assign the MSMQT message-label to a newly created GUID inside your orchestration. Try to do ......

Posted On Wednesday, November 10, 2004 3:24 AM

Copyright © Gregory Van de Wiele | Powered by: