Creating a database instance for a JDBC connection pool

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

1. If the database platform of the additional database is different than the database platform of Pega Platform, configure Pega Platform to access the database driver. For more information, see Defining the database driver.
2. In the header of Dev Studio, click Create > SysAdmin > Database.
3. Enter a short description, and in the Database field, enter a name for the additional database.
   The database name is case-sensitive.
4. Click Create and open.
5. Optional: To indicate the system of record, in the Integration system field, press the Down Arrow key and select the name of the integration system to associate with this database.
   The value that you enter is for informational purposes only, and does not affect the behavior of the database instance. You can use this value to organize rules for integration connectors, data types, and sources for data pages.
6. In the How to connect list, click Use JDBC Connection Pool.
7. Enter the JNDI names that have update permission, administrative permission, and read-only permission to the data source.
   These JNDI names correspond to the credentials that you enter in the next step.
   1. In the JNDI name field, enter the name of a JNDI data source that has read and update permission.
   2. Optional: In the Admin JNDI name field, enter the name of a JNDI data source that has permission to alter and create tables.
   3. Optional: In the Read-only JNDI name field, enter the name of a JNDI data source that has read-only permission.
8. Enter the credentials for the database user, the database administrative user, and the database read-only user.
   1. In the Username field, enter the name of a database user who has read and update permission, and in the Password field, enter the password for that user.
      Specify a user that is capable of accepting unqualified table names and converting them to fully qualified table names. If this database is to be accessed through Connect SQL rules, confirm that this database user has search, update, delete, and other permissions that support the SQL statements in those rules, and that this database is the default database of the user.
   2. Optional: In the Admin username field, enter the name of a database user who has permission to alter and create tables, and in the Admin password field, enter the password for that user.
      The admin user is used to configure tables that extend the Pega data schema. The admin user is used for platform-generated schema changes, property optimization, and circumstance definitions.
   3. Optional: In the Read-only username field, enter the name of a database user who has read-only permission, and in the Read-only password field, enter the password for that user.
      The read-only user is used by the Schema Tools, Query Inspector, and Query Runner landing pages for reading from the external database.
9. Click Save.
10. Optional: Click the Advanced tab.
11. Leave the Failover options fields blank. They are reserved for future use.
12. Optional: To specify a proxy class for determining access privileges to the Schema Tools, Query Inspector, and Query Runner landing pages, in the Proxyclass name field, enter the proxy class.
    The proxyclass is used with the read-only user that you define on the Database tab.
13. Optional: If this database is used for tables that you have configured for use by Pega Platform and the BLOB user-defined function is installed on the database, select the Use UDF for property lookup check box for best performance of Pega:Lookup tag references.
14. Optional: On the Advanced tab, specify the names of other database instances that should be reachable by views in this database.
    1. Under the Database Name list, click the Add item icon.
    2. In the Database Name field, press the Down Arrow key, and select the name of a database instance that views in the external database need to access.
    For example: This database instance describes the EXTERNAL1 database. Your Pega application needs to access a view in EXTERNAL1 that joins data from the DATA1 and DATA2 databases. Do the following steps:

    • Define database instances for DATA1 and DATA2.
    • On the database instance for EXTERNAL1, list DATA1 and DATA2 as other databases.
15. Click Save.
16. To test the database connection, on the Database tab, click Test connection.
    • If the test fails, diagnostic information appears in a new window. Modify the database instance until the test succeeds.
    • This test does not test the administrative user, if any, that you might have specified.