Installing Process Applications in a WebSphere ND Environment
 Technote (troubleshooting)
 
Problem(Abstract)
Why do you get a ClassNotFoundException when you try to install a process application in a WebSphere® ND environment?
 
Resolving the problem
For the installation of process applications in a cell you have to put the database driver of the respective database system onto the classpath of the DeploymentManager process. This is not necessary if you have a single-server environment.

In case you use a DB2 database as storage for the WebSphere Process Choreographer administration data, you have to add the full path of db2java.zip to the classpath. If you use a variable to specify the database driver location, make sure that this variable is actually defined on the DeploymentManager node. For further DB2 installation requirements or other database systems refer to WebSphere Infocenter.

You can change the classpath of the DeploymentManager process on the admin console:
On the navigator pane on the left-hand side of the admin console expand "SystemAdministration" and click "DeploymentManager".
Then a panel called "dmgr" is shown on the right-hand side. Under "Additional Properties", click "Process Definition", which is a link.
On the next panel, under "Additional Properties", click "Java Virtual Machine", which is a link again.
Add the database driver location to the "classpath" input field and save your changes. Shut down the DeploymentManager process and restart it before installing process applications.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1138321
IBM Group: Software Group
Modified date: Aug 2, 2004