Managing Itineraries is one of the more tedious and tricky aspects of BizTalk deployments because it is possible that some values in Resolvers are specific for a certain environment. For example a File location in the Development environment is probably not the same as in the Production environment.
To address this problem, the Deployment Framework includes in each BizTalk project an Excel spreadsheet named SettingsFileGenerator.xml that captures an unlimited number of "settings" (name/value pairs) stored as rows in the spreadsheet. Each setting (row) has a default value in addition to a value for any number of deployment environments (stored in columns). This makes it very easy to manage a large matrix of settings across environments in one place.
During the deployment process, setting values from your Excel settings spreadsheet are seamlessly merged with the Itinerary file(s) to produce an environment-specific Itinerary. In the Itinerary, you replace environment-specific values with tokens that correspond to setting names in the spreadsheet.
The following steps describe how you can automatically preprocess your itineraries to replace tokens with the environment specific values.
Once the itinerary is deployed to the Itinerary Store database and a Receive Location in BizTalk is created that uses the Itinerary, the solution is ready to be tested.
Run DebugView to watch the trace output.
For more information on using the Deployment Framework with ESB itineraries see: