Specifying the database with the engine code

Pega Platform stores engine code in the database as a CodeSet. Edit the prbootstrap.properties file provided in the configuration directory of your BIX distribution to add database connection settings that specify the Pega Platform database holding the engine code.

Specify the database connection settings by using the following naming convention: unique-identifier, dbtype, property where:
<unique-identifier>

A distinct value that together with <dbtype> identifies a specific data source.

<dbtype>
refers to a set of common properties associated with a given database type. The following values are available:
- oracle
- db2
- mssql
- derby
<property>

one of the key values needed to access the data source.
For example, to connect to an Oracle database:
```
com.pega.pegarules.bootstrap.allclasses.dbcpsource=example.oracleexample.oracle.url=jdbc:oracle:thin:@//localhost:1521/codebase
example.oracle.username=user
example.oracle.password=pass
oracle.jdbc.class=oracle.jdbc.OracleDriver
```
Specify any additional properties needed to connect to the database using the connectionProperties entry and provide a semicolon-separated list of values. For example:

example.oracle.connectionProperties=oracle.jdbc.V8Compatible=true

Result:

Note:

Set the system property com.pega.pegarules.bootstrap.ignorejndi to TRUE when using Pega-managed connections. This tells Pega Platform to ignore the JNDI data source information in the file and to use the Pega-managed connection settings instead.
For Pega Cloud applications, BIX is an add-on service that Pega configures if you choose it as part of your subscription. For on-premises applications, BIX is available when you purchase and install the BIX application.