db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francois Orsini <francois.ors...@gmail.com>
Subject Re: Derby and third party products
Date Mon, 16 Feb 2009 10:07:38 GMT
Hi Walter,

You need to enable the Derby's instance running in TomCat to act as a server
and allow remote connections.
See http://db.apache.org/derby/docs/10.4/adminguide/tadminconfig814963.html(for
turning on server mode)

You would then be able to connect from an OpenOffice client using Derby's
network client JDBC driver (instead of the embedded ones as the tutorial
shows). Of course you can still use the embedded driver to access the Derby
instance started from within TomCat.

For instance,
In 8) replace the Derby embedded connection URL with the one to connect to
the remote instance of Derby started within TomCat.
e.g. jdbc:derby://localhost:1527/*c:/myfolder/**EactsCongenitalDatabase*
or jdbc:derby://localhost:1527/*EactsCongenitalDatabase* (if you have set
DERBY_SYSTEM_HOME to point to a directory where to expect to find the
database(s) [recommended way] of if Derby was started in a directory where
the database is located).

in 9) Use Derby's network client driver instead of the embedded one class,
such as:
(make sure to have DerbyClient.jar in OpenOffice classpath as you did with

Hope this helps


On Sun, Feb 15, 2009 at 2:27 PM, Walter Rogura <mist@sudus.eu> wrote:

> Hey,
> Derby works fine with tomcat and even the connection to open office
> runs smoothly (thanks to that tutorial
> http://www.eactscongenitaldb.org/docs/OpenOffice_and_JDBC_for_data_access
> ).
> But what does not work is to connect tomcat and open office to one and
> the same derby db concurrently. I always need to stop one or the other
> application to successfully connect to the db.
> How can I solve this issue?
> Thank you,
> Walter

View raw message