Checklist: Deploying an Application

This topic describes the steps involved in deploying a BizTalk application and its artifacts in a production environment. It demonstrates how to deploy an application in the development environment, export it into an .msi file, and then import it into the production environment from the .msi file.

Application deployment consists of importing the application into a group and installing the application on individual servers (host instances) in the group. For more information about importing and installing applications, see How to Import an Application from an .msi File.

For more information about application deployment, see The Application Deployment Process (http://go.microsoft.com/fwlink/p/?LinkId=154716).

Steps Reference
Ensure that you have the appropriate permissions to perform the deployment. Permissions for Managing an Application
Set the deployment properties in Visual Studio for each project in the BizTalk Server solution, including the application that the assembly will be deployed to.

Deploy (or redeploy) the required BizTalk Server assemblies into the BizTalk application in the development environment.
- How to Set Deployment Properties in Visual Studio (http://go.microsoft.com/fwlink/p/?LinkId=154718).
- Deploying BizTalk Assemblies from Visual Studio into a BizTalk Application (http://go.microsoft.com/fwlink/p/?LinkId=154719).
- How to Redeploy a BizTalk Assembly from Visual Studio (http://go.microsoft.com/fwlink/p/?LinkId=154720).
- Deploying an Assembly
- "Deploying a BizTalk Application", "Creating a BizTalk Application", and "Deploying a BizTalk Assembly" sections of Best Practices for Deploying an Application.
- "Deploying a BizTalk Application" section of Known Issues with Deploying an Application.
Add artifacts to the BizTalk application and configure the artifacts in the development environment.

This can include factoring artifacts into multiple BizTalk Applications.
- How to Create or Add an Artifact (http://go.microsoft.com/fwlink/p/?LinkId=154724).
- Managing Artifacts (http://go.microsoft.com/fwlink/p/?LinkId=154725).
- Binding Files and Application Deployment (http://go.microsoft.com/fwlink/p/?LinkId=154726).
- Adding Artifacts to an Application
- "Adding Artifacts to a BizTalk Application" section of Best Practices for Deploying an Application.
- "Adding Artifacts to a BizTalk Application" section of Known Issues with Deploying an Application.
Export the BizTalk application into an .msi file in the development environment. - How to Export an Application to an .msi File
- "Exporting a BizTalk Application" section of Best Practices for Deploying an Application.
- "Exporting a BizTalk Application" section of Known Issues with Deploying an Application.
Import the BizTalk application into the production environment from the .msi file. (This operation consists of importing the application into the group and if the application includes file-based artifacts, installing the application on each server in the group.) - How to Export an Application to an .msi File
- How to Install an Application (http://go.microsoft.com/fwlink/p/?LinkId=154728).
- "Importing a BizTalk Application" section of Best Practices for Deploying an Application
- "Importing a BizTalk Application" section of Known Issues with Deploying an Application
Make any additional modifications to the BizTalk application in the production environment so it runs in that environment, such as changing port configurations. If you do so, export the application into an .msi file. - How to Export an Application to an .msi File
- Creating and Modifying BizTalk Applications (http://go.microsoft.com/fwlink/p/?LinkId=154727).
- How to Add a Binding File to an Application1
- "Exporting a BizTalk Application" section of Best Practices for Deploying an Application
- "Exporting a BizTalk Application" section of Known Issues with Deploying an Application
If you have made any additional modifications to the BizTalk application in the production environment, install the BizTalk application from the .msi file into any other computers in the production environment that will run it.

Also, import the application into any other BizTalk groups where you want to deploy it, and if the application includes file-based artifacts, install the application on the servers in those groups.
- How to Install a BizTalk Application (http://go.microsoft.com/fwlink/p/?LinkId=154728).
- How to Import an Application from an .msi File
- "Importing a BizTalk Application" section of Best Practices for Deploying an Application
- "Importing a BizTalk Application" section of Known Issues with Deploying an Application
Start the BizTalk application in the production environment from the BizTalk Server Administration console and verify that it is functioning correctly. - How to Start and Stop a BizTalk Application (http://go.microsoft.com/fwlink/p/?LinkId=154729).
- Testing an Application

See Also

Deploying an Assembly
Adding Artifacts to an Application
How to Export an Application to an .msi File
How to Export Bindings to a Binding File
How to Import an Application from an .msi File
How to Install an Application
How to Import Bindings from a Binding File