XML接收PipeLine问题 [英] XML Receive PipeLine Question
问题描述
我的应用程序中有以下流程：
流程：
1）使用SQL Adapter从SQL数据库接收数据
2）映射数据到指定的模式并将映射的消息作为XMLDoc发送到.net dll。
我正在使用SQL Adapter。
1）为XML接收管道配置SQL适配器接收端口。
2）我将传入的sql记录XML转换为模式。
3）为了记录转换消息，我将数据发送到文件发送端口。文件发送端口也是针对XML发送管道配置的。
这不起作用，除非我在发送端口上指定过滤器接收端口名称值。
：过滤器：BTS.ReceivePortname = {接收端口名称} '
问题：
1）如果我没有在发送端口上指定过滤器，我看不到发送文件端口中生成的映射文件。如果我指定过滤器，那么只有文件被转储到发送位置而不进行映射，并且不执行任何表达式形状语句（如trace.write或Call C＃代码）。
2）如果过滤器关联则任何跟踪在调试视图工具中没有显示接收和发送端口之间的表达式形式的语句。
3）这几天没有关联过滤器并且突然停止了。可能出现什么问题？
。Nilesh
Hi,
I have the following flow in my application;
Flow:
1) Receive the data from SQL database using SQL Adapter
2) Map the data to the schema specified and send the mapped message to a .net dll as a XMLDoc.
I 'm using SQL Adapter for this.
1) SQL Adapter receive port is configured for XML receive pipe line.
2) I have map transforming the incoming sql record XML to a schema.
3) For logging transforming message, I'm sending the data to a file send port. File send port also configured against XML send pipeline.
This does not work unless, I specify filter on my send port for receive port name value.
:Filter : BTS.ReceivePortname = {Receive Port name }'
Questions:
1) If I do not specify filter on send port, I see no mapped file generated in the send File port. If I specify filter then only file gets dumped on the send location without doing mapping and any expression shape statement (like trace.write or Call C# code) are not executed.
2) if filter is associated then any trace statements are written in expression shape in between receive and send port are not displayed in debugview tool.
3) This was working couple of days back without associating filter and suddenly stopped. What could have gone wrong?
.Nilesh
推荐答案
消息类型是否已更改，例如：目标命名空间已更改？< br>
我会查看BizTalk Mgmt控制台查询中的订阅，以查看消息框正在查找的内容，并查看已挂起的消息，并将消息与在此处定义的订阅进行匹配。
可能是业务流程已入伍但尚未启动，未列入清单或发送端口相同。
Has the message type changed eg: the target namespace has changed?
I would look in the subscriptions in the BizTalk Mgmt console queries to see what the message box is looking for and seeing a suspended message and matching up the messages compared to the subscriptions that are defined there.
It is probably the orchestration is enlisted but not started, unenlisted, or the send port the same.
这篇关于XML接收PipeLine问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
