Pega 7.2.2 integration with External database in Tomcat 7.0.69 - Linux - jdbc/DBNAME JNDI not bound error
Does any one faced similar issue during External database integration using connection pool configuration in Tomcat 7.0.69 - Linux. Any suggestion?
1) Added Resource in tomcat conf Context.xml file
<Context ...>
...
<Resource name="jdbc/EmployeeDB"
auth="Container"
type="javax.sql.DataSource"
username="dbusername"
password="dbpassword"
driverClassName="org.hsql.jdbcDriver"
url="jdbc:HypersonicSQL:database"
maxActive="8"
maxIdle="4"/>
...
</Context>
2) prweb.war - web.xml - Added resource reference.
<resource-ref>
<description>
EmpDB mapping
</description>
<res-ref-name>
jdbc/EmployeeDB
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
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].
Does any one faced similar issue during External database integration using connection pool configuration in Tomcat 7.0.69 - Linux. Any suggestion?
1) Added Resource in tomcat conf Context.xml file
<Context ...>
...
<Resource name="jdbc/EmployeeDB"
auth="Container"
type="javax.sql.DataSource"
username="dbusername"
password="dbpassword"
driverClassName="org.hsql.jdbcDriver"
url="jdbc:HypersonicSQL:database"
maxActive="8"
maxIdle="4"/>
...
</Context>
2) prweb.war - web.xml - Added resource reference.
<resource-ref>
<description>
EmpDB mapping
</description>
<res-ref-name>
jdbc/EmployeeDB
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
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***
Accepted Solution
Express Scripts
US
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.
Cognizant
US
Try configuring the datasource in prconfig.xml. For example:
<env name="database/databases/EXTDBTEST/dataSource" value="java:comp/env/jdbc/EXTDBTEST"/>
If this doesn't work then try placing the driver in common/lib folder of Tomcat. Verify if this works.
Express Scripts
US
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.
Accepted Solution
Express Scripts
US
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.