Checklist: Updating an Application Using Side-by-Side Versioning

The following checklist describes the process of deploying an updated version of a BizTalk application that will run side-by-side with an existing version.

A side-by-side installation enables you to roll out an application upgrade incrementally. You can make the installation available to a subset of business partners initially, rather than to all partners at once. Using this approach allows you to continue running the existing application to service the users who are not yet using the new version until you are ready to completely move over to the new version.

The two side-by-side applications will have to receive messages on two different receive locations. As a result, to run side-by-side applications you must ask those trading partners who should use the new version of the application to send messages to the new receive location, so that they will be processed by the new version. Those trading partners who should use the old version should send messages to the previous receive location.

Steps Reference
Create and implement a versioning strategy. "Versioning" section in Best Practices for Updating Applications.
Make any necessary changes to the projects that you want to deploy into the new version of the application. - How to Create or Add an Artifact (http://go.microsoft.com/fwlink/?LinkID=154724).
- Managing Artifacts (http://go.microsoft.com/fwlink/?LinkID=154725).
- Binding Files and Application Deployment (http://go.microsoft.com/fwlink/?LinkID=154726).
- Adding Artifacts to an Application
Increment the version number of each assembly. How to Update an Assembly
Set the deployment properties for each project in the solution (setting the destination application and enabling installation into the global assembly cache (GAC)). How to Update an Assembly
Deploy solutions containing the changed assemblies into an application in your development environment. - Deploying BizTalk Assemblies from Visual Studio into a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154719).
- How to Redeploy a BizTalk Assembly from Visual Studio (http://go.microsoft.com/fwlink/?LinkID=154720).
- Deploying an Assembly
Create a new receive port and any needed receive locations specifying the new URLs that you want partners to send messages to.

Create the appropriate send ports as necessary.

If necessary, bind the new application to the newly created receive and send ports, and test that the application works.
- How to Create a Receive Port (http://go.microsoft.com/fwlink/?LinkId=154843).
- How to Create a Receive Location (http://go.microsoft.com/fwlink/?LinkId=154844).
- How to Create a Send Port (http://go.microsoft.com/fwlink/?LinkId=154845).
- How to Configure an Application (http://go.microsoft.com/fwlink/?LinkId=154847).
Export the new application into an .msi file from your development environment. - How to Export a BizTalk Application (http://go.microsoft.com/fwlink/?LinkId=154848).
- Binding Files and Application Deployment (http://go.microsoft.com/fwlink/?LinkID=154726).
- How to Export an Application to an .msi File
- How to Export Bindings to a Binding File
Import the application .msi file into the BizTalk group in your production environment. - How to Import a BizTalk Application (http://go.microsoft.com/fwlink/?LinkId=154827).
- How to Install a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154728).
- How to Import an Application from an .msi File
- How to Import Bindings from a Binding File
Perform a full start of the application. - How to Start and Stop a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154729).
- Testing Tasks for BizTalk Application Deployment (http://go.microsoft.com/fwlink/?LinkId=154825).
Notify your partners that they should start sending messages to the new URLs. Once they do this, the application begins processing messages for the specified partners. -