Using the BizTalk Web Services Publishing Wizard to Publish an Orchestration as a Web Service

You use the BizTalk Web Services Publishing Wizard to publish an orchestration as a Web service.

Note  You must build your BizTalk projects prior to running the BizTalk Web Services Publishing Wizard.

To publish an orchestration as a Web service

1. Click Start, point to All Programs, point to Microsoft BizTalk 2004, and then click BizTalk Web Services Publishing Wizard.
2. On the Welcome to the BizTalk Web Services Publishing Wizard page, click Next.
3. On the Create Web Service page, select Publish BizTalk orchestrations as web services, and then click Next.
4. On the BizTalk Assembly page, in the BizTalk assembly file (*.dll) text box, type the name of the BizTalk assembly file or click Browse to browse to the assembly containing the orchestration(s) to publish, and then click Next.

   Note  If you have an orchestration open in Visual Studio .NET, the BizTalk assembly file populates with the assembly containing the orchestration.

   Note  Paths over 260 characters may get an error message that the path is too long.

5. On the Orchestrations and Ports page, expand the tree nodes for each assembly and orchestration by clicking the plus sign. Select orchestrations and ports to publish by checking the corresponding tree node check boxes, and then click Next.

The following figure shows the BizTalk Web Services Publishing Wizard Orchestrations and Ports page with the tree nodes for the assembly expanded.

1. On the Web Service Properties page, in the Target namespace of the web service box, type a target namespace for the Web service, select the appropriate boxes to specify how the wizard should handle SOAP headers and SharePoint Portal Server 2003 Single Sign-On (SSO) support for the Web service, and then click Next.

   Note  The selection any of the SOAP header options are applied globally to all Web services and Web methods that are created when running this instance of the wizard.

   Note  Selecting the Add SharePoint Portal Server 2003 Single Sign-On Support option, allows Windows SharePoint Portal Server 2004 to pass its Single Sign-On (SSO) tickets to BizTalk Server inside a SOAP header. For more information about support SSO support in Windows SharePoint Portal and BizTalk Enterprise SSO support in BizTalk Server, see SOAP Adapter.

2. If you selected Add additional SOAP headers option, the Request SOAP Headers and Response SOAP Headers pages appear. You can add and remove request and response SOAP headers using the Add and Remove buttons in the following dialog boxes:
   • To add a SOAP header, click Add. In the BizTalk assembly file (*.dll) text box, type or browse for the assembly containing the SOAP header schema. The Available schema types list view displays each root element of the schema. Select a root node to add as a request or response SOAP header. To select multiple items, hold the CTRL key and click OK.
   • To remove a SOAP header from the list, select it from the list of added SOAP headers, and then click Remove.
   • Click Next on each SOAP Header page to continue the wizard.

   Note  A target namespace and root element name define a SOAP header.

   Note  If the same combination of target namespace/root element name is added as a request and response SOAP header, it will not be treated as and in/out header. You must manually copy the incoming header to the outgoing header inside of an orchestration.

   Note  The same combination of target namespace/root element name can only be added once as a request SOAP header and once as a response SOAP header.

3. On the Web Service Project page, in the Project name text box, type the name for the project. You can accept the default location (http://localhost/<project_name>), type a location for the project in the Project location text box, or click Browse and select a Web directory. Select any of the following options:
   • Overwrite existing project. This option is only available if the project location already exists. You will only be able to publish to the same location if you select this option. Otherwise, you must enter a different project location.
   • Allow anonymous access to web service. This option adds anonymous access to the created virtual directory. By default, the virtual directory inherits the access privileges from its parent virtual directory or the Web site (if it is a top-level virtual directory).
   • Create BizTalk receive locations. This option automatically creates the SOAP adapter receive ports and locations that correspond to each generated .asmx file. If a receive location already exists, it is not replaced. Receive locations for the SOAP adapter are resolved using the format /<virtual directory name>/<orchestration namespace_typename_portname>.asmx.

     Note  The project location can exist on a different server. To publish a Web service to a different server, type the project name as http://<servername>/<project_name>.

     Note  The project location can exist on a non-default Web site. When publishing to a non-default Web site, include the port number of the Web site in the URL. For example, http://localhost:8080/<project_name>.

     Note  When using the wizard to create receive locations, the wizard creates the receive locations using the default values. The default values for receive and send pipelines are the Microsoft.BizTalk.DefaultPipelines.PassThruReceive and Microsoft.BizTalk.DefaultPipelines.PassThruTransmit. If messages received through the published Web service require any special pipeline processing (for example, validation, correlation, or inbound/outbound maps) then you should set the send and receive pipelines to Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines.XMLSend, or to a custom pipeline.

4. Click Next to review your settings for the ASP.NET Web service project.
5. Click Create to create the ASP.NET Web service.
6. Click Finish to complete the BizTalk Web Services Publishing Wizard.

See Also

Publishing an Orchestration as a Web Service

Mapping Orchestrations to Web Services

Troubleshooting Published Web Services