I think the SMA lookup (it is not a search) loaded up the SQL class/jar into the JVM Runtime and thus you get successful test result. This will work fine when you use the DB name record and is only an issue during test connectivity.
the easier approach is to add the jar to the endorsed directory. SMA lookup and proconfig approach suggested above simply calls for Class.forName and register the driver class. SMA is not feasible as it is manual; prconfig approach also requires manual handling of the the file, not ideal for large clusters (unless you use DSS).
Default location <tomcat home>/endorsed (need to be created) or you can use -Djava.endorsed.dirs. To be clear, we should use datasource as much as possible (i.e., using app server connection pool implementation). In that case, we do not need to pre-load the driver classes.
I was challenged with similar problem but having the endorsed folder in tomcat lib didnot help me. I have to add the environment variable for mysql in prconfig.xml. I have mysql jdbc jar in tomcathome/lib. Was just wondering if there is anyother way instead of editing prconfig.xml.
How do I load more than one external driver, say mysql and oracle. The purpose key looks to limit this ‘prconfig/database/drivers/default’ . Would there be any negative impact on my original default driver[Postgres was used to install Pega7]
Dhananjay Ubale | Certified Lead System Architect | Pegasystems Inc.
The driver used to connect to the Pega database is specified in your JDBC connection, so there wouldn't be any negative impact. I believe you can list multiple drivers in the same DSS by separating them with a semi colon, but I have not tried this before. For example: