Author |
Message
|
JohnSmith |
Posted: Sun Mar 28, 2010 8:29 pm Post subject: JDBC connection with Derby Database |
|
|
Voyager
Joined: 17 Mar 2010 Posts: 86
|
Is it possible to establish a JDBC connection with Derby database which come as a part of Message Broker Installation on Windows.
I am using JavaComputeNode with Message Broker(which is installed on Windows) and trying to establish a connection with derby database.
But not sucessful, is it because JDBC connection is not supported with Derby database? |
|
Back to top |
|
 |
Gaya3 |
Posted: Sun Mar 28, 2010 10:51 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
if you are using java, it is flexible enough to connect with any databases using JDBC connections.
Please check it once again, i dont agree with your last statement. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Vitor |
Posted: Mon Mar 29, 2010 5:26 am Post subject: Re: JDBC connection with Derby Database |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
JohnSmith wrote: |
I am using JavaComputeNode with Message Broker(which is installed on Windows) and trying to establish a connection with derby database. |
I would ask why you'd doing this. Undoubtably it's possible to do this, but I'm struggling to think of a good reason why you'd want to. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
JohnSmith |
Posted: Tue Mar 30, 2010 8:02 pm Post subject: |
|
|
Voyager
Joined: 17 Mar 2010 Posts: 86
|
Hi Vitor,
Quote: |
I would ask why you'd doing this. Undoubtably it's possible to do this, but I'm struggling to think of a good reason why you'd want to. |
what is wrong in that, our development server doesnt have any DB products and as Derby comes with message broker installation so we have no other choice, when we moved to production we would move to Oracle database(atleast that is the plan for now). |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Mar 30, 2010 8:12 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
JohnSmith wrote: |
Hi Vitor,
Quote: |
I would ask why you'd doing this. Undoubtably it's possible to do this, but I'm struggling to think of a good reason why you'd want to. |
what is wrong in that, our development server doesnt have any DB products and as Derby comes with message broker installation so we have no other choice, when we moved to production we would move to Oracle database(atleast that is the plan for now). |
Then you need to install Derby separately and not from the WMB disks. In fact you should probably run 2 instances of Derby. One for the broker (it is limited to the broker's connection) and one for all your other needs...
But as far as any DB goes you could potentially create an ODBC source for MYSQL ...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Vitor |
Posted: Tue Mar 30, 2010 8:20 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
JohnSmith wrote: |
what is wrong in that, our development server doesnt have any DB products and as Derby comes with message broker installation so we have no other choice, when we moved to production we would move to Oracle database(atleast that is the plan for now). |
My assumption was that you were looking for a solution that you'd propogate through to your production environment. I now wonder why you'd want to develop and test on a different database platform than you plan to run on in production.
I also question the wisdom of contending with broker for it's database. Especially when any maintenance applied could change, modify or rebuild the database.
Why not exploit the Oracle you already have on site? Granted it's not on your dev server but that's not an insurmountable problem. Alternatively if you're looking for an alternative DB why not use MySQL or similar? If nothing else it's a better fit for Oracle functionality wise.
I wonder aloud if using Derby like this would have implications for license or support. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Mar 30, 2010 11:09 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Vitor wrote: |
I wonder aloud if using Derby like this would have implications for license or support. |
A simple Google revealed that Derby is an Open Source Java DB. So, there are no licensing implications. Support? Maybe.
Personally, I'd go for the MySQL route or even look at the Oracle Licensing. From what I remember, you can use Oracle for free in a Dev environment if you are already using it in Production with a valid license. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|