NodeManager unreachable

If you meet one of the following problems
- NodeManager unreachable or you are not able to start your managed Server
- The domain was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the domain in the nodemanager

You will need to follow these steps;

1- Start Admin Server with start script startweblogic.sh. you can find this script under /BEA_HOME/Domains/YOUR_DOMAIN NAME/bin
2- Start WLS (Wblogic Scripting Tools)under /BEA_HOME/wlserver_10.3/common/bin/(wlst.sh)
3- Start Node Manager (you can start NodeManager with or without connecting to Admin Server
wls:/offline> startNodeManager()
4- Connect to Admin Server
wls:/offline> connect ('weblogic','XXXXXX','t3://YOUR HOST_NAME:7002')

Connecting to t3://XXXXXXXXX:7002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'base_domain'.
5- Enroll NodeManager
wls:/base_domain/serverConfig> nmEnroll('BEA_HOMEuser_projects/domains/base_domain',BEA_HOMEcommon/nodemanager')

Successfully enrolled this machine with the domain directory at /BEA_HOME/domains/base_domain.
wls:/base_domain/serverConfig>


Updated on 18-2-2012

After finishing with Enroll you'll need to  execute a couple of things.
See  http://docs.oracle.com/cd/E12839_01/web.1111/e13740/nodemgr_config.htm
You can start Managed server through the following ways;

- You can start a Managed Server using Node Manager through the Administration Console.

- Node Manager monitors the Managed Servers that it has started.
- Automatic restart of Managed Servers is enabled. Node Manager restarts server instances that it killed or were killed by another method.

To enable ManagedServer to be started through one of the above ways. You'll need to execute all of following steps

Now after starting AdminServer, you'll need to go to AdminServer Console (http://localhost:7001/console
1- Change this parameters to ture (default is false) StartScriptEnabled=true, StopScriptEnabled=true  in nodemanager.properties,

 for each server (incl. AdminServer) in the environment, go to the server start tab and put in the appropriate values.

- Java Home (D:\weblogic\Oracle\wls11g\jrockit_160_14_R27.6.5-32)
- Java Vendor Oracle
- BEA Home D:\weblogic\Oracle\wls11g
- Root Directory D:\weblogic\Oracle\wls11g\user_projects\domains\my_domain
- Classpath  is empty (reason this pramaeter is included in Startscriptenbaled
- Arguments -Xnohup ( Arguments If you’re using Sun JDK instead of JRockit, then use –Xrs instead of –Xnohup )
- Security Policy File D:\weblogic\Oracle\wls11g\wlserver_10.3\server\lib\weblogic.policy
-User Name ex. weblogic ( The user name to use when booting this server. The Administration Console inserts the user name that you supplied when you logged in to the console)
- Password  *************
- Confirm Password ***********


- Save
- Now do the same thing for each managed server.
- Activate the changes if required

Setting Node Manager Domain Username and Password


- Set the Node Manager username/password for the domain in the console
- Click in the console navigator
- Select Security tab
- Expand to the "Advanced" options about half-way down the page
- Choose a Node Manager username/password and put it in the username/password/confirm boxes your  credentials, these could be unique from your user used to start the AdminServer, but I chose to keep the same weblogic/*******. If you change this user name and password, then you’ll need to specify both when using the command nmConnect.
 The node manager  username & password are svaed under this direcotry
nm_password.properties: This file stores the Node Manager username and password.

This file is located in DOMAIN_HOME/config/nodemanager.

Test the NodeManager (Have NodeManager Start and Stop the Servers)

- Stop Admin Server or kill that process
- Now we will connect with Node Manager to start Admin Server and also Managerd Servers
wls:/base_domain/serverConfig> nmConnect('weblogic','XXXX password','You Host_ANME','5556','base_domain','/BEA_HOME/user_projects/domains/base_domain'
Connecting to Node Manager ...
Successfully Connected to Node Manager.

- Start Admin Server

wls:/nm/base_domain> nmStart ('AdminServer')

Note: during the start of AdminServer or even the ManagerServer, may be you'll need manually to create boot.properties file
You will need to create boot.properties file under /BEA_HOME/user_projects/domains/base_domain/servers/AdminServer/data/nodemanager. Just put the follwoing lines in this file. Just put these two lines
password= (password for adminserver)
username= weblogic
save file & start AdminServer again
- start Managed Server
wls:/nm/base_domain> start ('blog1')
Successfully started server blog1 ...
wls:/nm/base_domain> start ('blog2')
- Check the status of your servers
wls:/nm/base_domain> nmServerStatus ('AdminServer')
RUNNING
wls:/nm/base_domain> nmServerStatus ('blog1')
RUNNING
wls:/nm/base_domain> nmServerStatus ('blog2')
RUNNING

Another problem, Starting Managed Server without NodeManager

You can do that by adding boot.properites file to the security directory under your server_name\security
WL_\user_projects\domains\base_domain\servers\blog2\security.

Cheers,