|Configuring databases in Geronimo||Configuring and administering||Configuring the Transaction Manager Identity|
This topic is about how to set up a production environment for your applications.
- Adding JARs to the Geronimo repository — The server keeps common Java libraries in a repository using the same directory structure and naming conventions prompted by the Apache Maven project. If your Java EE asset depends on a library that is not already in the repository, you can update the repository to include the new library from console or using deployer command, and define the dependency in your Java EE asset's deployment plan.
- Configuring datasource — Database pools provide a mechanism for applications to access databases hosted on database managers without having to include the physical implementation details of the database in the application code. The database pools also relieve the application from managing things such as connection pools and timeouts.
- Configuring a DB2 datasource — This article shows you how to configure a DB2 datasource in Apache Geronimo.
- Configuring a derby datasource — You can use the embedded derby database and create a datasource for it.
- Configuring a MySQL datasource — This articles shows you how to configure a mysql datasource in Geronimo.
- Import database pools from JBoss 4 — In this article, we will walk you through in importing existing JBoss 4 database pools.
- Import database pools from WebLogic 8.1
- Removing database pools
- Configuring JMS resources — A JMS resource group is a resource adapter module that binds together the related connection factories, queues and topics. To create and access JMS resources such as queues, topics and connection factories in Geronimo, you have to create a JMS resource group.
- Configuring multiple repositories — The advantage of having multiple repositories is that they can reside on different server instances.