Publish a web service in biztalk using BizTalk WCF Service Publishing Wizard

Welcome you again in my Blog and let us do another mind blowing achievement that how to publish a WCF web service in BizTalk and as in previous post to Complete BizTalk project to host Schema as Web Service so If you want to expose/publish a web service, you should run through the BizTalk WCF Service Publishing Wizard. This wizard guides you through choosing what you want to expose as a web service.

This section walks you through the wizard step by step to publish WCF Web Service using  WCF-WSHttp-

Step-1: To start the wizard, go to Start, All Programs, Microsoft BizTalk Server 2016(version), BizTalk WCF Service Publishing Wizard. This fires up a welcoming screen, on which you just click Next. Consider disabling the welcoming screen for the future by checking the check box at the bottom. You will now see the screen shown in above figure.

Step-2: Choose the Service Endpoint option, and choose which adapter to use. Check Enable Metadata Endpoint if you want to expose the metadata about the service. If this is not checked, no one can automatically browse to https://yourownserviceurl.com?wsdl to get the metadata and automatically generate the proxy classes that are needed to call the web service. Checking the Create BizTalk Receive Locations in the Following Application option lets the wizard create receive locations for you that match what you have chosen in the wizard. The receive locations can be renamed and reconfigured later if needed. If you choose the Metadata Only Endpoint (MEX) option, you get the option to publish a WCF service based on the current setup of a configured receive location but Check the Enable Metadata Endpoint check box on development and test servers and

disable it on production servers. The information should not be needed on a production server because all development against your service should be done in a development or test environment. Click Next to open the screen showing in below Figure-

Step-3: In this screen, you need to choose if you will be exposing an orchestration as a web service or one or more schemas. Exposing an orchestration as a web service requires that the port type used for the port that is to be exposed from your orchestration is public. Exposing an orchestration should be avoided because this creates a service that has an interface that is the message type of the message your orchestration receives. This created a tight coupling of your exposed services and your internal

business processes. A better option is to choose to expose one or more schemas because this allows you to developed schemas to be used for the interface and then map too and from these schemas in your two-way receive port. Click Next to get to the screen shown in following picture-

Step-4: You can right-click any element in the tree view and choose to rename it. The service and the operation can also be deleted and replaced with something else. If you want a one-way web service, for instance, remove Operation1, right-click the service, and choose Add Web Method, One-Way. The name of the root node is used as the default name for the virtual directory that will be created for the web service in Internet Information Services (IIS). You should name your root node, service name, operation name, and message names appropriately. You also need to choose types for the messages. This is done by right-clicking either the Request or the Response and choosing Select Schema Type. This provides you with a file selector, where you need to find the assembly that contains the schema you want to use for that particular message, as below following image showing i.e. i am selecting request message schema that i have already deployed in my Global Assembly Cache (GAC)-

Similar i am doing for response message see the following picture-

and now showing complete view after selecting both request and response message type and if any update require then again deployed your project and it will be updated after updated GAC again.

Step-5: Clicking Next brings you to the screen where you need to set a target namespace for the web service itself. This does not influence the namespace of the XML you will be receiving in the end and therefore not the contract between you and the sending party. See the following image-

Step-6: Clicking Next takes you to the screen where you need to choose the location to deploy the web service to, as shown in Figure-

Step-7: Web services published by BizTalk needs to run on a BizTalk Server and the location is a virtual directory called "AccountValidationWS" located at the root of the localhost website. If this is not the first time you are publishing a web service to this URL, the Overwrite Existing Location check box is enabled, allowing you to check it if you want the existing location to be overwritten. You also need to choose whether to allow anonymous access to the web service. If you do not allow anonymous access, integrated security is required for the web service. Clicking Next brings up the summary, as showing in below image-

Step-8: Click Create and then click Finish to quite the wizard.

After publishing of the web service, you need to make sure of two things:

a. The IIS application pool your virtual directory is set to run under needs to run as a user that is a member of the BizTalk Isolated Host Users group.

b. The host assigned to the receive location must be the one you actually want to use.

and also see the reference link for web service configure setting in both IIS and BizTalk- Configure setting in IIS and BizTalk for web service

!! Keep visiting BizTalkLive !!