James has the capacity to use a JDBC-compatible database for storage of both message and user data. This section explains how to configure James to utilize a database for storage.
Using James with a database backend has certain requirements. Database configuration is extremely vendor-specific, so we can only state the requirements in general terms.
There must be a database instance accessible from the James server. An account with appropriate privileges (select, insert, delete into tables, and on initial startup creation of tables) and with sufficient quota for the data to be inserted into the database must be available. Also, since James will use JDBC to access the database, an appropriate JDBC driver must be available for installation.
It is important to verify the functionality of the database before attempting to configure James to use it as a repository. This will help ensure that configuration issues are properly identified.
Configuring the Phoenix container to work with JDBC is the first step in enabling James database support.
First, Phoenix must be able to load the JDBC classes. To make these classes available to Phoenix, place the jar/zip files for the JDBC driver in the lib subdirectory of the James installation directory. Any additional libraries upon which the JDBC library depends that are not part of the standard Java distribution should also be added to this directory.
Second, the config.xml must be modified so that Phoenix initializes the database connections. The relevant configuration is in the database-connections block. The database-connections tag has only a single child tag, data-sources. This latter tag is a simple container tag for a number of child elements. It is these child elements, data-source elements, that define the database connections.
Each data-source tag has a required attribute, name. This value must be unique to each data-source element. It is this name that will be used to specify the database connection in other parts of the config.xml file.
The data-source element has five children, all of whom are required.
The config.xml file has commented out examples for MySQL and MSSQL data sources, and for each of the standard repositories. For example, to use MySQL, you would uncomment and adjust the following data-source element.
You must create the database, in this case named mail, the user, and assign the user privileges. You may create the tables before running James or, if you so choose, James will automatically create the tables it needs. In the latter case the user must have table creation privileges.
<data-source name="maildb" class="org.apache.james.util.mordred.JdbcDataSource"> <driver>com.mysql.jdbc.Driver</driver> <dburl>jdbc:mysql://127.0.0.1/mail</dburl> <user>username</user> <password>password</password> <max>20</max> </data-source>
Once the data-source element has been created, it can be referenced elsewhere in the config.xml file. For example, the following element tells James to use the maildb data-source and dbfile storage mechanism for the message spool:
<spoolRepository> <repository destinationURL="dbfile://maildb/spool/spool" type="SPOOL"/> </spoolRepository>
The following element tells James to store mailboxes in a the maildb data-source:
<inboxRepository> <repository destinationURL="db://maildb/inbox/" type="MAIL"/> </inboxRepository>
The configuration file contains further examples.
There are some vendor-specific subtleties in using databases with James that have been observed by some users. These issues (and methods to resolve them) are recorded on the James FAQ as they are reported. Please consult the FAQ if you encounter any difficulties.