在通常情况下，网桥队列名称反映了WebSphereMQ目的地队列的名称。
Under normal circumstances, the bridge queue names reflect the name of the WebSphere MQ destination queue.
一种特殊的本地队列类型，消息将存储在其上，直到成功地将消息传输并存储在远程队列管理器上为止。
A special type of local queue on which messages are stored until they can be successfully transmitted and stored at a remote queue manager.
应用服务器环境的工作方式与排队网络很相似，一定要仔细地管理队列的大小，确保一层不会对另一层施加过大的压力。
The application server environment operates much like a queuing network, and it is important to manage the size of the queues so that one tier isn't overwhelmed by another.
服务器维护一个挂起请求队列，依次地执行它们，而不是先执行一个请求，然后再读取下一个请求，等等。
The server maintains a queue of pending requests, executes them one after another instead of executing one, reads the next request from the wire, and so on.
在上面的模型中，可以看到一个目的地(例如一个队列)唯一地分配给一个总线成员。
In the model above, it could be seen that a Destination for example, a Queue is uniquely assigned to a Bus Member.
这是一种优雅的系统，在队列满员之前，它都能很好地工作。
It's an elegant system that works wonderfully right up to the moment that the queue fills up.
默认情况下将从mq队列或主题单条地获取事件。
By default, events are retrieved from the MQ queue or topic as single events.
setmqaut命令用于授予和撤销授权，就像它一如既往地对队列所做的那样，但是具有一些新选项。
The setmqaut command is used to grant and revoke authorizations just as it always has for queues, but with a few new options.
如果数据成功地排到传输队列，则返回0。
If the data has been successfully queued for transmission, a zero is returned.
现在，我们已经在消息引擎中创建了一个队列目的地，如图19所示。
We have now set up a queue destination inside the message engine, as shown in Figure 19.
发送给队列的消息保留在队列中，直到显式地删除它们。
Messages sent to a queue remain on the queue until you explicitly delete them.
迁移将始终涉及到构建新的队列管理器、将应用程序和队列逻辑地移动到新的队列管理器，以及最终使旧的队列管理器退役。
Migration will always involve building a new queue manager, a logical move of the application and queues to the new queue manager, and the eventual decommission of the old queue manager.
这里隐含着一个难以察觉但非常重要的要求，在设计时，您必须知道目的地是队列还是主题。
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.
每个流定义了一组源目的地(例如，一组主题和队列)和一个目标目的地(消息将发往该目的地)。
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.
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.
动态临时目的地缓解了对CALLBACK队列的需求，减少了系统集成总线上队列的数量。
The dynamic temporary destinations alleviate the need for CALLBACK queues and reduce the number of queues on the system integration buses.
此目的地可以为主题或队列，具体取决于应用程序的域。
This destination might be a topic or a queue, depending on the application's domain.
接下来，创建映射到已经创建的队列目的地的队列。
Next, create a queue that is mapped to the queue destination you already created.
就我们此处的目的而言，只要理解异步是通过优化器明智地放置TQ(表队列)操作符而引入到联邦查询计划之中的就足够了。
For our purposes, it suffices to understand that asynchrony is introduced into a federated query plan by the optimizer's judicious placement of the TQ (Table Queue) operator.
常规的队列目的地可配置为从外部总线接收消息。
A regular queue destination can be configured to receive messages from a foreign bus.
设置队列的jms目的地。
第3部分描述了队列目的地的创建过程。
该目的地将成为常规队列目的地。
一名中尉立于队列的右侧，佩剑曳地，左手搭在右手上。
A lieu tenant stood at the right of the line, the point of his sword upon the ground, his left hand resting upon his right.
应用推荐