Microsoft TechNet
This topic has not yet been rated - Rate this topic

BTSWCFServicePublishing Command-Line Reference

[This is prerelease documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This topic provides reference information for the BTSWCFServicePublishing command-line tool. You can use BTSWCFServicePublishing to script the publishing of orchestrations as WCF services. You can also use this command-line tool to script publishing of service metadata for any WCF receive location.

To download this command-line tool, go to http://go.microsoft.com/fwlink/?LinkId=92955.

BtsWcfServicePublishing PathName [-AdapterName:value] [-EnableMetadata] [-ReceiveLocation] [-ApplicationName:value] [-MetadataOnly] [-MetadataReceiveLocationName:value] [-MergePorts] [-TargetNamespace:value] [-Location:value] [-Overwrite] [-Anonymous]

Parameter Required Description

PathName

Yes

Path and file name of BizTalk assembly (*.dll) or WCF service description (*.xml) file.

-AdapterName

No

Publish a service endpoint. Specify which adapter will be used: WCF-BasicHttp, WCF-WSHttp, or WCF-CustomIsolated. This field is valid when publishing a service endpoint.

The default is WCF-WSHttp.

-EnableMetadata

No

Enables metadata (MEX) endpoint in addition to service endpoint. This field is valid when publishing a service endpoint.

The default is False.

-ReceiveLocation

No

Create receive locations in the specified BizTalk application. This field is valid when publishing a service endpoint with BizTalk application name specified.

The default is False.

-ApplicationName

No

Name of the BizTalk application in which to create receive locations. This field is valid when publishing a service endpoint with receive location specified.

The default is BizTalk Application 1.

-MetadataOnly

No

Publish a metadata only endpoint. This field is valid when publishing a service endpoint.

The default is False.

-MetadataReceiveLocationName

No

Name of WCF-adapter receive location to expose at metadata only endpoint. You can further edit it in Web.config after publishing. This field is valid when publishing a metadata endpoint.

The default is Null.

-MergePorts

No

Merge all ports into a single WCF service if possible.

The default is False.

-TargetNamespace

No

Target namespace of WCF service.

The default is http://tempuri.org.

-Location

No

Location in which to publish. For example, http://host[:port]/path.

This is automatically generated based on the project name.

-Overwrite

No

Overwrite (delete contents of) specified location.

The default is False.

-Anonymous

No

Allow anonymous access to WCF service.

The default is False.

The following is an example of using the command-line tool:

BtsWcfServicePublishing.exe "MyAssembly.dll" -Location:http://localhost/MyVdir -Overwrite
  • Parameter names are not case sensitive and may be abbreviated. Consult the tool’s help file on how to properly abbreviate the names.

  • Parameter values are case sensitive.

  • PathName is required; all other parameters are optional.

  • For service endpoint, you can optionally specify the AdapterName, EnableMetadata, ReceiveLocation, or ApplicationName parameters.

  • For metadata only endpoint, you must specify the MetadataOnly parameter and you can optionally specify the MetadataReceiveLocationName parameter.

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Need to update App.config to use with BizTalk 2010.
Note: This tool is actually a BizTalk 2006 R2 tool, but can still be made to work with BizTalk 2010.
If you use this tool with assemblies created with BizTalk 2010 you will get an error because the assembly is a .Net 4 assembly.
To use this tool with BizTalk 2010 you need to edit the BTSWCFServicePublishing.exe.config file to specify to use the .Net runtime:

Add the following:

<configuration>
  <startup>
    <supportedRuntime version="v4.0" />
  </startup>
...