业务流程中的BizTalk关联 [英] BizTalk Correlation in Orchestrations

问题描述

Hello All，

Hello All,

我有一个场景，我在呼叫SP时它给了我一个回应。现在让我们将Request Msg的消息类型称为Arequest，将Response Msg的消息类型称为Aresponse。 Arequest中有一个名为ID的节点。在将数据发送到SP时，我正在将
Orchestration中的相关性初始化为该ID。当我收到来自SP的响应时我检查它是1还是0如果它是0我有一个接收形状，ID具有以下相关性，而不同的消息类型就是说Debatch。如果我从SP获得1，我会调用
一个视图，该视图将返回带有N个ID的响应。现在我必须为每个ID发送消息类型debatch，然后发布到消息框，以便它可以被脱水编排订阅（我之前用于脱水的接收形状
！）我能够做到所有这一切，但在调配业务流程后，我在BizTalk中遇到路由失败错误。当我检查挂起的orchestaration的订阅时，订阅是1.对于ID而消息类型是2，
订阅是debatched消息的根节点。

I have a scenario in which in am calling an SP and it gives me a response. Now lets call the messagetype of Request Msg as Arequest and messagetype of Response Msg as Aresponse. There is a node in Arequest called ID. I am in innitialising a correlation in Orchestration for that ID while sending the data to SP. when I recieve the response from SP I check if it is a 1 or a 0 if it is a 0 I have a receive shape with a following correlation of ID and a different messagetype say Debatch. If I get a 1 from SP I call a view which will return a response with N number of ID. now I have to debatch for each ID to a messagetype debatch and then publish to the messagebox so that it can be subscribed by the dehydrated orchestrations (the receive shape that I was using for dehydration earlier!) I am able to do all this but after debatching the orchestration I am getting a routing failure error in BizTalk. When I check the subscriptions for the suspended orchestaration the subscriptions are 1. for the the ID and 2 for the messagetype as the root node of the debatched message.

请帮助

推荐答案

据我所知，SP的调用是一个请求-Response，因此是一个双向的编排端口。这些是BizTalk / Adapter自动关联的，所以我不确定你为什么要在请求上初始化相关集？

It is my understanding that the invocation of a SP is a Request-Response and thus a TWO-WAY Orchestration Port. These are auto-correlated by BizTalk/Adapter so I'm not sure why are you initializing correlation sets on the request?

问候。

这篇关于业务流程中的BizTalk关联的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！