With BizTalk Server 2013 Beta, ESB Toolkit is now fully integrated with BizTalk Server. Also, the ESB Toolkit configuration experience is simplified to enable a quick setup. The installation and configuration is described on MSDN.
The Setup does not register the ESB Toolkit Itinerary Designer by default. (You can use the ESB Toolkit Itinerary Designer to create itineraries in Visual Studio.) The “Installation Guide.htm” in the Microsoft BizTalk ESB Toolkit folder describes that you can install the Itinerary Designer extensions by clicking Start> All Programs> Microsoft BizTalk Server 2010 ESB toolkit > Install Itinerary Designer Extensions. The Installation Guide is still for the ESB Toolkit 2.1 because in BizTalk 2013 Beta you don’t have this option. In Known Issues is described that you can find the Itinerary Designer Setup in the installation folder of BizTalk 2013 Beta.

Steps

Go to the installation folder of BizTalk 2013 Beta

Double click on Microsoft.Practices.Services.Itinerary.DslPackage.vsix.
VSIX_Installer
 
InstallerComplete

 

Test the ESB Toolkit installation

To test the installation I used a small BizTalk project with 2 schemas and a map to create a BizTalk application. You can open a BizTalk 2010 solution with Visual Studio 2012 and upgrade the projects in the solution to the new version of Visual Studio.

VisualStudio_2012
Notice that the number of Adapter Providers are still the same as in the previous versions of the ESB Toolkit!
 

To send a message to one of the on-ramps that are provided by the BizTalk ESB Toolkit I used the sample “GlobalBank.ESB.Samples.Itinerary” application. This application is still in the samples in ESBSource.zip.

Run the Itinerary Test Client to send a message with an itinerary to the ESB.ItineraryServices on-ramp.

Itinerary Test Client

 

Conclusion

My BizTalk 2010 solution opened easily in Visual Studio 2012 and it ran without problems. Only Tracing  in the ESB Toolkit did not seem to work,. Also it took a while before I had found the setup of the Itinerary Designer Extensions because at first I didn’t read the Known Issues on MSDN but now I know, first read the Known Issues when you're working with a Beta version!