至少必须为直接从本地队列管理器接受消息的每个远程队列管理器定义一个传输队列。
At least one transmission queue must be defined for each remote queue manager to which the local queue manager is to send messages directly. To configure the WebSphere MQ transmission queue.
WebSphereMQ传输队列是临时存储将发送到远程队列管理器的消息的队列。
WebSphere MQ transmission queues are queues that temporarily store messages that are destined for a remote queue manager.
如果可以(可靠地)将访问权授予给从那个远程队列管理器发送命令的特定身份，那么情况会好得多。
It would be much better if access could be granted (reliably) to specific identities sending commands from that remote queue manager.
一种特殊的本地队列类型，消息将存储在其上，直到成功地将消息传输并存储在远程队列管理器上为止。
A special type of local queue on which messages are stored until they can be successfully transmitted and stored at a remote queue manager.
如果您的应用程序要求从远程队列管理器上返回消息，则需要在两个队列管理器之间定义另一个相反方向的通道。
If your application requires messages to be returned from the remote queue manager, you need to define another channel to run in the opposite direction between the queue managers.
可以使用CNF，例如，如果远程队列管理器的证书由CA签名，那么只有CA的证书出现在本地队列管理器的密匙列表中。
A CNF can be used, for example, if the remote queue manager's certificate was signed by a ca, and only the ca's certificate is in the local queue manager's key ring.
这将使您立即能够访问任意本地队列管理器，如果安装了WebSphereMQ客户端，还可以访问任意远程队列管理器。
This will instantly give you access to any local queue managers and, assuming you have WebSphere MQ client installed, to any remote ones as well.
到队列管理器的远程连接通常通过通道进行。
Remote connections to a queue manager typically occur over a channel.
远程连接的身份验证：对于客户端连接和来自其他队列管理器的通道，存在许多与身份验证相关的常用实践。
Authentication of remote connections: There are a number of common practices that are related to authorization of client connections and channels from other queue managers.
由于它能截取队列管理器本身内的API调用，因而MA0W与应用程序所用的编程语言无关，实际上也与应用程序是本地的还是远程连接的也没有关系。
Since it intercepts API calls within the queue manager itself, MA0W is indifferent to the programming language the application USES, and indeed whether the application is local or remotely connected.
问题在于，您如何对远程连接用户、以客户端模式连接的应用程序以及来自其他队列管理器的连接进行身份验证。
The trick is in how you authenticate remotely connected users, applications connecting in client mode, and connections from other queue managers.
Queuemanagername：设置成远程WebSphereMQ队列管理器的名称。
Queue manager name: set to the name of the remote WebSphere MQ queue manager.
这个过程可以使设备上的任何队列都通过一个定义来寻址，从而将远程队列定义的数量降到与设备队列管理器的数量相同。
This procedure allows any queue on the device to be addressed through the one definition, reducing the number of remote queue definitions to the number of device queue managers.
该远程队列定义是用目标设备队列管理器名称和队列名称定义的。
The remote queue definition is defined with the target device queue manager name and queue name.
您可以利用MQ搜索顺序并只按照远程队列定义来定义设备队列管理器名称。
You can take advantage of the MQ search order and define just the device queue manager name as the remote queue definition.
正常的做法要求每个设备队列管理器都有一个远程队列定义。
Normal practice requires one remote queue definition for every device queue manager.
应用程序连接到(相对代理队列管理器来说)远程的队列管理器。
Applications connect to a queue manager which is remote from the broker queue manager.
该脚本的初始版本包含队列管理器的本地基准，例如设置死信队列、锁定远程管理访问以及优化通道。
The initial version of the script contains the local baseline for a queue manager, such as setting the dead queue, locking down remote administrative access, and tuning channels.
队列管理器也可以包含属于其他队列管理器的队列的定义，此类定义称为远程队列定义。
It can also have definitions for queues owned by other queue managers, which are called remote queue definitions.
同样，队列的远程定义不能被称为是真实的WebSpheremq队列名称，这是由于该引用不存在于网关队列管理器中。
Also, the remote definition of the queue can not be called the real WebSphere MQ queue name as that reference does not exist on the gateway queue manager.
与目标队列管理器名称相同的远程队列定义。
A remote queue definition with the same name as the target queue manager.
Q复制还支持WebSphereMQ客户机-服务器配置，其中 QCapture和 QApply程序运行在安装了 MQ客户机的系统上，并与远程的队列管理器连接。
Q replication also supports WebSphere MQ client-server configurations where the Q Capture and Q Apply programs run on a system with an MQ client installed and connect to a remote queue manager.
订单输入应用程序将MQEveryplace消息写入本地队列管理器中所定义的远程队列。
The order entry application writes the MQ Everyplace message to a remote queue defined in the local queue manager.
请求消息现在不仅通过JMS发送到基于JMS的服务提供者，而且通过WebSphereMQ转发到远程mq队列管理器控制的队列。
The request message was now not only sent via JMS to the JMS-based service provider, it was also forwarded via WebSphere MQ to a queue controlled by a remote MQ queue manager.
请求消息现在不仅通过JMS发送到基于JMS的服务提供者，而且通过WebSphereMQ转发到远程mq队列管理器控制的队列。
The request message was now not only sent via JMS to the JMS-based service provider, it was also forwarded via WebSphere MQ to a queue controlled by a remote MQ queue manager.
应用推荐