The startNode command reads the configuration file for the node agent process and constructs a launch command.
Depending on the options that you specify, the startNode command
creates a new Java virtual machine (JVM) API to
run the agent process, or writes the launch command data to a file.
If you are using the Windows platform
and the you have the node agent running as a Windows service, the startNode command
will start the associated Windows service and it will be responsible
for starting the node agent.
startNode command reads the
configuration file for the node agent process for a profile that has
been added to the WebSphere® Application Server, Network Deployment cell
and starts the server.
You do not have to use a user name and password with the startNode command because this command launches a server process but does not invoke an MBean method.
For more information about where to run this command, see Using command-line tools.
startNode [options]
The following options are available for the startNode command:
The following examples demonstrate correct syntax:
startNode
startNode -script (produces the start_node.bat or .sh file)
startNode -trace (produces additional trace statements in the startnode.log file)
startNode
startNode -trace (produces additional trace statements in the startnode.log file)
startNode (Starts the node agent process for the default profile.
The default profile must belong to a product cell.)
startNode -profileName mynode (Starts the node agent for the mynode profile
which belongs to a product cell.)
startNode -trace (produces trace files in the profile_root/logs directory)