If you do, you specify the cell manager profile name and the cluster name, and the installer will do the rest.
如果是，您指定单元管理器配置文件名和集群名，而安装程序会完成其余操作。
The deployment manager must have complete information for all nodes in the cell, so the backup directory must come from the V5 deployment manager node.
部署管理器必须具有单元中所有节点的全部信息，因此备份目录必须来自于V5部署管理器节点。
When the deployment manager is migrated to Version 6, the nodes in the cell remain unchanged at whatever release level they supported prior to the deployment manager upgrade.
当部署管理器被移植到版本6时，单元中的节点保持不变，不管它们在部署管理器升级以前支持什么版本。
Restart the V5 cell: After all V5 federated nodes and the deployment manager have been rolled back, and the disablement process reversed, start the deployment manager, then start each node in turn.
重新启动V 5单元：回滚所有V5联合节点、部署管理器并且反转禁用过程后，启动部署管理器，然后依次启动每一个节点。
Additionally, the cell name of the V6 deployment manager profile must match the cell name from V5 deployment manager.
另外，V 6部署管理器配置文件的单元名称必须与V 5部署管理器的单元名称相匹配。
All the V5 nodes in the cell remain unchanged and are unaware that they are being managed by a new deployment manager.
在单元中的所有版本5的节点没有发生改变并且未察觉到是在新的部署管理器的管理之下。
First, the job manager's realm must be established as a trusted realm for the registered base nodes and the deployment manager cell.
首先，作业管理器的领域必须作为注册基本节点和部署管理器单元的受信任领域建立。
If no new V6 node is to be added to the cell after migrating the deployment manager, the entire cell may be run in compatibility mode.
如果在部署管理器移植完之后不会有新的版本6的节点加入到单元中，那么可以让整个单元运行在兼容性模式下。
When migrating a V5 deployment manager to V6, the cell name value of the V6 profile must match the cell name from V5.
当将V 5部署管理器迁移到v6时，V6配置文件的单元名称的值必须与V5的单元名称相匹配。
Ensure that the name of the cell and the name of the deployment manager node match your existing cell.
确保单元的名称和部署管理器节点的名称都与现有单元匹配。
Again, through a series of configuration steps, the initial installation of WebSphere Portal is added to the cluster cell defined within the Deployment Manager.
此外，通过一系列配置步骤，WebSpherePortal的初始安装被添加到在Deployment Managers中定义的集群单元。
In the case of a hardware failure, the node can be easily recovered back to the last configuration reflected in the cell configuration maintained by the Deployment Manager.
一旦出现硬件故障，节点可以轻松恢复到DeploymentManager维护的单元配置中反映的最后配置。
Once the deployment manager has been upgraded to Version 7, all the nodes in the cell can stay unchanged at whatever release level they supported prior to the deployment manager upgrade.
将部署管理器升级到Version7以后，单元中的所有节点都可以保持不变，仍处于升级部署管理器之前它们所支持的任何版本级别。
For the different user registry configuration, John can submit a job against the deployment manager cell, specifying his user name and password for the deployment manager cell.
对于不同用户注册中心配置，John可以向部署管理器单元提交作业，并指定他在部署管理器单元上的用户名和密码。
In Version 6.0, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.0中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
In Version 6.1, when you federate an application server node into a deployment manager cell, the deployment manager instantiates the node agent server process on the application server node.
在Version 6.1中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
Again, the job manager isn't a replacement for a Network deployment cell or the deployment manager.
同样，作业管理器不是对Net workDeployment单元或部署管理器的取代。
Under Environment Selection, select Cell (deployment manager and a federated application server), then click Next.
在EnvironmentSelection之下，选择Cell(部署管理器和一个联合应用程序服务器)，然后单击Next。
This should not be done in a production cell, as it causes ALL notifications from ALL servers to be sent to the deployment manager.
但不应该预订生产单元中的通知，因为这会导致来自“所有”服务器的“所有”通知都被发送到部署管理器。
This infrastructure consists of node agents and a deployment manager node as the central point of administration of the entire cell that these clusters belong to.
这个基础设施包含一些节点代理和一个部署管理器节点，后者充当这些集群所属的整个单元的管理中心点。
The final step in the project will start all the processes in the cell including the Deployment manager, node agents, and application server cluster.
项目中的最后一步将启动单元中的所有进程，包括部署管理器、节点代理和应用程序服务器集群。
The loss of a deployment manager is a great blow to a production cell, and so it is critical that this server remain running and functional to ensure a highly available topology.
部署管理器丢失对生产计算单元是一个巨大的打击，所以此服务器务必保持运行并发挥功能，从而确保拓扑具有较高的可用性。
The deployment manager is both required for every cell, and limited to exactly one per cell.
每一个单元都需要部署管理器，而且每个单元只限于一个部署管理器。
The entire cell is rolled back when the deployment manager and all federated nodes that had been migrated are rolled back.
如果回滚了迁移后的部署管理器和所有联合节点，就会实现整个计算单元的回滚。
Once a cell has been setup in this way, the deployment manager and all node agents must be restarted to re-read the configuration.
按此方式设置了计算单元后，必须重新启动部署管理器和所有节点代理才能重新读取配置。
Whenever a V5 cell is migrated, the deployment manager profile must be the first profile migrated.
无论何时迁移V 5单元，部署管理器配置文件都必须是迁移的第一个配置文件。
The V6 migrated deployment manager profile can manage all V5 nodes in the cell.
迁移到V6的部署管理器配置文件可以管理单元中的所有V 5节点。
As a result, if you lose the data center where the deployment manager is running, you lose the ability to manage the cell until a backup deployment manager is brought up in the surviving data center.
因此，如果您失去运行部署管理器的数据中心，也就失去了管理计算单元的能力，直到仍然存在的数据中心启动备份部署管理器为止。
The deployment manager administrative console provides views of configuration information and status for the infrastructure resources of the cell.
部署管理器管理控制台提供配置信息视图以及单元的基础结构资源的状态视图。
However, once a federated node has been migrated to V6, the V5 version of the node may NEVER reconnect to the V6 deployment manager of the new cell.
然而，联合节点迁移到V6以后，该节点的V5版本可能不会重新连接到新单元中的V6部署管理器。
应用推荐