在上一节中，您配置了一个共享工作路径并设置了一个MI队列管理器，因此您可以继续第三步。
In the previous section, you configured a shared work path and set up an MI queue manager, so you can move on to third step.
你还应该看到右侧的脚本资源管理器中列出的所有验证点和测试对象。
You should also see all of the verification points and test objects listed in the Script Explorer on the right.
在部署中，有些队列管理器被选择用于存储和维护这些存储库。
In a deployment, some of the queue managers are chosen to store and maintain these repositories.
空业务空间显示在业务空间管理器中。
The empty business space is displayed in the business space manager.
在三层架构中，队列管理器只了解应用程序的身份。
In the three-tier architecture, the queue manager knew only the identity of the application.
在队列管理器中创建物理队列FROMWASQ。
在下面的示例中，假定部署管理器在与执行脚本的会话相同的主机的缺省端口运行。
In the examples shown below, the deployment manager is assumed to be running on the default port on the same host as the session in which the script is being executed.
恢复您在步骤8中备份的部署管理器配置。
Restore the deployment manager configuration you backed up in Step 8.
在此示例中，事务管理器流程使用以下参数连接到数据库。
This example causes the transaction manager process to connect to the database with these parameters.
在ha1上删除安装中的部署管理器日志目录。
Remove the deployment manager log directories from the installation on ha1.
启动Server2中队列管理器的备用实例。
注册是通知事务管理器关于事务中可能包括的资源管理器信息的过程。
Registration is the process of informing the transaction manager about the resource managers that could be involved in a transaction. There are two types of registration
在业务空间管理器中，您可以访问业务空间的任何页面。
In the business space Manager, you can access any of the pages for your business Spaces.
在启动IBMESBQM1的被动队列管理器后，集群中的两个队列管理器将继续处理消息。
After the passive queue manager of IBMESBQM1 comes up, both queue managers in the cluster continue processing the messages.
这个环境中没有部署管理器。
在此体系结构中，队列管理器是对象名称的根上下文，用于管理和操作的过程反映了这种倾向。
In this architecture, the queue manager is the root context for object names, and the procedures for administration and operation reflect this orientation.
创建从代理队列管理器到FTE网络中其他任何代理队列管理器的渠道。
Create channels from the agent queue manager to any other agent queue manager in the FTE network.
在作业管理器中，通过查询来检索节点以及其他作业管理器构件。
In the job manager, nodes as well as other job manager artifacts are retrieved by query.
如果在提交过程中事务管理器失败，则事务可能在资源管理器中处于未确定状态。
Should the transaction manager fail during the commit processing, the transaction may be left in-doubt in the resource managers.
在静态注册中，事务管理器包括向其注册的所有资源管器，即使资源管理器在事务分支中没有扮演角色也是如此。
In static registration, the transaction manager involves all the resource managers that are registered with it, even if a resource manager does not have a role to play in a transaction branch.
它完成在流程服务器配置中作为部署管理器节点的部件。
It completes the part serving as the Deployment Manager node in the process server configuration.
要把旧的连接从事务管理器的缓存中移除，这样的话，资源管理器恢复可用后的第一个事务调用就不会出错。
Stale connections should be removed from the transaction manager cache so that first invocations of transactions after the resource manager becomes available do not fail.
在通过此方式采用代理时，运行时代理中的状态将取代配置管理器中的任何信息。
When adopting a broker in this way, the state in the run-time broker supersedes any information in the configuration manager.
隐式依赖关系在管理器定义中通过对其他管理器的引用定义。
The implicit dependencies are defined by the references to other managers within a manager definition.
完整存储库队列管理器接收集群中其他队列管理器发送的消息，并据此更新其存储库。
The full repository queue managers receive information sent by the other queue managers in the cluster and update their repositories accordingly.
将此文件传输到创建了协调队列管理器的服务器，并在队列管理器中运行。
Transfer this file to the server where the coordination queue manager is created and run it against the queue manager.
由队列管理器用于从集群中的其他队列管理器检索信息。
Used by the queue manager to receive messages from the other queue managers in the cluster.
在新的范式中，队列管理器只是队列和主题的生命保障。
In the new paradigm, queue managers are merely life support for queues and topics.
这些变化一起促生了2.6内核中的内存管理器，它的设计目标是更高的性能、效率和稳定性。
These changes all work together to produce a memory manager in the 2.6 kernel designed for better performance, efficiency, and stability.
为了执行从故障场景中恢复，事务管理器和资源管理器必须能够在事务流程的任何点从故障中恢复。
In order to implement recovery from failure scenarios, the transaction manager and the resource manager must be able to recover from a failure at any point in the transactional flow.
应用推荐