Skip to main content

Installing Java and Apache Tomcat in your CentOS / Redhat Server

Installing Java and Apache Tomcat in your CentOS / Redhat Server

Steps :

Installing Java SDK

Step 1: SSH into the server using the following command
ssh –X root@ip-address-of-server
Then provide the root password. Please note that you need to use the root (admin) account itself, since you need super-user privileges to install applications in the server.

ssh to linux server

Step 2: Install jpackage-utils in the server using
yum install jpackage-utils

You can also get the packages (using wget) from http://www.jpackage.org/ and install them manually.

installing jpackage

This will automatically pull the packages from the repository and install them Smile

java-utils

Step 3: Now we are going to install the Java SE Development Kit 6u22 for Linux. You may check this site to find whether this is latest version or not.
Since I’m going to use wget, I need a direct link to download the package.You can grab the package from here


http://techblog.googlecode.com/files/jdk-6u22-linux-i586-rpm.bin

Now use wget and pull this package to your server.

downloading java sdk from techblog project site

Step 4: Once it has been downloaded directly to the server, change the permissions accordingly as shown below:
chmod +x package-name.bin



Now issue the following command and verify that Java has been installed properly.
java –version

verifying java installation

Installing Tomcat

Since Apache Tomcat is available in the repository, you can use the install command for installing it:
yum install tomcat*

This will install the server.

installing tomcat using yum

But in my case, it installed tomcat5 – which is an old version. The new version has a better memory management utility. So I had to remove the installation Sad smile
remove yum 

removing tomcat

Installing Tomcat6 manually

As of today the latest version is 6.0.29. So we use the wget utility and download the package from the server:
wget http://apache.mirror.testserver.li/tomcat/tomcat-6/v6.0.29/bin/apache-tomcat-6.0.29.tar.gz

Please note that it is better to download this file to the /opt directory. (You can do this either by ‘cd-ing’ to the directory before issuing the wget or moving the file to /opt once the file has been downloaded).

installing tomcat manually

Now untar the tarball using
tar –xvfz tarball-name.tar.gz

This will extract the items in the tarball and now you need to go to the bin directory in the extracted directory and run the startup.sh script. That’s it!
Now go to localhost:8080 (you may use Lynx for this) and verify that tomcat is running:
lynx
press g
enter “localhost:8080”

tomcat - using lynx

NOTE: Now you can try it at ip-address-of-server:8080. Please note that sometimes the datacentre may not have opened the port 8080. In my case, since Nazdrovia is using Planet Inc as the datacentre for providing the frontend and Amazon EC2 as backend, I had to ask them to open the port. So if you are getting a ‘server not found’ error, it is due the firewall – you may ask the datacentre to open it.

Starting Apache Tomcat during bootup

It is hard to run the start-up script manually every time you restart the server. So you may add the location of the script to
/etc/rc.d/rc.local
 
And it will be executed automatically every time you boot the system.
Please note that if you are using a Debian based distribution, then the location of the above mentioned file is at:
/etc/rc.local
 
Admin and Manager roles You need to assign admin and manager roles to the tomcat users in order to manage web apps using a web based interface. (Please note that if you put anything in the web-apps directory of the server, it will be deployed automatically).You can do this by going to the new folder you created by extracting the tarball and editing the tomcat-users.xml file (/conf/tomcat-users.xml).
nano tomcat-users.xml

Now you need to add the following lines to that xml file:



Please note that you have to change the default passwords of the existing users due to security reasons. Once you have done that you can login to the admin and manager pages :
ip-address-of-server:8080/admin

tomcat web app admin

ip-address-of-server:8080/manager

tomcat web app manager


Managing the service

You can start or stop the tomcat service using the following commands:

/etc/init.d/tomcat6 start
/etc/init.d/tomcat restart
/etc/init.d/tomcat stop


Have fun and enjoy!




FEED













SUPPORT US












VISIT COUNTER !!





Comments

Popular posts from this blog

Defacing Sites via HTML Injections (XSS)

Defacing Sites via HTML Injections Defacing Sites via HTML Injections What Is HTML Injection: "HTML Injection" is called as the Virtual Defacement Technique and also known as the "XSS" Cross Site Scripting. It is a very common vulnerability found when searched for most of the domains. This kind of a Vulnerability allows an "Attacker" to Inject some code into the applications affected in order to bypass access to the "Website" or to Infect any particular Page in that "Website". HTML injections = Cross Site Scripting, It is a Security Vulnerability in most of the sites, that allows an Attacker to Inject HTML Code into the Web Pages that are viewed by other users. XSS Attacks are essentially code injection attacks into the various interpreters in the browser. These attacks can be carried out using HTML, JavaScript, VBScript, ActiveX, Flash and other clinet side Languages. Well crafted Malicious Code can even hep the ...

EKS Cluster and Create CSI Driver to store credentials in AWS Secrets Manager via SecretProviderClass

EKS Cluster | CSI Driver | SecretProviderClass | AWS Secrets Manager Setup EKS Cluster and Manage Credentials at runtime using CSI driver using SecretProviderClass and Secrets Manager Assuming you have Configured/Installed AWS CLI, EKSCTL, KUBECTL, HELM. CSI Basic Information: CSI (Container Storage Interface) widely used as a Storage Technology. Created by Google | Mesosphere | Docker.  It has two two Plugins one runs on the Master Node (Centralized Controller Plugin) and another one on Worker Nodes (Decentralized headless Node Plugin).  CSI communication protocol is gRPC.   The communication between Container Orchestration to Controller Plugin (Master) and to Node Plugin (Worker Node) happens using gRPC .  CSI Drivers : vendor specific compiled into Kubernetes/openshift binaries. To use a CSI driver, a StorageClass needs to be assigned first.  The CSI driver is then set as the Provisioner for the Storage Class. CSI drivers provide three main service...

Linux Systems Performance/Observability (BPF (bpfcc-tools), BCC Tools

  Linux System Performance/Observability Tools Linux Systems Performance/Observability (BPF (bpfcc-tools), BCC Tools Assuming you have Linux Server in place and have the required BPF aka BCC related packages installed on the system(s) for the required Linux distribution. BPF(eBPF) aka BCC Tools (bpfcc-tools) : BPF, which originally stood for Berkley Packet Filter is the dynamic tracing tools for Linux Systems.  BPF initially used for the speeding up for the tcpdump expressions and since then it has been know as the extended Berkley packet Filter (eBPF).  Its new uses are Tracing Tools where it provides programmability for the BPF Compiler Collection (BCC) and bpftrace front ends .   Example: execsnoop, biosnoop etc is a BCC Tool. When facing production performance crisis these such list of tools comes handy to trace and fix the issue. However, it requires certain KERNEL level config options to be enabled such as CONFIG_FTRACE, CONFIG_BPF. Profiling tools typically re...