Tag Archive | node

AutoRestarting Application Servers With Nodeagent in WebSphere

Jan22

In WebSphere 7, by default, the Nodeagent will take no action if an application server fails. In order for the Nodeagent to intervene and automatically restart a failed application server instance, the ‘monitoring policy’ must be set for that application server.

Login to the Admin console, perform the following:

1 . Click Servers.>>Select Server Types >> Select WebSphere Application Servers. >>Select <server_name> to monitor

docview.wss

 

2) Navigate to <Application Server> –> Java and Process Management –> Monitoring Policy

 

docview.ws1s

3)  Check the box next to “Automatic Restart”

4).  In the “Node Restart State“, set the state to “STOPPED”

 

docview.wss2

 

  • If set to ‘STOPPED‘ actions above will allow the nodeagent to auto-restart a failed or killed application server
  • If set to ‘RUNNING‘ not only will the nodeagent restart a failed or killed application server, but it will autostart the application server upon a nodeagent restart.  (This may be unwanted in certain environments where application servers are only supposed to run at certain times or if there is a specific application start order.)
  • If set to ‘PREVIOUS‘ will enable  to return to its current state after the node restarts.

If you wish to have the nodeagent automatically start application servers when it comes online, set the state to “RUNNING“.

How to check if Node is in sync with Dmgr

Jan21

Option1: Login to the Admin console >> System Administration >> Nodes >>
Within the Nodes there would be a column for the Sync Status
If it is broken it means that the Sync is not synced

Refer the Snapshot below

syncnode1

The node01 and node02 are not synced

===================================================================

Option2:

===================================================================
First of all localize wsadmin tool on your host. It is located in <install_root>/AppServer/bin

cd <install_root>/AppServer/bin

Start wsadmin tool to connect to deployment manager

wsadmin.sh -host <dmgr_server> -port <dmgr_SOAP_port> -conntype SOAP -username <admin_username> -password <admin_password>

Assign node name to some variable I have used node_name in this example and mynode is the name of the node you would like to synchronize

set node_name [$AdminControl completeObjectName type=NodeSync,node=mynode,*]

For Eg
wsadmin>set node_name [$AdminControl completeObjectName type=NodeSync,node=mynode,*]
WebSphere:mbeanIdentifier=nodeSync,cell=my_cell,process=nodeagent,name=nodeSyn
c,platform=common,node=mynode,version=6.0.2.23,type=NodeSync

Now, when we know the exact name of the node we can check if it is in sync with deployment manager

$AdminControl invoke $node_name isNodeSynchronized

If node is in sync with deployment manager you will see following output

wsadmin>$AdminControl invoke $node_name isNodeSynchronized
true
wsadmin>

The “True” Represents that the Node is Synced