| Maik Weber 2005-02-12, 7:54 am |
| Did you follow these steps (taken from Infocenter), I don't know why
WPconfig does not change the classpath automatically when configuring
new database:
Manually verify the classpath information on WebSphere Application
Server, and update it if necessary. Perform the following steps to add
required DB2 JDBC provider files to the WebSphere Application Server
classpath. If this installation of WebSphere Portal is federated into a
cell that is managed by the WebSphere Application Server deployment
manager, these steps should be performed on the Administrative Console
for the deployment manager.
1. Open the Administrative Console by accessing the following URL in
a browser:
http://hostname.yourco.com:9090/admin
where hostname.yourco.com:9090 is the host name and port of the machine
where WebSphere Application Server is running.
2. After logging in, click Servers > Application Servers, and then
click WebSphere_Portal from the list of application servers.
3. Click Process Definition from the list of additional properties,
and then click Java Virtual Machine from the list of additional properties.
4. In the Classpath field, enter the directory path where the
db2java.zip file is located. Note that this directory path must also
match the value you specified for the DbLibrary property in the
wpconfig.properties file. For example, C:/PROGRA~1/SQLLIB/java/db2java.zip.
5. Click OK.
6. Click the Save link to go to the Save page, and then click Save.
Cluster users: Because JVM settings are node-specific and not
synchronized across nodes, you must specify the classpath value for each
cluster member.
Maik
David Pankros wrote:[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:
>
|