Article donated by: Hernan Cunico

This article is an attempt to cover as many administrative tasks as possible, common and not so common tasks. This article is grouped in four main sections having a similar flow to what you would find while using the Geronimo Administration Console, this way should be easier for you to familiarize on both tasks and console.

This article is organized in the following sections:

• #Administering the Apache Geronimo Server
  • #Changing the Web container [Jetty or Tomcat]
  • Starting and stopping the server
  • Configuring resources
  • Installing applications
  • Starting and stopping application modules
  • Configure log level
  • Performance monitoring
  • Adding new listeners for the Web containers
  • Configuring the EJB server engine
  • Configuring J2EE connectors
  • CORBA/IIOP
  • Configuring the UDDI server
• Configuring Services
  • Adding files to the Geronimo repository
  • Configuring database pools
  • Configuring JMS
  • Configuring JavaMail
• Administering applications
  • Installing and removing applications
  • Starting and stopping applications
• Administering security
  • Addiing security realms
  • Importing certificates
  • Configure LDAP
  • Configuring SSL

Administering the Apache Geronimo Server

Covered in this section are the most common, every day, server related administrative tasks you may deal with. Subsequent sections will focus on configuring services, managing applications and configuring security.

Changing the Web container [Jetty or Tomcat]

Selecting the Web container is very simple and it is limited to just renaming one file, the config.xml. Located in the <geronimo_home>/var/config directory there are several xml files. We will just focus on three of them:

• config.xml
• config.jetty.xml
• config.tomcat.xml

config.xml is the file actually being read at the server startup time, the other two are configuration templates for those particular Web containers. Renaming config.jetty.xml or config.tomcat.xml to config.xml will set the Web container to Jetty or Tomcat next time you start Apache Geronimo.

Back to Top

Starting and stopping the server

There are two command line ways to start the server. From a command line window or terminal change directory to <geronimo_home>/bin. From there you can either type:

java -jar server.jar

or simply

*startup

Refer to the Startup section for all the options for this command.

To stop the server you will have to open a new command line window or terminal, change directory to <geronimo_home>/bin and run the shutdown command. You will be prompted for username and password. Refer to the Shutdown section for all the options for this command.

If the server is already running you have the option of using the Geronimo Administration Console to stop or restart the server. With the server up and running open a Web browser and point to the following URL to access the console:

http://localhost:8080/console

Back to Top

Configuring resources

for example Database

Installing applications

Starting and stopping application modules

Configure log level

Performance monitoring

Adding new listeners for the Web containers

Configuring the EJB server engine

Configuring J2EE connectors

CORBA/IIOP

Configuring the UDDI server

Configuring Services

Adding files to the Geronimo repository

Configuring database pools

Configuring JMS

Connection factories, queues, topics and destinations.

Configuring JavaMail

Administering applications

Installing and removing applications

include hot deployment and redeployment

Starting and stopping applications

Administering security

Addiing security realms

Importing certificates

Configure LDAP

Configuring SSL

Back to Top