但是，最近的趋势是直接将用户的客户机连接到队列管理器。
The recent trend, however, has been to directly connect the user's client to the queue manager.
该示例首先连接到队列管理器，并打开用于进行输出的队列句柄。
The example begins by connecting to the queue manager and opening a queue handle for output.
前面提到过，用户从服务器应用程序后面出来并直接连接到队列管理器。
As noted earlier, users are coming out from behind server applications and connecting to the queue manager directly.
在本地绑定模式连接中，主体是与连接到队列管理器的进程相关联的帐户。
For a local bindings mode connection, the principal is the account associated with the process that is connecting to the queue manager.
另一方面，此服务可能拥有连接到队列管理器或访问其发起队列的相关问题。
On the other hand, the service might have problems connecting to the queue manager or accessing its initiation queue.
在下面的例子中，连接到队列管理器QMGR1的权限被授予group1。
In the following example, authority to connect to queue manager QMGR1 is being granted to group1.
使用OAM 时，由connect授权体授予连接到队列管理器的权限。
Using the OAM, permission to connect to the queue manager is granted by the connect authority.
通用规则是，被适当允许连接到队列管理器的任何实体都应该授予+in q权限。
As a general rule, anything that is legitimately permitted to connect to the queue manager should be granted + inq rights on the queue manager and any objects it opens.
使用证书颁发机构的一个值得注意的副作用是，它外化了连接到队列管理器所需的配置。
An interesting side effect of using a certificate authority is that it externalizes the configuration required to connect to a queue manager.
对于某些连接，比如通道启动器或CICS，只有区域本身需要授权才能连接到队列管理器。
For the some connections, such as the channel initiator or CICS, only the region itself needs authorization to connect to the queue manager.
例如，通道启动程序地址空间的用户ID需要连接到队列管理器的权限，但通道本身不需要。
For example, the user ID for the channel initiator address space needs the authority to connect to the queue manager, but the channels themselves do not.
还记得在本用例中，应用程序需要连接到队列管理器，添加一个消息到队列中，并获得回复。
Recall that in this case, an application requires the ability to connect to the queue manager, put a message to a queue, and get a reply.
用户必须连接到队列管理器才能获取或放置消息，发出定义或更改队列的命令，启动通道等。
A user must connect to the queue manager to be able to get or put messages, to issue commands such those that define or alter queues, start channels, and so on.
这使得通道压缩的使用对连接到队列管理器的其他WebSphereMQ应用程序同样透明。
This makes use of channel compression equally transparent to other WebSphere MQ applications connecting to the queue manager.
企业应用程序使用MQ消息传递提供程序连接到队列管理器时，共有两个主要方法来进行此连接。
When an enterprise application uses the MQ messaging provider to connect to a queue manager, there are two primary ways in which this connection is made.
和前面一样，该代码首先连接到队列管理器，并打开队列句柄，但这次是为了使用缺省队列定义接收消息。
As before, the code begins by connecting to the queue manager and opening the queue handle, but this time for retrieving messages using the default queue definition.
下面是的例子展示了RACFPERMIT命令为用户ID授予连接到队列管理器CSQ1的通道启动程序权限。
Here is an example of a RACF PERMIT command to grant the user ID for the channel initiator permission to connect to queue manager CSQ1.
您仅需要设置属性SSLCIPHERSUITE 的值，以便在连接到队列管理器时能够开始一个SSL连接。
You simply need to set a value for the attribute SSLCIPHERSUITE to enable an SSL connection to be initiated when connecting to the queue manager.
在第一个用例中，单一分组fruit授予了连接到队列管理器、查询请求队列以及获取、浏览和查询回复队列的权限。
In this first use case, a single group fruit was granted access to connect to the queue manager, put and inquire on the request queue, and get, browse, and inquire on the reply queue.
客户端身份验证将确保只有那些能证明其身份的客户端(在本例中仅为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.
例如，名为QM1的队列管理器将创建一个名为TO . QM1的集群接收器管道，其他的所有集群成员将使用这个管道连接到它。
For example, a queue manager named QM1 would create a cluster receiver channel called TO.QM1 and every other cluster member would use that channel to connect to it.
用户将他们的工作站上的浏览器或客户机连接到应用程序服务器，后者又连接到一个队列管理器。
Users connected a browser or client on their workstation to an application server, which in turn connected to a queue manager.
当然，如果连接测试顺利，这只说明您能够在一个非ssl通道上连接到您的队列管理器，且您没有执行任意wmqfte端配置。
Of course, testing your connections work could just mean that you are connecting on a non-SSL channel to your queue manager, and have not performed any of the WMQFTE side configuration.
用于将队列管理器连接到另一个队列管理器的通道称为MCA 通道，因为它们使用消息通道代理。
The channels that connect queue managers to one another are known as MCA channels because they use a message channel agent.
此外，连接到部分储存库队列管理器的应用程序需要将消息放到集群队列中，集群队列可能驻留在其他节点上。
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.
每当引用一个队列管理器类型时，您必须在对应的WMQFTE属性文件中配置ssl，以便相关类型的WMQFTE实体能够连接到它的队列管理器。
In each case where a queue manager type is referenced, you must configure SSL in the corresponding WMQFTE properties file to enable that type of WMQFTE entity to connect to its queue manager.
然后，客户端自动重新连接到活动队列管理器。
The client was then automatically reconnected to the active queue manager.
现在，队列管理器已经启动，可以创建和启动队列管理器侦听器，以便应用程序连接到活动队列管理器IBMESBQM，如清单13所示。
Now that the queue manager has been started, you can create and start the queue manager listener for applications to connect the active queue manager IBMESBQM, as shown in Listing 13.
任何带有空白mcauser值的入站管道将允许任何连接到的队列管理器管理本地队列管理器。
Any inbound channel with a blank MCAUSER value will permit whatever is connecting to administer the local queue manager.
任何带有空白mcauser值的入站管道将允许任何连接到的队列管理器管理本地队列管理器。
Any inbound channel with a blank MCAUSER value will permit whatever is connecting to administer the local queue manager.
应用推荐