To configure Node Manager -
Log in to weblogic Admin Console
Click on Environments -> Machines tab on left hand side
Click on new tab on right hand side
Noe click on created machine
To check status :-
Start node manager, click on machine name, click on Monitoring -> Node Manager Status
click on node manager tab, Status should be Reachable.
How to start Node Manager ?
$WL_HOME\server\bin\startNodeManager.sh (startNodeManager.cmd on Windows)
$WL_HOME\server\bin called NM_HOME, For Example - D:\Oracle\Middleware\wlserver_10.3\server\bin
To Stop Node Manager
In Unix/Linux, kill the process -
kill -9 `ps -ef | grep -i nodemanager.javahome | grep -v grep | awk {'print $2'} | head -1`
On window machine, close the window on which Node Manager started.
Node Manager Log Files
$WL_HOME/common/nodemanager/nodemanager.log
Important configuration file for node manager
$WL_HOME/common/nodemanager/nodemanager.properties- used by java based node manager. This file is created on first time start of nodemanager (startNodeManager.sh)
$WL_HOME/common/nodemanager/nodemanager.domains - contains mappings between the names of domains managed by Node Manager and their corresponding directories.
entry like
base_domain=D:\Oracle\Middleware\user_projects\domains\base_domain
soa_domain=D:\Oracle\Middleware\user_projects\domains\soa_domain
$WL_HOME/common/nodemanager/nm_data.properties- This file stores the encryption data the Node Manager uses as asymmetric encryption key. This file is created on first time start of nodemanager (startNodeManager.sh)
$DOMAIN_HOME/config/nodemanager/nm_password.properties- This file stores the Node Manager username and password used by Admin Server to connect to Node Manager.
Few other configuration files are boot.properties, startup.properties,server_name.addr, server_name.lck, server_name.pid, server_name.state
Log in to weblogic Admin Console
Click on Environments -> Machines tab on left hand side
Click on new tab on right hand side
Enter name of machine and select Machine OS as unix if you are on unix machine otherwise default, click ok
Select type plain, enter listen address and port
Start node manager, click on machine name, click on Monitoring -> Node Manager Status
click on node manager tab, Status should be Reachable.
$WL_HOME\server\bin\startNodeManager.sh (startNodeManager.cmd on Windows)
$WL_HOME\server\bin called NM_HOME, For Example - D:\Oracle\Middleware\wlserver_10.3\server\bin
To Stop Node Manager
In Unix/Linux, kill the process -
kill -9 `ps -ef | grep -i nodemanager.javahome | grep -v grep | awk {'print $2'} | head -1`
On window machine, close the window on which Node Manager started.
Node Manager Log Files
$WL_HOME/common/nodemanager/nodemanager.log
Important configuration file for node manager
$WL_HOME/common/nodemanager/nodemanager.properties- used by java based node manager. This file is created on first time start of nodemanager (startNodeManager.sh)
$WL_HOME/common/nodemanager/nodemanager.domains - contains mappings between the names of domains managed by Node Manager and their corresponding directories.
entry like
base_domain=D:\Oracle\Middleware\user_projects\domains\base_domain
soa_domain=D:\Oracle\Middleware\user_projects\domains\soa_domain
$WL_HOME/common/nodemanager/nm_data.properties- This file stores the encryption data the Node Manager uses as asymmetric encryption key. This file is created on first time start of nodemanager (startNodeManager.sh)
$DOMAIN_HOME/config/nodemanager/nm_password.properties- This file stores the Node Manager username and password used by Admin Server to connect to Node Manager.
Few other configuration files are boot.properties, startup.properties,server_name.addr, server_name.lck, server_name.pid, server_name.state
Posts
No comments:
Post a Comment