集群队列管理器。
Three WebSphere MQ cluster queue managers
三个WebSphereMQ集群队列管理器
Remote Queue Definition of Cluster Queue.
集群队列的远程队列定义。
A collection of information about the cluster queue managers.
关于集群队列管理器的信息集合。
A cluster queue manager does not have to host or advertise any queues.
集群队列管理器并不一定要承载或公布任何队列。
It can host cluster queues and advertise them to the other queue managers in the cluster.
它可以承载队列，并将其公布给集群中的其他队列管理器。
QM1 has a message producer application connected, putting messages to cluster queue DCQ1.
QM1 连接了一个消息生成方应用程序，并将消息放置到集群队列DCQ1 中。
Ideally, the cluster queue manager will also be tested before bringing applications back online.
理想情况下，集群队列管理器在使应用程序重新上线前也将被测试。
For a detailed example, see Migrating one cluster queue manager in the WebSphere MQ V7 information center.
请参见WebSphereMQV 7信息中心中的迁移一个集群队列管理器以获取一个详细示例。
This article explained how to deal with some of the major issues involved when migrating cluster queue managers.
本文讲解了如何解决在迁移集群队列管理器过程中涉及的一些主要问题。
QM5 holds QM3's changed cluster queue record, which includes the DEFPRESP attribute because QM5 is running at V7.0.
QM 5持有QM3的更改后的集群队列记录，由于QM 5运行在V 7上，所以该记录包含defpresp属性。
If a queue manager is the only host for a particular cluster queue, stopping that queue manager can obviously cause application outages.
如果一个队列管理器是一个特定集群队列的惟一宿主，那么停止该队列管理器显然会导致应用程序中断。
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 full repository contains a complete set of information about every cluster queue manager, while a partial repository contains a subset of this information.
完整的存储库包含关于每个集群管理器的完整信息集，而部分存储库包含此信息的子集。
To take advantage of the WebSphere MQ cluster configuration described earlier in this article, the configuration needs to change to use the cluster queue managers.
为了利用本文前面描述的WebSphereMQ集群配置，需要对配置进行修改，以利用集群队列管理器。
The solution USES a simple application to get each message from the cluster queue with no active message consumer applications and put them to another cluster queue.
这个解决方案使用一个简单的应用程序从没有活动消息使用方应用程序的集群队列提取消息，并将它们放置到另一个集群队列中。
Whether or not the plans and environments for test and production differ, it is always possible to find problems when migrating the production cluster queue managers.
无论测试和生产的计划和环境是否一致，总是会在迁移生产集群队列管理器时发现问题。
All future changes to the queues and queue managers in the cluster will be communicated through this repository.
所有将来对集群中的队列和队列管理器的更改都将通过此存储库进行通信。
You saw earlier that moving name resolution up to the cluster level diminished the role of the queue manager.
您在前面看到，将名称解析向上移动到集群级别减少了队列管理器的任务。
In Scenario 1, a large number of messages are sent to the flow and processed by both queue managers in the cluster.
在场景1中，大量消息被发送到数据流并通过集群中的两个队列管理器进行处理。
This makes administration of the clusters much easier and more reliable when clusters overlap, but it does restrict cluster and queue manager name lengths.
当集群重叠的时候，这使得集群的管理更加容易和更加可靠，但是也的确限制了集群和队列管理器名称的长度。
If the destination queue manager is not available, the messages are not routed to another queue manager in the cluster.
如果目标队列管理器不可用，则消息不会被路由到集群中的另一个队列管理器。
After the passive queue manager of IBMESBQM1 comes up, both queue managers in the cluster continue processing the messages.
在启动IBMESBQM1的被动队列管理器后，集群中的两个队列管理器将继续处理消息。
To ensure availability, set up at least two repository queue managers in a cluster.
为了确保可用性，请至少在集群中设置两个存储库队列管理器。
You can avoid these outages by defining the queue on other queue managers in the cluster, so that whilst migrating one queue manager, applications can use the alternate queues.
要避免这种中断，可以在该集群内的另一个队列管理器上定义该队列，这样，当您迁移一个队列管理器时，应用程序就可以使用备用队列。
You must choose at least one and preferably two queue managers in the cluster to serve as the full repository.
您必须选择集群中的至少一个（最好是两个）队列管理器作为完整存储库。
Build a queue manager and enroll it in the cluster.
构建队列管理器并在集群中对其进行注册。
The procedure could involve removing or suspending the queue manager from the cluster, backwards migrating, or keeping the queue manager offline until an external issue is resolved.
回撤流程可能包括从集群移除或挂起队列管理器、向后迁移和在外部问题得到解决之前保持队列管理器离线。
Used by the queue manager to receive messages from the other queue managers in the cluster.
由队列管理器用于从集群中的其他队列管理器检索信息。
Repeat these steps for the remaining queue managers in the cluster.
对集群中其他队列管理器重复这些步骤。
应用推荐