Database Table form – Completing the Database tab

Description

Identify a database instance that corresponds to the database containing the table or view.

Optional. Identify a database instance that contains a copy of this table, replicated through database software.

Complete this field only if a database administrator has created a mirrored replica of all or part of the PegaRULES database that is sufficient to support reporting needs, and established a replication process. To reduce the performance impact of report generation, you can specify that some or all reports obtain data from the reports database.

The sources for a report cannot span multiple databases. If a report definition presents data from multiple tables, all required tables must be in one database. This database can be either the PegaRULES database or a single reports database.

Optional. Identify the database catalog containing the schema that defines the table or view.

In special situations, a catalog name is needed to fully qualify the table.

Optional. Identify the name of the schema (within the catalog) that defines the table. The schema name is required in some cases, especially if multiple PegaRULES database schemas are hosted in one database instances.

Enter the name of the specific table that is to hold instances of the specified class or class group.

When allowed by the database account, enter only an unqualified table name. Preferably, the database account converts the unqualified table name to the fully qualified table name.

A few of the database table instances that are created when your system is installed identify database views rather than tables. Views are used only for reporting. By convention, the names of views in the initial PegaRULES database schema start with pwvb4_ or pcv4_.

If you create additional views in the PegaRULES database, you can link to them to a class using a database table instance. The view data then becomes available for reporting.

After you save this Data Table form, you can test connectivity to the database and table. This test does not alter the database. The test uses information on this form, the associated database data instance, and in some cases, information from the prconfig.xml file, Dynamic System Settings, or application server JDBC data sources.

Description

Identify a database instance that corresponds to the database containing the table or view.

Specify the number of elapsed seconds until a NoSQL document expires. The current TTL is applied whenever a document is saved or updated. For example, 25000. If not specified or set to zero, documents will not expire.

For Couchbase databases, valid values are 0 to 20*365*24*60*60.

Changing this value does not affect existing data.

After you save this Data Table form, you can test connectivity to the database and table. This test does not alter the database. The test uses information on this form, the associated database data instance, and in some cases, information from the prconfig.xml file, Dynamic System Settings, or application server JDBC data sources.