List of Figures

Chapter 1: Getting Started with Geronimo

Figure 1-1: Geronimo project home page

Figure 1-2: Geronimo download page

Figure 1-3: Startup screen for server10

Figure 1-4: Output from list-modules command

Chapter 2: Basic Geronimo Configuration

Figure 2-1: The operations of the progeron application

Figure 2-2: Inside the progeron.ear file

Figure 2-3: Components inside progeron.ear are deployed to different servers

Figure 2-4: Geronimo Web console login page

Figure 2-5: The progeron.ear application deployed and running on Geronimo

Figure 2-6: Installing the progeron.ear application via the Web console

Figure 2-7: Confirming the installation and running of Application EARs

Figure 2-8: The list of modules currently deployed on the server

Figure 2-9: The lifecycle of a Geronimo-managed module

Figure 2-10: Configurable attributes for TomcatWebConnector listener component

Chapter 3: Apache and Geronimo

Figure 3-1: Homepage of the Apache Software Foundation

Figure 3-2: Organization of projects at the Apache Software Foundation

Figure 3-3: Historical timeline of major events associated with the Geronimo project

Chapter 4: Geronimo’s J2EE 1.4 Components

Figure 4-1: J2EE tiers and container services in Geronimo

Figure 4-2: User access Geronimo through the Web tier

Figure 4-3: EJBs deployable at Geronimo’s business tier

Figure 4-4: Geronimo’s JCA 1.5 and EIS tier services

Figure 4-5: Geronimo support for incoming Web service clients

Figure 4-6: Geronimo support for component access to external Web services

Figure 4-7: Geronimo’s CORBA interoperation support

Figure 4-8: Geronimo’s client application container

Figure 4-9: Naming service support in Geronimo

Chapter 5: Geronimo Architecture and Directory Structure

Figure 5-1: Running Geronimo server comprises GBeans and a kernel

Figure 5-2: Geronimo kernel configuration management service

Figure 5-3: Configuration management in Geronimo

Figure 5-4: Storing deployed modules binaries within the repository

Chapter 6: The Geronimo Deployer

Figure 6-1: Geronimo run-time deployer

Figure 6-2: The interoperable JSR-88-compliant components

Figure 6-3: Online deployment versus offline installation

Figure 6-4: Using the Web console to display module run-time state

Chapter 7: Using the Geronimo Debug Console and jconsole

Figure 7-1: JMX levels

Figure 7-2: JMX Agent level

Figure 7-3: Operations of an MEJB in a JSR-77 server such as Geronimo

Figure 7-4: Geronimo debug console is a JSR-77 client application

Figure 7-5: State transitions and JSR-77 manageable states

Figure 7-6: Debug console configuration started in Geronimo console

Figure 7-7: jconsole local running JVM section dialog

Figure 7-8: A successful connection to the Geronimo JVM

Figure 7-9: Initial display of the debug console

Figure 7-10: Querying for deployed application components by using a domain filter

Figure 7-11: jconsole display of Geronimo MBeans

Figure 7-12: Debug console query results for objects in the progeron application

Figure 7-13: Objects in the progeron application in jconsole

Figure 7-14: Debug console displaying the MBean attributes for the AuthorEJB session bean

Figure 7-15: jconsole displaying details for the AuthorEJB session bean

Chapter 8: Geronimo Web Console

Figure 8-1: Logging on to the Geronimo Web console

Figure 8-2: Real-time system information display

Figure 8-3: Viewing and searching logs with Geronimo Web console

Figure 8-4: The Server Manager portlet for system shutdown

Figure 8-5: Configuration of Web server connectors with Web console

Figure 8-6: The statistics shown by the Web Server Manager portlet

Figure 8-7: Web Server Network connectors configuration possibilities

Figure 8-8: Configuring ActiveMQ message broker and connectors with Geronimo Web console

Figure 8-9: Thread Pool Configuration portlet and available thread pools

Figure 8-10: Use the Apache mod_jk Configuration Portlet to expose the application

Figure 8-11: Directory hierarchy of the Geronimo repository

Figure 8-12: The Repository Viewer and Installation portlet

Figure 8-13: The Database Pools configuration portlet

Figure 8-14: Creating JMS resource groups

Figure 8-15: The Install New Application portlet

Figure 8-16: Portlet showing all the installed enterprise application EAR modules

Figure 8-17: Creating, installing, and removing plug-ins

Figure 8-18: Creating a new security realm with the Security Realms Portlet

Figure 8-19: Using the Keystore Configuration portlet

Figure 8-20: Running SQL against the embedded database with Database Manager portlet

Chapter 9: Geronimo Deployment Plans

Figure 9-1: Deployment descriptors and deployment plans for modules’ deployment

Figure 9-2: Deployed modules stored in the repository

Chapter 10: Web Container Configuration and Jetty

Figure 10-1: Default welcome screen for Web container

