| Author |
Message
|
| JacobSteenDue |
 Posted: Tue Oct 25, 2005 2:29 am Post subject: WMB V6 Derby Broker Database |
 |
|
Novice
Joined: 22 Mar 2005
Posts: 13
|
I'm trying to get started with v6 and I want to use a Derby broker database (to get a smaller footprint on the machine - this is a local developer/test installation).
But it is not working - whenever I try to create the broker database I get an error message:
BIP9801I: No supported database product found.
The requested database was not created becuase a support database product could not be found.
Please check your database product installion.
(on a sidebar - notice the spelling , perhaps I should log that to IBM support  )
Anyways what I've done is:
Install MQ
Install MB
Install Toolkit
The downloadimage contained a DB2 client (which should include the Cloudscape ODBC drivers), but apparently the install package is corrupt because the installer complains of an error in the install files. So I downloaded the latest version of the DB2 Client and tried again.
With no change in behaviour ....
Next step is downloading and installing a complete cloudscape 10.1
With no change in behaviour .....
I do not want to install DB2 as it is overkill for the situation, but if it's the only way out so be it.
I'm kind of stuck, and I've found no posts in this forum that could help me. Has anybody out there succesfully created a derby/cloudscape broker database for use with WMB 6 ?
As usual all tips and help will be greatly appreciated.
_________________
Jacob Steen Due
Chief Consultant
IBM Certified Solution Designer - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 25, 2005 3:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is there a statement of support for Derby in v6?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JacobSteenDue |
| Posted: Tue Oct 25, 2005 3:37 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 13
|
The documentation says so - the following has been copied from the documentation (note that I am using Windows):
Under 'Supported Databases'
| Quote: |
| You can use the embedded Derby database for verification, evaluation, and test purposes only. Derby refers to IBM Cloudscapeâ„¢ Version 10.0, a database product that is built on the Derby database from the Apache Software Foundation. Cloudscape does not modify Derby in any way, but provides additional function including installers. Derby database support is embedded in the broker component on Windows only. For a production system, you might want to install and configure your chosen enterprise database |
.
In the documentation for the mqsicreatedb options
| Quote: |
-e dbType
(Optional) The database engine to be used to create and run the database. Currently supported values are DB2 and Derby. If you do not specify this option, and only one database engine is available, that engine is used. If both are available, the default engine is DB2. |
| Quote: |
The following example sets up a Derby database with the name derbydb, using port number 1527:
mqsicreatedb derbydb -i wbrkuid -a wbrkpw -e Derby -p 1527 |
So I would say that if that is not a statement of support then I can't see what would be.
_________________
Jacob Steen Due
Chief Consultant
IBM Certified Solution Designer - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Oct 25, 2005 3:50 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Indeed, the Derby database is Windows and non-production only.
If you don't have DB2 on your machine, the Launchpad will install the ODBC Drivers for Cloudscape for you... that's what I did.
After installing everything, run the Default Config Wizard (I can recommend it- it works now  ) and it will set up your broker using Derby for you.
Let me know how it goes.
-Matt |
|
| Back to top |
|
|
| JacobSteenDue |
| Posted: Tue Oct 25, 2005 4:14 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 13
|
Well - that's what doesn't work  I will now get a new install image and try installing on a completely new (virtual) machine. But at least somebody has actually managed to do this.
How did you install the ODBC drivers - in my install image that was not possible - i had to download the DB2 client again - but perhaps there was a transmission failure when I downloaded it
_________________
Jacob Steen Due
Chief Consultant
IBM Certified Solution Designer - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| JacobSteenDue |
| Posted: Tue Oct 25, 2005 4:56 am Post subject: |
|
|
Novice
Joined: 22 Mar 2005
Posts: 13
|
Arghhhhh - problem found. If you install the OBDC drivers from a network location (finding the install directory in Explorer) then it does not work.
If you map a network drive to the location and install - then it does work.
What can I say - problem solved but I'm a little upset 
_________________
Jacob Steen Due
Chief Consultant
IBM Certified Solution Designer - WebSphere MQ V5.3
IBM Certified Solution Designer - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Oct 25, 2005 6:18 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Glad you've solved the problem; shame it took a reinstall to figure out.
A couple of times I've had problems installing software (not broker) using UNC path names. Now I try not to use such path names more than I have to. |
|
| Back to top |
|
|
|
|
