- This topic has 6 replies, 1 voice, and was last updated 8 years, 4 months ago by
.
-
Posts
-
-
I have successfully published an orchestration as a WCF web service using the BizTalk WCF Service Publishing Wizard. It works great.
I would like to now take that WCF service and move it to a different IIS server, but make it continue to call the same orchestration. In other words, the WCF Service and the BizTalk orchestration will be on two different servers.
Is this possible?
-
Yes,
the easiest method would most likely be to re-run to WCF publishing wizard, at the point where you tell it generate the service, enter a different machine instead of localhost.
i.e. http://newmachine/my_service.wcf
You will need to read msdn on permissions, im not 100% sure on what it needed.
Tarun
-
Thank you for the suggestion. I have tried that and I can successfully publish the WCF service out to another machine, but I am unable to configure it correctly so that it communicates back to the BizTalk server. It acts like it’s trying to access a receive location on the local server, which doesn’t exist. The WCF service doesn’t appear to know how to make a call to the recieve location on the remote BizTalk server. I cannot find any place in the config file where you specify a different server.
In other words, after the WCF service is published to a different server using the WCF publishing wizard, how does it know how to connect back to the BizTalk server? Where do you configure that?
Cullen
-
Actually, you don’t have to re-publish your orchestration on the other server, you can simply copy the the virtual directory generated on the biztalk server to the web server and re-configure the receive location to point to http://[web server name]/xyz.svc instead of http://localhost/xyz.svc. Also you’ll have modify the IIS pool identity to be some account that has access to the BizTalk MsgBox database.
[quote user="Cullen"]how does it know how to connect back to the BizTalk server?[/quote]
it shouldn’t know about the BizTalk Server location, rather, the BizTalk server will listen to the web server IIS to get its requests from there (according to the recieve location configuration)
Currently, Do you have any erros/warnings in the application event log while invoking the service?
hope it helps,
Mike
-
You can only host WCF receive locations on the Biztalk server.
Check the .svc file, it references the following class:
Microsoft.BizTalk.Adapter.Wcf.Runtime.CustomWebServiceHostFactory, Microsoft.BizTalk.Adapter.Wcf.Runtime, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
This is part of the Biztalk install and will only be present on a Biztalk server.
Isolated adapters handle the message in a non Biztalk host process, in this case IIS. The entire message receipt, pipeline processing and publishing to the message box is all done on in the IIS process.
-
I am having the same dilemma with BizTalk. I want to publish the web service to another server but I don’t know the requirements for biztalk in this server.
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.