Problem:
- Product Name: BES AppServer
- Product Version: 5.x and 6.x
Why does the JNDI browser (on the BES console -> Tools -> JNDI Browser) show a "class not found exception", even though the correct JDBC driver and DAR file is deployed into the partition?
The user deployed the correct Oracle JDBC driver and the DAR file which contains the datasource into the BES partition.
Restarted the partition (since hot deployment of dar file doesn't affect partition until partition restart).
Opened JNDI browser, to look at the newly created datasource (right-click on details to view its properties) and saw "java.lang.ClassNotFoundException" in the details section.
Resolution:
This apparent error does not affect functionality, the console shows ClassNotFoundException exception when we deployed all correctly. Since the BES console does not have the Oracle JDBC drivers in its classpath, so the JNDI browser shows the java.lang.ClassNotFoundException in the details section.
To see the correct behaviour for BES Console, you need to edit the "console.config" file, located under the "$BES/bin" directory. Add the JDBC driver jar file location in the "console.config" file. For example:
addpath C:\\downloads\\JDBCdrivers\\ojdbc14.jar
Restart the Console and go to the JNDI browser. You will see the correct datasource name in the details section.
This solution is applicable to any JDBC compliant driver.
#Security
#VisiBroker
#JDBC
#ApplicationServer
#JNDI
#BESConsole
#AppServer
