Ha! Tricked You Didn’t I?
You thought this was going to be another Commerce Server post but it’s really a BizTalk Server post disguised as a Commerce Server post disguised as a BizTalk Server post. This integration stuf is pretty confusing at times (LOL).
One of my basic recommendations for any individual BizTalk Server “Application” is to run it in it’s own Host Instance. This helps separate each BizTalk application so that you can make changes to one application without affecting another. Pretty basic!
Setting this up is very simple and begins with right-clicking on the Hosts branch of the tree-view in the BizTalk Server 2006 Administration Console and selecting New, then Host…
This opens up the Host Properties dialog box where you setup your new Host as shown below.
The next step is to create a new Host Instance by right clicking on the console’s tree-view as shown below.
This opens up the Host Instance Properties dialog box where you select the Host you created in the previous steps.
Make sure you click on the Configure button and I recommend using one of the domain service accounts setup during your installation and configuration of Commerce Server 2007.
When you’re all done you have a new In-Process Host as shown here.
Only a few more steps to go!
Next, you need to create a new Send Handler and Receive Handler for each of the four new Commerce Server adapters. Right click on each new adapter in the console’s tree-view and select New, then Send Handler (or Receive Handler).
This opens the Adapter Handler Properties dialog box where you select the Host to run this under as shown below. I also recommend making this the default handler and then deleting the original BizTalkServerApplication handlers for this adapter.
When you’re finished, each of your four new Commerce Server adapters should look like this in the console.
This configuration isolates all your Commerce Server related BizTalk Applications from the other BizTalk Applications and runs them in their own process on the physical server. Now when you deploy your Commerce Server related BizTalk Application and restart your Host Instance, you won’t affect any other running BizTalk Application!
[tags: BizTalk, Commerce Server]