This is how the queue manager is able to access the key database without human intervention.
这是队列管理器在没有人类干预的情况下访问密匙数据库的方式。
Since we are using only self-signed certificates, all of these root certificates represent inappropriate access grants to our queue managers.
因为我们现在只使用自签名证书，所有这些根证书代表对我们的队列管理器的不恰当的访问授权。
All other access, whether from interactive users or from other queue managers, should arrive over a channel protected by a low-privileged MCAUSER.
所有其他访问，无论是来自交互式用户还是其他队列管理器，都应该使用受低权限mCAUSER保护的通道。
Previous attempts at solving this problem have generally relied on some form of access to a data store, such as a relational database or queue.
以前尝试解决此问题时通常都依赖于采用某种形式的数据存储区访问，如关系数据库或队列。
This code sample shows how an EJB component might access a message queue resource, using connection objects.
代码样本显示了EJB组件如何使用连接对象来访问消息队列资源。
That is, the messaging engine authorizes access to the queue based on the connection identity as we discussed earlier.
即，消息传递引擎将根据我们前面讨论的连接标识对此队列进行访问授权。
If the QALIAS names a topic as its target (rather than a queue), then the user opening the QALIAS must have access to not only the alias queue, but also the topic.
如果QALIAS将一个主题(而不是一个队列)命名为其目标，则打开QALIAS的用户不仅需要拥有别名队列的访问权，还需要拥有对主题的访问权。
Here, you require access to put messages onto all user-defined queues but without also granting the adjacent queue manager administrative rights.
您要求访问将消息保存到所有用户定义的队列中，但不会为相邻队列管理器赋予管理权限。
When an EJB component wants to access a database, a message queue server, or some other transactional resource, it acquires a connection to the resource manager (usually by using JNDI).
当一个EJB组件想访问数据库、消息队列服务器或者其它一些事务性资源时，它需要到资源管理器的连接(通常是使用JNDI)。
However, that would require any programs using the queue to be aware that two different names would need to be used to access the queue, depending on whether browse or put access was required.
不过，这要求使用该队列的所有程序都要知道，需要使用两个不同的名称来访问队列，具体情况取决于是否需要浏览或发布访问权限。
It would be much better if access could be granted (reliably) to specific identities sending commands from that remote queue manager.
如果可以(可靠地)将访问权授予给从那个远程队列管理器发送命令的特定身份，那么情况会好得多。
You can also set policies that control access to our SQS queue based on date, time, and source IP Address, as in Listing 2.
您还可以设置一个策略，它根据日期、时间和源ip地址控制SQS队列的访问，如清单2所示。
First, ensure that the JMS Client has access to the CA certificates that are required to authenticate the queue manager.
首先，要确保JMS客户机拥有对CA证书的访问权，这些 CA 证书是认证队列管理器所必需的。
For example, for a queue, an MQQUEUE profile is used to control MQI access to the queue, but other profiles in the MQADMIN class are used to control context and alternate user security.
例如，对于队列，使用一个MQQUEUE概要文件来控制对该队列的访问，但是mqadmin类中的其他概要文件用于控制上下文和用户安全性。
When a queue manager is configured as the default queue manager, applications can access it without knowing its name.
将队列管理器配置为缺省队列管理器时，应用程序可以在不知道其名称的情况下对其进行访问。
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.
该脚本的初始版本包含队列管理器的本地基准，例如设置死信队列、锁定远程管理访问以及优化通道。
Another JMS client (subscriber) can access the queue and retrieve the message from the server.
而另一个JMS客户机(订阅者)则可以访问这个队列，并从该服务器获取这条消息。
The account has no access unless profiles are created for it, but using the techniques from the first case study would require a profile for every queue to which the channel needs access.
在创建配置文件之前，帐户不具有权限。但使用第一个用例中的技巧需要为通道访问的每一个队列都创建一个配置文件。
When the first user with write access releases the file, the top-most user from the queue is then given the write mode access.
当第一个以写模式访问的用户释放文件后，队列顶部的用户就能以写模式访问。
The exclusive access lock on the queue manager data and logs is released, and the standby queue manager takes over.
队列管理器数据和日志上的独占访问权锁释放，备用队列管理器接管。
For capture you want to ensure that the access to MQ message queue can be secured so that no invalid messages can be sent to RFIDIC.
对于捕捉，希望保护对MQ消息队列的访问，以避免无效的消息被发送给RFIDIC。
The objective is to grant the adjacent queue manager very broad rights to place messages onto user-defined queues on the local queue manager, but without also granting administrative access.
其目标是为相邻队列管理器赋予广泛的权限，允许将消息添加到本地队列管理器的用户定义队列中，同时赋予管理权限。
Sooner or later in the lifetime of a queue manager, there comes a time when access will need to be revoked.
在队列管理器的生命周期中，访问迟早是要被撤销的。
This is the bare minimum that will restrict administrative access from an adjacent queue manager and is only used here for illustration.
这是限制相邻队列管理器的管理权限的最小基本配置，此处仅用于演示。
The switches (if any exist) and the access list for RESLVEL should be similar throughout all of your queue managers.
RESLEVEL的开关（如果存在）和访问列表应该在您的所有队列管理器之间相似。
Figure 6 demonstrates how a write mode time queue for file access can improve data consistency
图6显示了文件访问的写模式时间队列如何改善数据一致性
In order to create or manipulate queue items, you need the Secret Access Key (40-character, alphanumeric sequence).
为了创建或操作队列项，您需要使用SecretAccessKey(由40个字母和数字组成)。
From the write access queue, user B is at the top of the queue since user B requests first to access the file in write mode compared with user C. user B is provided the write access.
在写访问队列中，用户B在队列顶部，这是因为b先于c以写模式请求访问文件。
As an administrator of WebSphere MQ, I also like the ability to enable or disable external access before the connection request ever reaches the queue manager.
作为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.
这将使您立即能够访问任意本地队列管理器，如果安装了WebSphereMQ客户端，还可以访问任意远程队列管理器。
应用推荐