BizTalk 2009 ESB困惑

问题描述

我对BizTalk有点经验，并且在不使用BizTalk 2009 ESB Toolkit 2的情况下进行了尝试.首先，我想知道是否有人可以为我澄清几个概念:

1. 入口"和接收端口"有什么区别?
2. 为什么需要行程，难道不能仅使用端口和业务流程来创建相同的行程吗?我显然在这里错过了一些东西.

两个更常见的问题:

1. 所有消息是否还必须通过消息框?

在此先感谢您的见解.

解决方案

斜坡上

基于斜坡的是基于Web服务的接收端口，但是它们接受通用XML消息时有些不同.但是，消息将具有非常特殊的SOAP标头(如果需要的话，将带有信封")，具有所有必要的属性以使例如消息行程成为可能.您可以通过查看"EsbEnvGeneric.xsd"找到所有可能的标头.

入门

我喜欢NealWalter对此的答复.但是，我只是想添加消息行程方法，可以节省很多时间和开发工作.它可以使组织更加敏捷，并简化其流程中的更改.如果我们不必开发和部署全新的业务流程，而只需更改一些配置并使用我们现有的组件，那当然可以节省很多时间.正如我所看到的，这是ESB和消息行程中的最大价值.

消息框

BizTalk中的消息始终必须通过消息框输入.在下一版本中，MS暗示了BizTalk中的低延迟情况-也许我们可以获得更多控制权，但是到目前为止，更多的消息在通过BizTalk的过程中被保留了很多次，对此没有任何意义./p>

I have a little experience with BizTalk and am trying to understand BizTalk 2009 ESB Toolkit 2 without using it. Firstly, I am wondering whether anyone can clear up a couple of concepts for me:

1. What is the difference between an "on-ramp" and a "receive port"?
2. Why do you need itineraries, can you not simply create the same using ports and orchestrations? I am obviously missing something here.

A couple of more general questions:

1. Do all messages still have to go through the Message Box?

Thanks in advance for any insight.

解决方案

On-ramps

The on-ramps are web service based receive port but they are a bit different as they accepts generic XML messages. The messages will however have a very special SOAP header (a "envelope" if you will) with all the necessary properties to make for example message itinerary possible, You'll find all the possible header by having look in "EsbEnvGeneric.xsd"

itineraries

I like NealWalter reply on this on. I however just like to add the message itinerary approach can potential save a lot of time and development effort. It can make an organizations more agile and ease change in their processes. If we don't have to develop and deploy a whole new orchestration but only change some configuration and use our existing bits that can of course save a lot of time. And this is the big value in a ESB and message itinerary as I see it.

Message Box

Messages in BizTalk always have to go via the message box. In the next version MS have been hinting about a low latency scenario in BizTalk - maybe then we can gain a bit more control, But more but for now messages get persisted many times on their way through BizTalk and there is nothing to about that.

这篇关于BizTalk 2009 ESB困惑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！