System 5: Deployment Manager node.
系统5：部署管理器节点。
It completes the part serving as the Deployment Manager node in the process server configuration.
它完成在流程服务器配置中作为部署管理器节点的部件。
Ensure that the name of the cell and the name of the deployment manager node match your existing cell.
确保单元的名称和部署管理器节点的名称都与现有单元匹配。
The default scope displayed in the console is that of the deployment manager node. the key fields here are.
控制台中显示的缺省范围为部署管理器节点的范围。
If you look at the file system on the deployment manager, you will see all four nodes defined, as well as the deployment manager node.
如果您看一下部署管理器上的文件系统，就会看到定义的所有四个节点以及部署管理器节点。
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部署管理器节点。
For any reason, if a disaster happens, such as deployment manager node failures or database crashes, during the "Save" operation, do the following.
如果在执行保存操作期间发生灾难事故，比如部署管理器节点故障或数据库崩溃，那么执行以下操作。
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.
这个基础设施包含一些节点代理和一个部署管理器节点，后者充当这些集群所属的整个单元的管理中心点。
Similarly, the Process Manager and the Workflow Manager have been merged into a single Process Manager node because the Process Manager also has the workflow capabilities.
同样地，流程管理器和工作流管理器已经并入了单独的流程管理节点，因为流程管理也有管理工作流的能力。
Now we need to copy the application server WASServerKeyFile and WASServerTrustFile to the deployment manager node, and to any other application server nodes that may be in your cell.
现在我们需要将应用服务器WASServerKeyFile和WASServerTrustFile复制到部署管理器节点以及单元中的任何其他应用服务器节点上。
By replicating the entire configuration tree from the actual deployment manager node to another application server node, the deployment manager can be quickly restarted on the backup node.
通过将整个配置树从实际的部署管理器节点复制到另一个应用服务器节点，部署管理器可以在备份节点上快速重启。
If the job manager and the target node or deployment manager have the same user registry, then job submission does not require a user name and password.
如果作业管理器和目标节点或部署管理器具有相同的用户注册中心，则作业提交不需要用户名和密码。
After upgrading the configuration on the deployment manager, the local repository of the node is synchronized with the master copy from the deployment manager.
在将部署管理器上的配置升级之后，本地的节点存储库就会与部署管理器上的原版拷贝同步。
From right to left respectively, the Extendable nodes parts become the process server Deployment Manager, Custom node with Proxy server, and Custom node with process server configuration.
从右到左，可扩展节点部件将分别变成流程服务器部署管理器、包含代理服务器的定制节点和包含流程服务器配置的定制节点。
Actions invoked through these views are communicated by the deployment manager to the node agent of the corresponding application server node.
部署管理器将通过这些视图调用的操作传达至相应应用程序服务器节点的节点代理。
The deployment manager USES this node information to determine which administrative functions are actually valid for a given node.
部署管理器利用节点信息来确定对于特定节点，那些管理功能是真正有效的。
When this command argument is used, the node is added using the configuration from the Deployment Manager for that node.
使用这个命令参数时，使用来自节点的DeploymentManager的配置来添加节点。
In addition to installing the products, the image includes pre-configured WebSphere Application Server parts for the deployment manager, custom node, standalone node, job manager, and so on.
除了安装产品，映像还包括预配置的WebSphereApplicationServer部分，它们针对部署管理器、自定义节点、单机节点、作业管理器等。
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中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
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中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
Mixed node environment (such as V7 deployment manager managing V6.1 custom node).
混合节点环境(比如管理着V6.1自定义节点的V7部署管理器)。
The database manager on each node manages part of the database.
每个节点上的数据库管理器管理数据库的一部分。
This queue manager should be located on another node.
此队列管理器应位于另一个节点上。
This includes the deployment manager, node agents, and application servers.
这包括部署管理器、节点代理和应用服务器。
You can upgrade your deployment manager and node agent to 64-bit, and define a new server as 64-bit while maintaining your other servers as 31-bit servers.
您可以将部署管理器和节点代理升级到64位，并将新服务器定义为64位，同时将其他服务器保留为31位服务器。
You do, however, need to be authorized for the target node or deployment manager.
但是，您需要获得目标节点或部署管理器的授权。
The final step in the project will start all the processes in the cell including the Deployment manager, node agents, and application server cluster.
项目中的最后一步将启动单元中的所有进程，包括部署管理器、节点代理和应用程序服务器集群。
Stop the queue manager on the backup node.
停止备份节点上的队列管理器。
You will need to restart the deployment manager, node agents, and your application servers for these changes to take affect.
您将需要重新启动部署管理器、节点代理和您的应用服务器，以便使更改生效。
To federate the node immediately, the deployment manager process has to be up and running.
要立即联合节点，部署管理器进程必须启动并且正在运行。
应用推荐