Sponsored By Aspose - File Format APIs for .NET

Aspose are the market leader of .NET APIs for file business formats – natively work with DOCX, XLSX, PPT, PDF, MSG, MPP, images formats and many more!

BizTalk Server 2006: A Simple Deployment Scenario

If you’re like a lot of us, you purchased BizTalk Server 2006 Standard Edition which has a “hard limit” of five BizTalk applications. In BizTalk 2006, an application is “a logical grouping of all the BizTalk design-time artifacts (schemas, maps, pipelines, orchestrations), messaging components (receive ports, receive locations, send ports) and other related items such as policies that comprise an integrated business process”. In my previous post entitled BizTalk Server 2006 – Pricing and Licensing, I wrote about how this apparent “limitation” was really no limitation at all and that the licensing actually allows you to utilize your server configuration to it’s fullest extent, limited only by your choice of hardware and available bandwidth.

The only issue created by this new feature is deciding the best way to group and deploy your existing BizTalk solutions and projects into these five new applications. I certainly don’t want to lump everything under the default “BizTalk Application 1″ but I also don’t want to bump up against the five application limit either. After trying out several different scenarios on my development server, I’ve finally settled on one that I believe offers the best granularity and maintainability in the long run.

As you can see in the image above, I’ve broken down my BizTalk (VS) “Solution” into several (VS) “Projects” to make it easier to work on one project at a time. Each project contains all the specific artifacts needed including schemas, maps, pipelines and orchestrations. This (VS) “Solution” also corresponds to the BizTalk “Application” that I plan to deploy all these artifacts into. I’ve also created a “Shared” project which contains the schemas, maps, pipelines and orchestrations that are common to all the other “specific” projects.

I also chose a new “naming convention” to help me keep track of the various assemblies and artifacts I’ve deployed.

GCS – Company
BizTalk – Application Type
Invoices – Application Subject
Shared – For shared artifacts
Specific – For specific artifacts
Artifact – Artifact Name

example: GCS.BizTalk.Invoices.Vetco.ReceivePipeline

I’m looking for comments and suggestions here so don’t be shy!

This entry was posted in BizTalk Server. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

3 Responses to BizTalk Server 2006: A Simple Deployment Scenario

  1. jlynch says:


    Right click on any project to open the project’s properties pages. Then click on the “Deployment” element under the “Configuration Properties” in the left pane tree-view. You should see the “Application Name” attribute in the right pane which should be set to the name of your BizTalk application. If you set this the same for all projects under your solution and then deploy the solution (always deploy at the solution level, never at the project level) all your projects will show up under that one BizTalk application.


  2. Daniel Gigante says:

    It’s a nice suggestione but I couldn’t manage to do the same. I created a new “solution” then added my 5 BizTalk projects, compiled and published but I still see them inside the BizTalk Group as 5 separate applications. What could I have done wrong?

  3. I’ve been using a similar naming convention for a couple of years now, though I don’t distinguish shared and specific components so explicitly. It works very nicely, btw, I think.

Leave a Reply