October 2004 Entries
After hours of fighting it, I have concluded that deploying a solution that utilizes Roles and Party's can't be installed using an MSI created with the BTSInstaller. You can use the same binding file and assemblies and use BTSDeploy and it all works fine. I plan on posting all my deployment scripts here in the next few days as the BTSInstaller gets you about 85% there, and you're required to script the rest. Take a look at Scott Colestock's blog for a different option (Nant) to the BTSInstaller....
BizTalk server relies on a config file to store certain application information. This config file is located in \Program Files\Microsoft BizTalk Server 2004 and is named BTSNTSvc.Exe.Config. View your file here (DO NOT CHANGE THIS FILE WITHOUT BACKING UP!!!). Let's say that you have some .NET components that you want to consume from your BizTalk solution. Let's also assume that these components are possibly shared with another solution, and make use of a config file for things such as connection...
I applogize for being anything but prompt on this. The zip file can be found here. Steps for setting up Role Link Sample - 1. Create a receive port in BTS Explorer2. Create 2 send ports - RoleLinkTest_Approver1 and RoleLinkTest_Approver23. Set your transports, send or receive locations, etc for your ports4. Create a party called Approver1. Choose RoleLinkTest_Approver1 as their send port.5. Create a party called Approver2. Choose RoleLinkTest_Approver2 as their send port. At this point you should...
Before I begin, I promise I am working on getting my role link example up here. There was some confusion with server space to upload the example to. Ok....I know when I first started with BTS'04, it was slightly confusing to me what the whole host/host instance thing was. A fairly new concept from the previous versions. But, once the concept sinks in (things take longer for me ;-) ), it's actually extremely useful. So, we know that the Host is a “logical container”, and the Instance is...