Configuring and Starting Node Manager

Version: WebLogic 10.3.5
Description: This guide will show you how to configure and start node manager. After completing this guide, you will be able to start and shutdown your managed servers through the Weblogic Administration console.

The screenshots given below demonstrates how to shut down or start the servers through the Weblogic administration console. You may skip this if you are already familiar with the Weblogic console.

Node Manager Configuration
1. The "nodemanager.properties" file must be created. This file can be created for you the first time you run node manager.

2. Execute the "startNodeManager.sh" script. This can be found in the "<WL_HOME>/server/bin" directory.

cd /home/oracle/Oracle/Middleware/wlserver_10.3/server/bin
./startNodeManager.sh

3.  Shutdown node manager.

#Find the process id of node manager
ps -ef | grep nodemanager
#Kill the pid (Use the first number)
kill 7453

4. The "nodemanager.properties"  file should have been created for you. This file is located in "<wl_home>/common/nodemanager". Modify "startScriptEnabled" parameter to true.

cd /home/oracle/Oracle/Middleware/wlserver_10.3/common/nodemanager
vi nodemanager.properties

#In the nodemanager.properties file, set the startScriptEnabled to true
StartScriptEnabled=true

In order to stop the Node Manager through WLST, you must set the QuitEnabled property to true in the nodemanager.properties file.

#Enable stopNodeManager()
QuitEnabled=true 

Restart node manager for changes to take in effect.

5. A Node manager is associated with a machine. In order to start the servers with node manager, the servers must have a specified machine. The screenshots given below will show you how to create a machine and setup the servers to run under the node manager that is associated with that machine. I have set all servers to be able to be ran by one node manager. Adjust to your needs. The Weblogic server will need to be restarted after making changes.

Troubleshooting

The errors displayed in the picture happens whenever you try to start a managed sever in the WebLogic administration console without the node manager running.

Even when node manager is running, the managed servers may not start if node manager is not configured properly.  If node manager is not configured properly,  a managed server may appear to running in the Weblogic administration console. You can look at the enterprise manager console to see the exact statuses of your servers. To fix this problem, change the "startScriptEnabled" parameter to true in the "nodemanager.properties" file.