Create a database data instance so that Pega Platform can access a database in addition to PegaRULES and PegaDATA. To improve performance, you can create Pega classes and data types in a separate database, or use a separate database for Prediction Studio or for running reports. You can also create a database instance to access an external database.

• Defining the database driver

  Define a JDBC driver in your on-premises Pega Platform by using the Import Wizard and creating or updating a dynamic system setting.

• Creating database instances for prconfig references

  Create a database data instance so that Pega Platform can access a database whose connectivity is defined in the prconfig.xml file.

• Creating and updating external database instances with JDBC URLs

  Specify a JDBC URL to create a database data instance so that Pega Platform can access a supported external database. Pega Platform is optimized to connect to external databases via JDBC URLs in on-premises, client-managed cloud, and Pega Cloud environments.

• Creating database instances for JDBC connection pools

  Specify a Java Naming and Directory Interface (JNDI) name to create a database data instance so that Pega Platform can access a database via a JDBC connection pool.

• Creating Couchbase database instances

  Create a database data instance for a NoSQL Couchbase database so that Pega Platform can access that database.

• Creating Cassandra database instances

  Create a database data instance for a NoSQL Apache Cassandra database so that Pega Platform can access that database.

• Creating database instances by inheriting from an existing connection

  For informational purposes, you can define multiple database instances that point to the same underlying database but are associated with different integration systems. This is optional, and does not affect the behavior of Pega Platform or the underlying database instance. Integration systems make system configuration easier because they are reusable and selectable when creating data types, integration connectors, and databases.

• Database data instances