在给定时间通过biztalk发送(推送)Soap WS消息 [英] Sending (pushing) Soap WS messages trough biztalk at given time
问题描述
我想知道是否有人可以在示例教程中提供示例或链接，以显示如何通过biztalk使用肥皂作为工作(在给定时间)发送消息.我在使用JMS的Java环境中具有这种经验，但是我是第一次在.net及其技术中做到这一点.
I would like to know if someone could provide example or a link on some tutorial which would show how to send messages using soap as a job (at given time) trough biztalk. I have expirience doing this with in java enviroment with JMS, but Im doing it for the first time in .net and its technologies.
我需要做的事情可以分为几步.
What I need to do could be broken into steps.
- 创建WCF SOAP服务，该服务将具有一种方法，用于通过BizTalk将数据收集从我们的系统发送到供应商系统.
- 在给定的时间执行此操作-创建一个每天执行一次的作业(计时器).什么是最好的方法?我应该由我自己编写此作业，还是在服务器上使用某些Windows调度程序很普遍?
非常感谢您提出任何建议.
Thanx a lot for any suggestions.
通讯概念:app1-client(这是计时作业)->发送数据-> biztalk-server(WS)->发送数据-> app2-server(WS)
Concept of comunication: app1-client(here is the timing job)->sends data->biztalk-server(WS)->sends data ->app2-server(WS)
推荐答案
通常，拥有数据的系统也拥有发送数据的调度是有意义的.例如，如果数据来自SQL Server，请使用SQL Server的内置计划功能(SQL Jobs)作为触发整个过程的触发器.然后，让SQL Job使用文件适配器将数据转储到BizTalk接收位置监视的文件夹中的文件中. BizTalk吸收文件，并使用发送端口(该端口订阅从拉入文件的接收端口传入的消息)使用WCF或SOAP适配器将数据发送到外部服务器上的Web服务.
Typically it make sense to have the system that owns the data also own the scheduling of sending out the data. For example, if the data is coming out of SQL Server, use SQL Server's built-in functionality for scheduling (SQL Jobs) as your trigger to kick off the whole process. Then, have the SQL Job dump the data to a file, in a folder monitored by a BizTalk receive location using the file adapter. BizTalk sucks in the file and a send port, which subscribes to the messages coming in from the receive port that pulled in the file, uses a WCF or SOAP adapter to send the data to your web service on the external server.
如果您不想或无法那样做，我已经看到人们在使用:
If you don't want to or can't do things that way, I have seen people use:
- CodePlex上的计划任务适配器(如@tomasr所引用)
- Windows计划任务(更难管理，尤其是在Windows Server 2008之前)
- 第三方作业计划软件(尤其是如果已经在使用)
如果触发机制无法访问需要流经BizTalk的数据，则BizTalk当然可以将数据发送到服务器的Web服务之前(例如从SQL Server)获取数据.在这种情况下，计划的作业可能会将文件放到BizTalk监视的文件夹中，其中包含一些BizTalk不在乎的内容-只需确保文件中有内容，因为BizTalk喜欢丢弃空的0字节文件
If the triggering mechanism does not have access to the data that needs to flow through BizTalk, BizTalk can certainly go and get the data (e.g., from SQL Server), before sending it to the server's web service. In that case the scheduled job could drop a file in the folder monitored by BizTalk with some content in it that BizTalk doesn't care about - just make sure that there is something in the file, because BizTalk likes to discard empty, 0 byte files.
BizTalk不是作业计划程序.因此，尽管您可以使用诸如计划任务适配器之类的东西，但是BizTalk的最大优点实际上是消息的转换，路由和/或业务流程编排，以及可插拔的体系结构(使用适配器).通常，您希望让BizTalk处理所有这些功能，并使用其他一些系统(如果有)进行调度.
BizTalk is not a job scheduler. So, though you can use something like the scheduled task adapter, BizTalk's sweet spot is really the transformation, routing, and/or business process orchestration of messages, along with a pluggable architecture (using adapters). Typically you want to let BizTalk handle all of those functions and use some other system (if available) for scheduling.
这篇关于在给定时间通过biztalk发送(推送)Soap WS消息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
