Node Manageris Weblogic Server utility to start, stop and restart Admin and Managed Server Instances from remote location.
1. Node Manager Process is associated with a Machine and NOT with specific
Weblogic Domain (i.e. Use one node manager for multiple domains on
same machine)
2. There are two versions of Node Manager - Java-based and Script-based
Java-based node manager - 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
Script-based node manager - is available for
Linux and Unix systems only and is based on shell script.
3. There are multiple ways to access Node Manager
- From Administration Console : Environments -> Machines -> Configuration -> Node Manager
- JMX utilities (Java Management eXtension)
- From Administration Console : Environments -> Machines -> Configuration -> Node Manager
- JMX utilities (Java Management eXtension)
- WLST commands (WebLogic Scripting Tool)
4.Default port on which node manager listen for requests is
localhost:5556, 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.
5. Any domain created before creation of
Node Manager Service will not be accessible via node
Manager(even after restarting node manager), solution is to run the WLST
command “nmEnroll” to enroll that domain with the Node Manager.
6. 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‘ by the domain.
How to Configure Node Manager ?
1.Configure each computer (on which you wish to use Node Manager)
as a Machine in WebLogic Server
Environments -> Machines -> New (Add Machine)
Environments -> Machines -> New (Add Machine)
Environments -> Machines -> Machine Name (created above)
-> Configuration -> Node Manager
2. Assign each server instance to Machine.
Environments -> Machines -> Machine Name (created above) -> Configuration -> Servers -> Add (Add Server running on this node which you would like to monitor using Node Manager)
Environments -> Machines -> Machine Name (created above) -> Configuration -> Servers -> Add (Add Server running on this node which you would like to monitor using Node Manager)
3. Enroll domain (created before installation of Node
Manager) to Node Manager
Unix /Linux
cd $BEA_HOME/user_projects/domains//bin/
setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,'weblogic’, ‘t3://mymachine.mydomain:7001′)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/’, ‘$BEA_HOME/wlserver_/common/nodemanager’)
cd $BEA_HOME/user_projects/domains//bin/
setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,'weblogic’, ‘t3://mymachine.mydomain:7001′)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/’, ‘$BEA_HOME/wlserver_/common/nodemanager’)
where “mymachine.mydomain:7001″ is the reference to the Admin
Server of the domain to which the server and machine definition belongs
How to start Node Manager ?
$WL_HOME\server\bin\startNodeManager.sh (startNodeManager.cmd
on Windows)
Important Configuration files
– $WL_HOME/common/nodemanager/ nodemanager.properties,
nodemanager.domains, nm_data.properties
–$DOMAIN_HOME/config/nodemanager/nm_password.properties
–$DOMAIN_HOME/servers//data/nodemanager/ boot.properties,
startup.properties, server_name.addr, server_name.lck, server_name.pid,
server_name.state
Node Manager Log Files
$WL_HOME/common/nodemanager/nodemanager.log
$WL_HOME/common/nodemanager/nodemanager.log
QUANTUM BINARY SIGNALS
ReplyDeleteGet professional trading signals delivered to your cell phone daily.
Start following our trades NOW and profit up to 270% per day.