Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

JDBC driver configuration for external databases using JDBC URL

Suggest edit Updated on September 10, 2021

This content applies only to On-premises and Client-managed cloud environments

When you connect Pega® Platform to an external database using a JDBC URL, the external database driver file must be available to Pega Platform. If the file is not available, the connection to the database fails. For information about which database driver is correct for your database, refer to the vendor documentation.

Make the database driver JAR file available to Pega Platform in one of the following ways:

  • Ensure that the database driver JAR file is on the Java class path, for example, ojdbc7.jar for Oracle, sqljdbc4.jar for MS SQL, and so on. For information about how to add the driver file to the class path, refer to your application server and development environment documentation.
  • Add the database/drivers setting to the prconfig.xml file. The value for the setting is a list of Java driver class names separated by a semicolon, as shown in the following example.

<env name="database/drivers" value="com.microsoft.jdbc.sqlserver.SQLServerDriver"/>
<env name="database/drivers" value=" oracle.jdbc.OracleDriver;com.sybase.jdbc4.jdbc.sybdriver"/>

  • Previous topic How to configure non-J2EE database connections in the prconfig.xml file
  • Next topic When an activity fails, what happens to the database connection?

Tags

System Architect Lead System Architect Business Architect UX Professional Developer Project Manager System/Cloud Ops Administrator System Administration
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us