java.lang.ClassNotFoundException during or after migration
If custom application JAR files were added to the WebSphere® Application
Server installation in the
install_root/lib/ext directory, there might be a conflict
between the custom application classes and the IBM® Business Automation Workflow classes.
To solve the problem:
- Move the custom application JAR files out of the install_root/lib/ext directory into another directory.
- Update the classpath parameter to point to the directory that contains the JAR files. To update the classpath in the administrative console, go to and click the name of your server. Under Server Infrastructure, open Java and Process Management and click Process Definition. Under Additional Information, click Java Virtual Machine. Add your directory to the classpath.
You must update the classpath for each JVM that is affected, including the deployment manager and each of the application cluster members.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15