Thank u vinay for u r fastest reply....ia m running WLS 10.3.6 on win-7 mechine...configured Admin server ,and 2 manged server ....want to deploy my WAR in both managed instances ....is it possible to both managed server without NODE MANAGER.. i have configurd node manager in the same mechine (localmehcine port 5556) but not running ,,,,but node manager is not wotking.. can u tell me functionality of NM....?
Ramkiran Nandula www.techartifact.com/blogs/2014/03/configure-node-manager-in-weblogic-and-administer-managed-server.html . see this link and follow steps to configure NM. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances -- whether Administration Server or Managed Server -- that you want to control with Node Manager.
Ramkiran Nandula Running nmEnroll() ensures that the correct NodeManager user and password token are supplied to each managed server. You can start managed server without Node managers too.You have to use startManagedWebLogic.sh managedServerName .
vinay;;@ Hi vinay..i have 1 admin and 1 managed servers are running .....recently i have added another managed server instance .....by node manager error it's not going to shtudown..(suspended state) ...i unable to shutdown from Admin console..... showing this msg: The server TEST4QC(managed server) is in an incompatible state. [image: Message icon - Warning]All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed. any way to stop the managed server? is it correct to do--> ./stopmanagedweblogic.sh..................? any arguments...?
Ramkiran Nandula for each physical server you need to create a machine and you need to add respective managed server associated with the respective machine. Make sure you have node manager running on each physical server and check if the nodemanager is reachable from the admin console before you start the managed server .Check the node. In the general tab, is a machine assigned to it? To stop start managed servers from admin console u need to configure the machine and start the node manager associated with the machine. Make sure node manager shows it is reachable from Admin console before trying any actions from console on managed servers. Also you can start the managed servers from back end from the same server machine without configuring node manager.
Nice Presentation, I will explore with WLS to start nodemanager. Thank you
HI vinay...thanks alot for clear video.
hello i have a question i have a slowness on my home page from Enterprise manager , where is come
the issue?
Hi Vinay, for different machines we can have a single node manager rite !
+Prakash vec Yes.You can single node manager for multiple machine...
Thank you so much.
Very well explained....
Thank u vinay for u r fastest reply....ia m running WLS 10.3.6 on win-7 mechine...configured Admin server ,and 2 manged server ....want to deploy my WAR in both managed instances ....is it possible to both managed server without NODE MANAGER..
i have configurd node manager in the same mechine (localmehcine port 5556) but not running ,,,,but node manager is not wotking..
can u tell me functionality of NM....?
Ramkiran Nandula www.techartifact.com/blogs/2014/03/configure-node-manager-in-weblogic-and-administer-managed-server.html . see this link and follow steps to configure NM. Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances -- whether Administration Server or Managed Server -- that you want to control with Node Manager.
Ramkiran Nandula You can deploy war on manged instance without node manager too.
Hi vinay...can we start managed servre instances with out node manager?
why we nmenroll(...)?
Ramkiran Nandula Running nmEnroll() ensures that the correct NodeManager user and password token are supplied to each managed server. You can start managed server without Node managers too.You have to use startManagedWebLogic.sh managedServerName .
why remote nodemanager working but not connecting to local machine (admin) console while starting remote servers it won't be starting
Thanks Good explanation but very poor audio quality
vinay;;@
Hi vinay..i have 1 admin and 1 managed servers are running .....recently i
have added another managed server instance .....by node manager error it's
not going to shtudown..(suspended state) ...i unable to shutdown from
Admin console.....
showing this msg:
The server TEST4QC(managed server) is in an incompatible state.
[image: Message icon - Warning]All of the servers selected are currently in
a state which is incompatible with this operation or are not associated
with a running Node Manager or you are not authorized to perform the action
requested. No action will be performed.
any way to stop the managed server?
is it correct to do--> ./stopmanagedweblogic.sh..................? any
arguments...?
Ramkiran Nandula for each physical server you need to create a machine and you need to add respective managed server associated with the respective machine. Make sure you have node manager running on each physical server and check if the nodemanager is reachable from the admin console before you start the managed server .Check the node. In the general tab, is a machine assigned to it?
To stop start managed servers from admin console u need to configure the machine and start the node manager associated with the machine. Make sure node manager shows it is reachable from Admin console before trying any actions from console on managed servers. Also you can start the managed servers from back end from the same server machine without configuring node manager.
Audio quality is poor- You need to improve on the Audio
Nice