Technical data

Starting the Node Manager from the Command Line
Administration Guide 3-13
In the above example it is assumed that the JAVA_HOME variable points to the root
directory of the JDK installation.
You also need to set the path to the native UNIX libraries that be used by the Node
Manager. The following is an example on Solaris:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/lib/solaris:$WL_HOME/lib/solaris/oci8
16_8
The following is an example on HP UX:
SHLIB_PATH=$SHLIB_PATH:$WL_HOME/lib/hpux11:$WL_HOME/lib/hpux11/oci816_8
Setting the Classpath
The classpath can be set either as an option on the java command line or as an
environment variable. The following is an example (on Windows NT) of setting the
classpath as an environment variable:
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
Starting the Node Manager
If you don’t use a start script to start the Node Manager, be sure to start the Node
Manager in the root installation directory where you installed the WebLogic Server
software. This is the directory that contains the
\config subdirectory.
The command to start the Node Manager is:
java weblogic.nodemanager.NodeManager
Command-Line Arguments
The listen address of the Node Manager needs to be set when it is started. You can
specify the address on which the Node Manager will listen for requests from the
Administration Server with the following parameter:
-Dweblogic.nodemanager.listenAddress=host
where host is the DNS name or IP address of the machine where the Node Manager
is started.