NodeManager

1 created 1 Admin and 1 managedin 169.254.17.145
2 created 1 managed in 169.254.208.93

Configuring node manager:
1) created machine for admin and ms1 with their ip and port
2) Go to C:\bea10.3\wlserver_10.3\server\bin take nminstalsvc backup and make the changes
3) created folder nodemanager in C:\Weblogic\apps\nodemanager\nmDomain\nodemanager in 17.145  edited the installservices set NODEMGR_HOST=169.254.17.145
set NODEMGR_PORT=5556 and start the nodemanger
4) you will get nodemanager.properties and nm_data.properties
5) fro CrashRecovery and startupScriptsEnabled:
    We wnat to enable nodemanager to restore from their last known state after server reboot.

6)Enroll the domain in nodemanger:
- run setDomainenv
- java weblogic.WLST
-wls:/offline> connect('weblogic','weblogic','t3://169.254.17.145:5001')
-wls:/nmDomain/serverConfig> nmEnroll(domainDir='C:/Weblogic/apps/nodemanager/nmD
 omain',nmHome='C:/Weblogic/apps/nodemanager/nmDomain/nodemanager')
 Enrolling this machine with the domain directory at C:/Weblogic/apps/nodemanager
 /nmDomain ...
 Successfully enrolled this machine with the domain directory at C:\Weblogic\apps
 \nodemanager\nmDomain.  ---- make sure all are forward slashes.
- now you will get nodemanagers.domain in nodemagers home directory.

7) Prvide the approprivate values to server start in server tab in console

-javahome: C:\bea10.3\jdk160_05
-vendor= oracle
-Bea home=C:\bea10.3\wlserver_10.3
RootDir;C:\Weblogic\apps\nodemanager\nmDomain
Arguments: Xrs for jdk and -Xnohup for jrocket

if you dint provide also no issue you can able to start or stop remotely, but the server dint recovered automatically under any circumstances. If you provide remote start up then only any thing happened it will restart automatically.

So for any servers needs to configure remotely we need to enroll first