BTS.ReceivePortName存在 [英] BTS.ReceivePortName exists

查看:121
本文介绍了BTS.ReceivePortName存在的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


在业务流程中,我们使用直接绑定,在接收形状上我们正在制作过滤器:


BTS .ReceivePortName存在


想知道为什么使用这个过滤器?


如果在任何BizTalk应用程序中有多个业务流程,并且我们正在使用此过滤器在编排A然后,每当一个消息出现在任何接收端口上时,这个编排A将始终执行。


我是对的吗?


请建议。




提前致谢!

解决方案

通常你也会将逻辑端口连接到已定义消息类型的接收形状。   即使您没有明确地将其添加到过滤器,它实际上也会为消息类型设置AND条件。您可以通过BizTalk管理控制台通过执行新查询验证


搜索,等于,订阅


订阅类型,等于,激活订阅


服务名称,等于,<编排名称>





Hi,

In the orchestration, we are using direct binding and on receive shape we are making the filter :

BTS.ReceivePortName exists

Want to know why this filter is used ?

If there are multiple orchestration in any BizTalk applications and if we are using this filter on orchestration A then every time a message comes on any receive port, this orchestration A will always execute.

Am I right ?

Please suggest.


Thanks in advance !

解决方案

Usually you will also have the logical port attached to a receive shape that has a message type defined.   Even though you have not explicitly added that to the filter, it will actually have a AND condition for the message type. You can verify this via the BizTalk Administration Console by doing a New Query,

Search for, Equals, Subscriptions

Subscription Type, Equals, Activation Subscription

Service Name, Equals, <name of orchestration>



这篇关于BTS.ReceivePortName存在的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