Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Persistence Store Table Reference

The backing store uses relational tables and SQL data types for ease of maintenance. The SQL (DDL) scripts use ANSI SQL type definitions (where supported by the target DBMS product).

Each ontology type in the backing store has its own primary table and zero or more second-level tables. There are only two levels of tables, which makes the database easier to manage and easier to understand. Because the backing store adheres to SQL standards and a straight-forward structure, standard database tools can be used to view backing store data.

## Primary Tables

Primary tables contain only primitive properties such as the following:

JDBC Store Property | Cassandra Property | ActiveSpaces Property | Note
--- | --- | --- | ---
`cacheId` | `cacheId` | `cacheId` | Entity version number (starts with 1)
`payload__p` | `payload__p` | `payload__p` | The Event payload content.
`time_acknowledged$` | `time_ack_` | `time_acknowledged$` | Time when the Event was acknowledged.
`time_sent$` | `time_sent$` | `time_sent$` | Time when the Event was sent.
`time_created$` | `time_created_` | `time_created$` | Time when the entity was created
`time_last_modified$` | `updated_` | `time_last_modified$` | Time when the entity was last modified
`parent$_id$` | `rrfs_parent` | `parentid$` | Id of the parent for contained concepts
`id$` | `id_` | `ID` | Unique Id of the entity (must be unique across all entities)
`extId$` | `extid_` | `extid` | Unique (or null) extId assigned
`state$` | `state_` | `state$` | Always set to ‘C’ meaning ‘Created’ (reserved for future use)

## Secondary Tables (JDBC Only)

Secondary tables are used for complex properties, that is, arrays, properties with history, and concept relationship properties. Each array and history-enabled property has a separate table. Only primitive properties are stored in the primary table.

Note: Secondary tables are not used for ActiveSpaces and Apache Cassandra stores.

Secondary table structure
Property Type | Column | Description
--- | --- | ---
Array | `pid$` | Parent ID
| `valPid$` | Array index
| `val` | Item’s value
History | `pid$` | Parent ID
| `howMany` | Number of history items
| `timeIdx` | Item’s time stamp
| `val` | Item’s value
Array with History | `pid&` | Parent ID
| `valPid$` | Array index
| `howMany` | Number of history items
| `timeIdx` | Item’s time stamp
| `val` | Item’s value

## Reverse Reference Tables

Each concept also has a reverse reference table. This table’s name contains the concept name and ends with the characters `_rrf$`. It has these columns:

Column | Description
--- | ---
`pid$` | Parent ID from the main concept table
`propertyName$` | Property name (field) from the referencing concept.
`id$` | Identifier (`id$`) of the referencing concept.

## Class-to-Table Mapping

This table contains the mapping between class names and table names, and the mapping between complex property field names and secondary table names. For example:

    'be.gen.Ontology.DeleteVerifyEvent', 'D_DeleteVerifyEvent‘
    'be.gen.Ontology.Treatment', 'D_Treatment‘
    ‘be.gen.Ontology.Treatment', 'rrf$', 'D_Treatment_rrf$‘
    'be.gen.Ontology.BaseAlert', 'treatments', 'D_BaseAlert_treatments'

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.