THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Notes on Geronimo's internal Derby installation:
- Geronimo's Derby installation runs in network client mode. That means that both processes running in the same JVM as Geronimo (e.g., its underlying web applications) and different JVM's can access Derby databases created from within Geronimo's Console application.
- The Geronimo Derby listener runs on the Derby's usual network port 1527.
- Derby databases created from Geronimo's web-based Manager Console ("DB Manager" on the left-menu) are stored in the {geronimo install}/var/derby directory. To access a derby database instance from external applications (e.g., Derby's ij query tool), use the standard network-client URL form (replacing the server name and database path as appropriate):
(Linux) connect 'jdbc:derby://localhost:1527//usr/myapps/geronimo-1.1.1/var/derby/MyTestDB;'; (Windows) connect 'jdbc:derby://localhost:1527/c:\myDerbyDBs\MyTestDB;';
If your database requires a username/password, append a string similar to "'user=myuser;password=mypass';" to the above.
- As explained in the link below, for installing web applications using the Derby database, it is recommended for web applications using a pre-configured Derby database to use an EAR file, with the database compressed into a JAR file and kept separate from the WAR file. Next, using a Geronimo bean, the JAR file can be uncompressed and installed into the geronimo/var/derby directory (the usual location for embedded databases).
