Have you tried using the NetworkServerControl API as mentioned in the second point linked in your post? If yes, what kind of problems are you facing?
~s.o.s~
Failure as a human
11,938 posts since Jun 2006
Reputation Points: 3,281
Solved Threads: 734
I think you should first try with NetworkServerControl simply because it seems more logical than setting system properties (at the JVM level) and relying on the derby driver class loading to start the server.
Regarding the properties file, I think you just need to create the properties file with the contents as per your need and make sure it is on the classpath (look into how to set classpath for a given JVM process; tip: java -h). Also, read this .
~s.o.s~
Failure as a human
11,938 posts since Jun 2006
Reputation Points: 3,281
Solved Threads: 734
Why do you need to start the db as a server at all on a single machine? Do you have more than one client sharing the data?
In your earlier posts, it sounded as if you were wanting an embedded database for use with a single application instance.
Ezzaral
Posting Genius
15,986 posts since May 2007
Reputation Points: 3,250
Solved Threads: 847
Ezzaral
Posting Genius
15,986 posts since May 2007
Reputation Points: 3,250
Solved Threads: 847