Hi,
It seems that classpath is not setup correct. The easiest way to solve it is
copy your db2java.zip to was_root/lib

and restart the server to try again.

If it can solve the problem, you need to double check your setting in the
WAS admin console.
"David Pankros" <dpankros@miragy.com> wrote in message
news:cujqbq$2rva$1@news.boulder.ibm.com...[vbcol=seagreen]
> Did anyone ever find a resolution to this?
>
> I have a similar problem, and I agree that it is a backend connectivity
> problem.  In short, I've installed the portal server on win2k3 with LDAP
> (active driectory).  Everything was working fine with Cloudscape until I
> converted it over to use an existing DB2 instance on a linux server.
> After following the steps that IBM laid out for setting up DB2, I now
> get the "failed to load target servlet" when I try to access it and the
> logs show this bizzare message:
>
> 2b63c188 DataSourceCon E DSRA8040I: Failed to connect to the DataSource.
>   Encountered : java.lang.NoClassDefFoundError:
> javax/sql/ConnectionPoolDataSource
>
> As normal, there are two WAS application servers defined, server1 and
> WebSphere_Portal.  I know DB2 is working correctly because if I test the
> datasource connectivity from server1's admin console, everything works
> fine.  If I do the same test from WebSphere_Portal's admin console, it
> throws the above errors (NoClassDefFoundError on the ConnectionPool).
>
> Does anyone have any suggestions as far as what to look at to diagnose
> this issue?  I've been trying to compare the settings of the two servers
> with no success (all the classpaths look reasonably similar, for
> example).  I even tried putting j2ee.jar in the bootstrap classpath on
> WebSphere_Portal to see if I could force it to work.  It wouldn't even
> start in that configuration. :-)
>
> Any suggestions would be appreciated.  Thanks.
>
> Dave
>
>
> dbthomson@gov.pe.ca wrote: 

[ Post a follow-up to this message ]