请求管理器：这个子系统管理从客户端发送过来的搜索请求并把搜索请求分发到搜索子系统中。
Request Manager: This subsystem manages the search request from the client and then forwards the search request to the searching subsystem.
然后，客户端自动重新连接到活动队列管理器。
The client was then automatically reconnected to the active queue manager.
远程连接的身份验证：对于客户端连接和来自其他队列管理器的通道，存在许多与身份验证相关的常用实践。
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.
如果需要传输队列监听器，就必须与先前创建的客户端连接通道、队列管理器代理和网桥对象相关联。
If a transmission queue listener is required, it must be associated with the client connection channel, queue manager proxy, and bridge objects previously created.
首先，可以使用客户端连接在队列管理器上执行脚本命令。
First, there is the ability of using client connections to perform script commands on the queue manager.
SCA客户端(它可以是J2EE)通常在进程管理器外，例如它可以使用BPEL流程来编排工作流。
An SCA client (which could be J2EE) will typically be external to the process manager and might, for example, use BPEL flows to orchestrate workflow.
问题在于，您如何对远程连接用户、以客户端模式连接的应用程序以及来自其他队列管理器的连接进行身份验证。
The trick is in how you authenticate remotely connected users, applications connecting in client mode, and connections from other queue managers.
拥有J2EE客户端和设备管理器api包的程序员很快就可以开始研究IBM普及计算领域。
A programmer armed with a J2EE client, and the packages of the Device Manager API can quickly get started exploring the IBM pervasive computing universe.
这是多实例队列管理器和客户端自动重连接的说明。
Here is an illustration of the multi-instance queue manager and client auto-reconnect.
接下来，我们将配置JMS客户端用于同队列管理器进行安全ssl通信的通道。
Next, we will configure the channel with which the JMS client will communicate with the queue manager for SSL.
即使队列管理器与WebSphereApplicationServer运行在同一计算机上，您也必须使用客户端模式来进行通信，这是因为绑定模式并不支持SSL连接。
Even if the queue manager is co-located with the WebSphere Application Server, you must use client mode to communicate with it because bindings mode does not support SSL connections.
通过将消息从客户端发送到WebSphereMQ队列管理器来测试连接。
Test the connection by sending a message from the client to the WebSphere MQ queue manager.
客户端必须了解WebSpheremq队列管理器，以便将消息放到它的队列中。
The client must know about the WebSphere MQ queue manager in order to put messages to its queues.
将数据库管理器配置参数clnt _ pw _ plugin更新为NULL，以使用缺省的由ibm提供的客户端身份验证插件。
Update the database manager configuration parameter clnt_pw_plugin to NULL, to default to the client-side authentication plug-in provided by IBM.
这个客户端将把消息放在队列管理器IBMESBQM的输入队列ibmesbqm _ IN上。
This client would put messages on the input queue IBMESBQM_IN of the queue manager IBMESBQM.
自定义管理客户端将接收到部署管理器的j2ee.state.stopping通知。
The custom administrative client will receive a j2ee.state.stopping notification for the deployment manager.
它可以是连接到WebSphereMQ客户端通道的应用程序或用户，也可以是其他队列管理器。
It could be an application or user connecting to a WebSphere MQ client channel, or it could be another queue manager.
自定义管理客户端需要查询server类型的MBean，然后在一组返回的MBean中确定代表部署管理器的MBean。
The custom administrative client needs to query for MBeans of type Server, and then identify the one that represents the deployment manager in the set of returned MBeans.
但是绑定和客户端模式是根本不同的，因为在客户端模式下，通道存在于应用程序和队列管理器之间。
But the bindings and client mode are fundamentally different because, in client mode, a channel exists between the application and the queue manager.
在此情况下，可向自定义管理客户端添加一个过滤器，来识别仅应用于部署管理器的状态更改。
In this case, add a filter to the custom administrative client to identify only those state changes that apply to the deployment manager.
他们操作已经由客户端缓存管理器从文件服务器中取出的文件。
They work on files that have been fetched from file servers by the client-side cache managers.
现在我们已经配置好服务器连接通道，JMS客户端将使用此通道来与队列管理器进行通信。
We have now configured the server connection channel that the JMS client will use to communicate with the queue manager.
当队列管理器和应用服务器由网络连接的不同计算机承载时，将需要客户端模式连接。
When the queue manager and application server are hosted by different machines connected by a network, then a client mode connection is required.
如图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.
我们需要防止队列管理器接受来自只拥有队列管理器密钥存储区中的某个 CA 所签发证书的任何客户端的证书。
We need to prevent the queue manager from accepting a certificate from simply any client that has a certificate issued by one of the CA's in the queue manager's keystore.
通过将通道的SSLCAUT h属性设置为REQUIRED，管理员可以强迫客户端提供一个证书(请记住，本例中的“客户端”可以是另一个队列管理器)。
The administrator can force the client to present a certificate (keeping in mind that "client" in this case can be another queue manager) by setting the channel's SSLCAUTH attribute to REQUIRED.
如果WebSphereMQ管理团队使用桌面客户端访问队列管理器，此处所建议的配置将阻止此访问。
If the WebSphere MQ administration team USES a desktop client to access the queue managers, the configurations proposed here will break that access.
如果您的环境中不是这样，则必须提供- host和- port参数，以便管理客户端连接到部署管理器。
If this is not the case in your environment, then you must supply the -host and -port parameters to enable the admin client to connect to the deployment manager.
客户端身份验证将确保只有那些能证明其身份的客户端(在本例中仅为WebSphereApplicationServer)才能连接到队列管理器。
Client authentication will ensure that only those clients (in this case, only WebSphere Application Server) that can prove their identity will be able to connect to the queue manager.
为了提供这种支持，该API使得WebSphereMQ客户端连接到运行配置管理程序的队列管理器。
To provide this support, the API makes a WebSphere MQ client connection to the queue manager on which the configuration manager is running.
应用推荐