Is anybody familiar with setting up WCF-nettcp adapters for BTS?
有人熟悉为BTS设置WCF-nettcp适配器吗?
When I create a WCF-netTcp adapter for a Receive location, I am unsure how/when BTS will open up port 808 to listen on the address URI specified. It appears to only happen if I restart the entire BizTalk application. If it closes for some reason, I do not see any way of reconfiguring and reopening the port.
当我为接收位置创建WCF-netTcp适配器时,我不确定BTS将如何/何时打开端口808以侦听指定的地址URI。它似乎只有在我重新启动整个BizTalk应用程序时才会发生。如果由于某种原因它关闭,我看不到任何重新配置和重新打开端口的方法。
Furthermore, since that is only the net.tcp binding, there is no mex endpoint exposed. I believe client applications that wish to use that exposed WCF service needs mex metadata initially. Accessing that endpoint direct from a Visual Studio project would just yield
此外,由于这只是net.tcp绑定,因此没有公开mex端点。我相信希望使用暴露的WCF服务的客户端应用程序最初需要mex元数据。直接从Visual Studio项目访问该端点只会产生
Metadata contains a reference that cannot be resolved: 'net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc'.
Metadata contains a reference that cannot be resolved: 'net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc'.
If the service is defined in the current solution, try building the solution and adding the service reference again.
Cannot tell for such how to properly expose a mex endpoint to the service. the BizTalk WCF Service Publishing Wizard is confusing me; I cannot get it to reference the WCF adapter/Receive location I setup. I find no document that teaches what one ought to do for netTcp services; it is all about Http.
无法说明如何正确地将mex端点暴露给服务。 BizTalk WCF服务发布向导让我很困惑;我无法让它引用我设置的WCF适配器/接收位置。我找不到教授netTcp服务应该做什么的文件;这完全是关于Http。
1 个解决方案
#1
1
Funny, it took the walkthrough about publshing Net-Msmq WCF service to nudge me thinking how the WCF Service Publishing Wizard really works.
有趣的是,它花了很多关于发布Net-Msmq WCF服务的演练来推动我思考WCF服务发布向导是如何工作的。
The issue is this: When I manually created the WCF-netTcp Receive location, it has its endpoint URI e.g. net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc. When selecting the option to publish just an mex endpoint in the WCF Service Publishing Wizard, it will eventually ask for the WCF Service Location, which i confused to be the actual service location. Since it would accept nothing but Http URLs, it appeared to only support Http-based WCF endpoints.
问题是这样的:当我手动创建WCF-netTcp接收位置时,它有其端点URI,例如的net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc。当选择在WCF服务发布向导中仅发布mex端点的选项时,它最终将要求WCF服务位置,我感到困惑的是实际的服务位置。由于它只接受Http URL,它似乎只支持基于Http的WCF端点。
But for that textbox, one is supposed to place the Http URL that for just the mex endpoint, not the actual net.tcp WCF endpoint. That is the location in IIS where the wizard will create the necessary meta-data files. Once finished, that location, hosting a mex endpoint will inform clients of the real service located at the net.tcp endpoint.
但对于该文本框,应该只为mex端点放置Http URL,而不是实际的net.tcp WCF端点。这是IIS中的位置,向导将创建必要的元数据文件。完成后,托管mex端点的该位置将通知客户端位于net.tcp端点的实际服务。
#1
1
Funny, it took the walkthrough about publshing Net-Msmq WCF service to nudge me thinking how the WCF Service Publishing Wizard really works.
有趣的是,它花了很多关于发布Net-Msmq WCF服务的演练来推动我思考WCF服务发布向导是如何工作的。
The issue is this: When I manually created the WCF-netTcp Receive location, it has its endpoint URI e.g. net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc. When selecting the option to publish just an mex endpoint in the WCF Service Publishing Wizard, it will eventually ask for the WCF Service Location, which i confused to be the actual service location. Since it would accept nothing but Http URLs, it appeared to only support Http-based WCF endpoints.
问题是这样的:当我手动创建WCF-netTcp接收位置时,它有其端点URI,例如的net.tcp://biztalkserver/PostReceiveLocation_TCP/PostReceiveService.svc。当选择在WCF服务发布向导中仅发布mex端点的选项时,它最终将要求WCF服务位置,我感到困惑的是实际的服务位置。由于它只接受Http URL,它似乎只支持基于Http的WCF端点。
But for that textbox, one is supposed to place the Http URL that for just the mex endpoint, not the actual net.tcp WCF endpoint. That is the location in IIS where the wizard will create the necessary meta-data files. Once finished, that location, hosting a mex endpoint will inform clients of the real service located at the net.tcp endpoint.
但对于该文本框,应该只为mex端点放置Http URL,而不是实际的net.tcp WCF端点。这是IIS中的位置,向导将创建必要的元数据文件。完成后,托管mex端点的该位置将通知客户端位于net.tcp端点的实际服务。