3) Created a Database rule and mapped to Use Connection Pool option and used jdbc/EmployeeDB
We are getting the following error during test connection from the database configuration rule in Pega UI.
The DataSource jdbc/EmployeeDBis invalid: Unable to obtain DataSource object: code: <none> SQLState: Name [jdbc/EmployeeDB] is not bound in this Context. Unable to find [jdbc]. Message: <none>
DatabaseException caused by prior exception: javax.naming.NameNotFoundException: Name [jdbc/EmployeeDB] is not bound in this Context. Unable to find [jdbc].
***Edited 5/19/17 by Moderator, Maryrita: moved to PSC from Upgrade Center***
Thanks for your response. Held up in other priory migration issues so the delay in response.
we have tried with <env name="database/databases/EXTDBTEST/dataSource" value="java:comp/env/jdbc/EXTDBTEST"/> entry in prconfig.xml and it did not work. Oracle driver jar is in /usr/share/tomcat/lib where all our application and third party jars are in and we don't have a common/lib dir.
Posted: 4 years ago
Posted: 1 Jun 2017 21:34 EDT
Kevin Zheng (KevinZheng_GCS)
Director, Software Solutions Engineering
Thanks for your response. Our JNDI look up Issue has been RESOLVED.
we have been using "jdbc/DBName" in database rule - use connection pool option JNDI look up name similar to app running in Pega 6.x running IBM WAS 7. For tomcat it needs "java:comp/env/jdbc/DBName" and able to access connection pool now.