I figure we're all here developing, deploying and maintaining web apps, so...
My dev system is not my server system (duh ;) ), so I deploy to the server remotely using the Glassfish admin web app. Very cool.
However, I can't seem to figure out how to maintain the backing database. I like to use Squirrel SQL for doing database maintainance, but the server refuses the connection. I'm sure I have to open port 1527 on the router, but it seems I also have to tell the Derby and/or Glassfish server to allow an external host to connect. So maybe some of you have some common means of:
1) Backing up the database remotely, to my dev system's local drive. Of course, I'll need to re-deploy/restore the database once my changes are made. Setting up Squirrel to do this would be cool, but I'm open to other options.
2) Putting up a "Server will be/is unavailable" notice when I need to redeploy the app or update the database.
This seems pretty basic stuff, and maybe I've worked too many 20-hour days to figure it out on my own (I've tried). A good URL will do, or SQL and/or Java snippets. Whatever.
One other thing. My server runs ubuntu hardy. To start the database server, I use asadmin start-server on the command line. No, I don't want that to be automated - the server is still 'beta'. But is there a way to do this within the Glassfish admin web app? I've seen stuff about JDBC connection pools, but I haven't set one up (to my knowledge, but maybe NB did when I wasn't looking), so I don't know if start/stop is a Glassfish console capability.
TIA,
Dave
