You are here: Administration > Server Configuration > Changing the database configuration

Changing the database configuration

OEDQ stores data in two database schemas- the Director database schema, which stores all configuration data associated with Director projects, and the Results database schema, which stores all the processed data and generated metrics.

When OEDQ is installed, two PostgreSQL databases are created for the Director and Results databases. However, you can configure OEDQ to use other databases in one of two ways:

The database setup pages can be used to specify PostgreSQL or Oracle databases. The databases must use either PostgreSQL 8.0 or above, or Oracle 10g or above.
Alternatively, you use JNDI to specify a connection for either of the two databases.

Note that either or both of the databases may be hosted on a separate machine to the OEDQ application server, if required, though a fast and permanent network connection must exist between the machines in order for OEDQ to perform reliably.

In many cases, it may be appropriate to change only one of these databases. For example, for better performance when working with large data sets, such as when regularly processing many millions of records, it may be appropriate to change the Results database to use an Oracle database. Changing the Director database, however, will not improve processing performance. It is also less commonly required to change the Director database to use a database on a different machine.

Note: Changing the database using these pages will simply re-point the OEDQ server to a new database location. A valid database of the appropriate type (Director database or Results database) must first have been created at the specified location.

Using the Launchpad to specify alternate databases

The Server Configuration pages are accessed by following the Server Configuration link on the OEDQ Launchpad front page.

Click on the Database Setup option on the Server Configuration pages. You may be prompted to log in.
Specify the new database details. For example, the following screenshot shows example details for connecting to Oracle databases for both the Director database and the Results database:

Note: In Oracle terms, the Database ID corresponds to the SID, and the DataSource UserName corresponds to the Oracle User (and its default Schema)

Using JNDI to specify alternate databases

In order to use JNDI to specify your Director and/or Results databases, you must:

Configure and test the JNDI data source in your application server, then
Edit your director.properties file and enter the JNDI name of the data source as the value of resultsDataSource.jndiname or dataSource.jndiname, as appropriate. For example:

resultsDataSource.jndiname = java:comp/env/jdbc/results

dataSource.jndiname = java:comp/env/jdbc/director