Ok, lets see if I got you correctly:
I stop IBM Director.
I start the Derby Network Server giving it the database directory as home
(is this done within the start command?)
I then reconfigure IBM Director to connect with the network mode url (not
the embedded) and the new port number (because I
On 12.09.11 11:21, johny_quest wrote:
Ok, lets see if I got you correctly:
I stop IBM Director.
I start the Derby Network Server giving it the database directory as home
(is this done within the start command?)
I then reconfigure IBM Director to connect with the network mode url (not
the
That's about right.
I usually specify the directory I want by opening a command prompt in the
parent directory. For example, if the files are located in
C:/derby/databases/mydb, then I open a prompt in C:/derby/databases and
issue the start command from there. There are probably other ways to do
Hmm, this might be interesting. My goal is to change as little as possible in
IBM Director configuration, so this might be good for me. Otherwise there is
no difference because IBM Director is always ON, so the network server will
also be available at any time. Can you tell me how to achieve this
I checked the configuration options for IBM Director and Derby and here are
the available options:
;==
; Apache Derby
;==
DbmsApplication =
To make the embedded connection start a network server instead of an
embedded server, use the following property:
http://db.apache.org/derby/docs/10.5/adminguide/radminconfigstartnetworkserver.html
I think that page links to other useful properties in this scenario
(derby.drda.*).
On Mon, Sep
On 12.09.11 12:36, johny_quest wrote:
Hmm, this might be interesting. My goal is to change as little as possible in
IBM Director configuration, so this might be good for me. Otherwise there is
no difference because IBM Director is always ON, so the network server will
also be available at any
