> "Craig R. McClanahan" wrote:
>
> > Burt Alexander wrote:
> >
> > If you're running drivers that require native code, you also have to make
> > sure that the appropriate shared libraries (DLL files under Windows, SO
> > files under Unix) are in the right places, and defined in the right
> > environment variables (PATH under Windows, LD_LIBRARY_PATH under Unix).
>
> Yep. All these things are set up & working fine for other servlet engines.
> Its only JServ that has the problem.
When I first installed JSERV on my NT laptop, I had the same problem
when I tried to make a connection to the database (DB2 5.2 UDB for NT).
The DB2 JDBC application driver couldn't find the native CLI DLLs that
it uses to talk to UDB. This is the magic in my jserv.properties
file that fixed my problem:
# An environment name with value copied from caller to Java Virtual
Machine
# Syntax: wrapper.env.copy=[name]
# Default: NONE
wrapper.env.copy=PATH
Once the PATH environmental variable was made available to JSERV, my
database servlet connected just fine. It sounds like you have to use
this to mirror any environmental settings that InstantDB requires.
Also, don't forget to make any JAR files you need available via the
wrapper.classpath configuration option in jserv.properties.
Enjoy in moderation! :)
SunFox
--
*** ** Erik Williams (KF4JKR) -- Programmer/Consultant *** **
** *** Clayton, North Carolina ** ***
*** ** http://home.interpath.net/sunfox/ *** **
** *** ESSE QUAM VIDERI - "To Be Rather Than To Seem" ** ***
-- --------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
