Monitoring Policy on Websphere Application Server Process

 Monitoring Policy on Websphere Application Server      


When ever JVM goes down or unreachable or JVM ran into OOM(Out of Memory) ,explicitly user will be notified by Application team or monitoring team till that time Application will be un reachable or down. This will be potentially an impact and this need to have a manual efforts or intervention to start the JVM or Services .                                                  

To avoid this Websphere has a feature called monitoring policy which will monitor the health of the JVM process by nodeagent and start it when ever JVM goes down or un reachable or ran into OOM. We don't need any manual intervention needed until and unless if Nodeagent also fails to restart the JVM process. 

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.      

Process :        Login to the Websphere Admin console  

                                                                                                                                                                            

1. Click Servers.>>Select Server Types >> Select WebSphere Application Servers. >>Select <Server_Name> to monitor                
                                                                                                      
2. Navigate to <Application Server> –> Java and Process Management –> Monitoring Policy 







3. Check the box next to “Automatic Restart”     




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

  • If this property is set to STOPPED, node agent does not start the server.
  • If this property is set to RUNNING, the node agent always starts the server.
  • If this property is set to PREVIOUS, the node agent starts the server only if the server was running when the node agent stopped. It will enable  to return to its current state after the node restarts.

5.Click on OK to Save & Sync the configuration





Comments

Post a Comment

Popular posts from this blog

IBM WebSphere - Synchronize a node (syncNode)

Image
  IBM WebSphere - Synchronize a node (syncNode) Before we get into synchronization, let's talk about nodes and the master configuration. The master configuration is a collection of XML files that contain all sorts of information about a cell, such as the security settings and the applications in the cell. A node contains one or more WebSphere application servers. When a managed nodes is federated into the dmgr, the node needs to be synchronized with the master configuration so that the node is using the dmgr configuration. The synchronization is always from Dmgr to Nodes and it never happens vise versa. If you made any changes from the node side it will be cleared during next synchronization process. Let's consider a common example. You make some change in the WebSphere admin console, and you are presented wit the Save option. Selecting save updates the master configuration. This will cause the node to be out of sync with the master configuration. To know if a node is synchroni...
Read more

Daily usage Linux Commands for Any Middleware Administration

Daily usage Linux Commands for Any Middleware Administration Processes related: ------------------ $ ps -ef | grep <process_name> ----- will show the process ID of the proces $ ps -eaf --> to see the Process ID's $ telnet <hostname> <Port_Number> --> It is used to check whether port(server) is listening or not $ scp    -r     file_Name     username@hostname:path  ----- If you want to copy a file from one linux server to another sever $ kill -9 PID ----- Killing an unwanted process $ kill -3 PID ----- Used to take thredDump of the process $ ssh username@servername --> Command used to login to server $ nslookup <host_name> --> Query the nameserver for the IP address of the given HOST optionally using a specified DNS server (To identify the server ip_address by using nslookup command ) $ crontab Minute Hour DayOfMonth Month DayOfWeek (eg: 30 08 10 06 * /home/was/full-backup) ----- Used to scheduled a job on Li...
Read more

Backup and Restore of WebSphere Application Server configuration

                      Backup & Restore of IBM WebSphere Application Server Configuration Backup configuration in  WebSphere One of the major activity that we can perform in Websphere as a pre-requisites when ever we intended to perform any major configuration changes like Fix Pack upgrade ,Interim Fix upgrade, JDK upgrade etc. For any mission critical application, taking frequent backups is essential for recovering from severe errors. In the case of WebSphere Application Server, setting up of the application server environment is a demanding task and it is not an easy to repeat the setup if something bad happens. So, its wise to take backups whenever we make the first setup or when we do configuration changes. Depending upon our diskspace availability two types of backups is possible . 1) Full Backup A full backup can be performed by running the ./backupConfig command from the<WAS-ROOT>/bin di...
Read more