jbi
美 
英
- 网络规范(Java Business Integration)
例句
Such a request-response messaging pattern is also allowed in JBI and referred to as in-out.
这种请求-响应消息模式在JBI中也是允许的，被称为in-out。
The rest of this series is all about using JBI and configuring ServiceMix to build an HSB.
该系列其余部分关于使用JBI以及配置ServiceMix来构建HSB。
Two years after it was released, the number of ESB implementations that do not use JBI outweighs the number that do.
JBI发布了整整两年后，不采用它的ESB实现居然比用的还多。
Integration was the initial idea behind the spawning of JBI, but it will prove to be useful in other situations.
集成是导致JBI产生的初始念头，但在其他情况下，其效用也将被证明。
This File Binding Component configuration provides a JBI service with the name esb: mail-service and has an endpoint with the name sender.
这个文件绑定组件的配置提供了一个名为esb：mail-service的JBI服务，并拥有一个名为sender的端点。
There were few people interested in deploying to SCA, but it was "on the radar" as something they may need in conjunction with JBI.
虽然只有很少人感兴趣于部署到SCA，但看起来在与JBI协作时，需要一些东西。
Step 3: The BC transforms the service invocation request into a normalized format defined by the JBI specification.
第3步：BC将服务调用请求转换成JBI规范定义的规范化格式。
This example implements a provider, which can be accessed from other JBI services by sending a JIB message to this service endpoint.
这个例子实现了一个提供者，其他JBI服务可通过向这个服务端点发送一条JBI消息，从而对该提供者进行访问。
Step 9: The BC connected with the first JBI environment transforms the service invocation request into a normalized message.
第9步：连接第一个JBI环境的BC将把服务调用请求转换成规范化消息。
This allows atomic actions to be performed as part of a JBI Exchange.
这使得原子活动能够作为JBI交换的一部分被执行。
This example is a blending of the first two examples with an additional JBI instance containing a non-replicated service.
这个示例是前两个示例的混合体，其中一个额外的JBI实例包含了不同的服务。
On a higher level, Swordfish is using a subset of the JBI standard for messaging abstraction and message routing between components.
在上层有JBI标准来实现组件之间的消息抽取（messagingabstraction）以及消息路由（messagerouting）。
When you're working with Petals, you don't configure the Service Unit in an xbean. xml file, you configure it in a jbi. xml file.
当联合使用Petals的时候，你是在jbi.xml文件中而不是在xbean.xml文件中配置服务单元。
The JBI specification provides a detailed XML schema for defining the behavior of all BCs and SEs that you wish to host on JBI.
JBI规范提供了详细的XML模式，它用于定义所希望在JBI中托管的所有BC和SE的行为。
To implement components of the JBI environment, ServiceMix uses the popular open source Spring framework (see Resources).
为了实现JBI环境组件，ServiceMix使用了流行的开源Spring框架（参见参考资料）。
All you need to do is to configure an external service provider and a consumer in the first JBI server.
您只需要在第一台JBI服务器中配置一个外部服务提供商和一个客户。
Now you'll assemble the service units into a JBI service assembly.
现在您将组装服务单元到JBI服务程序组合中。
BCs provide connectivity to services consumers and providers external to a JBI environment.
BC为JBI环境外部的服务消费者和提供者提供互联性。
Whenever you want to integrate a service into JBI, you need a JBI component, whether the service is WSDL-based or industry-specific.
无论何时您想集成服务到JBI，您都需要JBI组件，无论该服务是基于WSDL还是特定行业。
Plus, IBM and BEA were not involved in the specification because they did not believe it was needed.
还有，IBM和BEA并没有被参与规范的制定，因为这兄弟俩并不认为他们需要JBI。
In the JBI-based implementation services do not interact with each other directly.
在基于JBI的实现中，服务之间并不直接交互。
This version is not yet released at the moment of writing, so we will use a Mail JBI component provided b y another JBI implementation.
在撰写本书的时候，该版本尚未发布，因此我们将使用由另一个JBI实现提供的邮件JBI组件。
These enhancements do allow a JBI management operation to target a specific instance or a set of instances, or all instances.
这些提升使得JBI管理操作可以针对单个特定实例、实例集或者所有实例。
It includes reference implementation model and interfaces, which JBI-compliant products or an in-house JBI solution must implement.
它包含了引用实施模型以及界面，JBI的产品或者室内JBI方案必须实施这些模型与界面。
The anchor construct in JBI is the service container object, which supports plug-ins communicating through message routers.
JBI之中的固定构筑是服务容器对象，它通过信息路由器来支持插件之间的交流。
This means you can simply use the configuration of the Radiology Department application as the second JBI server.
这意味着您可以简单地使用RadiologyDepartment应用程序的配置作为第二台JBI服务器。
The runtime consists of a light weight JBI core, and several components.
在运行时由重量轻JBI核心，若干组成部分。
Write the JBI configurations for the service provider (that is the Radiology Department application) as well as the service consumer.
为服务提供商（RadiologyDepartment应用程序）和服务客户编写JBI配置。
The JBI specification has a standard interface named javax. jbi. component. Component, which all BCs should implement.
JBI规范有个标准接口名为javax.jbi.component.Component，所有BC都应当实现。
Oh and I'll point out again that JBI and SCA are not in conflict.
并且我要再一次指出JBI和SCA并不冲突。
In addition to standardized service definitions JBI uses the notion of "normalized" messages supporting global components interoperability.
除了标准化的服务定义，JBI使用“通用化（normalized）”消息的概念支持全局组件互操作能力。
JBI is based around a messaging paradigm that makes routing and processing decisions on normalized messages at runtime.
JBI立足于一个在运行时对规范消息做出路由和处理决议的消息传递范式。
These two elements are described in the JBI specification, but don't allow service specific configuration.
JBI规范对这两个元素进行了描述，它们不允许使用特定于服务的配置。
Figure 4 shows a service consumer and an external service provider connected to one JBI server.
图4显示服务客户和外部服务提供商连接一个JBI服务器。
Configuring an external service provider simply means telling the first JBI server that the second is a web service.
配置外部服务提供商仅仅意味着告诉第一台JBI服务器第二台JBI服务器是Web服务。
JBI provides all the features of an ESB that I have discussed, so I'll use it to build an HSB.
JBI提供了我所讲述的所有ESB特性，因此我将用它来构建HSB。
In this example we'll be using a JBI component provided by the Petals project, which we already discussed in chapter 1.
在本例中，我们将使用Petals项目提供的JBI组件，该项目已经在第1章讨论过了。
In this example we specified the service and endpoint names for the File sender JBI service.
在这个示例中，我们指定了文件发送者JBI服务的服务和端点名。
Step 10: The BC connected with the first JBI environment hands over the normalized message to the NMR.
第10步：连接第一个JBI环境的BC将规范化消息移交给NMR。
SJ: JBI is engine-to-engine, SCA wraps up the code in the engines.
SJ：JBI是引擎到引擎（engine-to-engine）的，SCA包装了引擎中的代码。
