THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Article donated by: Hernan Cunico
The Geronimo Administration Console is a Web based interface that provides a convenient, user friendly way to administer many aspects of the Geronimo Server. Once you have the Apache Geronimo server started (see Tools and commands) you can access the Administration Console by pointing your browser to the following URL:
The Administration Console log in page is depicted in the following figure.
Log in by specifying system as the username and manager as the password. Once you are logged in you will be redirected to the console's welcome page. The console has two main areas, a navigation panel on the left and a main content area on the right.
The navigation panel on the left provides easy access to the individual tasks, it is always present and allows easy transition from task to task. The main content area on the right is where the real work happens, this area will change as you select the different tasks in the navigation panel on the left. Each view contains one or more portlets that typically include a link for help in the header, see the following figure as an example.
Console Navigation (left panel)
As briefly explained in the previous section, the navigation panel provides access to the different tasks for administering the resources in Geronimo. This navigation panel is organized in the following main groups:
#Welcome
#Server
#Services
#Applications
#Security
#Misc
Welcome
This is the welcome page you see when you log in. It provides a gerenal description of what the Geronimo Administration Console is as well as some shortcut links to common tasks such as:
Common Console Actions
Database Pools
Security Realms
JMS Resources
Deploy Applications
Web Server Ports
Memory & Uptime
This page also provide links to:
Geronimo Online
- The Geronimo Home Page
- Problem Tracking Database
- Users Mailing List
- Developers Mailing List
- Geronimo IRC chat
Geronimo Documentation
Server
Organized under the Server group you will find statistical information as well as links for configuring and administering the different servers. This group is organized as follows:
#Information
#JVM
#Server Logs
#Shutdown/Restart
#Web Server
#EJB Server
#JMS Server
#J2EE Connectors
#CORBA/IIOP
#UDDI Server
Information
This portlet displays the server's uptime and the resources being used by the JVM.
JVM
This portlet displays the values of the system properties available to the server process.
Server Logs
This option provides four portlets, Log Manager, Server Log Viewer, Derby Log Viewer and Web Access Log Viewer.
- Log Manager
This portlet allows the user to select a configuration file for logging and/or change the log level and Refresh period. The default "Config file" is a standard log4j file and defines the location where the Geronimo Server will log Geronimo output. The configuration file also defines the log level, the maximum log file size, and other attributes associated with logging.
- Server Log Viewer
This portlet displays the Geronimo server log and is helpful for debugging problems with the Geronimo Console and with deployed applications.
- Derby Log Viewer
This portlet displays the log file for Geronimo's internal database, Derby.
- Web Access Log Viewer
This portlet displays and filters the Jetty log file. The Jetty log file contains HTTP accesses and messages from JSP and servlet applications that are running on Geronimo. By default this portlet displays the contents of the log file for the current date. You can apply different filtering criteria to view only data of your interest.
Shutdown/Restart
This portlet allows a warm reboot of the server or a shutdown of it. A warm reboot will shutdown all applications and services and reboot the Geronimo kernel within the same process. The Administration Console session will be disconnected. Reconnect after the server is back up.
A shutdown will shutdown the server and cause the JVM to exit. To continue using the Geronimo Console after a shutdown, Geronimo must be restarted.
Web Server
This option provides two portlets, Web Server Manager and Network Listeners.
- Web Server Manager
When this portlet is enabled, it will collect server performance statistics. The values being meassured are:
-
- Requests
- Connections
- Errors
- Active Resquests
- Request Duration
- Connections Open
- Connection Requests
- Connection Duration
For the last five values, Count, Average and Maximum will be also displayed.
- Network Listeners
This portlet displays all the connector listeners (HTTP, HTTPS and AJP) and status for both Jetty and Tomcat Web containers. From this portlet you can add new listeners and change the status (stop, start, delete) of the existing connectors.
EJB Server
At this time, this portlet is not yet implemented.
JMS Server
This option provides two portlets, JMS Server Manager and JMS Network Listeners.
- JMS Server Manager
This portlet displays the available JMS Brokers and their status. From this portlet you can also start, stop, edit, add and delete JMS Brokers.
- JMS Network Listeners
This portlet displays all the network connectors configured for the currently available JMS Brokers. From this portlet you can also start, stop, edit, add and delete JMS network connectors.
J2EE Connectors
At this time, this portlet is not yet implemented.
CORBA/IIOP
At this time, this portlet is not yet implemented.
UDDI Server
At this time, this portlet is not yet implemented.
Services
Organized under this group you will find link for configuring the following services:
#Common Libraries
#Database Pools
#JMS
#Java Mail
Common Libraries
This portlet displays the artifacts installed in the server's repository. The layout of the repository is the same as that used by Apache Maven making it possible to easily copy files over. From this portlet you can also install new artifacts.
Database Pools
This portlet displays all the available database pools and their status. Only server-wide database pools can be edited in this portlet, database pools deployed as part of a single application cannot, you will have to change the deployment plan in the application instead.
From this portlet you can edit the available, system-wide, database pools. There is also a usage link with examples of how to use the pool from your application.
This portlet includes a database pool creation wizard for new pools and also lets you import database pools from JBoss 4 and WebLogic 8.1.
JMS
This option provides two portlets, JMS Connection Factories and JMS Destination Manager.
- JMS Connection Factories
This portlet displays the JMS connectors that are configured on the server. From this portlet you can see the connectors status, display details, test the connection and new JMS Conneciton Factories.
- JMS Destination Manager
This portlet is used to create and remove queues/topics.
Java Mail
At this time, this portlet is not yet implemented.