Cell configuration backup using a node agent.
使用节点代理的Cell配置备份。
The node agent server generates unique port assignments by default.
缺省情况下，节点代理服务器会生成唯一端口分配。
The resource was_nodeagent-rs represents the WebSphere node agent.
资源was_nodeagent - rs代表WebSphere节点代理。
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.
记住，这个步骤要成功，节点代理进程必须启动并运行。
Replacement of the Adminserver process with a Deployment Manager (DMgr) and a Node Agent (NA)
部署管理器（Deployment Manager，DMgr）和节点代理（Node Agent，NA）取代了Adminserver 进程
When the node agent is unavailable, administrators are unable to invoke any operations for that node.
当节点代理不可用时，管理员无法调用该节点的任何操作。
The article Running an Application Server and node agent from a non-root user may also be useful.
文章RunninganApplicationServerand node agentfroma non - rootuser可能对您也有帮助。
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.
首先创建启动和停止节点代理和应用服务器进程的两个脚本。
Watch the logs of Node Agent 1 to make sure they come up fine and that there are no errors in the logs.
观察Node Agent1的日志文件，确保它们是良好的，并且日志中没有出现错误。
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.
注意最好选择应用服务器而不是系统服务器，例如节点代理或是域管理器。
If you receive this error message when starting the WebSphere Application Server deployment manager or node agent.
如果您在启动WebSphereApplicationServer部署管理器或节点代理时接收到以下错误消息。
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。
Using the Local OS user registry requires the node agent, the deployment manager, and the application server process to run as root.
要使用LocalOS用户注册表，需要将节点代理、部署管理器和应用程序服务器进程作为根运行。
Actions invoked through these views are communicated by the deployment manager to the node agent of the corresponding application server node.
部署管理器将通过这些视图调用的操作传达至相应应用程序服务器节点的节点代理。
In a Network Deployment installation however, all notifications from the application server are also sent to the node agent on the same machine.
而在Net workDeployment安装中，还将来自应用程序服务器的所有通知发送到同一台机器上的节点代理。
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 脚本来启动部署管理器和节点代理。
Alternatively, you can configure a command-line argument for each node agent that will force a DNS cache refresh on a periodic basis. The property is.
此外，您可以为每个节点代理配置一个命令行参数，这将强制定期刷新dns缓存。
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.
考虑到节点代理在应用服务器启动自检中扮演的角色，您不希望节点代理长时间不可用。
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位服务器。
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中画出。
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 an application server (child) starts, the NodeAgent MBean (parent, running in the node agent process) usually emits a websphere.process.starting notification.
当应用程序服务器(子服务器)启动时，NoteAgentMBean(运行在节点代理进程中的父服务器)通常会发出一个websphere . process . starting通知。
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地址。
应用推荐