Removing database pools
Skip to end of metadata
Go to start of metadata

There are two alternatives for removing database pools, you can use the command line Deployer tool or the Installed J2EE Connectors portlet available from the Introducing Geronimo Administration Console.

If you choose to use the graphical option, click J2EE Connectors from the Administration Console to access the Installed J2EE Connectors portlet.

This portlet list all the available connectors and allows you to stop, start and uninstall any of those J2EE connectors. Just click Uninstall next to the connector you want to remove.

You can also remove the database pools by the Deployer tool. Among other things, this tool allows you to remove the available modules. The connection pools are listed by moduleID. In the console, the moduleID is listed in the Component Name column.

To remove the available connection pools, type the following command from the <geronimo_home>\bin directory:

deploy --user system --password manager undeploy console.dbpool/Derby_Test/1.0/rar

You will see a list similar to the following example.

>deploy --user system --password manager undeploy console.dbpool/Derby_Test/1.0/rar
Using GERONIMO_BASE:   E:\g\server\branches\2.2\assemblies\geronimo-tomcat6-java
ee5\target\assembly
Using GERONIMO_HOME:   E:\g\server\branches\2.2\assemblies\geronimo-tomcat6-java
ee5\target\assembly
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME:        d:\sunsdk160\jre
    Module console.dbpool/Derby_Test/1.0/rar unloaded.
    Module console.dbpool/Derby_Test/1.0/rar uninstalled.

    Undeployed console.dbpool/Derby_Test/1.0/rar

Labels
  • No labels