How to Export Bindings for a BizTalk Group
This topic describes how to use the BizTalk Server Administration console or the command line to export the bindings for a BizTalk group to an .xml file. You can then import these bindings into a BizTalk group or application, as described in How to Import Bindings into a BizTalk Group and How to Import Bindings into a BizTalk Application. For more information about using binding files, see Binding Files and Application Deployment.
Note
Exporting bindings for a group always exports global party information, whether this option is specified or not.
Prerequisites
To perform the procedures in this topic, you must be logged on with an account that is a member of the BizTalk Server Administrators or BizTalk Operators group. For more detailed information on permissions, see Permissions Required for Deploying and Managing a BizTalk Application.
To export bindings for a BizTalk group
Using the BizTalk Server Administration console
Click Start, click All Programs, click Microsoft BizTalk Server 20xx, and then click BizTalk Server Administration.
In the console tree, expand BizTalk Server Administration, expand the BizTalk group, right-click Applications, point to Export, and then click Bindings.
On the Export Bindings page, in Export to file, type the absolute path of the .xml file to which to export the bindings.
Example: C:\Bindings\Group1Bindings_Staging1.xml
Ensure that Export all bindings from the current group is selected, and then click OK.
The bindings are exported to an .xml file in the location that you specified.
Using the command line
Open a command prompt as follows: Click Start, click Run, type
cmd
, and then click OK.Type the following command, substituting the appropriate values, as described in the following table:
BTSTask ExportBindings /Destination: value /GroupLevel [/GlobalParties] [/Server:value] [/Database:value]
Example:
BTSTask ExportBindings /Destination:"C:\Binding Files\MyBindings.xml" /GroupLevel /Server:MyDatabaseServer /Database:BizTalkMgmtDb
Parameter Value /Destination Full path of the binding file to create, including the file name. If a binding file having the same path already exists, it is overwritten. If there are spaces in the path, you must enclose it in double quotation marks ("). /GroupLevel When specified, all bindings in the current BizTalk group are exported. /GlobalParties When specified, exports global party information for the group. /Server Name of the SQL Server instance hosting the BizTalk Management database, in the form ServerName\InstanceName,Port.
Instance name is only required when the instance name is different than the server name. Port is only required when SQL Server uses a port number other than the default (1433).
Examples:
Server=MyServer
Server=MyServer\MySQLServer,1533
If not provided, the name of the SQL Server instance running on the local computer is used./Database Name of the BizTalk Management database. If not specified, the BizTalk Management database running in the local instance of SQL Server is used.
See Also
Exporting Bindings
ExportBindings Command
Importing BizTalk Applications, Bindings, and Policies