行程消息传递与编排服务 [英] Itinerary messaging vs orchestration services

问题描述

   你能解释一下Messaging extender与Orchestration扩展器之间的行程服务之间的区别吗？我知道消息传递扩展器将在管道阶段运行，而Orchestration扩展器将在消息框中保留消息后运行。
但仍然不清楚，所以试过以下样本

    Could you explain the difference between Itinerary service in Messaging extender vs Orchestration extender. I know messaging extender will run in pipeline stage and Orchestration extender will run post the message persist in messagebox. But still not clear so have tried the below sample

Onramp - >消息传递扩展器（用于路由） - >编排扩展器（用于转换） - > off-ramp extender（用于从Orchestration扩展器路由转换后的消息） - > offramp

Onramp -> messaging extender( for routing) -> orchestration extender (for transformation) -> off-ramp extender( for routing the transformed message from Orchestration extender) -> offramp

我预计两个输出来自消息传递扩展器，另一个来自编排扩展器作为转换消息。

但是我只获得了转换后的消息。

I expected two outputs one from messaging extender and one from orchestration extender as transformed message.
But what i got only the transformed message.

这出了什么问题。

谢谢，

ChampBoss

ChampBoss

推荐答案

因为只有一条消息被"处理"， 

Because there was only one message being 'worked' on, 

行程是单条消息的路由单：

The itinerary is a routing slip for a single message:

如果你有一个消息扩展器，消息将通过它，做任何它的设计，然后它将通过业务流程扩展器，它将执行它需要做的任何事情。

If you have a message extender, the message will pass through that, doing whatever it is designed to do, then it will go through the orchestration extender, which will do whatever it needs to do with that.

因此：你会收到一条消息。

Hence: you will get one message out.

这篇关于行程消息传递与编排服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！