When running a custom application in Websphere, there are certain issues that can occur which do not occur in other application servers such as tomcat. The reason for many of these problems is because Websphere has several built in classes that it loads first before loading anything in the lib folder of a deployed application. This can be a problem if the classes that come with websphere are not compatibile with the classes in the deployed application.
The more notable classes that are known to be incompatible are the axis classes and log4j. As a result, if the classloader order is not set correctly, then SAP BusinessObjects custom SDK applications will not work.
Some errors that may occur:
- classNotFound Exceptions
- Class file <classname> couldn't be reached
- BusinessObjects Enterprise XI 3.1
- SAP BusinessObjects Business Intelligence platform 4.0
- SAP BusinessObjects Business Intelligence platform 4.1
- IBM Websphere v8
- IBM Websphere v8.5
websphere classdefnotfound classloader order loading sequence failed , KBA , bidep , htkba , BI-DEV-JAV , BI Software Development Kits (SDKs) - Java , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.