Hmm... Actually, I had already done exactly what you just mentioned. Yes, I
had run through the JDBC Connection Manager wizard, selected "Not Listed" -
instructions stated the drop-down list was for JRun's included drivers- and
the test keeps returning the error "cannot find driver". Both Admin and
Default have the paths to the jar files (JMC Java Settings classpath).
The same driver/URL works fine for my standard Java apps not running through
JRun, after registering the drivers on the system itself. I attempted to
use with a 30-day eval of IBM Websphere and had no problems setting up the
drivers. Using Merant's JDBCTest, even, produces results.
I'm waiting for JRun Advanced Edition to come in. I'll try Allaire's
built-in Type IV drivers (which I understand are Merant, anyway) and see
what happens.
TD
> Date: Mon, 04 Jun 2001 13:28:31 -0500
> From: "Celeste Haseltine" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: JRun-Talk-List V1 #8
> Message-ID: <[EMAIL PROTECTED]>
>
> TD,
>
> I'm a little confused. I test drove Merant's drivers, before deciding to
> purchase from another vendor. I had no problems setting up JRUN via JDBC
> Connection Manager Wizard to use Merant's drivers. You have to choose Not
> Listed in the drop down box for RDBMS server name (at least I did). The
> driver will NOT show up the drop down boxes of the Wizard, as it is an
> external driver. So follow's Merant's instructions on how to register the
> driver (this is part of the wizard), the URL to use, whether or not to use
> ConnectionPooling, and the userID and password. Most of the other
> parameters can be left blank by default.
>
> Did you also test the connection after running thru the wizard? If that
> doesn't show that you have "made" a connection, then you will not be able to
> use the driver in your servlets/JSP's.
>
> Otherwise, with the exception of later learning that the jar files had to be
> placed in the classpath (under Java Settings) for BOTH the admin server AND
> the default server, the drivers worked fine for me. I later decided to go
> with another vendor, and I had no problems setting them up via the JDBC
> Connection Manger Wizard either.
>
> Celeste
>
> -----Original Message-----
> From: tdavis [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 04, 2001 12:41 PM
> To: JRun-Talk
> Subject: Re: JRun-Talk-List V1 #8
>
>
> Hi Celeste. Thanks for your suggestion.
>
> Actually, I already placed the paths to the jar files in both Admin and
> Default classpaths (see my original message below). In addition, I cannot
> use JMC's Create JDBC Connections since JRun cannot even see the jar files
> for the Merant drivers - so you get the same error using JRun's Create JDBC
> Connections utility as you do explicitly writing servlets/JSP's calling the
> drivers/URL directly.
>
> See the rest of the thread for more info on what was attempted.
>
> TD
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
