Biztalk 编排发布为由计划任务适配器使用的 Web 服务
正如我此处所问，我有一个由作为 Web 服务发布的公共端口启动的编排。每次调用此服务时，编排都会启动，
我也需要每 30 分钟启动一次编排。
我最终使用 计划任务适配器 来调用我自己的端口。我创建了一个计划的接收端口，它在每个给定时间创建消息，以及一个带有过滤器的发送端口，从该端口接收消息并将它们发送到 Web 服务端口
Orchestration 正确启动，但出现错误：
System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
经过研究，我发现Biztalk 不喜欢单向 Web 服务（即使此 Web 服务是由“Biztalk Web 服务发布向导”生成的）
我找到了类似 WCF-proxy，但我想知道是否可以只需将编排 Web 服务配置为双向（在向导中您可以强制它），然后按照我现在正在做的方式调用它。我正在尝试，但仍然收到类似的错误
有人遇到类似的问题吗？
谢谢
As I asked here, I have an orchestration that is started by a public port published as a web service. Everytime this service is called the orchestration starts
I need to start the orchestration every 30 minutes too.
I ended up using the Scheduled Task Adapter to call my own port. I created a scheduled receive port that creates messages every given time, and a send port that with a filter, receives messages from the port and send them to the web service port
Orchestation starts correctly, but there is an error:
System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
After researching, I found out that Biztalk doesn't like one-way web services (even if this web-service was generated by "Biztalk Web Service Publishing Wizard")
I found solutions like a WCF-proxy, but I was wondering if I could just configure the orchestration webservice to be two-way (in the wizard you can force it) and then call it the way i'm doing now. I'm trying but still receiving similar errors
Anyone had a similar issue?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
将“监听”形状添加到编排的开头，然后您可以拥有 2 个（或更多）并行的“激活接收”形状。
将辅助接收形状连接到新的单向逻辑端口（稍后指定）
部署后，将计划任务适配器连接到单向端口，以便它接收定期计划的消息。
与 BizTalk 一样，给猫科动物脱毛的方法不止一种，但这是我第一个想到的。
Add a Listen shape to the start of your Orchestration, you can then have 2 (or more) parallel Activating Receive shapes.
Connect the secondary Receive shape to a new one-way logical port (Specify-later)
Once deployed, hook your Scheduled Task Adapter up to the one-way port, so it receives the regularly scheduled message.
As always with BizTalk, there is more than one way to de-fur a feline, but this was the first to come to mind.