Embedded Derby Server won't Start Outside Netbeans

[Sinsecato]

I'm creating a database to use at my Screen Printing shop. I'm not very good at Java programming, but i've been able to follow the "Cars Database" tutorial and modify it to work for me. Now i'm trying to deploy this app outside of Netbeans. I've downloaded the Derby .bin file package, set up my environment variables, etc.

I've gotten to the point where i can run my App outside of NetBeans, but only if i use the command prompt to start the Derby Server first (by navigating to the directory of my App and then typing "startNetworkServer"). I have put the database files (Price List) in that same folder (PriceQuoteApp). My understanding is that using the Embedded Derby Server method my App should automatically start the Derby Network Server when it is run. The code i found to use for this is:

try {
Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
} catch (ClassNotFoundException ex) {
System.out.println(ex);
}
try {
Connection con = DriverManager.getConnection("jdbc:derby:Price List;user=MyUserID;password=MyPassword");

} catch (SQLException ex) {
System.err.println(ex);
}

As far as i've been able to figure out this should start the server. I'm pretty much at a loss as to how to proceed. As I said the App runs if i've manually started the Derby Server through the Command Prompt (i run Windows XP by the way). I've read alot of forum posts to get as far as i've gotten, and have tried several variations of the Connection string (jdbc:derby://localhost:1527/Price List, and some others). Maybe I'm missing a line of code?

[Javier.Ortiz]

I also do this before trying to start Derby:

private void setDBSystemDir() {
// Establish the db system directory: <userhome>/.hims/
String userHomeDir = System.getProperty("user.home", ".");
String systemDir = userHomeDir + "/.hims";
// Set the db system directory.
System.setProperty("derby.system.home", systemDir);
}

Here I'm seeting it to the user's home but you can set it somewhere else.

Keep in mind that this is for embedded Derby.

Javier A. Ortiz Bultr

[likesjava]

I'm in a similar boat.

Using the embedded derby driver with "create=true" argument.

I can run from the jnlp file, but ONLY if NB (6.8 ) is running and has the Java DB started.

Is anyone else having this issue?

Also I can only run with a URL including local host. Plain old HOST = "jdbc:derby: <with db name etc> can never see the DB.

Is it normally this hard to set this up? I can only imagine its worse when deployed.

[javydreamercsw]

Did you state the derby home property?

I have it working. I think I posted code in this thread.

On Sat, Feb 27, 2010 at 12:04 PM, likesjava <address-removed ([email]address-removed[/email])> wrote:

[likesjava]

Sorry for the late reply.

yes I tried the code mentioned. I had to modify the home dir as follows:

[javydreamercsw]

Just make sure to check the dir exits on the machine, if not just create it with the File API. I guess you are loading the driver (that starts the server) after setting the location.

After doing that I use the "jdbc:derby:<db name>" without issues.

On Mon, Mar 1, 2010 at 10:20 PM, likesjava <address-removed ([email]address-removed[/email])> wrote:

[likesjava]

Ji Javy,

You posted "Just make sure to check the dir exits on the machine, if not just create it with the File API. I guess you are loading the driver (that starts the server) after setting the location. "

Actually I am loading the driver BEFORE setting the connection - does that matter?

As for making sure the directory exists on the machine - at this point we are talking about my own machine, where the directory's are a known factor. I don't really see an answer yet to what I asked in the previous post.

Could anyone with a working example of of an embedded DerbyDB that can autostart AND that can be deployed to another machine with a different file structure possibly post an example? Might save a lot of typing.

Thanks much

[Javier.Ortiz]

This is how I do it (working example)

In the module's ComponentOpen method:

@Override
@SuppressWarnings("static-access")
public void componentOpened() {
//SCR 1743: Add database support
setDBSystemDir();
//SCR 2394: Switch to embedded database if something goes wrong.
OutputHandler.setStatus("Connecting to database. Please wait...");
try {
DataBaseManager.get("HIMSPU");
} catch (Error e) {
log(e.getLocalizedMessage());
//Something's wrong with the main database. Use the embedded one
DataBaseManager.get("HIMSDerbyPU");
}
...

The setDBSystemDir(); just sets the derby home.

The database manager does the rest. here's what is called at this point:

public static DataBaseManager get(String pu) {
//SCR 2238: Allow to change the connection
if (instance == null ||
(instance!=null && !instance.getPersistenceUnitName().equals(pu))) {
instance = new DataBaseManager(pu);
getEntityManager();
puName=pu;
}
return instance;
}

And JPA does the rest.

Javier A. Ortiz Bultr

[likesjava]

Hi Javier,

Thanks for your patience - I am in need of a little more

The code you have above is so different from what I am doing that I am not sure how to apply it. (But thank you for posting it).

Perhaps I should post what I have and see if something seems obvious to you:

[Javier.Ortiz]

Is there a chance I can have the source and try it by myself?

I see the following:

You are not setting the derby home so it'll assume the default (user.di)

Maybe there's nothing there. When you run it from Netbeans probably Netbeans starts the server and sets up the variable properly.

If Netbeans starts it with a certain user and password. That would explain the login issues.

In my case I use a string like this one:
jdbc:derby:<db name>;create=true (I might be wrong)

Javier A. Ortiz Bultr

[likesjava]

Hi Javier,

I would be most grateful if you would be willing to look at the source.

I will slim the database down to a few entries of course. How can I get it to you? Can you PM with with your email? I have been stuck on this issue for a while now - your getting my hopes up

Hopefully when we get it sorted, we can post the solution for others.

[likesjava]

PS,

Just saw that PMs are disabled on this board.

Hmm, how can I get these files to you Javier?

[likesjava]

After a little more reading....

I may have failed to understand the whole concept of deploying an embedded derby db. Looking through the samples, they always demo creating tables on the fly in a new DB created by the app.

Thats not what I am doing.

I have an existing derby database that I want to deploy and run....

hmmm. Will post back if I get this figured out.

[Javier.Ortiz]

If you sent them to my personal email I should get them sometime tonight. I won't be able to take a look until tomorrow if that's the case.

Javier A. Ortiz Bultr

[Javier.Ortiz]

I though you were using JPA which would create the database tables if configured to do so. That plus using create=true will make the database available.

Javier A. Ortiz Bultr