BAM跟踪正确的方法? [英] BAM Tracking correct approach ?
问题描述
我有一个场景,由OrchA选择EDI x12发票文件并保存到SQL数据库。
取决于通知(如果标志更新设置为1),Orch B直接绑定并订阅来自数据库的消息。
所以,我想跟踪端口级别即发送和接收以及Orch A和Orch B中的订阅发送出去。
这一切都可以在一个活动中完成吗? 这将是一个很好的方法TPE或BAM API
MBH
TPE肯定。
BAM API允许用户使用"MessageTracking"命名空间,以帮助检索消息接收时间,但永远不会返回消息发送时间(这是因为发送是BizTalk中的另一个订阅者)。
使用业务流程BAM API和继续ID来过去必须在管道中声明复杂的属性模式和促销。
关于活动定义,是的,它可以在一个活动中完成。
问候。
I have a scenario where an EDI x12 Invoice file is picked up by an OrchA and is saved to SQL Database.
Depending on the notification(if flag update sets to 1), Orch B is directly binded and subscribes the Message from Database.
So, I want to track at Port levels i.e Send and Receive and within Orch A and Orch B when subscribes and sends out.
Can all this be done in one Activity? Which would be a good approach TPE or BAM APIs
MBH
TPE definitely.
BAM API permit one to use the "MessageTracking" namespace to help retrieve the Message receive times but never return a message send time (this is because the send is another subscriber in BizTalk).
Use the orchestration BAM API and continuation id's to get past having to declare complex property schemas and promotions in pipelines.
Regarding Activity definiton, yes it can be done in one activity.
Regards.
这篇关于BAM跟踪正确的方法?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!