The node agent is represented in the cell by managed beans, and the AdminControl object of wsadmin operates on those running MBeans. A node agent MBean exposes operations including stopNode and restart, so the administrator first obtains the MBean identifier, for instance with AdminControl.queryNames for type NodeAgent and the node name, and then calls AdminControl.invoke(nodeAgentMBean, 'restart'). The node agent then restarts itself, and the deployment manager's view of the node returns to normal when the process is up. Option B describes that call.
AdminConfig, option A, works with configuration documents in the repository, and it has no method that sets server status. AdminTask offers administrative commands such as startServer and stopServer, but the command shown in option C, restartServer with the serverName parameter, is not a node agent restart operation; the node agent has its own stop and start procedures. AdminApp, option D, deals with installation and updates of applications, so updateInteractive has no relationship to server restarts, and 'restartApp' is not a valid argument.
An important practical point is that a node agent that is stopped cannot be restarted through the deployment manager, because the process that carries the MBean is not running. In that situation the node's startNode command has to be run locally on the node.
[Reference: wsadmin scripting objects: AdminControl, AdminConfig, AdminTask, AdminApp; Node agent management; Restarting node agents.]
Submit