How to Export an Application to an .Msi File (withou admin console)

1. Open a command prompt as follows: Click Start, click Run, type cmd, and then click OK.
   
   
2. Type the following command, substituting the appropriate values, as described in the following table:
   
   
   BTSTask ExportApp [/ApplicationName:value] /Package:value [ResourceSpec:value [/Server:value] 
   
   
   [/Database:value]
   
   
   Example:
   
   
   BTSTask ExportApp /ApplicationName:MyApplication /Package:C:/MSI/MyApplication.msi /ResourceSpec:"C:\My Files\ResourceSpec.xml" /Server:MySQLServer /Database:BizTalkMgmtDb
   
   
   The artifacts you specified are exported into an .msi file in the location you specified.
   
   
   
   
   Parameter value:
   /ApplicationName: Name of the BizTalk application to export. If the application name is not specified, the default BizTalk application is used. If the name includes spaces, it must be enclosed with double quotation marks (").
   
   
   /Package:Path of the .msi file to be created, including its file name.
   
   
   /ResourceSpec: Path of the resource specification XML file, including file name. You can specify which artifacts to export by editing the resource specification XML file, which is created when you run the ListApp command with the ResourceSpec parameter, as described in ListApp Command. For more information, see "ListApp Command" in BizTalk Server 2006 R2 Help athttp://go.microsoft.com/fwlink/?LinkId=106823. You must manually edit this file to add the Internet Information Services (IIS) host server name for a virtual directory that you want to export if the Web server is on a remote computer.
   
   
   /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 from 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.

How to Export Bindings for a BizTalk Application (without Admin console)

1. Open a command prompt as follows: Click Start, click Run, type cmd, and then click OK.
   
2. Type the following command, substituting the appropriate values, as described in the following table:
   
   
   BTSTask ExportBindings /Destination:value [/ApplicationName:value] [/GlobalParties] [/Server:value] [/Database:value]
   
   
   Example:
   
   
   BTSTask ExportBindings /Destination:"C:\Binding Files\MyBindings.xml" /ApplicationName:MyApplication /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 (").
   /ApplicationName
   Name of the application from which to export bindings. The application must exist. To verify the application name, you can use the ListApps command, as described in ListApps Command. If this parameter is not specified, the default BizTalk application is used. If there are spaces in the name, you must enclose it in double quotation marks (").
   /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.