If you stop a node agent process, you can not start the process
using the wsadmin tool or the administrative console. Use this topic to restart
a node agent that has been stopped.
Before you begin
A node agent must exist in your configuration and must be in the stopped
state.
About this task
Use the following steps to restart a node agent process:
Procedure
- Launch the wsadmin
scripting tool.
- Determine the name of the node agent to restart.
- Using Jacl:
set na [$AdminControl queryNames type=NodeAgent,node=mynode,*]
- Using Jython:
na = AdminControl.queryNames('type=NodeAgent,node=mynode,*')
- Determine the NodeAgent MBean operation.
Use the
following help commands to return information about the restart option:
- Restart the node agent process.
As the help output
from the operations command displays, you must specify two boolean parameters
in the command invocation. First, specify
true for the syncFirst
parameter to synchronize your configuration before the command restarts the
node. Next, specify
true for the restartServers parameter to restart
all running servers while the command restarts the node. The following command
example synchronizes and restarts the application servers that are running
on the node when the node agent restarts:
- Using Jacl:
$AdminControl invoke $na restart "true true"
- Using Jython:
AdminControl.invoke(na,'restart','true true')
Results
The node agent process has been restarted.
What to do next
Verify that your node agent and servers successfully started.