您也可以在该集群上为SI总线手动创建附加的消息传递引擎。
You can also manually create additional messaging engines on that cluster for that SI Bus.
如果目标队列管理器不可用，则消息不会被路由到集群中的另一个队列管理器。
If the destination queue manager is not available, the messages are not routed to another queue manager in the cluster.
因此目的地上的消息可同时由两个集群成员处理。
Therefore messages on the Destination can be processed by both cluster members.
借助会话相关性，预定前往某个应用程序会话的消息总是被路由到集群中的同一个会话。
With session affinity, messages that are destined for a certain application session are always routed to the same session in a cluster.
在集群环境中搜集日志消息还面临着一些挑战。
Gathering log messages in a clustered environment also presents some challenges.
流量管理器将向机器上各个端口的广播域发出一条集群检测消息。
The traffic manager sends out a cluster detection message to the broadcast domains for each interface on the machine.
集群中的消息直接从发送节点提交到接收节点。
Messages in the cluster are delivered directly from the sending node to the receiving node.
这个解决方案使用一个简单的应用程序从没有活动消息使用方应用程序的集群队列提取消息，并将它们放置到另一个集群队列中。
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.
相比之下，集群中的消息从原点到达多个可能的目标点。
By contrast, messages in a cluster travel from a point of origin to one of several possible destinations.
两个节点的发送器通道指向彼此，以交换描述集群事件的消息，如向集群添加新队列等。
The two nodes point to each other to exchange messages describing cluster events, such as adding a new queue to a cluster.
由于这些原因，SOA的采用正在推动从点对点消息网络到集群环境的迁移。
For these reasons, adoption of SOA is driving migrations from point-to-point messaging networks to clustered environments.
这简化了集群内的连通，我们可以通过组或者实例名来定位集群、套接字和消息通道。
This simplifies connectivity within the cluster, the cluster, socket, and message channels are simply addressed by the group or instance name.
如果目标组件是集群成员，则将消息重新提交到同一集群成员，进而完成重试设置。
If the target component is a cluster member, the message is redelivered to the same cluster member up to the retry setting.
QM1 连接了一个消息生成方应用程序，并将消息放置到集群队列DCQ1 中。
QM1 has a message producer application connected, putting messages to cluster queue DCQ1.
由流程引擎用于向集群发送消息。
It is used by the process engine to send messages to the cluster.
由流程引擎用于从集群获取消息。
It is used by the process engine to get messages from the cluster.
启动消息传递集群。
在创建消息引擎之前，需要定义通过集群的请求处理的行为策略。
Prior to creating the messaging engines, a policy defining the behavior of request processing across the cluster needs to be defined.
如果不想重启消息传递集群服务器，可以不重启。
You do not need to restart the messaging cluster servers if you don't want to.
在本文中，您了解了IBMWebSphereMQ提供的集群选项，以及如何利用集群消息传递来改善工作负载平衡。
In this article, you explored the clustering options available in IBM WebSphere MQ and you learned how clustered messaging can be used to improve workload balancing.
将消息传递引擎集群添加到总线，并将数据库模式设置为正确值。
Add the messaging engine cluster to the bus and set the database schema to the correct value.
单击add，然后将消息传递引擎集群添加到总线。
集群消息传递基础结构。
启动集群，确保消息传递引擎能够工作(它们应处于“启动”状态，还应检查集群中服务器的SystemOut . log)。
Start the cluster to make sure that the messaging engines work (they should be in the "started" state, also check the SystemOut.log for the servers in the cluster).
此外，连接到部分储存库队列管理器的应用程序需要将消息放到集群队列中，集群队列可能驻留在其他节点上。
In addition, applications connected to the partial repository queue managers need to put messages to clustered queues which might be hosted on some other node.
不过，在任何给定时间仅有一个集群成员拥有活动的消息传递引擎。
However, only one cluster member will have an active messaging engine at any given time.
每个集群只能有一个活动消息传递引擎。
不过，为确保故障转移，您需要为每个消息传递引擎配置单独的集群。
To ensure failover, however, you need to configure separate clusters for each messaging engine.
可以直接将消息提交到集群，而仅接收显式地定向到其上的消息。
It can simply feed messages into the cluster and receive only responses that are directed explicitly to it.
集群消息传递基础结构也许是整个关于集群的讨论中最复杂的部分。
Clustering the messaging infrastructure is perhaps the most complex aspect of the overall clustering discussion.
应用推荐