This screen lets you select the pool name and basic database type:

Figure 6.3. Console: Database Pool -- Basic Settings

The fields here are:

Select Next to continue.

This screen handles the basic settings for the database pool:

Figure 6.4. Console: Database Pool -- Connection Properties

The fields here are:

The rest of the fields are different depending on which database was selected -- if unsure, consult the JDBC driver documentation. However, many databases use some or all of the following common fields:

Select Next to continue. Note that if the select driver cannot be loaded from the selected JAR, then you'll be returned to this page with an error:

Figure 6.5. Console: Database Pool -- Driver Error

This screen confirms the JDBC URL based on the properties from the previous screen, and handles pool settings:

Figure 6.6. Console: Database Pool -- Pool Settings

The fields here are:

There are three paths forward from here:

The test screen may show up one of two ways, depending on whether the test was successful.

Figure 6.7. Console: Database Pool -- Test Successful

If successful, you can select Deploy to deploy the pool and return to the database pool list screen, or select Show Plan to see the Geronimo deployment plan that will be used for the pool (see Section 6.3.4, “Generate a Plan for an Application or Client Scoped Pool”).

Figure 6.8. Console: Database Pool -- Test Failed

If the test failed, you have three options:

If you select a database type of "Other" or choose to edit setting after a test failure, the console loads a single screen where you can edit all the settings for the pool:

Figure 6.9. Console: Database Pool -- Detailed Edit

The fields here are similar to the options available from the 4-step process:

There are three paths forward from here:

Figure 6.10. Console: Database Pool List View

From the list of database pools on the right, select Add new database pool.

Figure 6.11. Console: Database Pool -- Select XA Database

The fields here are:

Select Next to continue.

This brings up the detailed database pool edit screen, configured for the selected XA driver:

Figure 6.12. Console: Database Pool -- New XA Database Pool

The fixed fields here (everything except the Basic Connection Properties) are:

The remaining fields on this screen are database-specific configuration settings controlled by the XA driver implementation. If the supplied property names and descriptions are not helpful enough, consult the XA driver documentation.

The options to continue from here are Deploy (deploy the pool and return to the pool list screen) and Show Plan (show the Geronimo deployment plan that would be used but don't actually deploy it yet -- see the next section for details).

Most products let you upload a product-specific configuration file to Geronimo to begin the import. For example here is the import screen for JBoss:

Figure 6.14. Console: Database Pool -- JBoss Import

Simply choose the correct database pool or server configuration file (noted above the Next button) and hit Next to continue. For JBoss, this is a JBoss database pool deployment file, named something-ds.xml and usually in the deploy directory.

WebLogic has an additional configuration option. Uploading the config.xml as above strips out the database connection passwords. The alternative is to point the console to the WebLogic server/lib directory and WebLogic domain directory, and then Geronimo can recover the passwords along with the rest of the connectivity information. Of course, this only works if Geronimo and WebLogic are on the same machine, and if the WebLogic directory is readable to the user that started Geronimo. The WebLogic import screen looks like this:

Figure 6.15. Console: Database Pool -- WebLogic Import

In this case either select the config.xml file (top) or enter the directory paths (bottom) and click the corresponding Next button to continue.

Once the configuration files have been identified and/or uploaded, Geronimo lists all the database pools it found on the import status screen:

Figure 6.16. Console: Database Pool -- Import Status

This screen shows all the pools that were found for import on the top, then the database pools configured in Geronimo already, then any messages generated during the import (usually related to content in the configuration file that was not processed). In Figure 6.16, “Console: Database Pool -- Import Status”, 6 pools were identified. One is listed as "Ignored" because it is an XA database pool but Geronimo does not have a corresponding XA driver (in this case, for Oracle). One is listed as "Deployed as..." because it was already processed when the screen shot was taken. The others have links to Confirm and Deploy, which is how you complete the import process for a database pool.

The confirm and deploy process loads the database pool edit screen (see Section 6.3.1.5, “Detailed Pool Edit Screen”) with all the settings Geronimo found in the imported database pool. Some settings may be missing if they could not be imported, and you may need to massage the imported data in any case (for example, if a WebLogic pool used the BEA driver for Oracle, it would need to be changed to the standard Oracle JDBC driver). Once you save the pool or cancel the editing process, the console returns to the import status screen.

When you've imported all the pools you're interested in, click Finish or Skip Remaining Pools to return to the main database pool list screen.

Figure 6.17. Console: Database Pool -- Show Plan

This screen shows the deployment plan that was generated based on the selections made on the previous screens. It also provides a command that could be used to deploy the pool on the command line, as well as providing a simple procedure to add the database pool to an EAR as an application-scoped pool.

The main step to take from this screen is to copy the entire contents of the Deployment Plan text area (using Ctrl-A or a similar shortcut to be sure). The next three sections discuss the different ways to use this plan.

	Tip
	If you plan to deploy more than one pool in the same server using this plan, be sure to change the configId attribute in the top connector element, and the name specified in the connectiondefinition-instance element.

java -jar GERONIMO_HOME/bin/deployer.jar deploy \
    GERONIMO_HOME/database-pool.xml \
    GERONIMO_HOME/repository/tranql/rars/tranql-connector-1.1.rar

Figure 6.18. Console: Database Pool List View

From the list of database pools on the right, select the edit link next to the database pool to edit. The edit screen will be configured slightly differently depending on whether this is a JDBC pool or an XA pool; these screens are described in the next two sections.

The JDBC pool edit screen looks like this:

Figure 6.19. Console: Database Pool -- Edit JDBC Database Pool

The fields here are similar to the options available when creating a pool:

When the settings are correct, hit Save to save the new settings for the pool and return to the pool list screen. Currently there is no way for the console to test changes to an existing pool, though that should be added in a future release.

The XA database pool edit screen looks like this:

Figure 6.20. Console: Database Pool -- New XA Database Pool

The fixed fields here (everything except the Basic Connection Properties) are:

The remaining fields on this screen (the Basic Connection Properties) are database-specific configuration settings controlled by the XA driver implementation. If the supplied property names and descriptions are not helpful enough, consult the XA driver documentation.

When the settings are correct, hit Save to save the new settings for the pool and return to the pool list screen. Currently there is no way for the console to test changes to an existing pool, though that should be added in a future release.