WebLogic‎ > ‎Domain Creation‎ > ‎

Start n Stop Server using NodeManager

Middleware Administrator need to work on daily/weekly scheduled restart activities . The Oracle WebLogic servers bouncing to avoid the overload on the JVM Heap filling up with the application related objects. This activity can be automated with the powerful scripting tool WLST. Before using WLST your environment must have NodeManager configured. In this page we will see the NodeManager configuration related issues and their workarounds.
In the sun Solaris environment we need to change few nodemanager.properties to run the NodeManager. There are two kinds of Node Managers available
1. Java based Node manager
2. Script based Node manager
On Unix machine like Solaris HP-UX we are allowed to use only script based Node manager.


Decide first, which mode you want to run the nodemanager ? There are two options to go:
1. Plain
2. SSL
3. SSH
4. RSH.

Login to Admin Console
1. Click Lock & Edit.
2. Environment --> Machines --> Click New 
3. Name --> mymachine, Machine os --> Unix, Click OK and activate the changes.
4. Click on mymachine --> configuration --> Node Manager 
5. Type --> Plain or SSL, Listen Address --> hostname, Listen Port --> 5556.
Click OK and Click on Activate changes in the Command Center.

1. Login to the Unix Box where admin server hosted.
2. Go to the Server root Directory.
3. Change directory and got to the following location cd DM_HOME/config/nodemanager.
4. Copy the default startNodemanager.sh script to this location.
5. Modify the script with Domain home, Java home & Nodemanager Home.
6. Copy the nodemanager.domains file from $WL_HOME/common/nodemanager directory to $DM_HOME/config/nodemanager directory( where $DM_HOME = Domain home).
6. Create a script to run the nodemanager process as a background process.
7. Start Nodemanager & Check for any errors in the nodemanager's log.

Assume that I have One Domain on a machine, 
Two Servers in the Domain: 1 AdminServer & 1 ManagedServer
1. using wlst connect to the nodemanager:
nmConnect('weblogic','weblogic','localhost','5556','mydomain')
2. start admin server nmStart('AdminServer')
3. open console and go to Servers -> AdminServer -> Configuration -> Server Start
4. Lock & Edit and put the following into Arguments: -Xrs
5. Save & Activate changes
  
At this point weblogic creates boot.properties and startup.proeprties in $DM_HOME\servers\AdminServer\data\nodemanager

The sample startup.properties looks like this:

#Server startup properties
#Thu Jan 31 06:35:51 GMT 2008
Arguments=-Xrs
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
AdminURL=http\://10.234.27.54\:7001
AutoRestart=true
AutoKillIfFailed=false

6. using WLST kill the server nmKill('AdminServer')
7. try starting it again: nmStart('AdminServer')
 
Node Manager starting time issue for Solaris
 
For starting the NodeManager on Solaris using WLST got the following error:
 
/opt/inst/Oracle/Middleware/wlserver_10.3/common/nodemanager
NMProcess: weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native
library could not be loaded
NMProcess:      at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:243)
NMProcess:      at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:182)
NMProcess:      at weblogic.nodemanager.server.NMServer.init(NMServer.java:177)
NMProcess:      at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:142)
NMProcess:      at weblogic.nodemanager.server.NMServer.main(NMServer.java:357)
NMProcess:      at weblogic.NodeManager.main(NodeManager.java:31)
NMProcess: Caused by: java.lang.UnsatisfiedLinkError: no nodemanager in java.library.path
NMProcess:      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1709)
NMProcess:      at java.lang.Runtime.loadLibrary0(Runtime.java:823)
NMProcess:      at java.lang.System.loadLibrary(System.java:1030)
NMProcess:      at weblogic.nodemanager.util.UnixProcessControl.<init>(UnixProcessControl.java:24)
NMProcess:      at weblogic.nodemanager.util.Platform.getProcessControl(Platform.java:114)
NMProcess:      at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:2
 
Sol:

The workaround for this issue is we need to check for the native libraries are available in the CLASSPATH environment variable that is LD_LIBRARY need to set the CLASSPATH for native library location for Sparc  location. Where it contains shared library files with the .so extension
.

YOU TUBE videos on Configuring WebLogic NodeManager


Contributors can donate an your experiments/experience using NodeManager starting with WLST
Send Us a Mail

Start AdminServer with NodeManager using WLST
Start Managed Server with NodeManager using WLST
Shutdown Managed Servers with NodeManager using  WLST
Shutdown AdminServer with NodeManager using WLST


 
 
Comments