此（路由器的）雷凌（芯片）硬件上不支持客户端网桥模式。
This ralink hardware does not support Client Bridge wireless mode.
不要在客户端使用usb无线网桥。
最后，您需要创建创建网桥队列，每个队列使用不同的客户端连接。
Finally, you need to create the bridge queues with each one using a different client connection.
每个网桥队列必须与单独的客户端连接相关联。
Each bridge queue must be associated with an individual client connection.
如果需要传输队列监听器，就必须与先前创建的客户端连接通道、队列管理器代理和网桥对象相关联。
If a transmission queue listener is required, it must be associated with the client connection channel, queue manager proxy, and bridge objects previously created.
为了减轻该问题，您可以创建多个网桥队列、客户端连接、服务器连接通道以及同步队列。
To alleviate this problem, you can create multiple bridge queues, client connections, server connection channels, and sync queues.
在标准配置中，单客户端连接连同单个网桥队列一起创建。
In a standard configuration, a single-client connection is created along with a single bridge queue.
需要创建多少个客户端连接对象，这取决于需要多少个网桥队列。
How many client connection objects you need to create will depend on how many bridge queues are required.
要想利用网关上的所有网桥队列，从而达到最佳消息吞吐量，网桥队列就需要在全部的客户端中平均分配。
To utilize all the bridge queues created on the gateway, and therefore achieve optimal message throughput, the bridge queues should be equally divided among all the clients.
如图1所示，如果有多个客户端经过通信监听器连接到网关队列管理器，网桥队列将会产生瓶颈。
As Figure 1 shows, if there are multiple clients connecting to the gateway queue manager through the communications listener, a bottleneck can be created by the bridge queue.
使用多个网桥队列和客户端连接对象可以显著提高从WebSphereMQeveryplace到websphere MQ的消息吞吐量。
Using multiple bridge queues and client connection objects can dramatically increase the throughput of messages from WebSphere MQ Everyplace to WebSphere MQ.
本文提供了循序渐进的指导，以帮助您使用WebSphereMQEveryplaceGatewayV2建立多个客户端连接和网桥队列，从而获得最佳消息吞吐量。
This article provides step-by-step instructions on how to set up multiple client connections and bridge queues to obtain optimal message throughput using WebSphere MQ Everyplace Gateway V2.
例如，如果现有3个客户端，每个客户端处于单独的网桥队列b 1、b2和b3，所有的远程队列定义可以有b的别名。
For example, if 3 clients existed each putting to separate bridge queues, b1, b2, and b3, all remote queue definitions could have an alias of b.
这就是说，如果有50 个网桥队列和 5,000 个客户端，那么就应该有 100 个客户端创建到bridgeq1 的远程队列定义，另外 100 个创建到bridgeq2 的远程队列定义，依此类推。
Therefore, if there are 50 bridge queues and 5,000 clients, 100 clients should create a remote queue definition to bridgeq1, another 100 should create a remote queue definition to bridgeq2 and so on.
这就是说，如果有50 个网桥队列和 5,000 个客户端，那么就应该有 100 个客户端创建到bridgeq1 的远程队列定义，另外 100 个创建到bridgeq2 的远程队列定义，依此类推。
Therefore, if there are 50 bridge queues and 5,000 clients, 100 clients should create a remote queue definition to bridgeq1, another 100 should create a remote queue definition to bridgeq2 and so on.
应用推荐