Checklist: Exporting Bindings from One Application to Another
This topic describes the steps involved in transferring the bindings of one application to another application in either a development or production environment. This process is similar to the process of deploying an application using an .msi file. However, when you deploy an application using an .msi file, the process will automatically create the application. When you transfer the bindings from one application to another, on the other hand, the destination application must already exist.
| Steps | Reference |
|---|---|
| Ensure that you have the appropriate permissions to perform the export operation. | Permissions for Managing an Application |
| Create a destination application to import the application bindings into. | - Creating an Application - "Creating a BizTalk Application" section of Best Practices for Deploying an Application |
| Export the bindings of a source application into a binding file. | - How to Export Bindings to a Binding 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 bindings in a binding file to the destination application. | - How to Import Bindings from a Binding 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. |