You work in an international company which is named TXTWIN. And you’re in charge of the company network and use Microsoft BizTalk Server 2006 R2.
You run the BizTalk Web Services Publishing Wizard. An orchestration is published as a Web service by you. And you are able to reference the Web service proxy in code. From a custom Microsoft .NET Framework application, you call the Web service proxy. No error is returned. But the orchestration behind the Web service does not instantiate. What should you do to make sure that when you call the Web service, the orchestration instantiates?

A.
Before the Web service proxy is called by using the custom .NET Framework application.
You should enable the receive location which is associated with the SOAP port by using the BizTalk administration console.

B.
Before you call the Web service proxy by using the custom .NET Framework application.
You should enable the receive location of the SOAP port that is associated with the orchestration.
Bind, enlist, and start the orchestration which was published as a Web service.

C.
The BizTalk Web Services Publishing Wizard should be run again.
Select the Merge all selected ports into a single web service check box on the Orchestrations and Ports page.
The Web service in the custom .NET Framework application should be re-referenced, and the Web service proxy should be called after the Web service is created.

D.
You should open the Receive Location Properties dialog box for the SOAP port by using BizTalk Explorer.
The SOAP port is associated with the orchestration.
The Enable the Service Window property should be set to True, and the Start Date and Stop Date properties should be set to Disabled.
The Web service proxy should be called by utilizing the custom .NET Framework application.

Explanation:
BURGOS: mnemo: “BizTalk Web Services Publishing Wizard … Web service proxy” = “by using the custom … SOAP …Bind, enlist, and start”