Previous: Publish API Next: Credits Table of contents

11.7 Miscellaneous

Copying a Database

If you ran RAMADDA with the default settings annd created some content that is in the database and you want to switch databases (e.g., from derby to mysql). Log in to the original RAMADDA and go to the Admin->SQL page. There is a Dump Database link. This will give you a text file of the entire database. Note: This might be a big file. You can save this file on the server or have it local.

Then, reconfigure RAMADDA to point to the new database and login again. Note: you'll have to add a new admin password, etc. Then go to the Admin->SQL page. If you saved the SQL file on the server then just enter:

file:/path/to/sql/file
in the text area and hit execute.

If you have the SQL file on your local machine upload through the sql file form.

Its probably best to shutdown and then restart RAMADDA after doing this and you should have your old database running in the new RAMADDA.

If you changed systems then you also need to copy over the storage directory tree to the new system. This is in:

<ramadda_home>/storage

Building from Source

The source release creates, at the top level, the ucar source tree and a lib directory. The lib directory has two jar files:
lib/repositorylib.jar
lib/repositorytds.jar
To compile stand-alone (e.g., using javac) put those 2 jar files in your class path.

To compile using ant:
The default ant target (all) will compile the repository source and create:

lib/repository.jar
lib/repository.war
You can run the repository stand-alone by doing:
java -jar repository.jar

The repository.war is a tomcat war file that needs to be placed in the tomcat install area.

 


Previous: Publish API Next: Credits Table of contents