ExportApp Command
Exports a BizTalk application to an .msi file. If an .msi file having the same file name and path already exists, the existing .msi file is overwritten.
You can use the ResourceSpec parameter to selectively export the artifacts in an application to an .msi file. You specify which artifacts to export by editing the XML file created when you run the ListApp command with the ResourceSpec parameter, as described in ListApp Command. You then use the location of this XML file as the value of ResourceSpec when running the ExportApp command. When you do this, only the artifacts listed in the specified XML file are exported to the .msi file.
Note
For security reasons, during application export, passwords are removed from application bindings. They are not removed from any binding files that have been added to the application. After installing the application from the .msi file, you must reconfigure the passwords in order for the application to function.
In addition, private keys are removed from certificate files.
Usage
BTSTask ExportApp [/ApplicationName:value] /Package:value [/ResourceSpec:value] [/GlobalParties] [/Server:value] [/Database:value]
Parameters
| Parameter | Required | Value |
|---|---|---|
| /ApplicationName (or /A, see Remarks) | No | Name of the BizTalk application to export. If the name includes spaces, you must enclose it with double quotation marks ("). If the application name is not specified, the default BizTalk application for the group is used. |
| /Package (or /P,see Remarks) | Yes | Full path of the .msi file. If the path includes spaces, you must enclose it in quotation marks ("). Example: Package:"C:\My MSI Files\My.msi" |
| /ResourceSpec (or /R, see Remarks) | No | Full path of the resource specification file. If the path includes spaces, you must enclose it in quotation marks ("). Example: ResourceSpec:"C:\My Files\MyResourceSpec.xml" |
| /GlobalParties (or /G, see Remarks) | No | If specified, global party information for the group is exported in the .msi file. |
| /Server (or /S, see Remarks) | No | 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 (or /D, see Remarks) | No | Name of the BizTalk Management database. If not specified, the BizTalk Management database running in the local instance of SQL Server is used. |
Sample
ExportApp /ApplicationName:MyApplication /Package:C:\MSI\MyApplication.msi
Remarks
Parameters are not case-sensitive. You do not need to type the entire parameter name to specify it; you can type the first few letters of the parameter name that identify it unambiguously.
See Also
BTSTask Command-Line Reference
How to Export a BizTalk Application
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for