By default RAMADDA uses a built in Java Derby relational database. RAMADDA also can run using MySQL, PostgresSQL, Oracle and H2. Derby works pretty well though there are some performance issues with search and doing many deletes. If you are planning on really using RAMADDA and foresee a large amount of content stored in the repository (by large we we mean the number of entries in the repository not the overall file size) then its probably a good idea to use mysql or postgres.

The database to use and its connection parameters are specified in a .properties file, e.g., The properties file can be placed in the ramadda home directory. To define the database just uncomment the appropriate ramadda.db properties in, e.g.:

And then specify the jdbc url and the login credentials. The URLS can be of the form:
jdbc:<db type>://<hostname>/<database name>
jdbc:<db type>:<database name>
jdbc:<db type>://<hostname>/<database name>
jdbc:<db type>://<hostname>:port/<database name>
If you are running the database on the same machine as RAMADDA the hostname can be "localhost". In the below examples we assume a database called "repository".


For MySQL:
ramadda.db.mysql.user=the database user
ramadda.db.mysql.password=the database password


For Postgres:
#note: the jdbc url uses "postgresql" as the database type
ramadda.db.postgres.user=the database user
ramadda.db.postgres.password=the database password


For H2 the default setting specifies the database to be in the RAMADDA home directory under the sub-directory h2db. The JDBC URL has the full file path of where to store the database.