Biztalk脱水去除 [英] Biztalk Dehydration removal

问题描述

我正在尝试更改当前应用程序的设计以删除/减少脱水计数，因为这会导致性能。问题 我有一个长时间运行的业务流程，它接收大量的消息，进程并将输出消息
发送到其他系统并脱水。一旦从其他系统（收听形状）收到响应，此业务流程就会进一步执行一系列操作，例如将收到的大邮件发送到另一个系统。 我需要在这个设计中消除这种脱水。
请建议如何在BizTalk中实现这一点。

I am trying to change the design of my current application to remove/reduce the dehydrated count since this leads to performance issues.  I have a long running orchestration which receives large message , processes and sends the output message to other system and dehydrates. Once the response received from other system(Listen shape), this orchestration has further set of actions like sending the received large message to another system.  I need to remove this dehydration in this design. Please suggest how this can be achieved in BizTalk.

推荐答案

在转发大邮件之前是否需要收集信息？

您可以从intermediant系统发送小型更新，将这些更新发送到进行异步更新的辅助系统

Do you need to collect information before forwarding the large message?
You could receive small updates from intermediant system post these to secondary system doing asynchronous updates

1. 系统A接收大量消息并转发它到系统B，同时相关的小消息被发送到D和C，但是A没有等待响应
2. B和C发回他们的响应并被转发到D进行延迟更新第一份工作中发送的数据（1）

/ Peter

这篇关于Biztalk脱水去除的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！