How to Install GlassFish on CentOS

How to Install GlassFish ESB on CentOS / Red Hat / Fedora

I did my installation on a CentOS 5.4 and I confirm all works, just follow

Download JDK 6u12
# cd /usr
# wget

Download GlassFish 2.1
# wget

Check current Java Version
# java -version
java version “1.6.0”
OpenJDK Runtime Environment (build 1.6.0-b09)
OpenJDK Server VM (build 1.6.0-b09, mixed mode)
# chmod +x /usr/jdk*
# ./usr/jdk-6u12-linux-i586.bin
Accept License, and enter

Adjust path
#vim /etc/profile

You may need to logout and login then:
# java -version
java version “1.6.0_12”
Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
Java HotSpot(TM) Server VM (build 11.2-b01, mixed mode)

Create user
# adduser esb
# passwd esb
# mkdir /usr/local/GlassFishESBv21
# mkdir /home/esb
# chown esb:root -R /usr/local/GlassFishESBv21
# mv /usr/ /home/esb
# chown esb:root -R /home/esb/GlassFishESBv21
# chmod 755 -R /home/esb/GlassFishESBv21

Add it to sudoers just for now
# vim /etc/sudoers



Login into the Gnome interface localy (via VNC wont work)
with the esb user execute from /home/esb
# sudo bash

On the install GUI
Set NetBeans IDE to:
Set Install GlassFish to:

Now lets configure the service to autostart
# cd /etc/rc.d/init.d
# vim glassfish

#Script to start/stop/restart GlassFish
# chkconfig: 35 20 80
# description: GlassFish ESB 2.1 Daemon
case “$1″ in
${GFPATH}/asadmin start-database
${GFPATH}/asadmin start-domain domain1
${GFPATH}/asadmin stop-database
${GFPATH}/asadmin stop-domain domain1
${GFPATH}/asadmin stop-domain domain1
${GFPATH}/asadmin start-domain domain1
echo $”Usage: $0 {start|stop|restart}”
exit 1

# chkconfig –add glassfish
# chkconfig –level 35 glassfish on
# service glassfish start

Once the service start it Should Display:

Starting database in the background.
Log redirected to /usr/local/GlassFishESBv21/glassfish/databases/derby.log.
Command start-database executed successfully.
Starting Domain domain1, please wait.
Default Log location is /usr/local/GlassFishESBv21/glassfish/domains/domain1/logs/server.log.
Redirecting output to /usr/local/GlassFishESBv21/glassfish/domains/domain1/logs/server.log
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Domain [domain1] is running [Sun GlassFish Enterprise Server v2.1 (9.1.1) (build b60e-fcs)] with its configuration and logs at: [/usr/local/GlassFishESBv21/glassfish/domains].
Admin Console is available at [http://localhost:4848].
Use the same port [4848] for “asadmin” commands.
User web applications are available at these URLs:
[http://localhost:8080 https://localhost:8181 ].
Following web-contexts are available:
[/web1 /__wstx-services ].
Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[service:jmx:rmi:///jndi/rmi://SERVERESB:8686/jmxrmi] for domain management purposes.
Domain listens on at least following ports for connections:
[8080 8181 4848 3100 3820 3920 8686 ].
Domain does not support application server clusters and otherstandalone instances.

To login via web go to


Remeber to open firewall for ports required
Check with ps if service is running
Reference to official documentation at:

5 Thoughts

  1. Very helpful. You have our thanks. The service script example was a real time saver.

    A couple suggestions for other readers and a possible edit:

    * Be cautious of cutting and pasting smart quotes from web pages into shell scripts.

    * The last two lines of the service script example should probably be three lines…

    Instead of

    exit 1

    we suggest

    exit 1

  2. This article was very helpful.

    Some additions, don’t forget to make the glassfish startscript executable:
    # chmod +x /etc/init.d/glassfish

    And it is not wise to run the application server as root. To run as eg user “glassfish”, follow these steps (CentOS):
    1. # adduser -M –shell /bin/false glassfish
    2. # chown -R glassfish:glassfish /opt/
    3. Modify the startscript and add “sudo -u glassfish” in front of all asadmin commands.

  3. I’ve the next message when I run the installation script ┬┐Any idea?

    Configuring the installer…
    Searching for JVM on the system…
    Extracting installation data…

    Installer file /home/esb/ seems to be corrupted

Leave a Reply

Your email address will not be published. Required fields are marked *