Skip to main content

Managing tomcat application

Tomcat is a servlet application which is ready to use after download. There is no need of installing this application. We can directly start or stop it from the bin directory. 

So in such case we should go to the bin directory in the CATALINA_HOME or else we need to use the startup script along with its absolute path. And the same is needed to shut it down.

We can use the below script to manage the tomcat application and we neither need to go to the CATALINA_HOME nor to use the absolute path. All we need to do is to change the permissions to make it executable and copy that to /sbin and /etc/init.d/ directories. If we copy this into /etc/init.d/ then also we need to mention the absolute path but we can easily memorize it as we know all the startup scripts exists there. But if we copy that into /sbin then there is absolutely no need of mentioning the path of the file.

We can use this like below:
 # tomcat start|stop|restart|status  
#!/bin/bash  
# Author : Arjun Shrinivas  
# Purpose : This script is usefull for managing tomcat  
   
 CATALINA_HOME=/u01/tomcat  
 OPTION=$1  
   
 echo "Usage: `basename $0` start|stop|restart|status"  
   
 case $OPTION in  
 start)  
      echo "Starting tomcat"  
      $CATALINA_HOME/bin/startup.sh  
 ;;  
 stop)  
      echo "Stopping tomcat"  
      $CATALINA_HOME/bin/shutdown.sh  
 ;;  
 restart)  
      PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
      if [ -z $PID ]  
      then  
           echo "Starting tomcat"  
           $CATALINA_HOME/bin/startup.sh  
      else  
           echo "Stopping tomcat"  
           $CATALINA_HOME/bin/shutdown.sh  
           sleep 20  
           PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
           if [ -z $PID ]  
           then  
                echo "Starting tomcat"  
                $CATALINA_HOME/bin/startup.sh  
           else  
                echo -e "Unable to shutdown tomcat. Force killing tomcat PID : $PID"  
                kill -9 $PID  
                echo "Starting tomcat"  
                $CATALINA_HOME/bin/startup.sh  
           fi  
      fi  
 ;;  
 status)  
      PID=`ps -ef | grep catalina | grep -v grep | awk '{print $2}'`  
      if [ ! -z $PID ]  
      then  
           echo -e "Tomcat is running on pid : $PID"  
      else  
           echo -e "Tomcat is not running"  
      fi  
 ;;  
 *)  
      echo "Invalid operation"  
 ;;  
 esac  
   
 # END

Comments

Popular posts from this blog

Troubleshooting Tomcat using Catalina log

Troubleshooting Tomcat using Catalina log We can get the  catalina  logs in  $CATALINA_HOME/logs Here we'll have a  catalina.out We can see some huge info in that log file. If we want to what exactly happens since the start of tomcat then we need to log that into a new file. By default we have log rotation enabled on this logs. For now let us stop tomcat and nullify the catalina.out file and then start tomcat to have some new info in the catalina.out # service tomcat stop # cd $CATALINA_HOME/logs # :> catalina.out (or) cat /dev/null > catalina.out # ll catalina.out -rw-r----- 1 root root 0 Feb 18 16:19 catalina.out # service tomcat start # ll catalina.out -rw-r----- 1 root root 17341 Feb 18 16:21 catalina.out We can see the log being written after the start of tomcat. Now we can notice the instance giving some information about the starting of tomcat, about the configuration for the startup, path of the servlet instance for which the log is responsible for,

Red Hat Enterprise Virtualization Manager RHEL 7 – Part 2

I have just published  what is RHEV  is the first article to understand RHEV Better. In order to maintain multiple RHEV-Hosts from central place RHEV-Manager is required. RHEV-M will be used as central place to manage all RHEV-Hosts. In this Article We are going to see HowTo Install RHEV-M Red Hat Enterprise Virtualization Manager RHEL 7. Red Hat Enterprise Virtualization Management (RHEV-M) is a virtual management console built on Red Hat Enterprise Linux (RHEL). It interacts with individual RHEV-Hosts using the Virtual Desktop Server Manager (VDSM). A VDSM agent is running on each of the RHEV-H nodes. RHEV-M allows administrators to manage/control number of data centers and their network, compute and storage resources. In addition RHEV-M provides a central repository for storing virtual machines, disks, images and virtual machine snapshots. Install RHEV-M Hardware Requirements Hard Disk Space Minimum 50GB RAM Minimum 4GB – Max 2TB Dual Core or High Processor 1Gbps NIC Ca

RHVH 4.1 Installation Steps for Red Hat Virtualization Host

Red Hat Virtualization Host (RHVH 4.1) is installed using a special build ( Download Link )of Red Hat Enterprise Linux with only the packages required to host virtual machines. It uses an Anaconda installation interface based on the one used by Red Hat Enterprise Linux hosts, and can be updated through the Red Hat Virtualization Manager or via yum. Using the yum command is the only way to install additional packages and have them persist after an upgrade. In this article we are going to see RHVH 4.1 installation RHVH features a Web interface for monitoring the host’s resources and performing administrative tasks. Direct access to RHVH via SSH or console is not supported, so the Cockpit user interface provides a graphical user interface for tasks that are performed before the host is added to the Red Hat Virtualization Manager, such as configuring networking and deploying a self-hosted engine, and can also be used to run terminal commands via the  Tools > Terminal. Access the C