When an itinerary is created using the Itinerary Designer you normally deploy the Itinerary with the ESB Itinerary Import Utility. This utility is located under the \bin directory of the BizTalk ESB Toolkit and is named EsbImportUtil.exe. It can be used to publish or deploy the itinerary XML into the ESBItineraryDB database. Unfortunately, the tool is not very convenient to use because you have to deploy the Itineraries manually.
Another option is to use the Deployment Framework for BizTalk. The Deployment Framework for BizTalk eliminates the pain associated with BizTalk application deployments, and goes far beyond BizTalk’s out-of-the-box deployment functionality because you can also use it to deploy ESB itineraries.

 

Steps

The Deployment Framework can automatically deploy your ESB itineraries during deployment.  Before an itinerary can be deployed, you must manually export it to an XML file using the Itinerary Designer’s XML Exporter. 
 
1. Set the IncludeEsbItineraries property to true
The property may be included in any PropertyGroup, but is commonly placed in the first PropertyGroup in the project file.

<PropertyGroup>
 ...
 <IncludeEsbItineraries>true</IncludeEsbItineraries>
 ...
</PropertyGroup>.csharpcode, .csharpcode pre
{
	font-size: small;
	color: black;
	font-family: consolas, "Courier New", courier, monospace;
	background-color: #ffffff;
	/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt 
{
	background-color: #f4f4f4;
	width: 100%;
	margin: 0em;
}
.csharpcode .lnum { color: #606060; }

 

2. Add an EsbItineraries ItemGroup

The following is a typical example that properly follows the common ItemGroup structure:

<ItemGroup>
 <EsbItineraries Include="MyItinerary1.xml">
   <LocationPath>..\Itineraries</LocationPath>
 </EsbItineraries>
</ItemGroup>

.csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; }

If you have more than one ESB itinerary, then repeat the <EsbItineraries> element for each file

(usually within the same ItemGroup).

Note

The Microsoft ESB Toolkit does not include a tool to undeploy itineraries, so the Deployment Framework cannot undeploy them.  Once deployed, they remain deployed.

 

See Also

For more information on using the Deployment Framework to deploy your ESB itineraries see: