The simplest way to shut down the Node Manager is to just close the command shell in which it runs. You can also invoke the WLST stopNodeManager command in the online or offline mode. The command stops a running Node Manager process. This will not work with the scripted version of Node Manager, though.

cd C:\MyOra\Middleware\wlserver_10.3\common\bin
wlst.cmd
wls:/offline> nmConnect('weblogic', 'welcome1', 'localhost', '5556', 'wl_server',
'C:\MyOra\Middleware\wlserver_10.3\samples\domains\wl_server','ssl')
wls:/nm/wl_server> stopNodeManager()

If you try to shut down the Node Manager with the stopNodeManager command when you haven't started the Node Manager with the startNodeManager command, you'll get the following error:

wls:/nm/wl_server> stopNodeManager()
Traceback (innermost last):
...
weblogic.management.scripting.ScriptException: weblogic.management.scripting.ScriptException:
Error occured while performing startNodeManager : Problem stopping
the Node Manager. : Disabled command: QUIT
Use dumpStack() to view the full stacktrace

However, you can successfully stop the Node Manager process, even if you haven't started the Node Manager with the startNodeManager command, provided you've specified the property QuitEnabled=true when starting the Node Manager. You can specify the QuitEnabled property in the nodemanager.properties file. Once you do this, you can start the Node Manager as a Windows service and stop the service remotely via WLST.

0 Comments