|
|
| Home > Apache Geronimo v1.2 > Documentation > Administration > Geronimo Administration Console |
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.
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
Embedded DB
JMX Viewer
LDAP Viewer
This is the welcome page you see when you log in. It provides a general description of what the Geronimo Administration Console is as well as some shortcut links to common tasks such as:
Database Pools
Security Realms
JMS Resources
Deploy Applications
Web Server Ports
Memory & UptimeThis page also provide links to:
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
Web Server
JMS Server
Thread Pools
Apache HTTP
This portlet displays the server's uptime and the resources being used by the JVM.
This portlet displays the values of the system properties available to the server process.
This option provides four portlets, Log Manager, Server Log Viewer, Derby Log Viewer and Web Access Log Viewer.
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.
This option provides two portlets, Web Server Manager and Network Listeners.
 |
For the last five values, Count, Average and Maximum will be also displayed. |
This option provides two portlets, JMS Server Manager and JMS Network Listeners.
This portlet lists all the thread pools defined in the server. It shows the pool size and allows you to monitor individually each of the listed thread pools. By monitoring these threads you can gather statistical information such as pool max, lowest recorded, highest recorded and threads in use.
This portlet is a wizard that walks you through the process of configuring Apache Geronimo to use a remote Apache 2 HTTP server. To configure the remote HTTP server you will need to install the mod_jk Apache module on the remote server. Based on a series of questions the wizard will guide you through the configuration process.
Organized under this group you will find links for configuring the following services:
Common Libs
Database Pools
JMS Resources
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.
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.
This portlet lists all the JMS resource groups available in the Geronimo server, that is queues and factories. From this portlet you can create new JMS resource groups, this portlet provides two wizards, one for ActiveMQ and one for another JMS provider. For this last one you will have to provide the specific resource adapter RAR needed to connect to that particular provider.
<!-- CONTINUE HERE -->
Organized under this group you will find links for installing and administering applications.
Deploy New
Application EARs
Web App WARs
EJB JARs
J2EE Connectors
App Clients
System Modules
Plugins
This portlet allows you to deploy new applications to the Apache Geronimo server. Web applications require deployment plans, which are either packaged with the war file or kept in a separate file which is typically called geronimo-web.xml.
This portlet displays the installed Application EARs and their status. From this portlet you can also stop, start and uninstall the available Application EARs.
This portlet displays the installed Web Applications and their status. From this portlet you can also stop, start and uninstall the available Web Applications.
This portlet displays the installed EJB JARs and their status. From this portlet you can also stop, start and uninstall the available EJB JARs.
This portlet displays the installed J2EE Connectors and their status. From this portlet you can also stop, start and uninstall the available J2EE Connectors.
This portlet displays the installed Application Clients and their status. From this portlet you can also stop, start and uninstall the available Application Clients.
This portlet displays the installed System Modules and their status. From this portlet you can also stop, start and uninstall the available System Modules.
This portlet allows you to install or create Geronimo plugins. From this portlet you can select a remote plugins repository and search for available plugins and install them or export to plugins just about any module you have already installed in Geronimo.
Console Realm
Security Realm
Keystores
Certificate Authority
This option provides two portlets, Console Realm Users and Console Realm Groups.
This portlet displays all available security realms and their status. Only server-wide security realms can be edited in this portlet, security realms 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, security realms. There is also a usage link with examples of how to use the realm from your application.
This portlet also includes a security realm creation wizard for creating new realms.
This portlet walks you through the process of configuring keystores to use with SSL connectors. From this portlet you can add or edit keystores, add Trust Certificates and create private keys.
This portlet allows you to create a Certification Authority (CA) in Geronimo and issue certificates in reply to Certificate Signing Requests (CSRs).
Organized under this group you will find links:
This portlet displays information about the internal database, such as:
This option provides two portlets, DB VIewer and Run SQL.
This portlet provides a tree like representation for you to browse the different types of MBeans. Each MBean will be represented as a tree node that shows its object name representation. All MBeans will give you a list of MBeans grouped by its domain.
This portlet lets you connect to any LDAP server and browse its content but not edit it. This portlet comes predefined to access the LDAP embedded in Geronimo, make sure the service is running before you connect to the server.
