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 the Using
command line tools article.
Syntax
The command syntax is as follows:
startNode [options]
Parameters
The following options are available for
the startNode command:
- -?
- Prints a usage statement.
- -curlib <product_library>
- Specifies the current library to use for the underlying Submit Job (SBMJOB)
CL command.
- -cpyenvvar
- Tells the startNode command to set the environment variables that
are currently defined for the node agent process. The default is to not set
the currently defined environment variables.
- -help
- Prints a usage statement.
- -inllibl <library_list>
- Specifies the initial library list to use for the underlying Submit Job
(SBMJOB) CL command.
- -inlaspgrp <ASP_group>
- Specifies the initial ASP group for the underlying Submit Job (SBMJOB)
CL command.
- -jobd <product_library/job_description>
- Specifies the job description for the underlying Submit Job (SBMJOB) CL
command.
- -jobq <product_library/job_queue>
- Specifies the job queue for the underlying Submit Job (SBMJOB) CL command.
- -logfile <fileName>
- Specifies the location of the log file to which trace information is written.
By default, the log file is named startServer.log and is created in your profile_root/logs directory.
- -nowait
- Tells the startNode command not to wait for successful initialization
of the launched node agent process.
- -outq <product_library/output_queue>
- Specifies the output queue for the underlying Submit Job (SBMJOB) CL command.
- -profileName
- Defines the profile of the Application Server process in a multi-profile
installation. The -profileName option is not required for running in a single
profile environment. The default for this option is the default profile.
- -quiet
- Suppresses the progress information that the startNode command
prints in normal mode.
- -replacelog
- Replaces the log file instead of appending to the current log.
- -sbs <product_library/subsystem_description>
- Specifies the subsystem to use for the underlying Submit Job (SBMJOB)
CL command.
- -script [<script fileName>] -background
- Generates a launch script with the startServer command instead
of launching the node agent process directly. The launch script name is an
optional argument. If you do not supply the launch script name, the default
script file name is
- start_node_agent.sh
- start_node_agent.bat
node_agent is the name of the node agent.The -background parameter
is an optional parameter that specifies that the script will run in the background
when you run it.
- -statusport <portNumber>
- An optional parameter that allows an administrator to set the port number
for node agent status callback. The tool opens this port and waits for status
callback from the node agent indicating that the node agent has started. If
the parameter is not set, an unused port is automatically allocated.
- -trace
- Generates trace information to the log file for debugging
purposes.
- Enables tracing of the native process code that starts
the node agent. The trace output is written to the was_jobname-jobuser-jobnum.log file which is located in the profile_root/logs directory.
- -timeout <seconds>
- Specifies the waiting time before node initialization times out and returns
an error.
- -usejobd
- Specifies to use the job description from the Submit Job (SBMJOB) process
for the node agent when switching to the Run-As user ID.
Note: This command
does not affect the USER field of the current job description.
Usage scenario
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 WebSphere Application Server, Network Deployment cell.)
startNode -profileName mynode (Starts the node agent for the mynode profile
which belongs to a WebSphere Application Server, Network Deployment cell.)
startNode -trace (produces trace files in the profile_root/logs directory)