Starting and stopping node agents
Node agents are administrative agents that represent a node to your system and manage the servers on that node. The node agent is a server process that must be started before you can communicate with the deployment manager or start servers on the node. If you need to stop or restart the node agent (for example, for system maintenance like changing the system clock), use the administrative console.
Before you begin
Before you can start and stop a node agent, you must federate the node into a cell.
If you used the BPMConfig command to create your profiles and deployment environment, and you did not specify the -federateLater option, the node has been federated automatically.
If you used the BPMConfig command to create your profiles and deployment environment, and you specified the -federateLater option, you need to first run the WebSphere addNode command before you can start and stop any node agents.
Before you can stop a node agent, you must stop all the servers managed by that node agent.
About this task
Use the following steps to start, stop, or restart a node agent.
Action | Perform these steps |
---|---|
Start a node agent |
|
Stop a node agent |
|
Restart a node agent |
|
Example
- To start the node agent in the default profile, type startNode
- To list the options, type startNode -help
- To start the node agent in the Custom03 profile, type startNode -profileName Custom03
- To start the node agent in the Custom03 profile and write trace information to the log file called install_root/profiles/Custom03/logs/startServer.log, type startNode -logfile -profileName Custom03