每个通道都有两个端点：在起始队列管理器内定义的发送端(sender)通道和在目的队列管理器内定义的接收端(receiver)通道，如图4中所示。
Each channel has two ends: a sender channel that is defined within the originating queue manager, and a receiver channel that is defined within the destination queue manager, as shown in Figure 4.
触发机制的目的是允许队列管理器基于消息的到达启动外部动作。
The purpose of triggering is to enable the queue manager to initiate external actions based on the arrival of messages.
根据本文的目的，我将使用两个队列管理器，我把它们称为QMA和Q MB。
For the purpose of this article, consider two queue managers, which I will refer to as QMA and QMB.
应用程序甚至可以将定义的搁置队列用于此目的。
The application could even use a defined backout queue for this.
例如，可在这里指定目的类型(队列或主题)。
For example, destination type (queue or topic) can be specified here.
Channel提供一个FIFO通信队列刚好能达到这一目的。
Channels provide a FIFO communication queue that can be used for just this purpose.
这是WebSpheremq队列管理器上的一个队列的名称，此目的地是该队列的别名。
This is name of the queue on the WebSphere MQ queue manager for which this destination is an alias.
现在，我们已经在消息引擎中创建了一个队列目的地，如图19所示。
We have now set up a queue destination inside the message engine, as shown in Figure 19.
集群队列管理器的目的是将运行不同版本的队列管理器加入到集群中，这也是分步迁移之所以成为可能的原因。
Cluster queue managers are designed to partake in clusters with queue managers running at different versions, which is why a staged a migration is possible.
队列是这样一个目的地：生产者向它发送消息，接收者从中取消息。
A queue is a destination to which a producer sends messages and from which the receiver takes messages.
动态临时目的地缓解了对CALLBACK队列的需求，减少了系统集成总线上队列的数量。
The dynamic temporary destinations alleviate the need for CALLBACK queues and reduce the number of queues on the system integration buses.
它只能浏览其所连接到的服务集成总线承载的队列目的地上的消息。
It can only browse messages on queue destinations hosted by the service integration bus to which it is connected.
接下来，创建映射到已经创建的队列目的地的队列。
Next, create a queue that is mapped to the queue destination you already created.
这里隐含着一个难以察觉但非常重要的要求，在设计时，您必须知道目的地是队列还是主题。
A more subtle but important implication is that you had to know whether the destination was a queue or a topic at design time.
这包括诸如服务集成总线、JMS提供程序、队列、主题、目的地等资源。
This includes resources such as service integration buses, JMS providers, queues, topics, destinations, and so on.
首先，您将了解如何利用队列目的地来使用点到点消息传递模型。
First you find out how to work with the point-to-point messaging model using queue destinations.
使用活动和过期队列出于以下目的：效率、负载平衡和其他一些目的。
The active and expiration queues are used for efficiency, load balancing, and other purposes.
每个流定义了一组源目的地(例如，一组主题和队列)和一个目标目的地(消息将发往该目的地)。
Each flow defines a set of source destinations (for example, a set of topics and queues) and a target destination to which the messages are to be delivered.
换句话说就是，JMS提供者可以向消息的发送方保证将消息发送到目的地(一个队列或主题)，并且是一次性发送。
In other words, the JMS provider can assure a message's sender that it was delivered to it's destination (a queue or topic) once and only once.
不过，队列和主题在传输级别上有本质的不同，所以必须将任何给定目的地的注册项专门定义为队列或主题。
However, queues and topics are inherently different at the transport level and so the registry entry for any given destination must be specifically defined as either a queue or topic.
jms目的地类型：队列或主题。
新的队列目的地将显示在总线的目的地列表中。
The new queue destination will appear in the list of destinations for the bus.
队列目的地，可以配置为进行点到点消息传递的目的地。
Queue destinations are destinations that can be configured for point-to-point messaging.
您可以把目的地看作是队列及主题的泛化。
You can think of destinations as a generalization of a queue and topic.
此目的地可以为主题或队列，具体取决于应用程序的域。
This destination might be a topic or a queue, depending on the application's domain.
如果匹配的话，您可将创建条目的用户别名添加到结果队列中。
If there is a match, you add the nickname of the user who created the entry to the results queue.
常规的队列目的地可配置为从外部总线接收消息。
A regular queue destination can be configured to receive messages from a foreign bus.
设置队列的jms目的地。
第3部分描述了队列目的地的创建过程。
第3部分描述了队列目的地的创建过程。
应用推荐