Cell configuration backup using a node agent.
使用节点代理的Cell配置备份。
The node agent server generates unique port assignments by default.
缺省情况下，节点代理服务器会生成唯一端口分配。
Starting the application server (s) and the node agent on the standby machine.
在备份节点上启动应用服务器和节点代理。
In the same way, all notifications in the node agent are sent to the deployment manager.
同样，也将节点代理中的所有通知发送到部署管理器。
A node agent is a fully functional member of the cell and has full administrative authority.
节点代理是计算单元的一个全功能成员，它有完整的管理权限。
Keep in mind that the node agent processes must be up and running for this step to be successful.
记住，这个步骤要成功，节点代理进程必须启动并运行。
When the node agent is unavailable, administrators are unable to invoke any operations for that node.
当节点代理不可用时，管理员无法调用该节点的任何操作。
First, a node agent is a fully functional member of the cell and thus has full administrative authority.
首先，节点代理是计算单元的一个全功能成员，因此它有完全的管理权限。
First, create a couple of scripts to start and stop the node agent and the application server processes.
首先创建启动和停止节点代理和应用服务器进程的两个脚本。
Now configure heartbeat to manage the WebSphere application server node agent and application server processes.
现在，配置heartbeat来管理WebSphereApplicationServer节点代理和应用服务器进程。
Be careful to select an application server rather than a system server, such as the node agent or domain manager.
注意最好选择应用服务器而不是系统服务器，例如节点代理或是域管理器。
Start the node agent server and verify that the system output and error logs do not contain any unexpected exceptions.
请启动节点代理服务器，并验证系统输出和错误日志中是否包含任何异常。
By default, each new node agent created is given the next free number in the sequence, for example, BBON002, BBON003 to BBONXXX.
缺省情况下，每个新创建的节点代理都将按顺序赋予下一个未使用的数字，例如从BBON002、BBON003到BBONXXX。
Actions invoked through these views are communicated by the deployment manager to the node agent of the corresponding application server node.
部署管理器将通过这些视图调用的操作传达至相应应用程序服务器节点的节点代理。
On Linux and UNIX, you're probably familiar with using the startManager.sh and startNode.sh scripts to start the deployment manager and node agent.
在Linux和UNIX 上，您很可能知道如何使用 startManager.sh 和startNode.sh 脚本来启动部署管理器和节点代理。
Given the role the node agent plays in bootstrapping application servers, you wouldn't want a node agent to be unavailable for an extended period of time.
考虑到节点代理在应用服务器启动自检中扮演的角色，您不希望节点代理长时间不可用。
A basic script to start a node agent (wasnode) is shown in Listing 2, and the script to start application servers (wasserver) on a node is shown in Listing 3.
清单2中是启动节点代理的一个基本的脚本(wasnode)，清单3是启动某个节点上应用服务器的脚本(wasserver)。
When a node is federated with a deployment manager, the base node's configuration is first backed up, then replaced with a new configuration containing the node agent.
当某个节点与部署管理器联合时，首先备份基本节点的配置，然后替换为包含节点代理的新配置。
As a result, once a connection has been made, all running node agent JVMs have a cache of the IP address for the original server that the deployment manager was running on.
因此，一旦建立起一个连接后，所有运行的节点代理JVM都缓存了运行部署管理器的原始服务器的IP地址。
In this context, "WebSphere application server" includes all WebSphere application server components, including deployment manager, node agent, application server, and so on.
在这个上下文中，WebSphereApplicationServer包括所有的WebSphere Application Server组件，包括部署管理器、节点代理、应用服务器，等等。
The first option requires you to stop and restart all the node agents in order to clear the "stale" cache in the node agent JVM that points to the old IP address for the server.
第一个选项要求您停止并重启所有节点代理，以清除节点代理JVM中的“陈旧”缓存，这些缓存指向服务器的旧IP地址。
Using a managed node requires that you place a node agent on the Web server machine (which is typically in the DMZ) and that this agent be part of the WebSphere Application server cell.
要使用托管节点，您需要在Web服务器(通常位于DMZ中)上放置一个节点代理，使该代理作为WebSphereApplication Server计算单元的一部分。
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中，当您将某个应用程序服务器节点联合到部署管理器计算单元中时，部署管理器会在该应用程序服务器节点上实例化节点代理服务器进程。
Replacement of the Adminserver process with a Deployment Manager (DMgr) and a Node Agent (NA)
部署管理器（Deployment Manager，DMgr）和节点代理（Node Agent，NA）取代了Adminserver 进程
Though not depicted in Figure 6, this last port is used for an EJB client initial request to the Location Service Daemon (LSD) running in the Node Agent.
最后这个端口用于EJB客户机对运行在节点代理(Node Agent)中的LocationServiceDaemon (LSD)的初始请求，不过没有在图6中画出。
Though not depicted in Figure 6, this last port is used for an EJB client initial request to the Location Service Daemon (LSD) running in the Node Agent.
最后这个端口用于EJB客户机对运行在节点代理(Node Agent)中的LocationServiceDaemon (LSD)的初始请求，不过没有在图6中画出。
应用推荐