In the example above, you will need to have a MySQL
server running on a host named 'j2-server' with a
database called 'j2' for production.
If you are going to run the unit tests you will also
need an additional test database called 'j2test'.
A user named 'jetspeed2' should be granted access to
both the 'j2' and 'j2test' databases.

MySQL Known Issues

None

Oracle

To run with Oracle, add the following properties to your
$HOME/build.properties:

In the example above, you will need to have a Oracle
server running on a host named 'j2-server' and have an
Oracle database SID named 'j2db' installed on that
server. Also, you will need a database user (schema)
called 'j2' for production usage.
If you are going to run the unit tests you will need an
additional user called 'j2test'.

Oracle Known Issues

Only for the first time you create the database for
Oracle, there is an issue with the drop statements.
To get around this problem, set your properties as
above in your $HOME/build.properties, and then run
these commands using the
Jetspeed 2 Maven plugin
:

Drivers

JDBC drivers are configured to work with the Maven build
by adding your specified JDBC driver jars to the Maven
class path. Specify the jars with the
org.apache.jetspeed.test.jdbc.drivers.path
and
org.apache.jetspeed.production.jdbc.drivers.path
properties in your $HOME/build.properties.

NOTE: The Derby JDBC driver is distributed with
Jetspeed and require no configuration.

Distributing Drivers

When Jetspeed is deployed to an application server
using the maven deploy target, only the Derby
JDBC driver is copied into the web application. To
distribute a specific driver (i.e. Oracle, MySQL),
you will need to copy the driver into the
application server's common class path for shared
code.

Application Server

Procedure

Tomcat 5 and 5.5

copy driver(s) to ${TOMCAT_HOME}/endorsed/

Datasource Configuration with Jetspeed-2

Jetspeed-2 requires a datasource to be configured in the application server on which it is being deployed.
For more information, see the RDBMS component documentation.