# startup node manager
cd $WL_HOME/server/bin
nohup ./startNodeManager.sh &
# shutdown node manager
cd $WL_HOME/server/bin
. ./stopNodeManager.sh
# the following command will give you just the PID a running Weblogic NodeManager- leave off the “awk” part of the pipes and you’ll see more info about the process than just the PID
ps aux | grep weblogic.NodeManager | grep -v grep | awk ‘{print $2} ‘
5192
# or I found the jcmd command that shows a running JVM(s) including node manager
[oracle@mid1 ~]$ echo $JAVA_HOME
/usr/java/jdk1.8.0_131
[oracle@mid1 ~]$ java -version
java version “1.8.0_131”
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
[oracle@mid1 ~]$ jcmd
5094 org.apache.derby.drda.NetworkServerControl start
5192 weblogic.NodeManager -v
5096 weblogic.Server
15706 sun.tools.jcmd.JCmd
5549 weblogic.Server
Note: jcmd is a java diagnostic tool that has many features for diagnostics individual JVMs – see Oracle documentation for more information
For example: to show node manager up time for PID 5192
jcmd 5192 VM.uptime
5192:
260026.099 s
#260026 s (seconds) is approximately 72 hours