The JMS JNDI objects are bound to the actual objects in the message engine.
将JMSJNDI对象绑定到消息引擎中的真实对象中。
Figure 9 shows how the message engine is part of the application server.
图9显示了如何使消息引擎成为应用服务器的一部分？
A message engine has its own data source, which is USES to store persistent messages.
消息引擎有自己的数据源，它用来存储永久性消息。
We have now set up a queue destination inside the message engine, as shown in Figure 19.
现在，我们已经在消息引擎中创建了一个队列目的地，如图19所示。
Queues are configured on individual bus members, which means they belong to a message engine.
在单独的总线成员中配置队列，这意味着它们属于消息引擎。
Messages that are managed-non-persistent, however, are lost when the message engine is restarted.
不过，Managed - non - persistent类型的消息会在消息引擎重启时丢失。
At this point, we have now implicitly created a message engine inside the application server (Figure 15).
这时，我们已经隐式地在应用服务器中创建了一个消息引擎(图15)。
A message engine is also established for the bus, and a DataSource for that message engine is established.
还会为总线建立一个消息引擎，为该消息引擎建立一个DataSource。
Here, we will create the connection factory that the session bean will use to connect to the message engine.
此时，我们将创建连接工厂，会话Beang将使用此连接工厂连接到消息引擎。
To optimize Monitor performance, you usually need to configure the Monitor and the message engine databases.
要优化Monitor性能，您通常需要配置Monitor和消息引擎数据库。
A message engine has exclusive control of its own data store, so no other message engine can be linked to that data store.
消息引擎具有其自身数据存储的专用控件，因此其他消息引擎不能链接到它的数据存储。
In Figure 18, we will assign the queue to a particular message engine by selecting the bus member that will host the queue.
在图18中，通过选择承载队列的总线成员来将队列分配给特定的消息引擎。
The M-Commerce platform USES a message path finding algorithm to create a message queue in XML message engine for routing.
此平台采用分布式消息路径选择算法生成消息交换路径树，便于XML消息引擎生成一个队列和路由策略。
We will now create a queue in the message engine. By doing so, we will define a messaging destination that will be available to the bus.
现在，我们将在消息引擎中创建一个队列。
Managed-persistent is the most reliable, using the message engine and store to persist messages across server and message engine restarts.
Managed - persistent最可靠，使用消息引擎，并进行存储来保存消息，不受服务器和消息引擎重启影响。
Managed-non-persistent USES a message engine to store requests, and so can recover from loss of messages due to network and server failures.
Managed - non - persistent使用消息引擎存储请求，因此您可以在网络或服务器发生故障时恢复丢失的消息。
Remote database data store: in this configuration, a database residing on a remote system is configured to act as the message engine data store.
远程数据库数据暂存器：在此配置中，远程系统中的数据库将充当消息引擎数据暂存器。
When an application server becomes a member of a bus, it automatically gets configured with a message engine that implements bus functionality inside the application server.
当应用服务器成为总线的成员时，总线就自动配置了一个消息引擎来在应用服务器内实现其功能性。
File-based data store: (default) If the message engine is configured to use a file-based data store, operating information and messages are persisted to the file system instead of a database.
基于文件的数据暂存器：(默认)如果配置消息引擎使用基于文件的数据暂存器，则操作信息和消息将持久化到文件系统中，而不是数据库中。
A use case that requires messages for a service be stored in a message engine and persist across server restarts would need to specify the following in its SCDL (for the "OrderStatusService" service).
如果用例需要将服务的消息存储在消息引擎中，并跨服务器重启，则需要在其SCDL中指定以下代码(对于“OrderStatusService”服务)。
The specification defines a message exchange protocol between the BPEL engine and a task component.
这个规范定义了BPEL引擎和任务组件之间的消息交换协议。
When using XMLT nodes, be aware that the message tree is first serialized and then sent to transformation engine.
使用xmlt节点时，请注意消息树将首先被序列化，然后再被发送到转换引擎。
This prevents the messaging engine from attempting to redeliver the message that caused the failure.
这将阻止消息传递引擎尝试重新传递引起故障的消息。
The information returned by the compensation service, its output message, does not have any affect to the process and is therefore discarded by the Process Choreographer engine.
补偿服务的返回消息、流程的输出消息不会对流程产生任何影响，因此被流程编排引擎丢弃。
At a minimum, you will need some type of SOAP processing engine to parse the messages that are received and to call the functions or methods that the message indicates.
至少，你需要某种类型的SOAP处理引擎来解析接收到的消息，以及调用消息指向的函数或方法。
When a SOAP engine receives a SOAP request, the usual way is to process the request and send the message in the same thread.
当SOAP引擎收到 SOAP请求时，通常的方法是处理请求并在同一个线程中发送消息。
This advantage may save the SOAP Engine from extra execution of matching the parameters in the input SOAP Request message (non WS-Address).
这种优点可以在输入SOAP请求消息(非ws -Address)中保存来自匹配参数的额外执行。
This is because the XPath runtime engine in Message Broker 6.1 (inline with the W3C XPath specification) doesn't support the concept of a NULL data type.
这是因为MessageBroker 6.1(符合W3CXPath规范)中的XPath运行时引擎不支持NULL数据类型的概念。
Stylesheets developed for use in another runtime engine such as WebSphere Application Server or the Mozilla Firefox Web browser can be reused without change in WebSphere Message Broker.
可以重用为了在另一运行时引擎(例如WebSphereApplicationServer或MozillaFirefoxWeb浏览器)中使用而开发的样式表，无需在WebSphereMessageBroker进行更改。
If you decide not to do this, the Process Choreographer engine will use the parts of the input and the output message of the forward service as input for the compensation service.
如果你不打算这么做，流程编排引擎将利用forward服务的输入和输出消息的不服那作为补偿服务的输入。
应用推荐