Beginning with Pega^® Platform 7.4, connection settings for PegaDATA are required in the prconfig.xml file. Prior to Pega 7.4, these settings could be blank. Explicitly specifying the connection settings ensures that your system runs correctly.

The settings that are required are based on the type of connection pooling that you use. The value of the connection settings must be the same for both PegaRULES and PegaDATA.

The database/databases/<database name>/defaultSchema default schema property does not have to be the same for PegaRULES and PegaDATA because it specifies which database schema to use by default when referencing the database data instance (Data-Admin-DB-Name).

Application server connection pooling

If you use Application server connection pooling, set the dataSource setting, for example:

<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES" />

<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES" />

Pega Platform connection pooling

If you use Pega Platform connection pooling, set the url, userName, and password settings, for example:

<env name="database/databases/PegaRULES/url" value="jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false" />

<env name="database/databases/PegaRULES/userName" value="a_username" />

<env name="database/databases/PegaRULES/password" value="a_password" />

<env name="database/databases/PegaDATA/url" value="jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false" />

<env name="database/databases/PegaDATA/userName" value="a_username" />

<env name="database/databases/PegaDATA/password" value="a_password" />