Technical data

Starting and Stopping Node Manager
Configuring and Managing WebLogic Server 4-7
! “Node Manager Properties” on page 4-10
Starting Node Manager as a Service
The WebLogic Server installation process automatically installs Node Manager as a
service, so that it starts up automatically when the system boots. This behavior is
appropriate for a production environment, as it ensures that Node Manager is available
to restart Managed Servers after a machine reboot.
Starting Node Manager with Commands or Scripts
Although running Node Manager as an operating system service is recommended, you
can also start Node Manager manually at the command prompt or with a script. The
environment variables Node Manager requires are described in “Node Manager
Environment Variables” on page 4-9. Command line options are described in “Node
Manager Properties” on page 4-10.
Sample start scripts for Node Manager are installed in the
WL_HOME\server\bin
directory, where WL_HOME is the top-level installation directory for WebLogic Server.
Use
startNodeManager.cmd on Windows systems and startNodeManager.sh on
UNIX systems.
The scripts set the required environment variables and start Node Manager in
WL_HOME/common/nodemanager. Node Manager uses this directory as a working
directory for output and log files. To specify a different working directory, edit the start
script with a text editor and set the value of the
NODEMGR_HOME variable to the desired
directory.
Edit the sample start script to make sure that the command qualifiers set the correct
listen address and port number for your Node Manager process.
Command Syntax for Starting Node Manager
In WebLogic Server 8.1, Node Manager properties can be provided on the command
line, or defined in the
nodemanager.properties file, which is installed in the
directory where you start Node Manager. Values supplied on the command line
override the values in
nodemanager.properties.