If you happen to have a few extra hours of free time, you might want to read the new BizTalk Server 2006 Developers Guide.
At first glance, this 133 page troubleshooting & development guide looks awesome and covers BizTalk from end to end.
Some top topics include:
It’s well worth a look.
This sample shows how to use multiple binding files inside an Application to allow for one MSI to be used on multiple target environments. When you add multiple binding files as resources to your application, a drop list will appear when you import your MSI on your target environments.
This sample works with BizTalk 2006 and BizTalk 2006 R2.
Get more information from the original blog post on this topic: http://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalk/archive/2006/09/12/how-to-add-multiple-binding-files-to-an-application-in-biztalk-2006.aspx
BizTalk 2006 makes it easy to add multiple binding files to an Application. By adding multiple binding files to an Application, you can easily select environment specific settings during deployment.
So if you have a Dev, Test, and Prod environment you can have three binding files all built into the same MSI package. Of course, you need to create and maintain multiple version of your binding files in order to use them in this manner.
To add multiple binding files to an Application, just follow these steps.
1. Export your binding files using BizTalk Server Administration (you'll need to change your setting for each environment).
2. Once you have all the binding files, inside BizTalk Server Administration add them as a Resource to your Application.
3. Add each Binding file and specify the Target Environment name.
4. Repeat for each Binding file and make sure the Environment variable is set for each file.
5. Create your MSI for your Application.
6. When you import your MSI on another Environment, you will get a selection menu to select what binding file you want to use.
I've put together a simple sample to show this. It will not actually run or do anything. It is just intended to show how to set up multiple binding files.
Download: Multiple Binding Files in an Application
A free book loaded with tips and tricks for visual studio… Nice!
Found it through Craig McMurtry’s blog
Eric Lee has a pretty interesting idea
here of integrating Visual
Studio Team Foundation Server with BizTalk Server to create a Virtual Kanban System.
Pretty funky stuff and pretty cool.
It sounds, though, as something where possible Windows Workflow Foundation would
be an even better choice than BizTalk: It’s more lightweight (certainly
less expensive for this case) and would offer a more expressive environment for this
kind of automation (using custom activities). WF integration for TFS v2.0 process
templates, anyone?
Then again, the BizTalk/WF distinction might not be needed one day 🙂
Technorati: BizTalk, Team
Foundation Server, TFS, Windows
Workflow, WF
Just published at the BizTalk Server Developer Center, the Developer’s Guide to Troubleshooting BizTalk Server 2006.
http://download.microsoft.com/download/3/7/6/376a6f6c-8c97-4ab5-9d5a-416c76793fbb/bts06developerstroubleshootingguide.doc
I decided to put these down somewhere as I always keep losing them.
Basically part of .NET Framework, you can retrieve config values from registry.
Great for BTSNTSvc.exe.config etc. There you have the best of both worlds –
keys that are accessible via the AppSettings, but the values are stored away from
prying eyes……
Here’s the go
<appSettings>
<add key=”InternalApprovalUrl’ value=”registry:HKLM\Software\SomeKey,someValue”
/>
….
</appSettings>
Also for .NET 1.x there is a hotfix KB329250 that allows entities like ProcessModel
username/pass to be stored in the Registry – encrypted!
Enjoy Mick.
Simple but I just want to make a note of it.
1. go to BizTalkMgmtDb.
2. query
select * from bt_DocumentSpec where msgtype like ‘http://schema.skico.com/%’ order by msgtype asc
– ‘http://schema.skico.com/%’ part can be switched.
BizTalk Server 2006 makes it simple to add environment specific binding files to an Application. By adding environment specific binding files to an Application, you can easily select a binding file during deployment. So if you have a Dev, AIT, and SIT environment you can have three binding files all built into the same MSI package. Of course, you will need to create and maintain multiple version of your binding files in order to use them.
To add environment specific binding files to an Application, just follow these simple steps.
1. Inside BizTalk Server Administration, export your binding files (you’ll need to change your setting for each environment).
2. Once you have all the binding files, in the BizTalk Server Administration add them as a Resource to your Application.
3. Add each Binding file and specify the Target Environment name.
4. Repeat for each Binding file and make sure the Environment variable is set for each file.
5. Create your MSI for your Application.
6. When you import your MSI on another Environment, you will get a selection menu to select what binding file you want to use.
I’ve put together a simple sam
I got this error today. Fixed the problem by putting the HttpReceive port and a web service port in separate application pools.