The idea of an ESB is not new.
ESB不是新构想。
The action is processed by ESB.
ESB处理上述动作。
What ESB features do we consider key?
我们认为哪些ESB功能是比较关键的？
So, is an ESB just a message bus?
那么，ESB就是消息总线吗？
Table 2: The minimum ESB capabilities.
表2：最低的ESB功能。
Figure 1 depicts the basic ESB pattern.
图1对基本esb模式进行了描述。
Current IBM Technology and the esb.
IBM目前的技术和esb。
那么ESB究竟是什么呢？
An ESB for message protocol transformation.
一个ESB，用于消息协议转换。
This is not specific to the ESB Gateway.
这并不是特定于esb Gateway的。
An ESB-centric view of the logical model.
逻辑模型的以esb为中心的视图。
Another strength of an ESB is performance.
ESB的另一个优点是性能。
ESB enforces security on application identity.
ESB基于应用程序标识执行安全性。
ESB的使用。
Different software products can form an ESB.
不同的软件产品可以构成ESB。
You're now ready to test the ESB integration.
您现在准备测试esb集成。
They sometimes even describe it as "An ESB but… ."
他们有时候甚至会这样描述需求“一个ESB，但……”。
ESB: Think of the bus as the glue in this scenario.
ESB：可以将总线视为此方案中的粘合剂。
Question: What is the difference between SOA and ESB?
问：SOA和ESB之间的区别是什么？
Data transformer: This is a key element of an ESB.
数据转换器：数据转换器是ESB的关键元素。
So what do they mean when they say they want an ESB?
那么，他们在说需要ESB的时候到底是希望什么呢？
Next generation, ESB-centric mainframe integration.
以esb为中心的下一代大型机集成。
The new action is received and processed by an ESB flow.
ES b流接收并处理这个新动作。
This guidance is based on a number of successful ESB projects.
指导工具包源于大量成功的ESB项目。
An ESB is an architectural pattern, not a software product.
ESB是一种体系结构模式，而不是软件产品。
This message bus is the gist of an ESB, and this is nothing new.
消息总线是ESB的基础，并且不是什么新鲜事物。
The problem is this: An ESB by itself produces no business value.
问题是：esb本身不产生任何业务价值。
Clients often don't think too much about the service part of ESB.
客户机经常不会太多考虑ESB的服务部分。
Deploying an ESB for such a solution is still very applicable.
为此类解决方案部署ESB仍然十分可行。
This adds an event object with information that is specific to ESB.
这添加一个带有特定于 ESB 的信息的事件对象。
应用推荐