Figure 10-2: Network Listeners portlet

Figure 10-3: Network Listeners portlet for setting up HTTP

Figure 10-4: Network Listeners portlet for setting up HTTPS

Figure 10-5: Install New Applications portlet of the Web console

Figure 10-6: Installed Web Applications portlet of the Web console

Figure 10-7: geronimo-web XML Schemas (XSD) for Generic, Jetty, and Tomcat

Chapter 11: Tomcat Web Container Configuration

Figure 11-1: Geronimo/Tomcat Welcome Screen

Figure 11-2: Tomcat/Geronimo object hierarchy

Chapter 12: Deploying Enterprise Applications (EAR) with OpenEJB

Figure 12-1: Web-tier module references to business-tier EJBs and other resources

Figure 12-2: Business-tier references to separately deployed EJBs and other resources

Figure 12-3: Resolved EJB references within an EAR module

Figure 12-4: Mapping external EJB references via a Geronimo-specific deployment plan

Figure 12-5: Creating the wroxauthors database for the CMP bean

Figure 12-6: Creating and populating tables in the wroxauthors database

Figure 12-7: Viewing the content of the authors table in the Derby wroxauthors database

Figure 12-8: Using the wizard to create the AuthorConnectionsPool database pool

Figure 12-9: Setting driver and parameters for the AuthorConnectionsPool

Figure 12-10: Displaying the deployment plan for the deployment of AuthorConnectionsPool

Figure 12-11: Successful deployment of the AuthorConnectionsPool

Figure 12-12: The example running with data from Derby RDBMS

Figure 12-13: The Geronimo application client container

Chapter 13: Configuring and Deploying JDBC Resources with PostgreSQL

Figure 13-1: PostgreSQL architecture

Figure 13-2: Geronimo console display of deployed J2EE resource adapters

Figure 13-3: The beginning of the Database Pools Wizard

Figure 13-4: Step 1 of the Database Pools Wizard

Figure 13-5: Step 2 of the Database Pools Wizard

Figure 13-6: Select the appropriate JDBC driver to download

Figure 13-7: After downloading the JDBC driver and providing the required information

Figure 13-8: Completing the database pool configuration

Figure 13-9: Testing the JDBC connection

Figure 13-10: The database pool plan

Figure 13-11: The ProGeronimoPool

Figure 13-12: High-level architecture of Sequoia

Chapter 14: Deploying Web Services and CORBA Interoperation

Figure 14-1: Web service interactions

Figure 14-2: JAX-RPC simplifies coding of Java Web services and Web service clients

Figure 14-3: JAX-RPC interoperation with non-Java Web service clients

Figure 14-4: Geronimo server exposing application components as Web services

Figure 14-5: Deploying the Web service WAR using the Web console

Figure 14-6: Accessing the WSDL of the Web service using a browser

Figure 14-7: A successful run of the standalone Web service client

Figure 14-8: The AuthorBean EJB-based application

Figure 14-9: IDL compiler and programming-language-specific binding

Figure 14-10: CORBA ORB brokering a remote call

Figure 14-11: RMI-IIOP supporting both CORBA client access and RMI client access

Figure 14-12: The CORBA CSIv2 implementation

Chapter 15: Security

Figure 15-1: Security realm

Figure 15-2: JAAS Security GBean relationships

Figure 15-3: JaasLoginCoordinator proxying calls to LoginModules

Figure 15-4: The Geronimo console’s Security Realms portlet

Figure 15-5: Security Realm portlet Step 1

Figure 15-6: Security Realm portlet Step 2

Figure 15-7: Security Realm portlet Step 3

Figure 15-8: Security Realm portlet Step 4

Figure 15-9: Security Realm portlet Step 5

Figure 15-10: Security Realm-Show Deployment Plan screen

Chapter 16: Configuring, Deploying, and Using JMS Resources with Apache ActiveMQ

Figure 16-1: A diagram of the ActiveMQ architecture

Figure 16-2: A listing of the system modules with the ActiveMQ module in a running state

Figure 16-3: A listing of the system modules with the ActiveMQ module in a stopped state

Figure 16-4: The JMS Server screen provides the ability to manage network listeners within ActiveMQ

Figure 16-5: Adding a jabber network listener

Figure 16-6: Verifying that the ProGeronimoTopic is deployed

Figure 16-7: Creating JMS Resources for ActiveMQ

Figure 16-8: Create either a connection factory or a destination

Figure 16-9: Determine the type of connection factory to create

Figure 16-10: Fill in the necessary metadata for the connection factory

Figure 16-11: The connection factory has been created

Figure 16-12: Adding a JMS queue

Figure 16-13: Naming the queue

Figure 16-14: The JMS queue has been created

Figure 16-15: Viewing the plan

Figure 16-16: The ProGeronimo JMS Resource Group deployed

Appendix B: Run-Time Deployer Command Reference

Figure B-1: Using the Web console to deploy modules