{"id":1182,"date":"2009-06-10T12:13:34","date_gmt":"2009-06-10T16:13:34","guid":{"rendered":"http:\/\/onlineappsdba.com\/index.php\/2009\/06\/10\/node-manager-in-oracle-weblogic-server\/"},"modified":"2015-12-03T09:34:22","modified_gmt":"2015-12-03T13:34:22","slug":"node-manager-in-oracle-weblogic-server","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2009\/06\/10\/node-manager-in-oracle-weblogic-server\/","title":{"rendered":"Node Manager in Oracle WebLogic Server"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Node Manager<\/strong>is Weblogic Server utility to start<\/strong>, stop<\/strong> and restart<\/strong>Administration and Managed Server Instances from remote location (There are other ways as well to start\/stop Weblogic check here<\/a> – Node Manager is optional component).<\/p>\n

1.<\/strong> Node Manager Process is associated with a Machine<\/strong> and NOT<\/strong> with specific Weblogic Domain<\/strong> (i.e. Use one node manager for multiple domains on same machine)<\/p>\n

2.<\/strong> There are two versions of Node Manager\u00a0– Java-based<\/strong> and Script-based<\/strong><\/p>\n

Java-based node manager<\/strong> – runs with in JVM (Java Virtual Machine) Process and more secure than script-based node manager. Configuration for java-based node manager are stored in nodemanager.properties<\/strong><\/p>\n

Script-based node manager<\/strong> – is available for Linux and Unix systems only and is based on shell script.<\/p>\n

3.<\/strong> There are multiple ways to access Node Manager
\n– From Administration Console<\/strong> : Environments -> Machines -> Configuration -> Node Manager
\n– JMX utilities<\/strong> (J<\/strong>ava M<\/strong>anagement eX<\/strong>tension) more here<\/a>
\n– WLST commands<\/strong> (W<\/strong>ebL<\/strong>ogic S<\/strong>cripting T<\/strong>ool)<\/p>\n

4.<\/strong>Default port on which node manager listen for requests is localhost:5556<\/strong>, When you configure Node Manager to accept commands from remote systems, you must uninstall the default Node Manager service, then reinstall it to listen on a non-localhost (IP’s other than 127.0.0.1) listen address.<\/p>\n

5.<\/strong> Any domain created before<\/strong> creation of Node Manager Service will not<\/strong> be accessible via node Manager(even after restarting node manager), solution is to run the WLST command “nmEnroll<\/strong>” to enroll that domain with the Node Manager.<\/p>\n

6.<\/strong> Any domains created after the Node Manager service has been installed should not have to be enrolled against the Node Manager. The Node Manager should automatically be ‘reachable<\/strong>‘ by the domain.<\/p>\n

.
\nHow to Configure Node Manager<\/u> ?
\n<\/strong>
\n1.<\/strong>Configure each computer (on which you wish to use Node Manager) as a Machine in WebLogic Server
\nEnvironments -> Machines -> New (Add Machine) Use Link here<\/a>
\nEnvironments -> Machines -> Machine Name (created above) -> Configuration -> Node Manager<\/p>\n

2.<\/strong> Assign each server instance (Admin or Managed that you wish to control with Node Manager) to Machine.
\nEnvironments -> Machines -> Machine Name (created above) -> Configuration -> Servers -> Add (Add Server running on this node which you would like to monitor using Node Manager) for more info\u00a0Click here<\/a><\/p>\n

3.<\/strong> Enroll domain (created before installation of Node Manager) to Node Manager<\/p>\n

Windows
\n<\/strong>cd $BEA_HOME\\user_projects\\domains\\<domain_name>\\bin
\nsetDomainEnv.cmd
\njava weblogic.WLST
\nwls> connect(‘weblogic’,’weblogic’, ‘t3:\/\/mymachine.mydomain:7001’)
\nwls> nmEnroll(‘C:\\bea\\user_projects\\domains\/<domainName>’, ‘C:\\bea\\wlserver_<version>\/common\/nodemanager’)<\/p>\n

.<\/strong>
\nUnix \/Linux
\n<\/strong>cd $BEA_HOME\/user_projects\/domains\/<domain_name>\/bin\/
\n. setDomainEnv.sh
\njava weblogic.WLST
\nwls> connect(‘weblogic’,’weblogic’, ‘t3:\/\/mymachine.mydomain:7001’)
\nwls> nmEnroll(‘$BEA_HOME\/user_projects\/domains\/<domain_name>’, ‘$BEA_HOME\/wlserver_<version>\/common\/nodemanager’)<\/p>\n

where “mymachine.mydomain:7001” is the reference to the Admin Server of the domain to which the server and machine definition belongs<\/p>\n

.
\nHow to start Node Manager<\/u> ?<\/strong><\/p>\n

$WL_HOME\\server\\bin\\startNodeManager.sh<\/strong>\u00a0 (startNodeManager.cmd on Windows)<\/p>\n

How to install Node Manager as Service on Windows<\/u> ?<\/strong><\/p>\n

Use $WLS_HOME\\server\\bin\\installNodeMgrSvc.cmd<\/strong>\u00a0 (Where default WLS_HOME location is c:\\bea\\wlserver_<version>)<\/p>\n

To uninstall Node Manager Service on windows use $WLS_HOME\\server\\bin\\uninstallNodeMgrSvc.cmd<\/strong><\/p>\n

installNodeMgrSvc.cmd<\/strong>\u00a0will create Windows server with name as Oracle WebLogic NodeManager (C_bea_wlserver_<version>)
\n.
\nImportant Configuration files<\/u> <\/strong><\/p>\n

— $WL_HOME\/common\/nodemanager\/ nodemanager.properties, nodemanager.domains,\u00a0nm_data.properties<\/p>\n

–$DOMAIN_HOME\/config\/nodemanager\/nm_password.properties<\/p>\n

–$DOMAIN_HOME\/servers\/<server_name>\/data\/nodemanager\/ boot.properties, startup.properties, server_name.addr, server_name.lck, server_name.pid, server_name.state<\/p>\n

.
\nNode Manager Log Files
\n<\/u><\/strong>$WL_HOME\/common\/nodemanager\/nodemanager.log<\/strong><\/p>\n

References<\/u><\/strong><\/p>\n